I have one user that is unable to get access to an Enterprise app, even though he is on the list of users able to use the app with his Outlook Calendar

Sean Reid 0 Reputation points
2026-08-17T16:13:31.28+00:00

I have a single user, out of a list of about 25, that is unable to get logged in to his calendar from a note taking app.

The application integration is working for every other user in the list. When logging in, it gets through MFA and then says that he doesn't have admin permissions, but I have already granted his permissions to the app as a User in the Enterprise application.

I have already removed him from the list and readded him, waited almost 72 hours for it to "resync", and still have the same issue with just this one user.

Has anyone run into this or know if there is a user limit or something for granting permissions to an Enterprise application that I may not be aware of here?

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. kagiyama yutaka 5,330 Reputation points
    2026-08-19T13:07:29.23+00:00

    I think Azure has no user‑limit for Enterprise app assignment and the user’s issue fits the case where assignment is not evaluated as effective, and running Check user access in the app is the simple way to re-evaluate it without touching anything risky.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-08-17T16:13:48.84+00:00

    There is no supported information here indicating a user limit for assigning an enterprise application. Since 24 other users work, focus on user-specific access conditions instead of a capacity limit.

    For this user, check these areas in order:

    1. Verify the app assignment model
      • In Microsoft Entra admin center go to Entra ID > Enterprise apps > All applications > [the app].
      • Open Properties and check Assignment required?
      • If it is Yes, the user must be explicitly assigned directly or through the correct group.
    2. Reconfirm the user is assigned in the app
      • In the app, open Users and groups and verify the affected user is listed.
      • If access is group-based, verify the user is a valid member of that exact assigned group.
      • A known sign-in failure in this area is AADSTS50105, which occurs when the user is not considered directly assigned or in a group with access.
    3. Check whether consent is the real blocker
      • The message about lacking admin permissions usually points to consent, not basic app assignment.
      • If the app is requesting administrator-level permissions, a Privileged Role Administrator must grant consent on behalf of the organization.
      • If the app is requesting only user-level permissions, the user must be able to complete user consent.
    4. Compare requested vs granted permissions for the app
      • Go to Entra ID > Enterprise apps > All applications > [the app] > Permissions.
      • Review the already granted permissions.
      • Select Grant admin consent to open the consent prompt and compare the permissions being requested with the permissions already granted.
      • If permissions appear in the consent prompt but not on the permissions page, those permissions have not yet been consented to and can cause unexpected consent or admin approval prompts.
      • Do not accept tenant-wide admin consent unless that is intended.
    5. Check tenant user-consent settings
      • Go to Enterprise applications > Consent and permissions.
      • If Do not allow user consent is configured, users cannot consent for themselves, and an admin must grant consent for the app.
    6. Check whether assignment-required plus missing admin consent is causing the failure
      • If Assignment required? is Yes and tenant-wide admin consent was never provided, the user can receive admin-consent-related errors even when assigned.
    7. Check other user-specific sign-in blockers
      • Since only one user is affected, verify the user account is not locked, is enabled, and is not being blocked by Conditional Access or MFA-related conditions.
      • Microsoft’s troubleshooting guidance for Microsoft applications specifically calls out account status, MFA, and Conditional Access as common causes when one user fails and others succeed.

    Most likely causes in this scenario:

    • The app is requesting permissions that require admin consent.
    • User consent is disabled tenant-wide.
    • Assignment required is enabled and the user is not effectively assigned in the way the app expects.
    • A Conditional Access or account-specific issue is affecting only this user.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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