Artifact Signing organization verification blocked by AU10TIX Verified ID failure

The AU10TIX message does not expose a specific rejection reason or a self-service reset, so keep the current request intact and escalate it through Microsoft Q&A with the Artifact Signing tag for service-side investigation.

What is confirmed

• South Korea is supported for Public Trust organization onboarding, and Korea Central is a supported Artifact Signing region; this is not, by itself, a country-eligibility failure.^1^
• The exact South Korea scenario—AU10TIX displaying “Sorry, you do not meet requirements to create a Verified ID at this time” while Azure remains at Action required—has been reported publicly. No accepted resolution or publicly documented failure reason is available for that case.^2^
• Identity validation can only be completed through the Azure portal, not through Azure CLI, so there is no CLI command that can complete or reset this verification.^1^

Escalate without a paid technical-support plan

Microsoft lists both Azure Support and Microsoft Q&A with the Artifact Signing tag as support routes for identity-validation problems.^3^ Because Basic support does not include technical cases, use or update the matching Microsoft Q&A thread and request routing to the Artifact Signing identity-validation/vetting team. Azure documentation confirms that technical support requires a support plan.^4^

Include:

• Artifact Signing account name and Azure region.
• Subscription ID and tenant ID only through a private channel requested by Microsoft staff, not in the public post.
• Identity Validation ID and current status.
• Validation type: Organization / Public Trust.
• Country: South Korea.
• Exact AU10TIX message and timestamp with time zone.
• Screenshot with document numbers, faces, QR codes, and identifiers redacted.
• Phone OS, Microsoft Authenticator version, and browser.
• Whether a Verified ID appeared in Microsoft Authenticator.
• Any AU10TIX case/reference number.
• Confirmation that document capture and facial capture completed before the error.

Suggested escalation text:

Artifact Signing organization/Public Trust validation in South Korea is blocked after AU10TIX document and facial capture. AU10TIX reports “Sorry, you do not meet requirements to create a Verified ID at this time,” while Azure remains “Action required.” Please route this to the Artifact Signing identity-validation/vetting team to identify the failed verification stage and advise whether the existing request can be reset or requires manual review. I can provide the Identity Validation ID, subscription ID, tenant ID, timestamps, and unredacted evidence privately.

Retry only under the matching condition

Do not create concurrent requests for the same entity while this request is still in progress; Microsoft states that additional in-progress requests do not help and cannot be expedited.^3^

A delete-and-recreate retry is documented for certain situations:

• A missed or expired organization email-verification link.
• An email validation marked Failed.
• Specific individual-validation errors such as address/name mismatch or FaceCheck failure.
• A stuck in-progress request where deletion is permitted; deleting such a request does not consume one of the three document-upload attempts, because that limit applies when the validation team requests additional documents.^5^

Your AU10TIX message is not one of the explicitly documented retry cases. Therefore, do not delete the current validation until Microsoft confirms that recreation is appropriate. If Microsoft directs a retry, first delete the existing request, remove any failed/partial Verified ID from Authenticator, then create one new organization validation request.

If Microsoft classifies it as a technical Verified ID failure

The documented technical checks are:

1. Close every running instance of Microsoft Authenticator.
2. Update Authenticator to the latest Android or iOS release.
3. Clear the browser cache or use another browser.
4. Disable VPN/proxy and use a stable connection.
5. Retry from another supported phone if available.^3^

These checks may address transport or app-handshake failures, but they cannot reveal or override an AU10TIX eligibility decision. A manual-review path is not guaranteed in the public documentation; it requires Microsoft-side assessment.

References

1. Quickstart: Set up Artifact Signing
2. Artifact Signing blocked by Verified ID creation error; AU10TIX ...
3. Artifact Signing FAQ
4. Create an Azure support request
5. Artifact Signing identity validation stuck on email verification – no resend option / third validation attempt - Microsoft Q&A