Authenticator Sharing Verified ID on Identity Pass fails

Error code 500 indicates an internal server error on the verifier (Identity Pass) side, not a problem with the Verified ID stored in Microsoft Authenticator.

From the Verified ID and Authenticator perspective, only a few conditions on the wallet side can block a presentation:

1. The requested credential doesn’t exist in Authenticator.
   • In this case Authenticator shows a message that the requested credential is not available.
2. The requested credential is expired.
   • Authenticator shows that the credential is expired and it cannot be shared.
3. The QR code / presentation request is malformed or no longer valid.
   • The verifier’s service typically returns an error (often surfaced as a 500) when trying to process the presentation.

Given that the first request already expired and a new attempt now fails with a 500, the most likely causes are:

• The new presentation request generated by Identity Pass is invalid or the backend is failing while processing it.
• There is a transient service issue on the verifier’s side.

Recommended steps:

1. Confirm the credential in Authenticator
   • Open Microsoft Authenticator.
   • Go to Verified IDs.
   • Check that the relevant Verified ID is present and not marked as expired. If it is expired or missing, it must be re‑issued before it can be presented again.
2. Retry with a fresh QR code
   • In the Identity Pass flow, start a completely new verification and generate a new QR code.
   • In Authenticator, use Verified IDs → QR code icon to scan the new code and select Share when prompted.
3. If the credential is expired or deleted
   • If the credential was deleted from Authenticator, it must be issued again; deletion is irreversible and there is no recycle bin.
4. If the 500 error persists
   • Because 500 is an internal server error, it must be investigated by the Identity Pass / verifier operator or Microsoft support backing that service.
   • Provide them with the timestamp, Request-ID, and CorrelationId shown in the error so they can locate the failing request in their logs.

For Partner Center / Identity Pass scenarios that rely on a VC from a trusted ID verification vendor (such as AU10TIX), if issuance or presentation repeatedly fails, the supported path is to contact Partner Center support so they can review the verification and VC status and, if needed, help re‑issue the credential.

References:

• Use the Microsoft Authenticator with Verified ID
• Get verified credentials from a trusted ID verification vendor
• Frequently asked questions (FAQ)
• Microsoft Authenticator FAQs