Artifact Signing: Authenticator cannot find an existing AU10TIX Verified ID

Swarm Hosts 0 Reputation points
2026-10-09T23:40:39.7133333+00:00

Public Individual identity validation remains at Action Required.

On a Samsung Galaxy S23 Ultra (SM-S918U), Google Play offers only Open for Microsoft Authenticator, with no update offered. Microsoft Authenticator’s Verified IDs wallet contains “AU10TIX Government issued ID - Global.” Its details include populated document fields and a Face Photo. I scan the Microsoft verification QR using the scanner in that same Verified IDs wallet.

The sharing screen says “Share with Artifact Signing,” “Verifiable Credential Required / Verified ID not found,” and “Result of face check required by organization.” Next is disabled, and there is no action available to start the face check.

Fresh QR sessions using the existing identity request have the same result. Fully closing and reopening Authenticator, then scanning a fresh QR, also reproduces the same error. Switching the Android phone from Wi-Fi to mobile data also reproduces “required verified ID not found.” The desktop verification page shows “Processing...” after the scan. Earlier attempts also showed “unknown status code” immediately after scanning. The Microsoft verification page is signed in with the same email used for the identity request. Retrying the request in a separate desktop browser also did not resolve it.

What credential issuer/type or other requirements should be checked, and how can I complete verification without unnecessarily recreating the existing identity request or government ID credential?

Microsoft Authenticator feedback was submitted after reproducing the credential-not-found error. I can provide its reference privately to Microsoft support.

Please route this to the Artifact Signing / Verified ID team for investigation of the existing presentation request. Can the team determine whether the accepted issuer, credential type, expiry/revocation checks, or Face Check configuration is rejecting the populated AU10TIX credential, and provide a supported recovery path? We have not received a Verification Successful result and cannot create a Public Trust signing profile.

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-09T23:40:55.5666667+00:00

    The supported checks and recovery steps are:

    1. Verify the presentation flow is using the credential in Microsoft Authenticator, not the device camera alone. For Verified ID, scanning the QR code is intended to be done with Microsoft Authenticator. On Android, camera-app scanning can fail or open the wrong Authenticator instance if the phone has separate work and personal profiles.
    2. Confirm the credential actually matches the presentation request. If the presentation request doesn’t match any verifiable credential in Authenticator, Authenticator shows that the requested credential isn’t available. If the matching credential is expired, it also can’t be shared.
    3. The expected Artifact Signing flow for Individual identity validation is:
      • complete the trusted ID-verifier steps,
      • select Open Authenticator,
      • scan the browser QR code again,
      • select Add to add the verified ID to Microsoft Authenticator,
      • when the browser shows Present your Verified ID, scan that QR code,
      • select Verifiable Credential,
      • select Share,
      • wait for the browser to update to Verification Successful,
      • then allow a few minutes for Azure portal status to change to Completed.
    4. For technical errors during identity validation with Authenticator and Verified ID, use these supported troubleshooting steps:
      • Close all open instances of Microsoft Authenticator on the phone, then relaunch it.
      • Make sure the latest version of Microsoft Authenticator is installed.
      • Clear the web browser cache, or retry in a different browser.
      • Avoid weak internet connections and avoid VPN or proxy services.
      • Try a different mobile device, because device-specific settings or security policies can interfere.
    5. For the specific Artifact Signing identity-validation errors address does not match, first name last name not matched, or FaceCheck fail, the documented recovery is to delete the existing identity validation request, remove the associated Verified ID from Microsoft Authenticator, then submit a new identity validation request and create a new Verified ID. The guidance also says to ensure the information is accurate and the verification environment has adequate lighting.
    6. If the current request remains in Action Required and the credential still isn’t accepted, the documented path is to initiate a new identity validation request. A similar accepted resolution for a disabled delete/cancel scenario also states that a new identity validation request must be started.
    7. A Public Trust signing profile cannot be created until there is at least one completed identity validation request matching the certificate profile type.

    The context does not provide a supported way to inspect the backend presentation request for accepted issuer, credential type, revocation, expiry, or Face Check policy details for an existing request. The supported guidance in the available documentation is limited to the matching/expiry checks, the standard troubleshooting steps above, and recreating the identity validation request and Verified ID when FaceCheck or identity-match validation fails.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.