Partner Center Onboarding Blocked: API Error 500, 401 (Identity) & Feature Disabled

Question

Hello,

I am trying to register for a new Individual Developer Account in the Partner Center, but backend errors are completely preventing me from completing the onboarding process.

The UI freezes without showing explicit error messages, but the browser's developer console reveals several critical backend failures even when using a clean Incognito session without ad-blockers:

1. Cannot save progress: > [OnboardingDraft] Draft save returned non-success: Feature disabled (accountType: individual).

2. Address validation crash: Failed to load resource: the server responded with a status of 500 (Internal Server Error) at the endpoint /api/onboarding/validate-address.

3. Identity Verification (Au10tix) failure: Error validating token: 401 (Unauthorized) stating token has been redeemed. This prevents the camera from opening entirely. (Request ID: 9D69A023B8254F769D459C2C6820D200).

Troubleshooting steps already taken:

Used Incognito mode.

Disabled all extensions/ad-blockers.

Used standard, non-special characters for the address.

Since these are backend errors (500/401), I cannot proceed. Could a support engineer please look into my account or reset the onboarding flow from the database? Thank you.

Answer 1

The behavior described indicates backend and authentication issues on the Partner Center side that cannot be fixed client-side. The appropriate next step is to open a Partner Center support request so engineering can investigate the specific tenant/account and reset or repair the onboarding state if needed.

For Partner Center and Cloud Partner Portal–related API/authentication problems, the documented guidance is:

1. For persistent 401/403/500 errors that block normal flows, collect:
   • Correlation/Request IDs (such as 9D69A023B8254F769D459C2C6820D200).
   • Timestamps, affected endpoints (for example /api/onboarding/validate-address), and HTTP status codes (401, 500).
   • Screenshots or console logs showing messages like Feature disabled and token has been redeemed.
2. Open a Partner Center support ticket so the service team can:
   • Check whether any onboarding or feature flags for the account type (Individual Developer Account) are incorrectly disabled.
   • Inspect backend logs for the 500 errors on validate-address and the 401 identity-token failures.
   • Reset or clear the onboarding draft/identity-verification state in the backend if it is stuck.
   Use the Partner Center support channel described in the Partner Center documentation (for example, the “schedule support appointment” flow) and include all of the above technical details in the case description.
3. While waiting for support, avoid repeatedly restarting the identity verification flow, because the token has been redeemed message indicates a one-time token that may already be consumed; repeated attempts will continue to fail until support refreshes or reissues the token.

Because the errors are 500 (Internal Server Error), 401 (Unauthorized for identity), and Feature disabled on draft save, resolution requires direct intervention by Microsoft support on the tenant/account; there is no documented client-side or configuration workaround for these backend failures.

---

References:

• Partner Center REST error codes
• Troubleshooting common authentication errors
• How to Troubleshoot Common Issues
• WNS OAuth token request returns “invalid_client_id” for Package SID provisioned via Partner Center - Microsoft Q&A