A cloud-based identity and access management service for securing user authentication and resource access
Issue Description:
I am able to successfully log into my Azure account, however, any action I attempt within the portal results in authentication errors. The primary error messages I receive are:
- AADSTS160021: Application requested a user session which does not exist
- PassthroughTokenValidationFailed: Token validation failed. A passthrough token was detected without proper resource provider context
- SSL_PROTOCOL_ERROR when accessing login.live.com
{
"sessionId": "db4d10db0d64463599989fec603d6ba5",
"errors": [
{
"errorMessage": "interaction_required: AADSTS160021: Application requested a user session which does not exist. Trace ID: bf1cce98-4ead-4015-984d-3bf6b8be9e00 Correlation ID: 5ff6803e-7941-43b2-a33b-df6e128fe962 Timestamp: 2026-03-10 15:02:37Z",
"clientId": "c44b4083-3bb0-49c1-b47d-974e53cbdf3c",
"scopes": [
"2086cb78-e8e8-4df3-9f9d-a03079825584/.default"
]
}
]
}
Troubleshooting Steps Already Attempted:
- Tested on multiple browsers (Chrome, Firefox) including incognito/private mode
- Cleared all browser cache, cookies, and site data
- Tested on different devices (desktop computer and mobile phone)
- Created a new Microsoft account with a different email address - the same errors occur
- Attempted connection via mobile hotspot and directly through mobile data (not WiFi)
- Temporarily disabled Windows Defender and Windows Firewall
Network Configuration:
I am currently using a mobile hotspot for internet connectivity (not traditional WiFi or ethernet). I have tested both through the hotspot on my computer and directly on my mobile device using cellular data - both produce the same errors.
Impact:
This issue is preventing me from:
- Accessing any Azure resources or subscriptions
- Using Azure Cloud Shell
- Creating or managing any Azure services
- Submitting support requests through the Azure Portal
I suspect this may be related to either my mobile carrier's network filtering or a deeper authentication issue with Azure Active Directory sessions. The fact that a completely new Microsoft account experiences identical errors suggests this is not account-specific.