A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing blocked by Verified ID creation error; AU10TIX referred us to Microsoft
We are completing Public organization identity validation for Azure Artifact Signing in South Korea.
After completing the driver’s license capture and facial verification steps in the AU10TIX / Microsoft Verified ID flow, it displays:
“Sorry, you do not meet requirements to create a Verified ID at this time.”
Repeated attempts produced the same result. The Azure portal still showed Action Required on September 8, 2026, and the details pane asks us to complete verification. It does not show a specific failure reason.
We contacted AU10TIX support. After clarifying that we use the Microsoft Artifact Signing integration, their support team referred us to Microsoft for Entra Verified ID platform assistance. They did not provide a failure reason or confirm a session reset.
We also attempted an Azure technical support request for Artifact Signing, but the Basic support plan blocks submission. We are following the Artifact Signing documentation’s Microsoft Q&A support route.
Could the Artifact Signing / Entra Verified ID team help with:
- A private support route for reviewing the verification attempt and identifying the actual failure reason.
- Determining whether the existing verification session should be reset/reopened and which team can do this.
- How to obtain case-specific assistance when the Azure technical support request is blocked by the Basic support plan and AU10TIX refers us back to Microsoft.
We can provide the Azure Identity Validation ID, tenant/subscription identifiers, AU10TIX case number and correspondence privately to verified Microsoft support staff. Please provide an appropriate private channel.