A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing organization validation: Android Face Check UNEXPECTED_CLIENT_ERROR after Verified ID issuance
Hello Microsoft Artifact Signing / Verified ID team,
We need help completing the representative identity step for Public organization validation in Artifact Signing.
On an Android phone, the initial government-ID photo and selfie verification/match completed successfully and a Verified ID was created in Microsoft Authenticator. When we return to Microsoft's verification page, scan its QR code, select/present the existing Verified ID, and perform the subsequent Face Check, it repeatedly fails with:
face check failed
reason=UNKNOWN_FUTURE_VALUE
LivenessError=UNEXPECTED_CLIENT_ERROR
recognitionError=NONE
The Azure validation request is in Action Required. The relevant Artifact Signing Owner / Identity Verifier roles are assigned. We have preserved the current request and Verified ID rather than repeatedly deleting and recreating them. The failure is in this later presentation/liveness step. The error text alone does not establish the root cause.
Could the responsible team investigate this exact Android client/liveness error and advise a supported way to resume the existing request? If recreation is required, please confirm the correct recovery procedure and whether manual review or another supported verification route is available.
Please provide a private Microsoft support channel for any incident/correlation ID or account-specific diagnostics. No government-ID images, selfies, addresses, email addresses, tenant/subscription/validation identifiers, or verification links/tokens are included here.
This blocks company code signing for our release. Other development and testing continue. We are requesting technical recovery guidance, not expedited identity validation.
Thank you.