Azure Artifact Signing individual identity validation stuck in "Action Required" after AU10TIX verification

nilson huamanta gonzales 0 Reputation points
2026-11-01T01:14:39.1533333+00:00

Hello Microsoft Azure Support and Community,

I am experiencing an issue with individual identity validation for Azure Artifact Signing.

I created an Artifact Signing account using the Basic tier and submitted a Public Individual identity validation request.

I followed the Microsoft Verified ID process and was redirected to AU10TIX for identity verification. During the process, I completed the requested passport, facial verification, and email verification steps.

However, the process did not finish successfully. AU10TIX displayed the following error:

"Oops! Something went wrong! Please contact your administrator."

My identity validation request in the Azure portal still shows "Action Required."

I have already tried returning to the Microsoft Verified ID page and using Microsoft Authenticator, but I have not been able to complete the process.

Could you please advise:

How can I determine whether my verification results were received?

Is there an official way to resume or recover the existing identity validation request without repeating the entire process?

Which Microsoft or AU10TIX support channel can investigate this verification issue without requiring a separate paid technical support plan?

I would appreciate guidance on the appropriate next steps.

Thank you.

Artifact Signing
Artifact Signing

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


1 answer

Sort by: Newest
  1. AI answer

    2026-11-01T01:16:23.27+00:00

    Fully close and update Microsoft Authenticator, clear the browser session, disable any VPN or proxy, and reopen the existing verification link before deleting or recreating the identity-validation request.

    Recover the existing request

    Since simply returning to Verified ID and Authenticator did not complete the flow, perform these specific technical-error checks:

    1. Fully close every Microsoft Authenticator instance on the phone, then install its latest Android or iOS update.
    2. Clear the browser cache, or use a different supported browser.
    3. Use a stable connection without a VPN or proxy.
    4. If possible, try another phone or device.
    5. In the Azure portal, open: Artifact Signing account → Objects → Identity validations → your name → “Please complete your verification here.”
    6. Sign in with the same primary email address used when the validation request was created, and attempt to complete the existing flow again.

    These are Microsoft’s documented troubleshooting steps for technical errors involving Authenticator and Verified ID.^1^ The normal documented behavior is that Action Required remains until the verification step is completed; after successful individual verification, the request returns to In Progress while validation continues.^2^

    Determine whether the result was received

    The documented portal experience does not expose AU10TIX transaction details or an acknowledgement showing exactly which passport, face, or email results were received. If the request remains Action Required, Artifact Signing has not recognized the flow as successfully completed; that does not establish whether AU10TIX captured some or all of the submitted information.

    Record the following before escalating:

    • Identity Validation ID
    • Artifact Signing account name and Azure region
    • Subscription and tenant IDs
    • UTC date and time of the attempt
    • Exact AU10TIX error text
    • Screenshot of the error and portal status
    • Whether Authenticator contains a Verified ID credential
    • Whether the existing verification link still opens or reports that it was already used

    Do not post tenant, subscription, or validation identifiers publicly. Supply them only through a private support exchange.

    If the same error persists

    There is no documented portal control for viewing the AU10TIX transaction, resetting it, or resuming it at a particular completed step. Request investigation of the existing Identity Validation ID:

    1. No-paid-plan route: continue this Microsoft Q&A case with the Artifact Signing tag and ask whether a moderator can arrange private escalation to the Artifact Signing identity-validation team. Moderator-facilitated escalation and backend investigation are not guaranteed, but Microsoft officially lists Q&A as an identity-validation assistance channel.^1^
    2. Azure Support route: Azure portal → Help + support → Create a support request, then select the closest available Artifact Signing/security technical category and request a backend review of the existing validation. Microsoft must determine whether that transaction can be resumed, reset, or must be replaced. Azure technical support generally requires a support plan; subscription-management support is available without one.^3^

    A comparable Artifact Signing case was resolved only after support collected the Identity Validation ID and account details and had the internal team investigate the request from the backend.^4^

    Microsoft’s published Artifact Signing guidance directs validation problems to Azure Support or Microsoft Q&A. It does not identify a dedicated public AU10TIX support channel for investigating an Artifact Signing transaction, so Microsoft should remain the primary escalation owner.

    Do not delete or duplicate the request yet

    Microsoft states that creating additional identity-validation requests for the same entity while one is in progress does not help.^1^ Wait for Microsoft to inspect the existing request unless:

    • Support instructs you to replace it; or
    • The verification link has expired. An expired email-verification link cannot be resent for the same request, so a new request is required.

    Deletion is irreversible: a deleted identity-validation request cannot be recovered.^5^


    References

    1. Artifact Signing FAQ
    2. Quickstart: Set up Artifact Signing
    3. Create an Azure support request
    4. Artifact Signing Individual Public identity validation stuck at Action ...
    5. Renew or delete Artifact Signing Identity Validations
    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.