Error in microsoft partner registration and DUNN address is already udpated

Question

Error in microsoft partner registration and DUNN address is already udpated

Romeo Antony 0

Microsoft runs on trust. We engage in a rigorous set of evaluation and certification processes; as a result your request was blocked.

## Questions for the community
1. Has anyone else experienced this cache-lag scenario after updating their D&B record? How long did it take for Microsoft's trust check to reflect the update?
2. Is there a Microsoft endpoint, queue, or refresh process that I can request to force a re-evaluation of the trust check against the now-updated D&B record?
3. Should I file a Microsoft Partner Center support ticket via the unauthenticated deep link (the one PrivatusBryan documented earlier this year) and what evidence should I attach for the fastest resolution?
4. For Australian Pty Ltd companies that pass ASIC + ABR verification cleanly, is there an alternative business-identity provider Microsoft uses besides D&B that I should also ensure is up to date?

0 comments

1 answer

Your answer

Answer 1

The context confirms that Microsoft uses external company databases such as Dun & Bradstreet (DUNS ID) as part of business verification, but it does not document specific cache-lag behavior or typical propagation times after a D&B update. It only states that verification usually completes in 3–5 business days and that inaccurate or mismatched profile data is a common cause of delays.
The context does not describe any public Microsoft endpoint, queue, or manual refresh mechanism to force re-evaluation of D&B data. The documented way to move verification forward is to:
- Ensure the Legal business profile company name and address exactly match official registration records and any external data source used (such as DUNS), and
- Upload additional proof documents through the interactive verification/vetting experience when requested.
The context does not mention an unauthenticated deep-link support path. It does state that if verification has not completed after five business days, or if verification is blocked/rejected, the next step is to contact support via standard Partner Center support channels and appeal, with the primary contact providing official documentation. Evidence that is explicitly called out as useful includes:
- Formation documents (articles of incorporation, partnership deed).
- Government-issued business registration or tax registration certificates.
- Franchise/agency appointment letters.
- Lease/tenancy documents.
- Letters or statements from a financial institution or utility company.
- Records from government registry websites (with the site/link visible in the document).
- Stock exchange filings or tax filing records.
- External company database records (such as Dun & Bradstreet / DUNS ID or state registry).
- Receipts from the company’s home country/region or municipality.
The primary contact can also appeal rejections directly from Partner Center under Account settings > Legal info, using the Fix now and appeal flow, and can do so up to three times.
The documented business-identity sources used by Microsoft for verification include:
- Official business registration and tax records.
- Government registry websites.
- External company databases such as Dun & Bradstreet (DUNS ID) or state registries.
The context does not list any additional, Australia-specific identity providers beyond these categories. For Australian Pty Ltd entities, the key requirement remains that the Legal business profile (name, address, registration ID) exactly matches the official registration records and any external data source used (for example, the DUNS record).

In all cases, if verification is blocked or delayed beyond five business days after correcting external data (such as D&B), the documented next step is to review and correct the Legal business profile and then contact Partner Center support, providing the strongest available official documentation and, where applicable, DUNS evidence.

References: