Artifact Signing: AU10TIX Verified ID failed after document and selfie submission

Request Microsoft-side investigation through Microsoft Q&A using the Artifact Signing tag, and provide the validation identifiers only after a Microsoft moderator opens a private-message conversation.

Supported recovery procedure

1. Keep the existing identity-validation request intact.
   Do not create duplicate requests while the current request remains in progress; Microsoft states that duplicates for the same entity do not help. Artifact Signing identity-validation assistance is available through either Azure Support or Microsoft Q&A with the Artifact Signing tag.^1^
2. Ask for escalation to the Artifact Signing identity-validation team.
   Add a comment to this Q&A thread requesting:
   • Investigation of the AU10TIX/Verified ID session.
   • Confirmation whether the existing session can be reopened or reset.
   • A private message for supplying the Identity Validation ID and account-specific details.
   Q&A users cannot perform the escalation themselves; escalation is a moderator operation.^2^
3. Provide only non-sensitive diagnostic facts publicly:
   • Validation type: Organization/Public Trust.
   • Exact message: “Sorry, you do not meet requirements to create a Verified ID at this time.”
   • Approximate failure date/time and time zone.
   • Confirmation that email verification succeeded.
   • Confirmation that document capture and selfie submission completed before the message appeared.
   • Device OS, Microsoft Authenticator version, and whether a VPN/proxy was used.
   • Confirmation that AU10TIX redirected support responsibility to Microsoft.
   • Whether any previous validation request or Verified ID exists.
4. Wait for a Microsoft moderator to initiate private messaging.
   Private messages can be seen only by the question author and Microsoft moderators. They support attachments and may be used for subscription or tenant IDs, logs, traces, and support-ticket IDs. The conversation is deleted 30 days after the moderator’s first private message.^3^
5. Provide these items privately when requested:
   • Azure subscription ID.
   • Tenant ID, if requested.
   • Artifact Signing account name and resource group.
   • Identity Validation ID.
   • UTC timestamp of the failed attempt.
   • Screenshot containing the exact error, with unrelated personal information removed.
   • Microsoft Authenticator incident ID and logs, if requested.
   • Previous validation IDs or case numbers relevant to the same organization.
   Do not send document photographs, selfie/biometric images, QR codes, verification URLs, access tokens, passwords, or secrets unless an assigned Microsoft support engineer explicitly provides an approved secure collection method.

Can Microsoft review or reset it?

Microsoft can investigate the validation state and associated backend records. A closely related Artifact Signing case involving unexplained repeated failures was resolved after a support case was raised and the internal team reviewed the Identity Validation ID and account details.^4^

A reset is not guaranteed, and no public self-service “hard reset” is documented for this exact generic AU10TIX rejection. Microsoft must first determine whether the session can be reset, whether a new request is appropriate, or whether the validation decision is final.

The FAQ does prescribe deleting the validation request and removing its Verified ID when Azure specifically reports an address mismatch, name mismatch, or Face Check error.^1^ Because none of those specific errors was shown here, do not delete and recreate the request unless Microsoft directs it; deletion could discard the state needed for investigation.

If an Azure support request becomes available

With an eligible technical support plan, open the request from:

Azure portal → Artifact Signing account → Support + Troubleshooting → Create a support request

Creating technical support requests requires an eligible support plan and suitable subscription permissions, such as Owner, Contributor, or Support Request Contributor.^5^

A suitable escalation comment is:

Please escalate this Artifact Signing Organization/Public Trust identity-validation failure for Microsoft-side review. Email verification succeeded, but AU10TIX displayed “Sorry, you do not meet requirements to create a Verified ID at this time” after document and selfie submission. AU10TIX Support redirected the case to Microsoft. Please initiate a private message so the Identity Validation ID, Artifact Signing account details, timestamps, and screenshots can be supplied securely. Please confirm whether the existing verification session can be reviewed or reset before another validation request is created.

References

1. Artifact Signing FAQ
2. Escalate a question on Microsoft Q&A
3. Private messages on Microsoft Q&A
4. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
5. Create an Azure support request