Artifact Signing organization validation failed after Verified ID sharing error

The failed request now requires the Artifact Signing validation team to inspect the backend record; the portal alone cannot determine whether the Verified ID presentation failed technically or was rejected for a data mismatch.

Request a private backend investigation

Keep the failed validation and existing Verified ID unchanged until the team reviews them. In your existing Microsoft Q&A post, ask a Microsoft moderator or support engineer to arrange a private exchange and have the validation team:

1. Confirm whether the Verified ID presentation reached the service at approximately 2026-11-12 19:00 UTC.
2. Correlate it with the failed identity-validation ID.
3. Determine whether the failure was:
   • a presentation/session processing error;
   • a first-name, last-name, organization, or other data mismatch;
   • a Face Check failure; or
   • an inability to validate the organization from the supplied information.
4. Confirm whether the failed record can be reconciled or whether it must be replaced.

Comparable cases where the portal displayed only Failed were resolved after the identity-validation ID and Artifact Signing account details were passed privately to the validation team for backend investigation.^1^ Another case was verified after the validation team examined the supplied request details.^2^

Provide through the private channel:

• Microsoft Authenticator incident ID;
• Artifact Signing identity-validation ID;
• subscription and Artifact Signing account details;
• the UTC timestamp;
• screenshots of the Authenticator sharing result, consumed-link message, and Azure status transitions;
• the validation-failure email.

Do not post account identifiers, diagnostic logs, identity documents, or unredacted screenshots publicly.

Microsoft Q&A is an officially documented support route for Artifact Signing identity validation. Azure technical support tickets otherwise require a qualifying support plan.^3^^4^ A community answer cannot itself guarantee or create a private case, but a Microsoft moderator can request private details and escalate a matching backend issue, as occurred in the cases above.

Do not reuse the consumed link

The existing link cannot be treated as a retry path. The documented validation sequence expects the status to return from Action Required to In Progress after successful individual verification, followed eventually by Completed or Failed.^5^

Because this request has reached Failed, wait for the backend determination before deleting it. Preserving it gives the team the record needed to correlate your Authenticator incident and presentation timestamp.

Recovery after Microsoft identifies the failure category

• Technical presentation/session failure: Create a new identity-validation request if the validation team confirms that the failed request cannot be reset or reconciled. An already-used link should not be reopened.
• Existing Verified ID remains valid and no mismatch was reported: The FAQ says to present the existing valid, unexpired Verified ID for Artifact Signing.^3^
• First/last-name mismatch or Face Check error: Delete the failed identity-validation request, remove the associated Verified ID from Authenticator, create a new request, and issue a new Verified ID. Enter the representative’s first and last names exactly as shown on the government-issued ID.^3^
• Organization-data correction required: Create a new request with corrected information; Artifact Signing does not support changing a public identity-validation request after creation.^5^
• Different primary email is needed while an organization validation already exists: Contact support rather than creating competing requests. The FAQ specifically requires support for that onboarding case.^3^

Do not create multiple simultaneous requests while awaiting review; Microsoft states that additional requests for the same entity while one is in progress do not help.^3^

References

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