What causes AADSTS90033?

Transient MSODS backend outage in the Entra ID (Azure AD) region serving your tenant. Ongoing Microsoft 365 / Entra ID service incident affecting authentication. Throttling or temporary unavailability during a Microsoft-side failover or maintenance window. Network path issue between the token endpoint (login.microsoftonline.com) and MSODS. Cascading impact on dependent services (Power BI, Fabric, ADF, Databricks) using the same tenant for OAuth token acquisition

How do I fix AADSTS90033?

Retry the sign-in or token request after 30–60 seconds with exponential backoff — AADSTS90033 is transient by definition and usually resolves without action. Check the Microsoft 365 Service Health dashboard (admin.microsoft.com → Health → Service health) and status.office.com for an active Entra ID / Authentication incident. For Power BI scheduled refreshes, ADF linked services, or Databricks OAuth: re-run the refresh / activity once Microsoft reports recovery — do not rotate credentials or reconfigure the data source, the config is fine. If the error persists for more than ~15 minutes with no reported incident, open a Microsoft support ticket with the correlation ID and timestamp from the error response. Avoid mass retries from automation — they won't succeed during the outage and may trigger throttling once MSODS recovers

Low severityauthentication

Power BI Refresh Error:
AADSTS90033

What does this error mean?

Microsoft's directory backend (MSODS) is temporarily unreachable, blocking Entra ID (Azure AD) token issuance.

Common causes

1Transient MSODS backend outage in the Entra ID (Azure AD) region serving your tenant
2Ongoing Microsoft 365 / Entra ID service incident affecting authentication
3Throttling or temporary unavailability during a Microsoft-side failover or maintenance window
4Network path issue between the token endpoint (login.microsoftonline.com) and MSODS
5Cascading impact on dependent services (Power BI, Fabric, ADF, Databricks) using the same tenant for OAuth token acquisition

How to fix it

1Retry the sign-in or token request after 30–60 seconds with exponential backoff — AADSTS90033 is transient by definition and usually resolves without action
2Check the Microsoft 365 Service Health dashboard (admin.microsoft.com → Health → Service health) and status.office.com for an active Entra ID / Authentication incident
3For Power BI scheduled refreshes, ADF linked services, or Databricks OAuth: re-run the refresh / activity once Microsoft reports recovery — do not rotate credentials or reconfigure the data source, the config is fine
4If the error persists for more than ~15 minutes with no reported incident, open a Microsoft support ticket with the correlation ID and timestamp from the error response
5Avoid mass retries from automation — they won't succeed during the outage and may trigger throttling once MSODS recovers

Frequently asked questions

What does AADSTS90033 mean?

The Microsoft Online Directory Service (MSODS) isn't available.

How do I fix this error?

Check your application registration, token configuration, and user permissions in the Azure portal. Review Conditional Access policies if the error is policy-related.

Source · learn.microsoft.com/en-us/entra/identity-platform/reference-error-codes#aadsts-error-codes