Artifact Signing Organization Identity Validation fails with HTTP 409 CosmosDB conflict

Question

Yuya Kaeriyama 0

Hello Microsoft Artifact Signing Team,

We are trying to complete Public Organization Identity Validation for Azure Artifact Signing for our Japanese company, TOMUP Co., Ltd.

Our Artifact Signing account was created successfully in the Japan East region, and the required RBAC permissions were assigned.

However, during the Microsoft Authenticator Verified ID presentation process, we received the following error:

HTTP 409 Conflict

The targeted resource in CosmosDB already exists.

After this error, the identity verification page displayed:

No Access - This link has been used already.

The identity validation status subsequently changed to Validation Fail.

We also ran Azure's automated troubleshooting tool, which found no issues with resource provisioning, RBAC permissions, or regional availability.

We suspect a possible conflict in the backend identity-validation state, but cannot confirm the root cause.

Could a Microsoft Artifact Signing engineer please clarify:

Is this a known issue affecting Verified ID presentation?

Does the failed identity-validation request need to be deleted and recreated?

Could an existing verification record cause HTTP 409?

Is a backend reset or manual intervention required before retrying?

How can we securely provide our validation ID, Request ID, and Correlation ID for investigation?

We would appreciate guidance before submitting another identity-validation request.

Thank you.

0 comments

1 answer

Answer 1

For this failure pattern, the supported guidance is to delete the existing identity validation request and start a new one.

Relevant documented cases:

If individual identity validation shows verification errors, the guidance is to delete the existing identity validation request, remove the associated Verified ID from Microsoft Authenticator, and then submit a new identity validation request and create a new Verified ID.
If organization identity validation fails because the email verification link was missed or expired, a new identity validation request must be created.
For public identity validation, if changes are needed after creation, a new identity validation request is required.
Identity validation processing can take 1 to 20 business days, and if more documentation is required, the request status changes to Action Required and documents can be uploaded in the Azure portal.

Based on the documented guidance, the practical next step is:

Delete the failed identity validation request.
Remove any associated Verified ID from Microsoft Authenticator.
Create a new organization identity validation request in the Azure portal.
Ensure the primary email is monitored, accepts external messages, and that the verification link is used within seven days.
Ensure all submitted organization details exactly match the legal business entity information.

What is documented about support and escalation:

Azure support can be contacted by creating a support ticket in the Azure portal.
If another identity validation is needed for the same organization with a different primary email address, support must be contacted to continue onboarding.

What is not documented in the available guidance:

No documented confirmation that HTTP 409 Cosmos DB conflict is a known Verified ID issue.
No documented statement that an existing verification record specifically causes HTTP 409.
No documented self-service backend reset process.
No documented secure channel details for sharing validation ID, request ID, or correlation ID beyond using Azure support.