Azure Artifact Signing identity validation blocked by Verified ID HTTP 409 CosmosDB conflict

Escalate the existing identity-validation request to Azure Support and ask the Artifact Signing validation team to recover or reconcile its backend state; do not create another validation request while this one is unresolved.

The successful AU10TIX issuance and Face Check followed by HTTP 409, tokenError, and “resource … already exists” requires service-side investigation. A Cosmos DB 409 means an attempted resource ID conflicts with an existing resource, but it does not by itself establish which Artifact Signing record is duplicated or authorize a customer-side repair.^1^ Similar Artifact Signing validation cases were completed only after Support collected the validation ID and account details and involved the internal validation team.^2^

Open the support request without using the failing blade

Try a different supported entry point rather than returning to the blank embedded page:

1. In the Azure portal, open the affected Artifact Signing account.
2. From its resource menu, select Support + Troubleshooting.
3. Describe the issue and select Create a support request if the suggested diagnostics do not resolve it.

Alternatively, from anywhere in the portal:

1. Select ? in the global header.
2. Enter “Artifact Signing identity validation Verified ID HTTP 409.”
3. Select Create a support request.

Azure also supports creating tickets programmatically through the Azure support ticket REST API or Azure CLI if the portal remains unusable.^3^

For a subscription-scoped request, the submitting account needs one of these roles at subscription scope:

• Owner
• Contributor
• Support Request Contributor
• A custom role containing Microsoft.Support/*

Technical support also requires an eligible support plan.^3^ If ticket access should be available but is not, ask the tenant administrator or support-agreement owner to verify the account’s permission and support entitlement.^4^

Information to put in the ticket

Use a summary such as:

Artifact Signing Public Organization identity validation fails during Verified ID presentation with HTTP 409

AU10TIX Government Issued ID issuance and Face Check complete successfully. Presenting the credential to Artifact Signing repeatedly fails with:

• HTTP status: 409 Conflict
• Error code: tokenError
• Message: The targeted resource in CosmosDB already exists.
• CompleteRequestStatus: failed
• AppIntegrityStatus: Success

Please route this case to the Artifact Signing identity-validation team and, if required, Microsoft Entra Verified ID engineering. Please inspect and reconcile the existing validation transaction; advise whether the current request can be recovered or must be cleared before another request is submitted.

Attach through the private support case:

• Existing identity-validation ID and previous request ID
• Subscription ID, tenant ID, resource group, and Artifact Signing account name
• UTC timestamp of the latest failure
• Authenticator and mobile OS versions
• Full diagnostic output and screenshots
• Browser trace showing the separate blank support-blade failure, if available

Do not publish those identifiers or logs in Microsoft Q&A. Q&A is an official Artifact Signing support option for public technical discussion, but account-specific backend work must proceed through a private support case.^5^

Avoid another validation request for now

Microsoft’s Artifact Signing guidance says that creating more validation requests for the same entity while one is in progress does not help, and requests cannot be expedited.^5^ Since a replacement request has already been created after the earlier email-verification failure, wait for Support to determine which record is authoritative and whether stale state must be cleared.

Do not attempt to modify Cosmos DB directly: the database named in the message is part of Microsoft’s service workflow, not a Cosmos DB account under your subscription.

References

1. HTTP Status Codes for Azure Cosmos DB
2. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
3. Create an Azure support request
4. Microsoft Cloud Portals: Self-Help When a Support Request Cannot Be Opened
5. Artifact Signing FAQ