Artifact Signing Individual Public identity validation stuck at Action Required after AU10TIX succeeds but Verified ID is not issued

jonathan franklin 0 Reputation points
2026-08-26T22:27:39.8266667+00:00

am setting up Microsoft Azure Artifact Signing using Individual Developer / Public identity validation in the United States.

The identity-validation request was created successfully and changed from In Progress to Action Required.

I then followed the Microsoft-documented verification flow:

Opened the existing Action Required validation.

Followed “Please complete your verification here.”

Signed in with the same Microsoft account used for the request.

Selected the trusted ID-verifier flow.

Completed the AU10TIX government-ID and face verification.

AU10TIX displayed: “Success! We’re ready to create your Verified ID. Open the Authenticator app to finalize the creation of the Verified ID.”

However, the Verified ID handoff did not complete.

Current state:

Azure Artifact Signing identity validation: Action Required

AU10TIX ID/face verification: reached the success screen

AU10TIX browser session subsequently displayed: “Oops! Something went wrong! Please contact your administrator.”

Microsoft Authenticator → Verified IDs contains no credential; it only offers “Scan a QR code”

No Government Issued ID / AU10TIX Verified ID was added to Authenticator

No certificate profile has been created

I have not deleted or recreated the existing validation

I have not retried the AU10TIX verification

Could Microsoft please advise how to repair or resume the existing Individual/Public identity validation so that the already-completed AU10TIX verification can issue/present the Verified ID?

If possible, I would specifically like to avoid repeating the government-ID and biometric verification unless Microsoft confirms that a new verification is required.

I can provide non-public identifiers privately to Microsoft support personnel if needed, but I do not want to post subscription IDs, validation IDs, tenant IDs, or identity information publicly.

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. AI answer

    2026-08-26T22:27:58.68+00:00

    For this Artifact Signing Individual/Public flow, there is no documented way to repair or resume a partially completed Verified ID handoff after AU10TIX succeeds but no Verified ID is added to Microsoft Authenticator. The supported guidance is:

    1. Try the documented technical troubleshooting first:
      1. Close all open instances of Microsoft Authenticator on the mobile device, then relaunch it.
      2. Make sure Microsoft Authenticator is updated to the latest Android/iOS version.
      3. Clear the browser cache, or retry in a different browser.
      4. Avoid weak Wi-Fi and do not use a VPN or proxy.
      5. If possible, try a different phone.
    2. If the issue was an email/account mismatch, verify that the email entered in the individual identity validation request is exactly the same email used to sign in to access the identity validation link. A mismatch causes permission/access problems.
    3. If the Verified ID still was not issued or presented, the documented recovery path for failed individual verification states to:
      • delete the existing identity validation request,
      • remove any associated Verified ID from Microsoft Authenticator if one exists,
      • submit a new identity validation request,
      • create a new Verified ID.
    4. Do not create multiple in-progress requests for the same entity to try to force progress. That does not help, and requests cannot be expedited.
    5. For assistance with Artifact Signing identity validation, use Azure Support or Microsoft Q&A with the artifact-signing tag.
    6. For issues specifically in the AU10TIX identity-verification experience, including problems completing the AU10TIX verification flow, contact AU10TIX Support directly.

    Relevant constraints from the documented flow:

    • Identity validation can only be completed in the Azure portal, not through Azure CLI.
    • For Individual/Public validation, the primary email entered in the request is the email used during the verification flow.
    • After successful completion, the Azure portal status should update from Action Required to Completed after a couple of minutes. Since the status remains Action Required and no Verified ID exists in Authenticator, the flow did not complete successfully.

    References:

    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.