Stuck for 2+ months: Account verification loop with null data corruption, support unresponsive (TrackingID#2609180060002858)

A Microsoft Q&A moderator cannot inspect or repair Partner Center backend records, so the supported next step is to update the existing Partner Center case with reproducible diagnostics and an explicit request for escalation to the account-verification team rather than opening duplicate cases.

Update the existing case with escalation evidence

1. Sign in to Partner Center with the work account that opened the request.
2. Select Help (?) → View my support requests, then open the existing request. Partner Center documents this as the location for tracking open and closed Marketplace support cases.^1^
3. Add a concise escalation note containing:
   • Registration date and elapsed time.
   • Current account type and verification status shown in Partner Center.
   • Dates of the latest substantive response and subsequent template replies.
   • The expected state: organization/company account.
   • The actual state: individual account and any fields visibly displayed as blank or null.
   • Business impact: Store submission/deployment blocked.
   • Explicit request: “Please escalate this case to the Partner Center account-verification/vetting team to review and correct the account-type and verification records.”
4. Attach screenshots of:
   • Settings → Account settings → Organization profile → Legal profile → Developer.
   • The verification loop and any visible blank/null values.
   • Verification Summary, including its status and available buttons.

The Developer tab is the documented place to see the account type, verification status, Seller ID, and verification steps. Publisher identifiers are assigned by Microsoft and cannot be edited there.^2^

Do not describe “database corruption” as confirmed unless support has explicitly established it. Report the observable values and ask engineering to determine the backend cause.

Attach diagnostics to the same case

If Partner Center displays Collect more information when the problem occurs:

1. Select it and save the generated diagnostics report.
2. Review the file and remove unnecessary personal or sensitive information.
3. Attach it to the existing support request.

If that prompt is unavailable, capture a HAR file:

1. Open Edge or Chrome DevTools with Ctrl+Shift+I.
2. Select Network, clear existing entries, and start recording.
3. Reproduce the account-type or verification-loop problem.
4. Stop recording and select Export HAR.
5. Review the HAR because it can contain sensitive account data, then attach it to the existing case.

Microsoft specifically supports adding diagnostic reports and HAR files to an existing ticket.^3^

Use the verification appeal only if Partner Center offers it

Check Settings → Account settings → Legal info → Verification Summary. This is the authoritative location for verification status and required actions.^4^

If the page displays Resolve or User Action Needed:

1. Select that button.
2. Upload official documents whose legal name, address, and domain exactly match the Partner Center record.
3. In the comments, state that the organization is incorrectly represented as an individual and reference the existing support request.
4. Submit the appeal and monitor Legal info.

The appeal must be submitted by a Global Admin, Compliance Admin, Account Admin, or a Developer-program Manager/Owner, and no more than three appeals can be submitted.^4^

If neither button appears, an appeal is not currently available; document that absence in the existing case rather than repeatedly resubmitting verification.

If the case cannot be updated

Use Partner Center’s AI assistant → Contact Support, or Help (?) → Contact Support where the assistant is unavailable. Enter the existing case reference prominently and request continuation/escalation rather than creating an unrelated investigation. Microsoft warns that requests created by other Partner Center users can delay resolution and cause confusion.^5^

Q&A has examples where Microsoft’s validation team ultimately completed stuck identity validations, but those cases do not document a public self-service backend repair or guarantee that posting identifiers will trigger escalation.^6^

Avoid publishing Seller IDs, tenant details, diagnostic files, or full support correspondence in a public Q&A thread.

References

1. Support for Microsoft Marketplace program in Partner Center
2. Manage a Microsoft Marketplace account in Partner Center
3. Send diagnostics to Microsoft
4. Submit a verification appeal in Partner Center
5. Get help and contact support in Partner Center
6. Organization Identity Validation Stuck in 'In Progress' since 10 days - Microsoft Q&A