Azure PAYG signup fails due to locked Developer Account address, causing tenant provisioning failure and Entra MFA deadlock on personal MSA

I am using a personal Microsoft Account (MSA) for Visual Studio Subscriptions (Dev Essentials). The Developer Account profile associated with my Dev Essentials benefits contains an outdated and locked address, and I cannot update it because Partner Center does not allow sign‑in with personal accounts.

This locked developer profile has caused Azure Pay‑As‑You‑Go signup to fail. Azure attempts to validate my credit card against the old developer address, and tenant provisioning never completes.

Because the tenant did not provision correctly, Azure is now enforcing Entra MFA on my personal MSA. Personal MSAs cannot satisfy Entra MFA requirements, which has created a login deadlock:

• Azure portal forces Entra MFA

My MSA cannot access Entra MFA setup or reset pages

Tenant provisioning never completed

I cannot access portal.azure.com

I cannot open Azure support because I have no subscription

I cannot update the developer profile because Partner Center rejects MSAs

Additionally, repeated failed sign‑in attempts (caused by the MFA deadlock) triggered a Microsoft Account Smart Lockout. I can still sign into MSN and Outlook, but when accessing Azure through Dev Essentials, I receive:

“You’ve tried to sign in too many times with an incorrect account or password.”

This confirms that the lockout is a symptom of the underlying identity failure.

I need assistance from the Microsoft Data Protection team, as this issue cannot be resolved through self‑service. They are the only team that can:

reset the Entra MFA state for my MSA,

detach my MSA from the incomplete tenant, or

update the locked developer profile address so Azure can complete provisioning.

This issue is blocking my ability to complete required certification work and impacting project timelines. I would greatly appreciate escalation and guidance on next steps.

Thank you.