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

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-20T01:48:32.64+00:00

    The request can remain In Progress while validation is still being processed. For identity validation cases where all documents were submitted, the guidance in similar cases indicates processing is around 7 days when everything is in order, and if there is an issue Microsoft contacts the primary email address.

    For the Authenticator/Verified ID error, the supported troubleshooting steps are:

    1. Close all open instances of Microsoft Authenticator on the mobile device, then reopen it.
    2. Make sure Microsoft Authenticator is updated to the latest version.
    3. Clear the browser cache, or retry in a different browser.
    4. Avoid weak Wi-Fi and do not use a VPN or proxy during the verification flow.
    5. If possible, try the verification on a different device.
    6. If contacting support, send Microsoft Authenticator logs and the incident ID.

    For the current In Progress state, the documented support path is to contact Azure Support or post on Microsoft Q&A with the artifact-signing tag. The documentation also states that creating more identity validation requests for the same entity while one is already in progress does not help, and requests cannot be expedited.

    If the verification email was missed or expired, a new identity validation request is required because the link expires after seven days and cannot be resent on the same request. If the issue was not caused by a missed email verification, and the validation team cannot determine the request from the submitted information, onboarding cannot proceed further.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.