Microsoft Partner Center | Other
Other features or issues related to Microsoft Partner Center
Issue resolved,
Delete the User from Entra ID to revoke the conflicts.
#Helped by Microsoft Support
Apps & Games lost after MSA publisher owner became Entra EXT user (MSA → #EXT# conversion)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 3%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERK%3C/text%3E%3C/svg%3E)
REYAS KHAN M
0
Reputation points
any Partner Center expert please HELP!!!!!!!!!
I’m experiencing a Partner Center issue caused by the interaction between a personal Microsoft Account (MSA) and an Entra (Azure AD) tenant.
Clear example of the problem
- Original Publisher Owner (MSA):
******@outlook.com→ This account created and published all Apps & Games in Partner Center.
Later added Entra tenant: exampletenant.onmicrosoft.com
After associating the Entra tenant with Partner Center:
The original MSA (******@outlook.com) was converted into a B2B guest user inside Entra:
example_outlook.com#EXT#@exampletenant.onmicrosoft.com
From this point, Partner Center behavior changed.
What broke after this change
When signing in as ******@outlook.com (MSA):
Apps & Games workspace disappeared
Publisher appears to exist but is no longer accessible as before
When signing in under the **Entra tenant context**:
The publisher exists
Access appears role-based
Ownership semantics are different from the original MSA-owned model
No apps were deleted
No new publisher or seller account was created
Same Publisher ID, same apps — only identity context changed
Key clarification
Owner account is an MSA (Outlook)
Entra account is a B2B guest (#EXT# @*.onmicrosoft.com)
Apps were created under MSA authority, not Entra
After MSA → EXT conversion, Apps & Games no longer bind to the MSA
What I’m trying to confirm
Is this expected behavior when an MSA publisher owner is later associated with an Entra tenant?
Is there a supported way to:
Restore MSA (******@outlook.com) as Publisher Owner, while keeping the Entra tenant attached, OR
Rebind Apps & Games visibility back to the MSA authority?
Is it possible to **reverse or correct the MSA → EXT guest conversion** specifically for Partner Center publishers?
Constraints
I do not want to:
Create a new publisher
Migrate apps
Lose the existing Publisher ID
I’m looking for official guidance, known limitations, or escalation paths from Partner Center / Store engineering.I’m experiencing a Partner Center issue caused by the interaction between a personal Microsoft Account (MSA) and an Entra (Azure AD) tenant.
Clear example of the problem
Original Publisher Owner (MSA):
******@outlook.com
→ This account created and published all Apps & Games in Partner Center.
Later added Entra tenant:
exampletenant.onmicrosoft.com
After associating the Entra tenant with Partner Center:
The original MSA (******@outlook.com) was converted into a B2B guest user inside Entra:
example_outlook.com
From this point, Partner Center behavior changed.
What broke after this change
When signing in as ******@outlook.com (MSA):
Apps & Games workspace disappeared
Publisher appears to exist but is no longer accessible as before
When signing in under the **Entra tenant context**:
The publisher exists
Access appears role-based
Ownership semantics are different from the original MSA-owned model
No apps were deleted
No new publisher or seller account was created
Same Publisher ID, same apps — only identity context changed
Key clarification
Owner account is an MSA (Outlook)
Entra account is a B2B guest (#EXT# @*.onmicrosoft.com)
Apps were created under MSA authority, not Entra
After MSA → EXT conversion, Apps & Games no longer bind to the MSA
What I’m trying to confirm
Is this expected behavior when an MSA publisher owner is later associated with an Entra tenant?
Is there a supported way to:
Restore MSA (******@outlook.com) as Publisher Owner, while
keeping the Entra tenant attached, OR
Rebind Apps & Games visibility back to the MSA authority?
Is it possible to **reverse or correct the MSA → EXT guest conversion** specifically for Partner Center publishers?
Constraints
I do not want to:
Create a new publisher
Migrate apps
Lose the existing Publisher ID
I’m looking for official guidance, known limitations, or escalation paths from Partner Center / Store engineering.
and I already created a support ticket, but still i need some quick solution if possible.
Microsoft Partner Center | Other
3 answers
Sort by: Most helpful
-
AI answer
2026-02-03T12:39:30.69+00:00 It appears that the behavior you are experiencing is related to how Microsoft handles the association of personal Microsoft Accounts (MSA) with Microsoft Entra tenants. When an MSA is converted into a B2B guest user in an Entra tenant, it can lead to changes in access and ownership semantics in Partner Center, as you have described.
This behavior is expected when an MSA publisher owner is later associated with an Entra tenant. The original MSA account may lose direct ownership visibility over the apps and games that were published under its authority, as the ownership context shifts to the Entra tenant.
Currently, there is no documented supported method to revert the MSA to its original state or to rebind the apps and games visibility back to the MSA authority while keeping the Entra tenant attached. The conversion to a B2B guest user is a significant change in identity context, and reversing it specifically for Partner Center publishers may not be feasible.
For official guidance, known limitations, or escalation paths, it is advisable to continue working with your support ticket, as they may provide the most accurate and tailored assistance for your specific situation.
If you have not already, you may also want to consult the Partner Center documentation or reach out to Microsoft support for further clarification on this issue.
AI-generated content may be incorrect. Read our transparency notes for more information.