A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Pause additional validation attempts and ask Azure Support to route the existing case—or a follow-up case referencing it—to the Artifact Signing identity-validation team for backend review.
What to request
If the existing support case can be reopened, add the request there. Otherwise, create a new Azure Support request and reference:
- The previous support case.
- All five validation IDs already listed in this Q&A post.
- The earlier Microsoft Q&A question.
- The approximate submission and failure times for each attempt.
- The fact that each request changed from In Progress to Failed within 15–60 minutes.
- The fact that no verification or Action Required email arrived.
- The checks already completed: exact registered legal name/address, active good-standing status, company-domain mailboxes, paid subscription, and Identity Verifier role.
Suggested wording:
Please route this case to the Artifact Signing identity-validation team or the appropriate backend team. Five Public Organization validation requests failed within 15–60 minutes without an Action Required state, verification email, or portal explanation.
Please correlate the five validation IDs supplied in the case and advise what actionable correction is required before another submission. Specifically, please determine whether the failures relate to organization-record matching, business-identifier matching, email/domain validation, individual representative validation, an attempt limit, or backend state requiring service-side review.
If the precise internal signal cannot be disclosed, please provide the corrective requirement or final onboarding determination that can be shared. Please also confirm whether another request should be submitted or whether support must address the current backend state first.
Do not send subscription details or documents in the public thread. Provide them only through the authenticated support case or another Microsoft-approved secure upload method.
What a Q&A moderator can do
A Microsoft Q&A moderator may be able to forward the validation IDs to the appropriate team; similar Artifact Signing cases were resolved after moderators or support engaged an internal validation team.^1^ ^2^
However, a public Q&A response is not a secure support channel, and a moderator cannot be expected to publish backend fraud, risk, or compliance signals. The response may therefore contain only a required correction, a request for additional evidence, or a final determination—not necessarily the exact internal rule that triggered the failure.
Why another submission should wait
The documented workflow sends the primary contact an email when individual verification or additional documents are required and changes the request to Action Required. A completed unsuccessful process changes to Failed.^3^
The FAQ separately says:
- If no email can be found, another request can normally be created.
- Additional requests do not help when a request for the same entity is still in progress.
- A non-email-related failure means the validation team could not make a determination from the supplied information.
- The three-attempt restriction applies specifically when extra documents were requested and all three attempts were exhausted.^4^
Because there have already been five rapid failures, creating a sixth request could reproduce the same result. Wait until support confirms whether a specific correction, a fresh request, or backend action is appropriate. The documented three-attempt rule should not be assumed here unless extra documents were actually requested.
References