Link your account fails with 400 error (azure-verify) on MVP Student Ambassadors registration

humaira bibi 0 Reputation points
2026-06-14T03:16:30.3966667+00:00

Hello,

I am trying to register for the Microsoft Student Ambassadors program via mvp.microsoft.com/en-US/account/. On the "Registration Start-Here" page, when I click "Link your account", the request fails.

Details from browser DevTools (Network tab):

My account details:

  • Email used: ******@szabist.pk
  • I have an active Azure for Students account ($100 credit, "Default Directory - bscs2312420szabist.onmicrosoft.com")
  • Sign-in to Azure Portal works fine with this account
  • I tried in Incognito mode after clearing cookies, signed in with the same account, but the error persists
  • I also previously got "AADSTS50177: User account does not exist in tenant 'Microsoft'" when trying via a different flow

Could you please check on the backend why the azure-verify endpoint is returning 400 for this account, and help resolve the linking issue?

Thank you. .

[Moderator edit: Changed tags from: Azure | Azure Monitor ]

Community Center | Not monitored
0 comments No comments

2 answers

Sort by: Most helpful
  1. Nathan Roberts (SN) 12,656 Reputation points Student Ambassador Volunteer Moderator
    2026-06-14T05:31:09.8366667+00:00

    Hey there, humaira bibi

    Please can you make sure you are signing into the Microsoft MVP portal (https://mvp.microsoft.com/account) using your personal Microsoft account. It could be that you are trying to sign into the portal with your organisational account.

    Once you have done this, please can you try and link your account to your Azure Student Subscription. If you are continuing to have problems with this, please reach out to the Microsoft Student Ambassador team by emailing them at sa-help@microsoft.com

    They will be able to help further with this.

    I also previously got "AADSTS50177: User account does not exist in tenant 'Microsoft'" when trying via a different flow

    This is expected, when you haven't been added to the Microsoft tenant as a guest. When signing in, the sign-in process checks whether the account is a member of the tenant either as a guest or member. I would stick to the flow on the official pages.

    Hope this helps & good look!
    Nathan

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-06-14T03:16:45.6766667+00:00

    The 400 response from the azure-verify endpoint indicates that the sign-in or account data being sent from the MVP Student Ambassadors registration page cannot be processed as a valid Microsoft account/tenant combination for that flow.

    From the provided information and similar account/tenant issues in the context, the most likely causes are:

    1. The email being used isn’t correctly set up as a Microsoft account identity for this scenario.
    2. There’s a conflict between a work/school account in Microsoft Entra ID (Azure AD) and a personal Microsoft account (MSA) using the same email.

    Use the following steps to unblock the account side before retrying the “Link your account” action:

    1. Confirm the Microsoft account for the university email
      1. Go to the Microsoft account sign-in page: account.microsoft.com.
      2. Sign in with the university email address (the @szabist.pk address).
      3. On the ribbon, select Your info.
      4. Select Manage how you sign in to Microsoft.
      5. Complete identity verification (email or other method) if prompted.
    2. Ensure the university email is a valid alias on a Microsoft account
      1. In Manage how you sign in to Microsoft, look under Account alias.
      2. If the university email address is not listed as an alias, select Add email and add it.
      3. If the university email is the only alias and is tied to a personal Microsoft account while also being used as a work/school account in Entra ID, add a separate personal email address (for example, an Outlook.com or other personal address) as an additional alias.
    3. Resolve possible work/school vs personal account conflict The error AADSTS50177: User account does not exist in tenant 'Microsoft' and the 400 from azure-verify are consistent with the scenario where a work/school domain is federated with Microsoft Entra ID and the same email is also configured as a personal Microsoft account. In that case:
      1. Sign in to the Your Info page of the Microsoft account for the university email.
      2. Go to Manage how you sign in to Microsoft.
      3. Under Account alias, add a personal email address if one is not already present.
      4. Use that personal email as the primary alias for the personal Microsoft account, and keep the university email reserved for the work/school (Entra ID) identity.
    4. Verify Azure/Microsoft account linkage for student scenarios For student programs that require a Microsoft account:
      1. Ensure that the university email is either:
        • A Microsoft account created with that university email, or
        • Properly added as an alias to an existing Microsoft account that is used for student benefits.
      2. After adjusting aliases as above, sign out of all Microsoft sessions in the browser.
      3. Clear cookies or use a fresh private/incognito window.
      4. Sign in again with the intended account (the one where the university email is correctly configured) and retry the “Link your account” step.

    If the 400 error persists after ensuring the account is correctly configured and aliases are separated as above, the next step is to contact the program’s support (MVP/Student Ambassadors support) or general Azure/Microsoft account support with the exact error details, as the backend azure-verify API is not user-configurable and may require a server-side fix or manual unblocking.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.