Artifact Signing individual validation blocked: Verified ID card missing after AU10TIX verification

Minitrike 0 Reputation points
2026-10-01T21:01:15.4+00:00

Hello Microsoft Support,

I am completing Public identity validation as an individual for Azure Artifact Signing. The request remains Action Required / In Progress.

AU10TIX shows "Session already verified", but no AU10TIX Verified ID card appears in Microsoft Authenticator. When attempting to share the credential with Artifact Signing, Authenticator shows "VerifiableCredential — Card missing" and the Next button is disabled.

The Open Authenticator/Add step was already attempted without producing a card. I contacted AU10TIX support. They replied that Microsoft manages the Verified ID platform and related services, and directed this platform-functionality issue to Microsoft.

Please help investigate the missing credential issuance/handoff to Authenticator and recover the existing validation flow. Please advise before any deletion or creation of a duplicate identity-validation request.

I can provide the validation request ID and the AU10TIX case reference through a private support channel. I will not post identity documents, verification URLs, tokens, or personal address details publicly.

Thank you.

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: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-01T21:01:32.1333333+00:00

    This issue matches the documented Artifact Signing + Verified ID technical-error path.

    1. Do not create duplicate in-progress identity validation requests. Creating more requests for the same entity while one is already in progress does not help, and requests cannot be expedited.
    2. Since the Open Authenticator/Add step was already attempted and the card is still missing, run the documented technical checks for Microsoft Authenticator and Verified ID:
      1. Fully close all open instances of Microsoft Authenticator on the mobile device, then reopen it.
      2. Update Microsoft Authenticator to the latest version on Android or iOS.
      3. Clear the browser cache used for the Verified ID flow, or retry with a different browser.
      4. Avoid weak Wi-Fi and do not use VPN or proxy during the handoff between browser and Authenticator.
      5. If possible, retry on a different phone because device-specific settings or security policies can interfere.
    3. For first-time use of Authenticator with Verified ID, the app must be initialized through its startup screens. In Authenticator: Accept the first screen, choose the app-usage-data option, then Skip the Sign in with Microsoft screen.
    4. In the normal Artifact Signing individual flow, after AU10TIX completes on the mobile device, the next steps are Open Authenticator, scan the browser QR code again, then select Add to add the Verified ID card. If that card is not present, the issuance/handoff did not complete successfully.
    5. If the problem persists after the above checks, use the documented Artifact Signing support channels for identity validation assistance: Azure Support or Microsoft Q&A with the artifact-signing tag.
    6. If Microsoft determines the existing flow cannot be recovered, the documented reset path for identity-validation mismatches or verification failures 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. This is a reset action and should be done only after support confirms it is necessary.

    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.