Azure Artifact Signing Verified ID Face Check fails at 75% after successful AU10TIX issuance

I am completing Public Organization identity validation for Azure Artifact Signing. The required individual identity-verification step is currently in “Action Required” status.

AU10TIX successfully completed the government-ID and selfie verification process and issued two Government Issued ID – GLOBAL credentials. Both credentials are stored successfully in the current Microsoft Authenticator app.

The reproducible failure occurs afterward, when presenting either existing credential to Artifact Signing:

I generate a new presentation QR code from the identity-validation request.

Microsoft Authenticator recognizes the credential and begins Face Check.

Face Check progresses normally to exactly 75%.

It then consistently returns “Something went wrong.”

This has occurred more than eight times across at least five newly generated QR presentation requests. Microsoft Authenticator is current, and the same phone and front-facing camera successfully completed the AU10TIX selfie process approximately one hour before these failures.

This is not an AU10TIX document-issuance, ID-image, lighting, camera-permission, QR-expiration, or Azure SDK logging problem. The Verified IDs were issued successfully, and the repeatable failure occurs during Microsoft’s subsequent Verified ID presentation/Face Check processing.

Please have an Azure Artifact Signing or Microsoft Entra Verified ID engineer inspect the server-side presentation and Face Check transaction logs. If private identifiers or logs are required, please escalate this to a private support case. I can provide the tenant ID, subscription ID, Artifact Signing account, identity-validation ID, timestamps, screenshots, device information, and Authenticator version privately. I will not publish those identifiers in this public Q&A post.