AADSTS16000 blocks Microsoft for Startups onboarding and Program Support access

Submit the direct Microsoft for Startups support request form to bypass the Azure portal’s failing Help + Support blade and request correction of the startup’s owner/tenant association.^1^

What to submit

Open the Microsoft for Startups support request linked under Other issues → Can’t activate Azure benefit plan → Microsoft for Startups in the signup troubleshooting page above. In the request:

1. Select the closest program/onboarding, portal access, or account ownership category.
2. State that:
   • The startup is SupplyEdge.
   • You can reach the Microsoft for Startups dashboard using a personal Microsoft account.
   • Both startup onboarding and Azure Help + Support fail during token retrieval.
   • The error is interaction_required / AADSTS16000.
   • The identity provider is live.com, and the resource tenant shown is Microsoft Services.
   • Signing out, private browsing, and removing the previous Foxtale guest association did not resolve it.
3. Ask support to verify and correct:
   • the owner account attached to the startup application;
   • the Microsoft Entra tenant associated with that account;
   • any incomplete identity provisioning for the Startups portal.
4. Attach the screenshot and provide the following as text:
   • UTC timestamp;
   • trace ID;
   • correlation ID;
   • application name and application ID displayed in the error;
   • affected account address;
   • startup/application ID, if visible.

Send account details and diagnostic identifiers only through the private support form, not in a public Q&A post.

This belongs with Microsoft for Startups Program Support: its documented scope includes program onboarding, portal issues, and correcting the owner account tied to an Azure sponsorship.^2^

What the error establishes

AADSTS16000 means the live.com identity does not exist in the tenant from which the application is requesting its token and therefore cannot access that application there. Microsoft also notes that this commonly occurs when a personal Microsoft account reaches Microsoft Entra without an associated directory.^3^

Removing the Foxtale guest relationship does not add the account to the separate Microsoft Services tenant. Because that tenant and the Azure Portal application are Microsoft-controlled, this is not something you can repair by inviting yourself as a guest or changing the application’s sign-in configuration.

Conditional account path

If Startup Support confirms that the application must be associated with a customer-owned Microsoft Entra tenant rather than the current personal-account context, create or use an Azure account with its own directory and ask support to transfer or re-associate the startup application with that identity. A closely matching Azure portal case documents creating an Azure account/tenant as the resolution when a personal account is left in the restricted Microsoft Services tenant.^4^

Do not create a second startup application or delete the existing startup account unless Program Support explicitly directs it; account deletion is irreversible and also closes associated licenses.^5^

A Microsoft Q&A moderator generally cannot modify tenant membership or startup ownership directly. The public thread can be flagged for moderator attention, but the direct Startups support request is the appropriate escalation channel for the required private account investigation.

References

1. Troubleshoot issues when you sign up for a new account in the Azure portal
2. Microsoft for Startups Program Support
3. Microsoft Entra authentication and authorization error codes
4. How to fix subscription issues - Microsoft Q&A
5. Microsoft for Startups Program Page within the Azure Portal