Azure "Default Directory" masking "Individual" MSA in Partner Center

Issue 1: Authentication Loop in Downloads Hub

I am an individual developer (MSA: <pii removed>) with a published app (FlyPhotos) in the Microsoft Store. I was managing it with Partner Center with no issues. From the last week, Downloads Hub within the Insights section has entered a perpetual sign-in loop and failure state. I suspect this has a connection with me logging in to Azure portal once with same email ID.

Symptoms: All other Partner Center pages (Overview, Submissions) function correctly. Only the Downloads Hub fails to load data.

Console Details from Browser:

• POST https://partner.microsoft.com/dashboard/maicppinsights/analyticsapi/partneruserengagement returns 401 (Unauthorized).
  • GET https://support-api-prod-afd-audaf4eybfc0g0ay.z01.azurefd.net/api/clientsessioncontext returns 403 (Forbidden).

Suspected Root Cause: The Downloads Hub is attempting to authenticate against a newly created Entra ID (Azure AD) tenant instead of my original Personal/MSA identity.

Issue 2: Identity Masking (App invisible in Partner Center)

The problem got worse after I created a trial Azure subscription with the same Outlook email ID. A Default Directory tenant was created. This tenant has masked the Personal/Shadow? Tenant where my published app and historical data reside.

• Personal Tenant -<PII REMOVED>
• Default Directory Tenant - <PII REMOVED>

Impact: When I log into the Partner Center, it defaults to the Default Directory context. Because my app was provisioned under my Personal identity, it is invisible in this new directory, and I cannot manage my store listings in Partner Center.

How Can I?

1. Unlink/De-prioritize the Default Directory from my Partner Center profile.
2. Restore/Force my Personal/MSA (Live ID) as the primary identity for all Partner Center services.
3. Ensure the Downloads Hub correctly recognizes my Personal identity to resolve the 401 authentication error.

Note - I don't mind removing everything connected with Azure as access to my App is the most important priority now. Also it was done just to explorer Azure around.