Azure student account

Hello**Thomas,**

Greetings! Thanks for raising this question in the Q&A forum.

The error in your screenshot, post_request_failed, is a generic MSAL (Microsoft Authentication Library) error meaning the browser could not complete the network call to Microsoft's sign-in endpoint while trying to sign you in to the Azure Portal. Since you are signing directly into portal.azure.com rather than a custom-built app, the usual "register the redirectUri as SPA" advice does not apply to you, that guidance is for developers building their own applications. In your case the block is happening locally, in the browser or on the network path, before the request ever reaches Microsoft's servers. This is commonly caused by browser extensions, cached sign-in data, or a network or firewall blocking Microsoft's identity endpoints, which is common on college or campus Wi-Fi.

1. Try signing in from a private or InPrivate window first

Open a new InPrivate window in Edge (Ctrl+Shift+N) and go to portal.azure.com. This bypasses extensions and existing cached data, so if sign-in succeeds here, you know the problem is local to your normal browser profile rather than your account or network.

1. Clear cached sign-in data for the identity domains

In your regular browser window, go to Settings then Privacy, search, and services then Clear browsing data, and clear cookies and cached files specifically for these sites if your browser lets you scope it:

• portal.azure.com
• login.microsoftonline.com
• login.live.com

If you cannot scope it, a full clear of cookies and cached data for the last 24 hours is fine. Then close and reopen the browser completely before trying again.

1. Temporarily disable browser extensions

Your screenshot shows Edge with several extensions and Copilot enabled in the toolbar. Ad blockers, privacy or script blockers, and VPN extensions are the most common cause of this exact error because they interfere with the POST request MSAL makes to the token endpoint. Go to edge://extensions, toggle all extensions off, and try signing in again. If it works, re-enable them one at a time to find the culprit.

1. Test on a different network

If you are on a college, library, or shared Wi-Fi network, its firewall or proxy may be blocking or altering traffic to Microsoft's identity endpoints. Try a mobile hotspot or a different network to see if the sign-in succeeds there. If it does, the campus network is the root cause and you would need to raise it with your school's IT department to allow traffic to *.microsoftonline.com and *.azure.com.

1. Check your device's date and time

An inaccurate system clock can break the token exchange during sign-in. Confirm your date, time, and time zone are set correctly and, ideally, set to update automatically.

1. Try a different browser

Since your screenshot shows Edge, try the same sign-in in Chrome or Firefox. If it works there, the issue is specific to your Edge profile, and steps 2 and 3 above are the ones to focus on.

1. Use the built-in self diagnostics on the error page

The sign-in failure page itself has a Perform self diagnostics option directly on it. Running that captures the specific failure details tied to your Browser ID (072ce20f-8373-4372-8225-2986aee43aab in your screenshot) and is the fastest way to get a precise root cause if the steps above do not resolve it.

1. Contact support if it persists

If none of the above resolves it, use the Contact support link on the same error page. Since this is an Azure for Students account, mention that you are on the student offer and include your Browser ID from the debugging information section so support can trace the exact failed request.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.