Azure Artifact Signing – AU10TIX Identity Verification Failed (Request for Manual Review)

Request backend investigation through Azure Support and provide the existing Identity Validation ID privately; a closely matched Artifact Signing case with an unexplained AU10TIX failure was resolved after support sent that ID and the relevant account details to the validation team, which completed the existing request successfully.^1^

Information to include in the support case

In Azure Portal, open Help + support → Create a support request, select the Artifact Signing resource where possible, and include:

• Existing Identity Validation ID
• Artifact Signing account and Azure subscription identifiers
• Microsoft Entra tenant ID
• Azure region and validation type, such as Organization/Public
• Approximate UTC date and time of the AU10TIX attempt
• Current portal status and the complete failure message
• Any correlation, incident, or request ID displayed
• Confirmation that both sides of the Korean driver’s license and the selfie were captured successfully
• Confirmation that the earlier permission problem is resolved
• A request to preserve and investigate the existing validation, rather than create another one

Do not post tenant, subscription, account, or identity-document details publicly in Q&A. Supply them only through the private channel opened by Microsoft support or a Microsoft moderator. Azure Support and Microsoft Q&A with the artifact-signing tag are the documented assistance channels.^2^

A concise escalation description would be:

Please escalate this existing Artifact Signing Identity Validation to the validation/vetting team for backend review. AU10TIX failed after successful capture of both sides of the government-issued ID and completion of the selfie. The portal does not provide a specific reason. Please identify the failed check and advise whether the existing request can be manually completed or moved to document review. Identity Validation ID and account details are available privately.

Manual review and the failure reason

There is no documented user-facing control for selecting manual identity verification or requesting document review. The normal workflow requests additional documents only when the validation team determines they are needed; the request then changes to Action Required and an email is sent.^3^

Therefore:

• Only the validation/support team can determine the specific backend reason.
• Additional-document review may be offered by that team, but it cannot be initiated directly in the portal.
• The old ID photo being responsible remains a hypothesis unless support confirms a Face Check failure.
• Creating parallel requests for the same entity while one remains in progress does not help, and validation cannot be expedited.^2^

If support confirms a Face Check failure

The documented self-service recovery for a confirmed Face Check error is to delete the existing identity-validation request, remove its associated Verified ID from Microsoft Authenticator, and submit a new request. During the new capture, use even moderate lighting, avoid backlighting and shadows, keep the face centered and unobstructed, and clean the camera lens.^2^

That procedure does not preserve the existing request, so it should be treated as a fallback only after the backend-review request has been answered. If Microsoft determines that the organization validation failed because the submitted information was insufficient—or confirms that all three requested-document attempts were exhausted—the FAQ states that onboarding cannot proceed through that request.^2^

References

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