Artifact Signing: AU10TIX Verified ID rejection; Developer Support escalation requested

Create the paid technical-support case from the Azure portal’s global Help + support entry rather than the Artifact Signing resource’s stalled Get Support flow, and request backend review of the existing Identity Validation ID without deleting or duplicating the validation.

Submit the private support case

1. In the Azure portal, select ? in the global header.
2. Describe the issue, then select Create a support request.
3. Select:
   • Issue type: Technical
   • Subscription: The subscription containing the Artifact Signing account
   • Service: Artifact Signing, if offered; otherwise choose the closest Azure technical service and state Microsoft.CodeSigning / Artifact Signing prominently in the summary.
   • Support plan: Developer
   • Severity: The highest option the plan offers
4. If recommended articles appear, select Return to support request and then Next.
5. Use a summary such as:

   Artifact Signing organization identity validation blocked after AU10TIX Verified ID rejection — backend review/reset required

6. Include these non-secret details in Problem details:
   • Artifact Signing resource name and region
   • Organization/Public validation
   • Status: Action Required
   • Exact AU10TIX message
   • Date and approximate time of the verification attempt, including time zone
   • Confirmation that no validation was deleted and no duplicate was created
   • Business impact: production Windows signing profile cannot be created
   • Request to route the case to the Artifact Signing identity-validation team
   • Link to Q&A question 6058968 and a request to correlate it with the ticket
   • Request to determine whether the existing representative-verification session can be reset or reopened and which submitted field needs correction
7. Provide the Identity Validation ID, subscription details, tenant details, and account-specific evidence only through the private ticket, not in Q&A.
8. Select the Developer plan, preferred contact method, and Create. Microsoft documents this global-header route separately from the resource-specific support entry, and the selected subscription controls which resources the assigned engineer can access.^1^

Matching Artifact Signing cases with unexplained validation failures were resolved after support obtained the Identity Validation ID and relevant account details for backend investigation.^2^ Another failed validation was likewise verified after the validation team reviewed its ID.^3^

Do not create another validation yet

The Artifact Signing FAQ says that additional requests for the same entity while one is in progress do not help and that identity validations cannot be expedited. It identifies Azure Support or Microsoft Q&A as the assistance channels.^4^

The documented delete-and-recreate recovery applies when a specific address mismatch, name mismatch, or Face Check error is shown. Your generic eligibility message does not establish any of those conditions, so do not use that destructive recovery path unless support identifies the corresponding mismatch. The same FAQ also says to create a new request when an email-verification link expired, which is not the symptom described here.^4^

New Zealand organizations are eligible geographically for Public Trust onboarding. A completed identity validation is required before a certificate profile can be created, so the present validation state is the blocker.^5^

Support priority and stalled-ticket fallback

A Q&A post cannot confirm a private support entitlement, assign priority, route an engineer, or expose backend validation findings. Those actions begin only after Azure creates a support-request number.

For the Azure Developer plan, the maximum severity is Severity C, with a documented initial response target of less than eight business hours; Severity A and B are unavailable on that plan. “Priority Community Support” is not a documented Developer-plan severity.^6^

If the global-header workflow also remains stuck and no support-request number appears:

1. Go to Help + support → All support requests and confirm that no case was created.
2. Retry from the global header in a new browser session.
3. If a case exists, open it and use New message to add the Q&A link and request Artifact Signing identity-validation routing.
4. If the problem is specifically managing or completing the original support request, create another support request describing that support-workflow failure and reference the original request where available. Microsoft documents this as the fallback for assistance managing a support request.^7^

References

1. Create an Azure support request
2. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
3. Artifact Signing Account Organization Identity validations failed - Microsoft Q&A
4. Artifact Signing FAQ
5. Quickstart: Set up Artifact Signing
6. Support scope and responsiveness
7. Manage an Azure support request