A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
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.