Artifact Signing Organization/Public identity validation failed after AU10TIX verification — recovery guidance required

玉置卓也 5 Reputation points
2026-09-20T15:21:16.52+00:00

Hello Microsoft Artifact Signing team,

We are onboarding our Japanese organization to Microsoft Artifact Signing Public Trust.

Our Organization/Public identity validation reached Action Required. The organization representative proceeded through the identity verification flow, including government-issued ID capture and facial verification. During that process, an error occurred, and the same Artifact Signing identity validation request subsequently changed to Failed / Validation Fail.

We contacted AU10TIX Support regarding the failed verification flow.

AU10TIX Support advised us that the failed Artifact Signing request and the available recovery options are managed by Microsoft, and that we should contact Microsoft for guidance on whether to retry, delete, or create a new identity validation request.

Before making any changes to the existing failed request, could you please confirm the supported recovery procedure?

Specifically, please advise whether we should:

  1. Retry the same failed Organization/Public identity validation request.
  2. Create a new Organization/Public identity validation request without deleting the failed request.
  3. Delete the failed identity validation request and then create a new request.
  4. Correct any organization or representative information before creating a new request.
  5. Provide additional documentation through an appropriate secure Microsoft channel.
  6. Wait for Microsoft backend/manual review.

Current state:

  • The failed identity validation request has NOT been deleted.
  • No new identity validation request has been created.
  • No certificate profile has been created.
  • No code signing has been performed.

This was not a missed email-verification-link case. The failure occurred after proceeding through the identity verification process.

AU10TIX Support explicitly directed the Artifact Signing recovery decision back to Microsoft.

Please advise us of the supported recovery path before we make any changes to the failed request.

Thank you.Hello Microsoft Artifact Signing team,

We are onboarding our Japanese organization to Microsoft Artifact Signing Public Trust.

Our Organization/Public identity validation reached Action Required. The organization representative proceeded through the identity verification flow, including government-issued ID capture and facial verification. During that process, an error occurred, and the same Artifact Signing identity validation request subsequently changed to Failed / Validation Fail.

We contacted AU10TIX Support regarding the failed verification flow.

AU10TIX Support advised us that the failed Artifact Signing request and the available recovery options are managed by Microsoft, and that we should contact Microsoft for guidance on whether to retry, delete, or create a new identity validation request.

Before making any changes to the existing failed request, could you please confirm the supported recovery procedure?

Specifically, please advise whether we should:

  1. Retry the same failed Organization/Public identity validation request.
  2. Create a new Organization/Public identity validation request without deleting the failed request.
  3. Delete the failed identity validation request and then create a new request.
  4. Correct any organization or representative information before creating a new request.
  5. Provide additional documentation through an appropriate secure Microsoft channel.
  6. Wait for Microsoft backend/manual review.

Current state:

  • The failed identity validation request has NOT been deleted.
  • No new identity validation request has been created.
  • No certificate profile has been created.
  • No code signing has been performed.

This was not a missed email-verification-link case. The failure occurred after proceeding through the identity verification process.

AU10TIX Support explicitly directed the Artifact Signing recovery decision back to Microsoft.

Please advise us of the supported recovery path before we make any changes to the failed request.

Thank you.

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-09-20T15:21:42.3366667+00:00

    Based on the documented Artifact Signing guidance, the supported recovery path is:

    1. Do not retry the same failed request. For failed identity validation, the guidance is to start a new identity validation request rather than reuse the failed one.
    2. Create a new Organization/Public identity validation request. Artifact Signing guidance states that if identity validation fails, a new request must be initiated. The documentation also states that if changes are needed after creation, a new identity validation request is required.
    3. Correct organization and representative information before creating the new request. Ensure the organization details and the representative’s first and last name exactly match the legal entity records and the government-issued identification used in the verification flow. For public identity validation, the documentation emphasizes providing correct information and notes that changes after creation require a new request.
    4. If Microsoft requests more documentation, upload it through the Azure portal on the request. When more documentation is required, the request status changes to Action Required and an email is sent. The documents are uploaded in the Azure portal. The documentation must be current and meet the stated requirements.
    5. Use Microsoft support for assistance with identity validation. For Artifact Signing identity validation questions, the documented support paths are Azure Support or Microsoft Q&A with the artifact-signing tag.
    6. Do not expect the failed request to be recoverable through AU10TIX. AU10TIX support is specifically for issues in the AU10TIX identity-verification experience, such as document upload, facial verification, or use of the AU10TIX flow. The Artifact Signing identity validation outcome and onboarding assistance are handled through Microsoft support channels.

    Additional notes relevant to the current state:

    • Since this was not an expired or missed email-verification-link case, the specific “missed email” recovery guidance does not apply.
    • If the failed request was due to inaccurate information or verification mismatch, the documented pattern is to submit a new request with corrected information.
    • If the request had reached Action Required because more documents were needed, the supported path is to provide those documents through the Azure portal when prompted.
    • If the request is already in Failed state, the documentation supports creating a new request rather than waiting for the same failed request to resume.

    A practical next step sequence is:

    1. Review the organization and representative details for exact accuracy.
    2. Check whether the failed request included any documentation request email or portal prompt that was not completed.
    3. If the request is already definitively Failed, create a new Organization/Public identity validation request with corrected information.
    4. If any uncertainty remains about whether another request for the same organization should be created, open an Azure Support case before submitting another request.

    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.