Artifact Signing organization verification: Authenticator 500 "Unexpected session payload" persists after new request and Verified ID

We are completing Public Trust organization identity validation for Azure Artifact Signing.

During representative verification, the AU10TIX identity document flow completed far enough to issue a new Verified ID, which is visible in Microsoft Authenticator on an iPhone. We then scanned the QR code on credentials.microsoft.com and presented that newly issued Verified ID.

Microsoft Authenticator displayed:

Error code: 500

Error details: Unexpected session payload

At the same time, the browser displayed "Error: Face Check failed" and "Verification unsuccessful". We do not yet know whether facial matching itself failed or whether the failure occurred while processing the presentation/session response.

We have already deleted the previous failed identity validation request, submitted a replacement request, and created a new Verified ID, but the same error recurred. For the latest attempt, the Microsoft account used on the verification website matched the primary email address in the application.

Could the Artifact Signing / Verified ID team please investigate or advise on the supported recovery path? Specifically:

1. Is this a known session/presentation-processing issue?
2. Can the current verification session be reset or reissued without repeatedly deleting the application and recreating the Verified ID?
3. How can we privately provide the request ID, correlation ID, timestamp, validation ID, and relevant diagnostics if needed?

We have those error identifiers available, but are deliberately omitting company details, email addresses, identifiers, verification URLs/tokens, screenshots, and full logs from this public question. Please provide a private collection channel if required.