Artifact Signing identity validation: Verified ID presentation fails with HTTP 409 CosmosDB conflict

Stop retrying the consumed presentation and do not create another identity-validation request; this HTTP 409 presentation-stage pattern requires Microsoft to inspect and recover or reset the existing Artifact Signing/Verified ID transaction. Closely matching reports associate the 409 “resource already exists” response with conflicting backend presentation state, but no public self-service recovery procedure is documented.^1^

Escalate the existing transaction

Microsoft documents two support routes for Artifact Signing identity validation: Azure Support and Microsoft Q&A with the artifact-signing tag. It also explicitly warns that creating more validation requests for the same entity while one is in progress does not help.^2^

1. Continue through Microsoft Q&A without creating duplicates

Because Basic support does not include Azure technical support, use this Q&A case as the escalation record and request that a Microsoft moderator route it to the Artifact Signing identity-validation team.

Add the following, but provide identifiers only through a private message or secure support upload:

• Exact failure time: 2026-10-18 02:48 UTC
• Artifact Signing account name and Korea Central
• Identity-validation request ID
• HTTP status and full message: 409 — “The targeted resource in CosmosDB already exists”
• Earlier HTTP 404 timestamps
• Correlation, transaction, and request IDs
• Confirmation that:
  • AU10TIX successfully issued Government Issued ID – GLOBAL
  • The credential remains valid in Microsoft Authenticator
  • Failure occurs while presenting that existing credential
  • Portal status remains Action Required
  • No replacement validation request has been created

Use this explicit request:

Please route this to the Artifact Signing/Verified ID identity-validation engineering team. Recover or reset the existing presentation transaction and clear any conflicting backend transaction state without deleting the issued Verified ID or creating another organization identity-validation request. Please preserve the current request if recovery is possible and issue a fresh presentation session only if the existing session cannot be recovered.

Transaction IDs and timestamps are the appropriate artifacts for tracing credential-validation attempts.^3^

2. Azure technical support, if a plan becomes available

From the Artifact Signing account in the Azure portal:

1. Open Help → Support + Troubleshooting.
2. Select Create a support request after the suggested diagnostics.
3. Choose Technical and select the Artifact Signing resource/subscription.
4. Describe the issue as Artifact Signing organization identity validation / Verified ID presentation HTTP 409.
5. Attach the browser trace or screenshot and provide the IDs through the ticket’s secure fields.

Opening a technical ticket requires a support plan; billing and subscription-management support does not cover this backend identity-validation failure.^4^ The submitting identity also needs Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope.^4^

What not to change

• Do not delete the Authenticator credential. The FAQ directs users who already have a valid, unexpired Verified ID to present that existing credential.^2^
• Do not create duplicate organization requests. Microsoft explicitly says additional in-progress requests do not help.^2^
• Do not recreate the signing account solely for this error. The failure is after account provisioning and during credential presentation.
• Do not repeat RBAC remediation. The assigned Artifact Signing Identity Verifier role is the role required to manage identity validation, and the request already reached presentation.^5^

South Korea is listed as an available geography for Public Trust organization onboarding, so the stated location is not, by itself, evidence of an unsupported-region problem.^6^

No separate publicly documented, free Artifact Signing backend-recovery channel is identified beyond Azure Support and Artifact Signing-tagged Microsoft Q&A. The published support route for a technical backend investigation therefore requires either Q&A escalation or an Azure technical-support plan.^2^

References

1. Artifact Signing Organization Identity Validation fails with HTTP 409 ...
2. Artifact Signing FAQ
3. Plan your Microsoft Entra Verified ID verification solution
4. Create an Azure support request
5. Tutorial: Assign roles in Artifact Signing
6. Quickstart: Set up Artifact Signing