Other features or issues related to Microsoft Partner Center
Error 400 in this context indicates that the sign-in or account operation with a password could not be processed. It is typically caused by repeated sign-in attempts or an issue with the browser, device, or network.
To troubleshoot and work around Error 400 when converting the Microsoft account for Xbox developer use:
- Use a different sign-in method
- At the sign-in or verification prompt, select Other ways to sign in.
- If already configured on the account, choose one of:
- Use face, fingerprint, PIN, or security key
- Approve sign-in with Microsoft Authenticator (mobile app)
- Send a code to an alternate email address
- This can bypass the failing password-based request that is triggering Error 400.
- Try a different browser or app
- Completely close Chrome and sign out of all Microsoft accounts in the browser.
- Clear cookies and site data for Microsoft/Partner Center domains.
- Try again in a different browser (for example, Edge) or in a private/incognito window so no cached sign-in data is reused.
- Switch device
- Attempt the Partner Center / Xbox developer enrollment from another PC or mobile device to rule out a device-specific issue.
- Change network
- If currently on Wi‑Fi, switch to mobile hotspot or a different network.
- If on mobile data, try a trusted Wi‑Fi network.
- This addresses cases where the current network path is interfering with the sign-in request.
- If Error 400 persists
- Because the error is occurring at ~90% of the enrollment flow and across multiple accounts, it is likely a transient service or configuration issue on the backend rather than the age of the account.
- After trying the above, wait some time and retry the enrollment. If it still fails, collect screenshots and timestamps of the Error 400 and open a support case via Partner Center so the backend sign-up flow for the account can be checked.
References: