Artifact Signing identity validation stuck in "Action Required" - AU10TIX does not recognize Oklahoma driver's license

Riley Slater 0 Reputation points
2026-10-20T03:20:24.6433333+00:00

My organization identity validation request for Artifact Signing is stuck in "Action Required."

When I complete the AU10TIX verification step, it does not recognize my document type. I am using a current US state driver's license (Oklahoma, REAL ID). I have attempted verification approximately 10 times with the same result, using good lighting, no glare, and the physical card. I do not have another current government ID.

My subscription is on the Basic support plan, so I cannot open a technical support ticket. Please advise how to complete verification or provide an alternate verification method. I can share my validation ID and account details privately.

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: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-20T03:21:20.4133333+00:00

    Stop retrying the AU10TIX capture and request Microsoft-side review of the existing Identity Validation ID through Azure Priority Community Support or this Microsoft Q&A thread.

    Escalate the existing request

    1. In the Azure portal, open Help + Support or the Artifact Signing resource’s Help → Support + Troubleshooting.
    2. Describe the issue as:
      • Service: Artifact Signing
      • Area: Organization identity validation / Public Trust
      • Status: Action Required
      • Failure: AU10TIX does not recognize a current Oklahoma REAL ID driver’s license
      • Request: Escalate the existing validation to the Artifact Signing identity-validation team for backend review or an alternate verification process.
    3. If the Basic plan routes the request to Microsoft Q&A instead of offering a technical ticket, publish the generated question with the Artifact Signing tag. This is the documented Priority Community Support path: the portal can create a Q&A draft, and an Azure engineer or moderator can continue the case from there.^1^
    4. Include publicly:
      • Exact AU10TIX error text
      • Current status (Action Required)
      • Approximate attempt count
      • Document type and issuing jurisdiction, but not the license number
      • Date/time and time zone of the latest attempt
      • A request for a private message to provide the validation and account identifiers
    5. Provide the following only after a Microsoft moderator opens a private-message conversation:
      • Identity Validation ID
      • Azure subscription ID
      • Artifact Signing account/resource details
      • Primary email associated with the request
      • Screenshots with license number, address, birth date, barcode, and other personal data removed

    Microsoft Q&A private messages are visible to the question author and Microsoft moderators and are intended for account identifiers and diagnostic information that should not be posted publicly.^2^

    A suitable escalation statement is:

    AU10TIX repeatedly returns “We couldn’t recognize your ID type” for a current Oklahoma REAL ID driver’s license. The Artifact Signing organization identity validation remains in Action Required after approximately 10 capture attempts. Please escalate the existing Identity Validation ID for backend review and advise whether the verification session can be reset or an alternate verification method can be enabled. I can provide the validation ID, subscription ID, and Artifact Signing account details through a Microsoft moderator’s private message.

    Do not create duplicate validation requests

    Microsoft’s Artifact Signing FAQ states that creating more identity-validation requests for the same entity while one is in progress does not help, and validation requests cannot be expedited.^3^ Keep the current request unless the Artifact Signing team explicitly instructs you to delete or replace it.

    The documented process sends an Action Required request through the portal’s verification link to a trusted ID verifier such as AU10TIX; identity validation itself cannot be completed through Azure CLI.^4^ The available documentation does not specify a user-selectable alternate provider for this Artifact Signing session.

    Matching Artifact Signing cases have required the validation ID and account details to be reviewed by Microsoft’s internal team; after backend investigation, the existing requests were completed successfully.^5^^6^

    Since the capture conditions and physical-card attempts have already been exhausted, repeating lighting, glare, browser, or device checks is unlikely to move this case forward. The next action is private investigation of the existing validation, not another public submission of identity data.

    References

    1. Get Azure help through Priority Community Support (PCS)
    2. Private messages on Microsoft Q&A
    3. Artifact Signing FAQ
    4. Quickstart: Set up Artifact Signing
    5. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
    6. Artifact Signing Account Organization Identity validations failed - 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.