Azure Artifact Signing individual identity verification blocked after AU10TIX license and selfie check

I am a U.S.-based individual developer attempting to complete Individual Developer / Public Trust identity validation for Azure Artifact Signing.

My Artifact Signing account was created successfully, my subscription is active, and I have both required roles:

Artifact Signing Identity Verifier

Artifact Signing Certificate Profile Signer

I created an Individual/Public identity-validation request and followed the Microsoft Verified ID flow through AU10TIX. I scanned my valid U.S. driver’s license and completed the selfie/liveness step. The process then ended with this message:

Sorry, you do not meet the requirements to create a Verified ID at this time.

No explanation, reason code, retry guidance, or corrective action was provided. No Verified ID was issued to Microsoft Authenticator.

This is not an organization-validation issue, business-history issue, IAM issue, XML-validation issue, managed-identity issue, or subscription-payment issue. The validation request itself was created successfully. The failure occurred inside the AU10TIX identity-verification flow after the ID and selfie were submitted.

My Azure billing account is an active Microsoft Customer Agreement account under my legal name. My driver’s license displays my surname on one line and my first and middle names on another. After the first failure, I created a new billing profile and Individual validation request using my complete legal name, including my middle name, exactly as displayed on the license.

This raises two related problems:

Microsoft’s Artifact Signing documentation does not explain how middle names should be entered, normalized, or matched during Individual validation.

The AU10TIX error does not indicate whether the failure was caused by document recognition, name matching, address matching, face comparison, liveness, attempt limits, or another eligibility rule.

I would prefer not to expose my middle name in the final public signing certificate unless it is genuinely required. The documentation does not make clear whether a middle name used for verification will necessarily appear in the certificate subject.

The Azure support-request workflow has also not provided a usable path for this issue. Its automated troubleshooting repeatedly returns unrelated material about organization validation, XML schemas, Operator Nexus, Private Link, and managed identities. Standard technical support also appears to require purchasing a separate paid support plan, despite Artifact Signing already being a paid service.

Could a Microsoft moderator or Artifact Signing team member please contact me privately and escalate this to the appropriate Artifact Signing / Microsoft.CodeSigning / Microsoft Verified ID team?

I can provide the following privately:

Artifact Signing account name

Subscription and tenant identifiers

Identity-validation request identifiers

Exact UTC timestamps

Screenshots of the AU10TIX result

Billing-profile details

I will not post government-ID images or private Azure identifiers publicly.

I need Microsoft to determine:

Which AU10TIX or Verified ID check failed.

Whether my identity has an attempt-limit, eligibility, or anti-fraud restriction.

Whether Microsoft or AU10TIX must reset the verification record.

Whether I should keep or delete the existing validation requests.

Whether a documented retry period exists.

Whether the middle name is required for validation and whether it will appear in the public certificate subject.

Please do not redirect this to organization onboarding or generic Azure validation documentation. I am specifically requesting assistance with an Individual Developer AU10TIX Verified ID issuance failure for Azure Artifact Signing.