Artifact Signing identity validation remains In Progress after Authenticator tokenError: CosmosDB resource already exists

Temkay 0 Reputation points
2026-11-20T01:47:56.7233333+00:00

Hello,

I am completing Public organisation identity validation for an Australian company using Azure Artifact Signing. The signing account is deployed in East US.

On 11 November, I attempted to complete the Verified ID step using Microsoft Authenticator, after obtaining a verified identity through the recommended provider.

During verification, Authenticator displayed:

Error Code: tokenError

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

The identity-validation request currently shows In Progress in the Azure portal. Nine calendar days have now passed since that verification attempt, and I have not received any further instructions.

Could someone please clarify:

Is it normal for the request to remain In Progress after this error, or could the error have prevented the identity-verification result from being recorded?

What processing timeframe and next update should I expect?

Is there anything I need to do to resolve the error or allow validation to continue?

I can provide the validation ID and any other diagnostic details privately through an appropriate Microsoft support channel.

Thank you for your help.

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.