A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.
Recover the Microsoft account previously linked to GitHub first, and if it is no longer recognized, use Azure’s sign-in-free support request to have Microsoft restore the identity-to-subscription association.
1. Recover the existing GitHub-linked Microsoft account
“Sign in with GitHub” uses GitHub as a credential for an underlying Microsoft account; it does not make the GitHub or Gmail identity itself the Azure account. Microsoft checks the email addresses associated with GitHub and links the GitHub credential to the matching Microsoft account.^1^
- Open Microsoft’s Recover your account page:
https://account.live.com/password/reset - Enter the exact Gmail address attached to the GitHub account when Azure was originally created.
- Complete verification and add/reset a Microsoft-account password.
- Sign in to Azure with that Gmail address and the new Microsoft-account password rather than selecting GitHub.
- If prompted to choose an account type, try Personal account. Azure customers can have personal and work/school identities using the same email, but only one may have access to the subscription.^2^
Adding a Microsoft-account password does not alter the GitHub password or unlink GitHub; it creates another sign-in method for the same linked account.^1^
If recovery still reports that the username does not exist, do not continue through the flow that offers to create a new account. A newly created identity would not automatically own the existing production subscription.
2. Open an Azure support request without portal access
Azure documents a support-request route specifically for customers who cannot sign in to the portal.^3^
Use Create a support request from that page and classify the issue as:
- Service: Billing and subscriptions
- Problem: Unable to sign in / subscription access
- Description: Existing paid production subscription; historical sign-in used GitHub; linked Microsoft account is no longer found; GitHub authentication now enters a blocked account-creation flow.
Provide the following only in the private support case, not in Microsoft Q&A or another public post:
- Microsoft Entra tenant ID
- Subscription ID, if shown on an invoice
- Billing-account or invoice number
- Exact billing email address
- Recent invoice date and amount
- GitHub username and the verified GitHub email used originally
- Screenshot and exact text of “Account creation has been blocked”
- Date, time, and time zone of the failed sign-in
- Any trace ID, correlation ID, timestamp, or error code shown under error details
Ask support to:
- Identify the Microsoft account/object that owns the subscription.
- Restore access to that existing identity or repair its GitHub linkage.
- Confirm the tenant-specific sign-in endpoint if the general sign-in route is selecting the wrong tenant.
- Avoid creating or transferring resources to a replacement account unless Microsoft confirms that recovery is impossible.
After access is restored
If sign-in succeeds but Azure shows No subscriptions found, select the profile menu in the upper-right corner, choose Switch directory, and select the directory matching the tenant ID. That message can result from being in the wrong directory or from the restored identity lacking subscription permissions.^4^
Because private windows, multiple browsers, and disabled extensions have already failed, repeating those browser steps is unlikely to advance this case. The next steps are identity recovery and sign-in-free Azure billing escalation.
References