Artifact Signing
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Azure Artifact Signing identity validation fails after successful Face Check with HTTP 500 (facecheckSessionFailure: Unexpected session payload)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 92%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
Pranav Srihari
0
Reputation points
I am trying to complete Azure Artifact Signing organization identity validation for a paid Azure subscription.
The identity verification process reaches Microsoft Authenticator and AU10TIX successfully.
Environment
Azure Artifact Signing
Organization identity validation (Public)
Microsoft Authenticator (iOS)
Azure subscription: Pay-As-You-Go (Azure Plan)
Identity verification provider: AU10TIX
What happened
Created an Artifact Signing account.
Created an Organization Identity Validation.
Received the "Action Required" email.
Completed AU10TIX document verification.
Successfully received the Verified ID in Microsoft Authenticator.
Scanned the presentation QR code from the Artifact Signing verification page.
Completed the required Face Check successfully.
At this point, the verification fails.
The Authenticator logs show that Face Check completed successfully:
FaceCheckStatus=success
Immediately afterwards, the presentation request fails with an HTTP 500:
internalServerError claimValidationError facecheckSessionFailure Unexpected session payload
Relevant diagnostics:
Request-ID: 06dc34281c6fa5f4378a35d57a383549 MS-CV: SHUPNE/bRlCvQ9Boz+s2hA.3.7 Flow ID: 22F0A983-B76E-4D29-A6D7-2404F0DB45C2
The browser verification page eventually becomes unusable and reports:
No Access Sorry, this link has been used already.
The Azure portal now shows the Identity Validation status as:
Failed
Previous issue encountered
Earlier in the same validation I also encountered:
404 notFound Request with requestId 'e4a375ad-d59b-4567-975b-4612aec83c1c' not found which appeared to be an expired or invalid presentation request.
Question
Has anyone encountered this specific facecheckSessionFailure / Unexpected session payload error?
Is this a known Microsoft Entra Verified ID backend issue?
Can the failed identity validation be reset or repaired without deleting it and repeating the entire AU10TIX verification process?
This appears to be a server-side failure after Face Check completed successfully rather than an identity verification failure.
Artifact Signing
Sign in to answer