Artifact Signing: Identity Validation Failure After Verified ID Presentation — Need Explanation

S-9601 0 Reputation points
2026-11-10T16:29:44.6766667+00:00

Title: Artifact Signing (Trusted Signing): Verified ID issued, but presenting it fails with a network timeout in AuthenticatorProblem description

Organization identity validation in Artifact Signing (formerly Trusted Signing) fails at the last step: presenting the Verified ID. AU10TIX proofing succeeds and a Verified ID is issued to Microsoft Authenticator. Sharing that credential back to Artifact Signing then fails every time. The portal and the emails give no reason for the failure.EnvironmentProduct: Artifact Signing (Trusted Signing), Basic tier, East USScenario: organization identity validation (Public identity type), US-registered businessProofing: AU10TIX document and selfie check → Microsoft Entra Verified ID in Microsoft Authenticator (Android)Requester location: outside the USWhat I've already triedTwo proofing attempts with other ID documents did not issue a Verified ID ("Sorry, we can't verify").An attempt with a passport did issue a Verified ID, and Authenticator confirmed the live selfie matched the ID photo. Presenting it failed. Support suggested the cause was a personal email on the credential that didn't match the business email on the request.I followed support's guidance:deleted the old credential from Authenticatorstarted a new validation request with an individual business mailbox on the organization's own domainredid proofing using that mailbox onlya new Verified ID was issued with the business email.Presenting the new credential still fails. Authenticator shows:Oh no! Something went wrong! Unable to continue because of a technical problem with the request. Try again later. Error Details: LocalNetworkException: Failed to send request because of timeout SocketTimeoutException: timeout SocketTimeoutException: Read timed out Timestamp: Nov 10, 2026 1:38:11 PM GMT+02:00Screen recording of the failure: https://drive.google.com/file/d/1i2b0n1Il7lFqX-fn4WwMeeLHsbe9VNFx/view?usp=sharingThe support case only returns automated responses. Support had said that if the failure repeated with a matching business email, the cause would likely be a presentation or service issue rather than an email mismatch.Current status The validation request is in "Action Required". It has also asked for additional organization documents (a domain registration receipt), which I'm providing separately. The Verified ID presentation itself still can't complete.QuestionsIs this a known issue with the Verified ID presentation endpoint for Artifact Signing, for example for requesters connecting from outside the US or on mobile networks?Should I retry the presentation with the same credential, or does the request have to be reset first?Could a Microsoft moderator escalate this to the Artifact Signing team so they can check the service-side logs for this timestamp? I can share the validation request ID and support case number privately.

Artifact Signing
Artifact Signing

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

0 comments No 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.