Artifact Signing Individual Identity Validation Failed After Successful Verified ID Verification

I am trying to complete Individual/Public identity validation for Azure Artifact Signing.

I successfully completed passport verification through AU10TIX and received a Verified ID in Microsoft Authenticator. My browser subsequently displayed "Verification successful!", although Authenticator also showed an error.

Despite this, my Azure identity validation status changed to "Failed" without providing a reason.

I have checked my Azure billing information against my proof-of-address document. The address matches, but my Azure billing name omits my middle name. My passport contains my full middle name, while my utility bill contains only the middle initial.

Azure's automated troubleshooter found no problems with resource provisioning or role assignments. Unfortunately, my Basic support plan does not permit submitting a technical support ticket.

Could a Microsoft Artifact Signing team member help identify the actual validation failure reason and advise whether I should update my billing information or resubmit the verification?

I can provide validation identifiers privately through an approved support channel.

Update: Exact error identified — tokenError / Cosmos DB conflict

I attempted verification again and received the following error in Microsoft Authenticator:

Error code: tokenError

Error details: "The server cannot fulfill the request due to a server conflict. The targeted resource in CosmosDB already exists."

I found two other Artifact Signing reports from October 10, 2026, describing the same error.

My passport verification and Verified ID issuance succeeded, but the final Authenticator verification failed.

This now appears to be a possible server-side conflict rather than a document mismatch.

Could the Artifact Signing or Microsoft Entra Verified ID engineering team investigate whether an existing verification record is causing the conflict?

I can provide the request ID, correlation ID, timestamps, and identity-validation ID privately through an approved support channel.