Artifact Signing identity sharing technical error, used verification link, then Failed

James Hamelton 0 Reputation points
2026-10-04T09:36:26.02+00:00

I submitted an organization Public Trust identity validation request. I completed government-ID and facial verification and clicked Share. During the sharing step, a technical error appeared. Reopening the verification link displayed “No Access — this link has been used already.”

Azure initially showed Action Required in the list and In Progress in the details. The request has now changed to Failed, with no failure reason visible in its details.

How can I confirm whether the shared verified identity was received, and recover or retry correctly? Should I submit a new identity validation request, or does this require the verification link/sharing flow to be reset? I do not have a paid Azure technical support plan.

Artifact Signing
Artifact Signing

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

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. kagiyama yutaka 5,575 Reputation points
    2026-10-04T13:22:56.8433333+00:00

    I think the used link does not prove whether the Verified ID presentation reached Artifact Signing. Since the request is already Failed, do not retry that link. Start a new identity validation request, and keep the failed validation ID and Share error details for support if it fails again.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-04T09:36:40.4833333+00:00

    For this scenario, the supported recovery path is to start a new identity validation request.

    What can be confirmed from the documented behavior:

    1. If the email validation link has expired or can no longer be used, a new link cannot be resent on the same request. A new identity validation request must be started.
    2. If individual identity validation shows technical errors with Microsoft Authenticator and Verified ID, the recommended troubleshooting is:
      • Close all open instances of Microsoft Authenticator and relaunch it.
      • Update Microsoft Authenticator to the latest version.
      • Clear browser cache or try a different browser.
      • Avoid weak Wi-Fi, VPN, or proxy connections.
      • Try a different device.
    3. If identity validation fails and the failure is related to the verification flow not completing successfully, the documented action is to delete the existing identity validation request and submit a new one.
    4. For Artifact Signing identity validation assistance without a paid support plan, the documented support options are Azure Support or Microsoft Q&A using the artifact-signing tag.

    Based on that, the practical recovery path is:

    1. Do not keep retrying the already-used verification link.
    2. Delete the failed identity validation request.
    3. Create a new organization identity validation request from the Artifact Signing account.
    4. When the flow reaches the individual verification/share step again, complete it after applying the technical mitigations above.
    5. Monitor the request status in the Azure portal. Documented statuses include In Progress, Action Required, Completed, and Failed.
    6. If the new request again fails or the sharing step again produces a technical error, raise the issue through Azure Support or Microsoft Q&A with the artifact-signing tag.

    The available documentation does not provide a way to confirm separately whether the shared verified identity was received after the link shows No Access. It also does not describe any self-service reset of the verification link or sharing flow for the same request. The documented recovery is to submit a new identity validation request rather than reset the existing one.

    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.