Summary

I am a Microsoft FTE and successfully activated the monthly Azure credit benefit through my Visual Studio subscription using my personal Microsoft Account (MSA): ******@gmail.com. The activation process appears to have completed successfully, but I am unable to sign in to Azure Portal because Azure requires Microsoft Authenticator MFA that appears to be misconfigured or out of sync.

Account Information

• Visual Studio subscription activated with Microsoft FTE account.
• Azure benefit redeemed using personal MSA: ******@gmail.com.
• Azure Portal login is performed using the same MSA account, as instructed in the activation guide.

What Worked

1. Successfully activated the Azure benefit through Visual Studio subscription.
2. Can sign in to my Microsoft Account (account.microsoft.com) using Windows Hello / passkey.
3. Can access Microsoft Account security settings.
4. Microsoft Account security methods originally showed:
   • Email verification
     • SMS verification
       • Microsoft Authenticator
         • Windows Hello / passkey imageturn8search10†image.png(Image: Microsoft account security methods)

Original Problem

During Azure Portal sign-in, Azure required Microsoft Authenticator verification.

The available Azure MFA options were:

• Approve a request in Microsoft Authenticator
• Enter a verification code from Microsoft Authenticator

Issue #1 – No Authenticator Notifications

When Azure attempted to send a Microsoft Authenticator approval request, no notification appeared on the phone.

Issue #2 – Verification Codes Rejected

Authenticator generated valid-looking 6-digit codes, but Azure rejected them as incorrect.

Troubleshooting Already Performed

Microsoft Account Security

Verified that the Microsoft Account contained multiple authentication methods:

• Email
• SMS
• Authenticator
• Windows Hello

imageturn8search10†image.png(Image: Microsoft account security methods)

Authenticator Investigation

The Microsoft Authenticator entry appeared to function only as a TOTP/code generator and did not seem to support approval requests.

The account details inside Authenticator showed only one-time password functionality. imageturn10search12†image.png(Image: Authenticator showing OTP only)

Removed Authenticator Registration

To rule out a stale registration, I removed:

1. The Microsoft Authenticator sign-in method from Microsoft Account security settings.
2. The ******@gmail.com account from Microsoft Authenticator.

After removal, Microsoft Account security methods no longer showed Authenticator. imageturn18search13†image.png(Image: Authenticator removed)

Unexpected Behavior After Removal

Even after completely removing Authenticator from:

• Microsoft Account security settings
• Mobile Microsoft Authenticator app

Azure sign-in still requires Microsoft Authenticator MFA and continues showing:

• Approve a request on my Microsoft Authenticator app
• Use a verification code

imageturn27search6†image.png(Image: Azure MFA still requiring Authenticator)

When selecting "Use a verification code", Azure still waits for a code from Microsoft Authenticator despite there no longer being any Authenticator registration available. imageturn26search8†image.png(Image: Azure requesting authenticator code)

Why This Seems Incorrect

There appears to be a mismatch between:

Microsoft Account Security Configuration

Authenticator has been removed from the account.

Azure MFA Configuration

Azure / login.microsoftonline.com still believes Microsoft Authenticator is configured and requires it as the only MFA method.

This suggests a stale, orphaned, or out-of-sync MFA registration.

Request

Please help determine:

1. Why Azure MFA still requires Microsoft Authenticator after it was removed from the account.
2. Whether there is a separate MFA registration associated with this Azure subscription or identity.
3. How to reset or re-register the MFA methods for this Azure login.
4. Whether the Visual Studio Azure subscription is associated with a different identity provider or tenant than expected.

Expected Outcome

I should be able to sign into Azure Portal using the MSA account that owns the Visual Studio Azure credit benefit and either:

• Use available authentication methods (Windows Hello / Email / SMS), or
• Re-register Microsoft Authenticator from a clean state.

  Unable to Access Azure Subscription (Visual Studio $150 Benefit) Due to MFA / Authenticator Registration Issues

  Summary

  I am a Microsoft FTE and successfully activated the monthly Azure credit benefit through my Visual Studio subscription using my personal Microsoft Account (MSA): ******@gmail.com. The activation process appears to have completed successfully, but I am unable to sign in to Azure Portal because Azure requires Microsoft Authenticator MFA that appears to be misconfigured or out of sync.

  Account Information

  • Visual Studio subscription activated with Microsoft FTE account.
  • Azure benefit redeemed using personal MSA: ******@gmail.com.
  • Azure Portal login is performed using the same MSA account, as instructed in the activation guide.

  What Worked

  1. Successfully activated the Azure benefit through Visual Studio subscription.
  2. Can sign in to my Microsoft Account (account.microsoft.com) using Windows Hello / passkey.
  3. Can access Microsoft Account security settings.
  4. Microsoft Account security methods originally showed:
     • Email verification

       - SMS verification
       
             - Microsoft Authenticator
       
                   - Windows Hello / passkey imageturn8search10†image.png(Image: Microsoft account security methods)
       

  Original Problem

  During Azure Portal sign-in, Azure required Microsoft Authenticator verification. The available Azure MFA options were:
  • Approve a request in Microsoft Authenticator
    • Enter a verification code from Microsoft Authenticator
  imageturn24search12†image.png(Image: Azure MFA challenge)

  Issue #1 – No Authenticator Notifications

  When Azure attempted to send a Microsoft Authenticator approval request, no notification appeared on the phone.

  Issue #2 – Verification Codes Rejected

  Authenticator generated valid-looking 6-digit codes, but Azure rejected them as incorrect.

  Troubleshooting Already Performed

  Microsoft Account Security

  Verified that the Microsoft Account contained multiple authentication methods:
  • Email
    • SMS
      • Authenticator
        • Windows Hello
  imageturn8search10†image.png(Image: Microsoft account security methods)

  Authenticator Investigation

  The Microsoft Authenticator entry appeared to function only as a TOTP/code generator and did not seem to support approval requests. The account details inside Authenticator showed only one-time password functionality. imageturn10search12†image.png(Image: Authenticator showing OTP only)

  Removed Authenticator Registration

  To rule out a stale registration, I removed:
  1. The Microsoft Authenticator sign-in method from Microsoft Account security settings.
     1. The ******@gmail.com account from Microsoft Authenticator.
  After removal, Microsoft Account security methods no longer showed Authenticator. imageturn18search13†image.png(Image: Authenticator removed)

  Unexpected Behavior After Removal

  Even after completely removing Authenticator from:
  • Microsoft Account security settings
    • Mobile Microsoft Authenticator app
  Azure sign-in still requires Microsoft Authenticator MFA and continues showing:
  • Approve a request on my Microsoft Authenticator app
    • Use a verification code
  imageturn27search6†image.png(Image: Azure MFA still requiring Authenticator) When selecting "Use a verification code", Azure still waits for a code from Microsoft Authenticator despite there no longer being any Authenticator registration available. imageturn26search8†image.png(Image: Azure requesting authenticator code)

  Why This Seems Incorrect

  There appears to be a mismatch between:

  Microsoft Account Security Configuration

  Authenticator has been removed from the account.

  Azure MFA Configuration

  Azure / login.microsoftonline.com still believes Microsoft Authenticator is configured and requires it as the only MFA method. This suggests a stale, orphaned, or out-of-sync MFA registration.

  Request

  Please help determine:
  1. Why Azure MFA still requires Microsoft Authenticator after it was removed from the account.
     1. Whether there is a separate MFA registration associated with this Azure subscription or identity.
        1. How to reset or re-register the MFA methods for this Azure login.
           1. Whether the Visual Studio Azure subscription is associated with a different identity provider or tenant than expected.

  Expected Outcome

  I should be able to sign into Azure Portal using the MSA account that owns the Visual Studio Azure credit benefit and either:
  • Use available authentication methods (Windows Hello / Email / SMS), or
    • Re-register Microsoft Authenticator from a clean state.