AU10TIX Verified ID failed during Azure Artifact Signing organization validation

Question

AU10TIX Verified ID failed during Azure Artifact Signing organization validation

Luca King 5

I am completing an Azure Artifact Signing Public Trust organization identity validation. The organization validation request routed the human representative through AU10TIX / Verified ID for personal identity proofing. The AU10TIX flow ended with this message: > Sorry, you do not meet requirements to create a Verified ID at this time. No specific reason, error code, or corrective action was shown. This is an organization validation, not an individual validation, and the personal identity proofing step appears to have failed before any business-document request or Action Required guidance was provided. Questions: - Is this a known failure mode for Artifact Signing organization validations routed through AU10TIX? - Should the existing validation be reset/reopened by Microsoft support, or should a new validation be created? - What information can be safely provided through a private support channel so Microsoft can investigate without posting subscription IDs, tenant IDs, validation IDs, email addresses, or identity documents publicly? - Can support confirm whether representative name matching, email format, document processing, or selfie/liveness processing is the likely area to check? I can provide the private identifiers, approximate failure time, and screenshot through a secure Microsoft support channel if needed.

Goutam Pratti 6,300 Reputation points Microsoft External Staff Moderator

2026-08-18T17:48:28.5633333+00:00
Hi @Luca King ,

Thank you for providing the details regarding the issue encountered during the Azure Artifact Signing Organization Identity Validation process.

Based on our review, the message below is a known scenario that has been reported by multiple customers during the AU10TIX / Microsoft Verified ID identity proofing step:

"Sorry, you do not meet requirements to create a Verified ID at this time."

Unfortunately, this message does not provide a specific error code or indicate the underlying cause of the failure. Similar cases have been observed during both Organization and Individual Artifact Signing identity validations.

At this time, Microsoft documentation does not provide a self-service method to determine whether the failure is related to representative name matching, identity document validation, email verification, face comparison, liveness verification, or another eligibility check. These details can only be reviewed internally by the Artifact Signing identity validation team.

Regarding next steps:

We do not recommend creating duplicate identity validation requests while an existing request is still in progress, as Microsoft documentation indicates that doing so does not help expedite the validation process.

If the original email verification link was missed or expired (links expire after seven days), a new identity validation request may be required.

Additionally, one customer reported success after retrying the verification process from a smartphone using a private/incognito browser session, although this is not an officially documented workaround. [learn.microsoft.com]

1 answer

Your answer

Goutam Pratti 6,300 Reputation points Microsoft External Staff Moderator

2026-08-18T17:48:28.5633333+00:00

Hi @Luca King ,

Thank you for providing the details regarding the issue encountered during the Azure Artifact Signing Organization Identity Validation process.

Based on our review, the message below is a known scenario that has been reported by multiple customers during the AU10TIX / Microsoft Verified ID identity proofing step:

"Sorry, you do not meet requirements to create a Verified ID at this time."

Unfortunately, this message does not provide a specific error code or indicate the underlying cause of the failure. Similar cases have been observed during both Organization and Individual Artifact Signing identity validations.

At this time, Microsoft documentation does not provide a self-service method to determine whether the failure is related to representative name matching, identity document validation, email verification, face comparison, liveness verification, or another eligibility check. These details can only be reviewed internally by the Artifact Signing identity validation team.

Regarding next steps:

We do not recommend creating duplicate identity validation requests while an existing request is still in progress, as Microsoft documentation indicates that doing so does not help expedite the validation process.

If the original email verification link was missed or expired (links expire after seven days), a new identity validation request may be required.

Additionally, one customer reported success after retrying the verification process from a smartphone using a private/incognito browser session, although this is not an officially documented workaround. [learn.microsoft.com]

Answer 1

Yes. In Artifact Signing organization identity validation, the representative is required to complete individual identity validation, and the link for that step is sent to the primary email address. After the organization request is created, the status can move to Action Required and the representative must follow the individual identity validation steps. If that individual step completes successfully, the status returns to In Progress and the organization validation continues.

For the current request, the documented self-service path is:

In Azure portal, open the Artifact Signing account.
Go to Objects > Identity validations.
Check the current request status.
- Action Required means follow the requested next step.
- In Progress means validation is still being processed.
- Failed means the request did not complete.
Check the primary email account, including Junk or Spam.
Confirm the primary email can receive messages from external senders and that messages containing links are not filtered.
If email verification was missed or the verification link expired after seven days, create a new identity validation request.

On reset or reopen: the available guidance does not describe a reset or reopen flow for a failed AU10TIX/Verified ID step. The documented guidance is to create a new identity validation request if the email verification link was missed or expired. If identity validation failed for another reason, the guidance is to contact Azure Support or Microsoft Q&A using the artifact-signing tag. Creating more in-progress requests for the same entity does not help, and requests cannot be expedited.

On what to share privately: the available guidance supports using Azure Support for investigation. It does not list a required data set for private submission, but it does state that if more documentation is required, that request is handled through the Azure portal, and status updates are sent by email. Sharing private identifiers, approximate failure time, and a screenshot through Azure Support is aligned with the documented support path.

On likely failure area: the available guidance does not provide a breakdown such as representative name matching, email format, document processing, or selfie/liveness processing. The documented causes that can be checked directly are:

missed or expired email verification link
inability of the primary email account to receive external messages with links
inability of the validation team to determine the request from the information provided
exhaustion of the three attempts when extra documents were requested

If the request is already Failed and the failure was not due to the seven-day email verification link, the next documented step is to open Azure Support or post on Microsoft Q&A with the artifact-signing tag.