Can not link student azure account to register for Microsoft Student Ambassador

The 400 (Bad Request) error when selecting “Link Your Account” indicates the backend service for the student/Azure verification is rejecting the request, not a local browser or cache problem. Clearing cache or using Incognito typically won’t fix this, as confirmed by similar sign‑in and registration issues in Microsoft services.

Based on the patterns in the provided context, use these steps to troubleshoot and then escalate:

1. Sign out of all Microsoft accounts and clear auth state
   • Sign out from all Microsoft properties in the browser (for example, account.microsoft.com, Microsoft Learn, Azure Portal) so only the intended student account is used.
   • Clear cookies/site data specifically for Microsoft domains and the registration site, then close and reopen the browser.
   • This is similar to the fix where a user “had to sign out of all Microsoft accounts and clear all site data in my browser then it let me in.”
2. Use a clean/private session with correct account
   • Open a new InPrivate/Incognito window.
   • Sign in only with the student Microsoft account that should be linked (for example, the university‑provided Microsoft account if applicable).
   • Ensure the account itself is healthy: verify sign‑in at the Microsoft account profile page and complete any required verification if prompted (for example, “MSA account requires additional verification steps”).
3. Check for account type/domain conflicts
   • If the student email domain is also used by an organization with Microsoft Entra ID (formerly Azure AD), and that same email is also configured as a personal Microsoft account (MSA), conflicts can cause sign‑in and registration failures in portals.
   • In similar cases (Partner Center/Collaborate), the workaround is to rename the personal Microsoft account so it no longer uses the work/school email as its sign‑in alias:
     1. Sign in to the Your Info page of the Microsoft account.
     2. Select Manage how you sign in to Microsoft.
     3. Under Account alias, add a purely personal email address (or get a new one from Microsoft) and make that the primary alias.
     4. Remove the work/school (university) email from the personal account if present.
   • After that, use the university account only as an organizational account where required.
4. Try a different browser and ensure cookies are allowed
   • Use a supported browser such as Microsoft Edge or Chrome.
   • Ensure third‑party cookies are not blocked, as some Microsoft sign‑up and verification flows require them (similar to Azure sign‑up and Cloud Shell issues where blocking third‑party cookies prevents progress).
5. If the error persists, contact the event/program support channel
   • A 400 from the azure-verify endpoint can indicate a backend configuration or synchronization issue rather than anything on the client side.
   • In a similar Virtual Training Day case, Microsoft support confirmed the issue was caused by a synchronization delay between systems and resolved it by asking the user to re‑register for a later session.
   • Use the official support/contact channel for the Student Ambassador program or the registration page and provide:
     • The exact error (HTTP 400 on .../api/students/azure-verify/).
     • The email address used for registration.
     • Confirmation that sign‑in to the Microsoft account works elsewhere.

If the problem is on the service side (for example, sync or registration data issue), only the program’s support team can correct it; local troubleshooting will not remove the 400 error.

References:

• Troubleshooting common training issues in Microsoft Learn
• Resolve student sign-in problems
• How to Troubleshoot Common Issues
• Troubleshoot issues when you sign up for a new account in the Azure portal
• Unable to join Azure Virtual Training Day due to login failure - Microsoft Q&A
• Can not access Azure - Microsoft Q&A