Organization identity validation fails repeatedly at Verified ID Face Check ("accepted, then expired") - Artifact Signing

Question

Organization identity validation fails repeatedly at Verified ID Face Check ("accepted, then expired") - Artifact Signing

Streamline Software 0

I am setting up Azure Artifact Signing (Trusted Signing) for my company, an Irish registered business. The organization identity validation form is accepted and the certificate subject preview is correct, but the representative Verified ID check has now failed three times, each time ending the whole validation request as Failed.

The pattern each time: the AU10TIX government ID capture completes, the Verified ID credential is issued into Microsoft Authenticator, and the final Face Check appears to accept - then reports the session/credential has expired, and the validation request flips to Failed in the portal. The third attempt was completed immediately after the verification link arrived, in one uninterrupted sitting with good lighting, no VPN, and an up-to-date Authenticator, and still failed the same way.

Failed identity validation IDs: ab084224-df6c-4d2b-b123-d541... (plus the two earlier ones - I can supply full IDs) Artifact Signing account: streamline-software (North Europe)

Can someone check the failure reason on the backend? I need to know whether the reference photo from the ID document is the problem (should I redo with a passport?), or whether this is a session-expiry issue in the verification flow. My current code signing certificate expires 2026-09-20 so I would appreciate guidance on how to get a validation through before then.

0 comments

1 answer

Your answer

Answer 1

Backend failure reasons can’t be checked here, but the supported next steps are clear:

Do not keep creating overlapping in-progress requests for the same entity. That does not help, and requests can’t be expedited.
If the request is already Failed, create a new identity validation request.
For the new request, verify these inputs before submitting:
- The Primary Email is a monitored mailbox on a domain owned by the legal business entity.
- The mailbox can receive messages and links from external senders.
- The Secondary Email is different from the primary email, and for organizations its domain matches the primary email domain.
- All organization and representative details exactly match the legal and identity documents.
If the request reaches Action Required, complete the follow-up steps from the email promptly. The verification links expire after seven days.
If Face Check or individual verification continues to fail with address/name mismatch or FaceCheck-related errors, delete the existing identity validation request, remove the associated Verified ID from Microsoft Authenticator, then submit a new identity validation request and create a new Verified ID. Ensure all information is accurate and complete the verification in adequate lighting.
If more documents are requested, upload current documents in the Azure portal. Documents must be issued within the previous 12 months, and there are three attempts for documentation upload.
For direct assistance with identity validation, use Azure Support or Microsoft Q&A with the artifact-signing tag.

Relevant service behavior:

Identity validation is completed only in the Azure portal, not with Azure CLI.
Processing can take 1–20 business days.
If identity validation expires before renewal, certificate renewal stops and signing associated with those certificate profiles stops.
Renewal can start 60 days before expiration. If renewal through Renew shows validation errors, or the identity validation is already expired, create a new Identity Validation.

Because the repeated failure is happening after the Verified ID/Face Check stage, the only documented self-service remediation is to remove the associated Verified ID, submit a new identity validation, and recreate the Verified ID with exact matching information and good verification conditions.

References: