Azure Artifact Signing organisation identity validation is blocked by AU10TIX Verified ID issuance.

This requires escalation through the existing Microsoft Q&A thread to the Artifact Signing identity-validation team; do not create another validation request while the current request remains in progress.

Request a private backend investigation

Artifact Signing documentation explicitly permits identity-validation assistance through Microsoft Q&A using the Artifact Signing tag and warns that duplicate requests for the same entity do not help or expedite validation.^1^

Add a reply to this thread asking a Microsoft moderator or engineer to:

1. Escalate the case to the Artifact Signing identity-validation / Entra Verified ID team.
2. Establish a private exchange before requesting sensitive identifiers.
3. Check the backend result associated with the Identity Validation ID.
4. Confirm whether Microsoft should reset the existing session or whether you should delete and recreate the request.
5. Confirm whether an assisted alternative is available.

A closely matching Artifact Signing case—repeated validation failures without a portal reason—was resolved after support obtained the Identity Validation ID and account details and worked with the internal team.^2^ Another organization-validation case received a moderator response that the team had been contacted.^3^

Do not post the validation ID, subscription ID, tenant ID, screenshots containing personal data, ID-document data, or contact details publicly. Prepare these for the private handoff:

• Identity Validation ID
• Subscription and tenant IDs
• Artifact Signing account name and Azure region
• UTC timestamps of the latest attempt
• Current validation status shown in the portal
• Screenshot of the exact AU10TIX message
• Representative’s country and identification-document type
• Microsoft Authenticator incident ID, if available

To generate an Authenticator incident ID:

1. Open Microsoft Authenticator.
2. Select Send feedback from the app menu.
3. Select Having trouble?
4. Submit the feedback and logs.
5. Record the resulting incident ID for Microsoft support.^4^

Suggested escalation text:

The AU10TIX document and selfie processing completes but issuance stops with “Sorry, you do not meet the requirements to create a Verified ID at this time.” No Verified ID is issued, so the organization-validation flow cannot continue.

Please escalate this to the Artifact Signing identity-validation / Entra Verified ID team and initiate a private exchange. Please determine the backend failure category and advise whether the existing session should be reset, deleted and recreated, or handled through another supported verification method. The Identity Validation ID, subscription/tenant details, timestamps, screenshot, and Authenticator incident ID are available privately.

Do not delete or replace the request yet

The documented delete-and-recreate procedure applies to a Face Check, first/last-name mismatch, or address-mismatch error after obtaining a Verified ID and scanning the QR code.^1^ Your failure occurs before issuance and does not identify one of those errors, so that procedure is not established as the fix here.

Likewise, the FAQ requires a new request when the email link expired, but your email verification completed successfully. A new request should therefore be created only if the Artifact Signing team instructs you to do so. The normal organization workflow expects successful individual verification to return the request to In Progress while organization validation continues.^5^

Eligibility and alternatives

New Zealand organizations are eligible for Public Trust, while Individual Developer validation is limited to the United States and Canada.^5^ Because this is Organization / Public Trust, the Individual Developer country restriction does not by itself explain the failure.

AU10TIX is a supported Microsoft Entra Verified ID identity-verification partner.^6^ However, the public Artifact Signing documentation does not specify:

• what this exact AU10TIX message means;
• a customer-operated session-reset mechanism; or
• a generally available alternative verification method for this failure.

Those answers require account-specific backend review. An alternative process has been mentioned in Microsoft Q&A for accessibility-related cases, but it is conditional and not documented as a general fallback for an AU10TIX eligibility decline.^7^

Basic support-plan limitation

Azure technical support ordinarily requires a paid support plan.^8^ Microsoft Q&A is therefore the documented channel available for Artifact Signing identity-validation questions under Basic support.^1^

If the Azure portal offers Priority Community Support for this request, use it: eligible cases remain linked to Microsoft Q&A, and a Microsoft engineer can continue privately through Q&A or email when sensitive information or deeper investigation is required.^9^ Availability depends on the support plan, so this option might not appear with Basic.

References

1. Artifact Signing FAQ
2. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
3. Azure Artifact Signing: Identity validation rejected without specific reason — ACE of ESS AB (Sweden) - Microsoft Q&A
4. Send Microsoft Authenticator logs and get an incident ID
5. Quickstart: Set up Artifact Signing
6. Microsoft Entra Verified ID identity verification partners
7. How to sign up/register for Artifact Signing without a smartphone - Microsoft Q&A
8. Create an Azure support request
9. Get Azure help through Priority Community Support (PCS)