If Account settings → Financial details offers Associate your Microsoft account, associate the original 2016 MSA and sign back in with it; if that option is unavailable or the account still reports no linked partner account, Microsoft support must investigate and, if necessary, restore the legacy publisher association.
Try the legacy MSA association
- Open Partner Center in a private browser window.
- Sign in using an account that currently exposes the old developer account.
- Select Settings (gear) → Account settings.
- Under Financial details, select Associate your Microsoft account.
- Authenticate with the original personal Microsoft account used for the 2016 developer registration.
- Sign out completely, then sign back in using that MSA.
Microsoft documents this association flow as the prerequisite for configuring payout details. An MSA already associated with another Partner Center account cannot be associated again.^1^
Also test every Microsoft account historically used for the publisher in a separate private session. Do not rely only on Partner Center’s account picker: it displays accounts already available to the current sign-in context.^2^
Determine whether the publisher context is restored
After signing in with the associated MSA:
- Go to Settings → Account settings → Organization profile → Legal info → Developer.
- Confirm that the old Seller ID, User ID, or Publisher ID is displayed.
- Open Payout and tax → Payout and tax profile assignment.
Partner Center stores developer identifiers under the Developer profile, while access to particular settings depends on account enrollment and permissions.^3^
If the developer identity is visible but Payout and tax is not, this is a permissions issue: the tax profile requires Owner or Financial Contributor access. An existing owner must grant that role.^4^
Once access is restored:
- Select the relevant program and Seller ID.
- Create and submit the tax profile first.
- After submission, create and assign the payout profile.
- Allow up to 48 hours for validation.
Paid/transactable submissions require validated tax and payout profiles; free submissions do not.^5^
If association is unavailable or fails
Since the dedicated MSA Engage Center route already denies access, use the documented Partner Center ticket route that does not require signing in:
https://partner.microsoft.com/support?stage=2&topicid=6b52f3cf-3b36-df07-f75b-27aa68bf8a01
That route is documented for sign-in and account-access problems and is the appropriate fallback when the normal authenticated support path is inaccessible.^6^
In the case, include:
- “Legacy Windows Developer account created in 2016”
- Original MSA alias, but not its password
- Publisher display name and any visible Seller/Publisher ID
- Exact error: “No partner account is linked to your sign-in.”
- Free submissions work; paid submissions are blocked
- Tax and payout settings are inaccessible
- The MSA Engage Center support link returns access denied
- Whether Associate your Microsoft account was absent, failed, or said the MSA was already associated
- Screenshots and UTC timestamps
- Request: Investigate the legacy Store publisher-to-MSA association and restore or re-associate it so the Owner can configure tax and payout profiles
Support-form category names can vary; select the closest options for Partner Center account access, developer account management, or payout and tax. Do not create a second developer account as a workaround, because that would not repair the existing publisher identity or its apps.
References
- Manage your Microsoft Marketplace account in Partner Center
- Switch accounts in Partner Center
- Partner Center Account Setup - Partner Center | Microsoft Learn
- Set up Microsoft Marketplace payout and tax profiles
- Manage a Microsoft Marketplace account in Partner Center
- Troubleshoot sign-in issues and account access problems