Microsoft Entra ID Cannot Login to Azure Using Microsoft Login

Charles Michael 0 Reputation points
2026-08-03T21:34:09.2+00:00

Hello, I'm using a 15+ year old account from Microsoft Ads to try and login to Azure to use Microsoft Ads Developer API's but I'm stuck on the Microsoft Services system tenant with no directory errors. Cannot create a new tenant, cannot register applications, don't qualify for M365 Developer Program, Azure free signup loops back to the same placeholder tenant. Need a proper Entra ID tenant provisioned for app registration. I need to use this specific account as it has 15+ year of advertising history.

RESOLVED: Azure required a credit card on file to properly issue the ID.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

1 answer

Sort by: Most helpful
  1. Jerald Felix 18,200 Reputation points Volunteer Moderator
    2026-08-04T17:23:48.0466667+00:00

    Hello Charles Michael,

    Greetings! Thanks for raising this question in Q&A forum.

    I understand this is frustrating, especially when you need to use an existing Microsoft Ads account with a long history. Based on the error AADSTS16000, the most likely issue is that your Microsoft personal account (live.com) is currently associated with the Microsoft-managed system tenant and does not have access to a customer-managed Microsoft Entra ID tenant where application registrations can be created.

    1. Sign in to the Azure Portal and check whether you have access to any existing Microsoft Entra tenant under Settings > Directories + subscriptions.
    2. If no usable tenant is available, try creating a new Azure subscription using the same Microsoft account through Azure account management rather than through the Azure Portal onboarding flow.
    3. Verify whether the account is being treated as a personal Microsoft account (MSA) rather than a work or school account. Personal accounts cannot directly create app registrations unless they have access to an Entra tenant.
    4. If Azure signup continues looping back to the Microsoft Services tenant and tenant creation remains unavailable, this requires Microsoft account and Azure provisioning teams to review the account configuration on the backend.
    5. Open a support request with Azure Subscription/Account Support and provide the correlation ID, trace ID, and tenant ID shown in the error. The support team can validate whether tenant provisioning is blocked and assist with attaching the account to a usable Entra ID tenant.

    The next action is with Microsoft Support, as a forum response cannot provision or modify tenant ownership for your account. They will need to review the backend account-to-tenant association and determine why the account is restricted to the Microsoft Services tenant.

    If this answer helps you kindly accept the answer which will help others who have similar questions

    Best Regards,

    Jerald Felix.

    Was this answer helpful?

    0 comments No comments

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.