Artifact Signing Verified ID presentation fails with 404 "requestId not found"

Freddie Collins 0 Reputation points
2026-10-05T17:22:24.4933333+00:00

I am completing an Organization identity validation for Azure Artifact Signing.

The trusted ID verifier / AU10TIX step completes successfully and the Verified ID is issued in Microsoft Authenticator.

However, when I scan a newly generated QR code to present the Verified ID back to Artifact Signing, Authenticator immediately fails with HTTP 404:

Request with requestId '...' not found.

The QR code is fresh — the presentation request was scanned and failed within approximately 2 seconds. Repeating the process with a newly generated QR produces the same issue.

The Artifact Signing identity validation therefore remains at Action Required.

Is this a known Artifact Signing / Verified ID issue, and can the presentation request be reset or repaired without repeating the successful identity-verification process?

Artifact Signing
Artifact Signing

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

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Zoha Fatima 510 Reputation points
    2026-10-05T18:16:30.86+00:00

    Hi Freddie,

    Since AU10TIX completed successfully and the Verified ID was issued, but a newly generated presentation QR fails immediately with “requestId not found,” this appears to be occurring during the Microsoft Verified ID/Artifact Signing presentation stage rather than during the AU10TIX identity check. Similar 404 presentation failures have also been reported by other Artifact Signing users.

    I would not repeatedly recreate the identity validation yet. Microsoft’s Artifact Signing guidance specifically says that creating additional validation requests for the same entity while one is in progress does not help.

    Please open an Azure Support request for Artifact Signing and provide the identity validation ID, approximate failure time, screenshot of the 404, and Authenticator diagnostic details. Support can determine whether the existing presentation request requires backend intervention or whether the validation must be recreated.

    Do not post the requestId, subscription ID, identity documents, or other validation details publicly.

    Thank you, and feel free to respond back for more assistance.

    Was this answer helpful?

    0 comments

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.