Artifact Signing identity verification failing at the "Share with Artifact Signing" step in Authenticator

Dave 211 Reputation points
2026-08-31T04:54:47.6+00:00

I have set up a Verified ID with AU10TIX and the Microsoft Authenticator app. Twice now, I have tried to get past the "Share with Artifact Signing" step in Microsoft Authenticator. Both times, the Authenticator app returned a socket error, even though the website says "Verification successful!" The Identity validation in Azure remains in "Action Required" status. If I select the Retry option in the Authenticator app, I get an exception message about a Cosmos DB ID conflict. If I select the "Please complete your verification here" link in Azure, I get "Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request."

So I'm stuck in a perpetual cycle of Identity validation exceptions.

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

  1. AI answer

    2026-08-31T04:55:02.0666667+00:00

    For this Artifact Signing identity validation state, the supported recovery path is to restart the identity validation request rather than trying to reuse the existing link.

    1. In Azure portal, open the Artifact Signing account and go to Identity validations.
    2. Delete the current identity validation request.
    3. In Microsoft Authenticator, remove the associated Verified ID.
    4. Create a new identity validation request.
    5. Complete the verification flow again, making sure:
      • the email address entered in the request is the same email address used to sign in to access the validation link
      • the mailbox can receive messages and links from external senders
      • the email address is not a distribution list
      • Microsoft Authenticator is updated to the latest version
      • all open instances of Authenticator are closed before relaunching
      • browser cache is cleared or a different browser is used
      • no weak Wi‑Fi, VPN, or proxy is used during the flow
      • if possible, a different phone is tried

    Important supported behaviors for the symptoms described:

    • If the validation link has already been used or expired, a new link cannot be resent on the same request.
    • If email validation failed or the link cannot be used, a new identity validation request must be created.
    • Creating multiple requests for the same entity while one is already in progress does not help.

    If the new request still gets stuck in Action Required after the browser shows Verification Successful, use the supported escalation path for Artifact Signing identity validation assistance through Azure Support or Microsoft Q&A with the artifact-signing tag.

    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.