API access and integration with Microsoft Partner Center for managing partner data
Enrollment blocked for weeks — Account A stuck on error 2100 (orphaned legal entity), Account B closed with "no appeals left" after name-format identity mismatch. Requesting manual engineering assistance to onboard.
1. Summary
I am trying to enroll my company in the Microsoft AI Cloud Partner Program (free tier) to obtain a PartnerID for publisher verification of our production Entra app registration. I have been blocked for several weeks across two accounts by two separate known issues:
• Account A (current, fresh): enrollment impossible due to error 2100 — a legal entity was created on first submit but never linked to any program enrollment; every retry attempts to re-create it and fails. Legal info is empty. Self-serve UI cannot complete.
• Account B (previous): identity verification failed due to a name-format mismatch with my UAE-issued ID (explained below — root cause now understood and corrected), and the application was closed with "no appeals available." The portal itself instructed me to create a fresh account, which is why Account A exists.
I am requesting manual assistance from the Partner Center team to link or clear the orphaned record on Account A so enrollment can complete. I have legal entity documentation and can complete identity verification immediately with a passport whose name matches the account exactly.
2. Business context / impact • Product: Clozo — a live, customer-facing B2B SaaS application. • Entra app registration: "Clozo", Application (client) ID 0954c9bd-da72-454d-be64-c08801ed4d85, tenant 79ba0cca-c63c-49ed-81a0-aa517d0fb228, multi-tenant.
• Publisher domain clozo.ai is live and serving the verification file at https://clozo.ai/.well-known/microsoft-identity-association.json.
• The only remaining step is publisher verification, which requires a vetted PartnerID. Every week of delay shows our customers an "unverified publisher" warning on the Microsoft consent screen.
- Account details
| Account A (current) | Account B (previous) | |
|---|---|---|
| Sign-up email | ******@outlook.com | ******@gmail.com |
| Entra identity | ******@Cl0z0fzellc.onmicrosoft.com (Its two zeros, not the alphabet O) | ******@clozofzellc.onmicrosoft.com |
| Status | Enrollment blocked by error 2100 | Application rejected due to identity verification failing and closed, "no appeals available |
4. Problem 1 — Account A: error 2100 (orphaned legal entity)
• On first enrollment, the legal-entity/billing-account submission appeared to succeed.
• Since then, every enrollment attempt fails on submit with:
Error code 2100 — "A legal entity matching the request payload already exists when creating the legal entity."
Source: PartnerAccountEnrollmentApi
• Current state: Account settings → Organization profile → Legal info is empty (the page itself says "If Legal info section is empty or has no call to action, retry enrollment"). Programs shows no enrolled programs. Retrying enrollment — including in a clean InPrivate session, and including selecting the existing entity when the flow offers it — still fails on submit with 2100, because the flow attempts to create the entity again instead of linking the existing one.
• This exactly matches the known issue described publicly here: https://learn.microsoft.com/en-us/answers/questions/5957727/ — a backend record mismatch requiring an engineer to link the existing legal entity to the enrollment, or remove the orphaned record.
• I also cannot open a support ticket from Partner Center on this account: the support form's Workspace dropdown returns no results because no programs are enrolled (same blocker as the thread above).
5. Problem 2 — Account B: identity verification failed, no appeals (root cause identified)
• Identity verification failed because of a name-format mismatch I did not understand at the time: • Entered on the form: First Name Sounak, Last Name Bhattacharya.
• Document used: UAE Resident Card (Emirates ID), which prints my name as **Sounak Bhattacharya Santanu Bhattacharya** — UAE IDs combine the holder's name with the father's name.
• I now hold the correct document for a clean match: my passport, which shows exactly Sounak Bhattacharya (Given Name Sounak, Surname Bhattacharya, no middle name) — matching the account name character-for-character.
• Account B's application is closed with "There are no appeals available," and the portal instructed me to create a fresh account — which I did (Account A).
6. What I am requesting
- On Account A (******@outlook.com): link the existing legal entity to my program enrollment, or clear the orphaned record so I can re-create it — whichever is faster. I can then complete enrollment and identity verification (with the passport) immediately.
- On Account B: no appeal is requested — but please confirm the closed application and its legal-entity record will not conflict with or flag Account A (same company), and close/merge any duplicate company record on your side if needed.
- If a manual verification path or a direct contact is required, please advise — I am happy to provide the trade license, passport, and domain-ownership proof to a human reviewer.