Azure Artifact Signing organization identity validation failed after successful AU10TIX verification

Open an Azure Support case for backend review of the existing Identity Validation ID rather than immediately creating another request; closely matching cases with successful identity checks followed by an unexplained Failed status were resolved only after the Artifact Signing validation team examined the request. ^1^

What the AU10TIX result means

“Verification successful” confirms completion of the individual representative’s identity-verification step. It does not mean that the complete organization Public Trust review passed.

After individual verification succeeds, Artifact Signing returns the request to In Progress while organization validation continues. Microsoft may then request documents through email and change the status to Action Required; the terminal status becomes either Completed or Failed. ^2^

Consequently, the portal status does not establish whether the failure involved:

• Processing of the AU10TIX result;
• The organization’s public records or submitted business details;
• The applicant’s association with the organization; or
• Another validation-side condition.

Microsoft’s FAQ states that, when the failure was not caused by a missed email-verification link, the validation team could not make a determination from the information supplied. ^3^

Information to include in the support request

In the Azure portal, open Help + support → Create a support request and provide:

1. The Identity Validation ID.
2. Azure subscription ID, resource group, Artifact Signing account name, and East US region.
3. Organization name: DEEPATHOLOGY LTD.
4. The primary email domain used by the request.
5. Approximate UTC timestamps for:
   • Submission;
   • AU10TIX completion;
   • The change from In Progress to Failed.
6. A screenshot of “Verification successful” and the failed portal status.
7. Any correlation or activity IDs shown in the portal.
8. A request for the validation team to confirm that the AU10TIX result was associated with this Identity Validation ID and to review whether the existing request can be corrected or completed.

Azure Support and Microsoft Q&A under the Artifact Signing tag are the documented assistance channels. The FAQ also warns that creating additional requests for the same entity while one is being handled does not help. ^3^

There is no documented customer-facing portal field or command that independently confirms receipt of the AU10TIX payload. Identity validation itself can be completed only through the Azure portal, not Azure CLI, so backend confirmation must come from support. ^2^

Existing request versus a new request

Do not delete or resubmit until support reviews the existing validation:

• Matching unexplained-failure cases have been passed after the internal validation team reviewed the Identity Validation ID and account details. ^1^ ^4^
• If Microsoft identifies incorrect organization information that must be changed, the quickstart says changes require a new identity validation request. ^2^
• If another request must use a different primary email address while an identity validation already exists, contact support to continue onboarding. ^3^

Additional documents

Do not upload unsolicited documents unless the request or support team asks for them. If additional evidence is requested, provide current official records that establish both:

• The legal existence and registered details of DEEPATHOLOGY LTD; and
• The representative’s authority or association with the company.

A similar documented case required official business documents establishing the applicant’s connection to the organization, dated within the preceding 12 months. ^5^ Ensure the legal company name, business identifier, address, website, representative name, and organization-domain email match current authoritative records.

Israel eligibility

Public Trust Artifact Signing is supported for organizations in Israel. East US is also a supported Artifact Signing resource region. Therefore, the stated country and selected Azure region are not documented eligibility blockers. ^2^

References

1. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
2. Quickstart: Set up Artifact Signing
3. Artifact Signing FAQ
4. Artifact Signing Account Organization Identity validations failed - Microsoft Q&A
5. Identity validation failed - Microsoft Q&A