Azure Artifact Signing organization validation stuck at Action Required after AU10TIX selfie

Jason A 0 Reputation points
2026-11-11T19:12:09.5066667+00:00

I'm trying to complete organization identity validation for public code signing in Azure Artifact Signing. My validation request is still in the "Action Required" state.

The AU10TIX ID scan succeeded, but after I submitted the selfie I received this message:

"You do not meet requirements to create a Verified ID at this time."

Azure diagnostics reported that the Artifact Signing resource was healthy. How can I find out what triggered the message, and can I retry verification on the existing request?

If Microsoft needs to review the request, what private support channel can I use with the Azure Basic 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 No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-11-12T06:55:20.7433333+00:00

    The message does not identify which Verified ID requirement failed, so preserve the current request and ask Microsoft to inspect the failed session before deleting or creating another validation.

    Request a private investigation

    With an Azure Basic plan, general technical support tickets are not included; technical support requires a qualifying support plan.^1^ The practical route is:

    1. Create a Microsoft Learn Q&A question using the Artifact Signing tag. Artifact Signing’s FAQ explicitly lists Microsoft Q&A as a support option.^2^
    2. Include only non-sensitive facts publicly:
      • Organization/Public validation.
      • Current status: Action Required.
      • Exact AU10TIX message.
      • Approximate date, time, and time zone of the failed selfie session.
      • Azure region and Basic SKU.
      • Confirmation that the document scan completed.
    3. Ask a moderator to initiate a private message or private escalation to the Artifact Signing vetting team. Similar cases have been moved to private communication when account-specific details were required.^3^
    4. Provide the following only through that private exchange:
      • Identity Validation ID.
      • Subscription and tenant IDs.
      • Artifact Signing account and resource details.
      • AU10TIX/Verified ID session or incident ID, if displayed.
      • Screenshot of the message with unrelated personal data removed.

    A private moderator escalation is case-dependent, not a guaranteed support entitlement under the Basic plan. A matching organization-validation case indicates that Microsoft support must inspect the failed Verified ID session to determine the rejection reason.^4^

    Do not publish identity-validation, tenant, subscription, session, or account identifiers in the public Q&A post.

    Can the existing request be retried?

    There is no documented user-controlled reset for this generic message. Artifact Signing identity validation is completed only through the Azure portal, and the normal organization workflow returns from Action Required to In Progress after individual verification succeeds.^5^

    Before deleting anything:

    1. Open Azure portal → Artifact Signing account → Identity validations.
    2. Select the existing validation.
    3. If Please complete your verification here remains available, record the validation ID and timestamps, then try that existing link once. This continues the existing request rather than creating a duplicate.
    4. If it returns the same eligibility message, stop retrying and request the private investigation above.

    Creating additional requests for the same entity while the current request remains in progress does not help, and identity-validation requests cannot be expedited.^2^

    Delete and recreate only after the failure type is established

    If the portal or Microsoft confirms Face Check failed, a first/last-name mismatch, or an address mismatch, the documented recovery is:

    1. Delete the existing identity-validation request.
    2. If the failed attempt actually created a Verified ID that appears in Microsoft Authenticator, remove that associated Verified ID.
    3. Create a new organization/public identity-validation request.
    4. Ensure the representative’s first and last names exactly match the government-issued ID.
    5. For a Face Check retry, use even, moderate lighting; avoid direct sunlight, backlighting, and shadows; clean the lens; keep the face centered; and remove anything obscuring it.^2^

    Deletion is destructive, so first retain the validation ID, failure time, and screenshots needed for investigation. If Microsoft identifies a backend/session issue instead, ask the team to repair or reset the existing request; comparable Artifact Signing cases have been resolved by the service team and then retried on the existing request.^6^


    References

    1. Create an Azure support request
    2. Artifact Signing FAQ
    3. Artifact Signing (Trusted Signing): organization identity validation ...
    4. Artifact Signing organization validation – "Sorry, you do not meet ...
    5. Quickstart: Set up Artifact Signing
    6. Artifact Signing organization validation (Poland): verification link signs in to the Microsoft Accounts tenant and shows You need permission - Microsoft Q&A
    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.