Embed Power BI for your organization's internal users—for enterprises user login error

yuqf 1 Reputation point
2022-01-07T06:50:08.387+00:00

hi
A user login error occurred while embedding power Bi for internal users of the organization. At login, the user is asked to enter the reason for requesting this application

162966-%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87-20220107144346.png

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
21,406 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. AmanpreetSingh-MSFT 56,556 Reputation points
    2022-01-10T11:35:53.887+00:00

    Hi @yuqf • Thank you for reaching out.

    For certain permissions, admin approval is required. If you don't want the users to provide a justification and wait for admin to approve their requests, you can provide admin consent in advance for the entire organization so that individual user doesn't get the consent prompt.

    There are 2 ways to do this:

    1. Using app registration blade: (If you have Global Admin rights)
      • Sign in to Azure Portal using Global Administrator account.
      • Navigate to Azure AD > App registrations > Search and open your app > API Permissions > Click on Grant admin consent for your_tenant_name button.
    2. By constructing the admin consent URL: (If you don't have Global Admin rights)

    Once admin consent is provided using any of the above methods, users will not be required to provide consent or justification to request access.


    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


  2. yuqf 1 Reputation point
    2022-02-24T03:03:09.577+00:00

    Hi @AmanpreetSingh-MSFT Thank you for reaching out.

    We tried scheme 1 before asking the question, and the result is as described in the question

    177329-16456716791.jpg

    We have tried many ways to solve this problem and tried to re register the application. But not successful. Strangely, by using other principals to complete the same process, and the permission configuration is the same, the result is normal. I think there are some security policies or other settings we don't know?

    I'm in great pain

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.