AADSTS500022 Access to tenant is denied and Developer Program error 41102

Chan Joey 20 Reputation points
2026-09-29T01:51:41.2866667+00:00

I have a Microsoft 365 Developer Program tenant.

The tenant exists and OpenID metadata is accessible.

However all administrative portals return:

AADSTS500022: Access to tenant is denied.

Affected portals:

  • Microsoft 365 Admin Center
  • Microsoft Entra Admin Center
  • Azure Portal

In addition, the Microsoft 365 Developer Program Dashboard returns Error 41102.

I am unable to determine whether the tenant has been restricted or requires backend review.

I can provide tenant details privately if required.

Microsoft 365 and Office | Development | Microsoft 365 Developer Program
0 comments No comments

Answer accepted by question author
raymond osei 80 Reputation points
2026-09-29T02:09:04.0833333+00:00

Hello Chan,

The error code AADSTS500022 paired with Developer Program error 41102 indicates that the sandbox tenant has been suspended, flagged as inactive, or administratively decommissioned by the Microsoft 365 Developer Program automated compliance systems.

Here is what is happening and the troubleshooting steps to take:

  1. Root Cause Analysis:
    • AADSTS500022 explicitly means: "Access to tenant is denied." The Microsoft Entra ID (formerly Azure AD) STS service blocks token issuance because the tenant state is disabled or expired on the identity backplane.
    • Developer Program Error 41102 indicates that your sandbox profile has lost active entitlement or failed the automated telemetry activity threshold required for renewal (or was flagged during periodic automated screening).
  2. Check Sandbox Lifecycle Status on Dashboard:
    • Navigate to the Microsoft 365 Developer Program Dashboard: https://developer.microsoft.com/en-us/microsoft-365/profile
    • Sign in with your primary Microsoft account (the personal account linked to the program, not the onmicrosoft.com admin).
    • Check the banner status:
      • If it indicates "Expired" or "Deleted", Microsoft allows a short grace period before the tenant and data are permanently purged.
      • If it displays an active state but sign-in is blocked, there is a synchronization lock between the dev portal and the Entra tenant backplane.
  3. Resolution Options:
    • Attempt Incognito / InPrivate Browser Window: Clear all cached tokens and session cookies to ensure you are not passing stale tenant authority IDs.
    • Self-Service Deletion & Recreation: If your dashboard displays error 41102 and the tenant cannot be revived, the fastest route to get a functional environment is to delete the current sandbox profile directly from the Developer Program dashboard and provision a fresh sandbox tenant.
    • Developer Support Ticket: If you had critical development assets or an active paid Visual Studio subscription attached to the profile, you must contact Microsoft Developer Support directly via the support options at https://developer.microsoft.com/en-us/microsoft-365/support, as individual community moderators cannot bypass backend security tenant suspensions.

Hope this clarifies the status of the tenant!

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Oldest
  1. Hani-Ng 2,070 Reputation points Independent Advisor
    2026-09-29T02:20:54.7966667+00:00

    Hi Chan Joey

    The error AADSTS500022: Access to tenant is denied indicates that access to the Microsoft Entra tenant is being denied. This error can be associated with tenant access restrictions or other tenant-level conditions.

    Microsoft Entra authentication & authorization error codes | Azure Docs

    Since you are receiving the same error when accessing the Microsoft 365 Admin Center, Microsoft Entra Admin Center, and Azure portal, while the Microsoft 365 Developer Program dashboard separately returns error 41102, this does not appear to be something that can be fully diagnosed or resolved through the public forum. Similar cases involving error 41102 have been directed to the appropriate Microsoft support channel when the status of the Developer Program account requires further review. You an refer to: Microsoft 365 Developer Program – Error 41102 – Unable to Sign In After E5 Developer Subscription Ex…

    Just a quick note that this forum is a peer-to-peer community, so members can only share advice and experiences. They do not have access to tenant backend information or Developer Program account records to determine whether your tenant or Developer Program account has been restricted, nor can they remove a tenant-level restriction.

    In this situation, please contact Microsoft support / Microsoft 365 Developer Program support and provide the relevant error information, including the Request ID, Correlation ID, timestamp, tenant ID/domain, and the MS-CorrelationId associated with error 41102, so that the appropriate team can review the account and tenant status.

    For further instructions, you can follow this:

    Microsoft Engage Center Get Help | Microsoft Learn

    Please do not post your tenant details, correlation IDs, or other private organizational/account information publicly in the forum. Provide them privately only when requested through an official Microsoft support channel.

    I hope this information helps. If you have any further questions about the errors or the available support path, please feel free to ask.

    Was this answer helpful?

    0 comments No comments

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.