Artifact Signing individual validation: CosmosDB resource already exists during Verified ID presentation

Dustin Dean 0 Reputation points
2026-10-12T21:42:45.97+00:00

Hello Microsoft Artifact Signing team,

I am an individual developer in the United States using Artifact Signing Basic in East US with an active paid Azure subscription.

I completed the government-ID verification flow and added a Verified ID to Microsoft Authenticator. When presenting the credential to Artifact Signing, I was prompted for another face check and Authenticator reported:

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

The Microsoft verification webpage reports "Error: Face Check failed" and "Verification unsuccessful!". Azure still shows the current Public individual identity-validation request as "Action Required".

After an earlier FaceCheck failure, I followed the published recovery guidance by deleting the original Azure validation request and creating a replacement. I repeated the verification flow and encountered the CosmosDB conflict above. I have kept the current request and credential unchanged since this error.

Could the Artifact Signing / Verified ID team investigate the current verification transaction and advise whether the request can be recovered or whether any service-side state needs to be reconciled before another attempt?

I can provide the current and previous validation identifiers and relevant diagnostics through an official private support channel. Please advise how to share those securely; I will not post ID documents, verification URLs, or account identifiers publicly.

Thank you.

Artifact Signing
Artifact Signing

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

0 comments

3 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Meha-MSFT 2,545 Reputation points Microsoft Employee Moderator
    2026-10-28T21:24:07.7666667+00:00

    please retry this has now been fixed

    Was this answer helpful?

    0 comments
  2. Meha-MSFT 2,545 Reputation points Microsoft Employee Moderator
    2026-10-13T16:47:21.4733333+00:00

    we are looking into this

    Was this answer helpful?

  3. AI answer

    2026-10-12T21:44:21.71+00:00

    Open an Azure support request now and ask Artifact Signing/Verified ID engineering to inspect and reconcile the current replacement transaction before deleting it or attempting another presentation.

    Submit the private support request

    1. In the Azure portal, open Help + support → Create a support request.
    2. Select:
      • Issue type: Technical
      • Subscription: The paid subscription containing the Artifact Signing account
      • Service: Artifact Signing, if available
      • Resource: The affected Artifact Signing account
      • Problem type/subtype: The closest identity-validation or Verified ID option shown
      Portal labels can vary. Artifact Signing’s FAQ identifies an Azure support ticket as the private support route for identity-validation assistance.^1^
    3. Use a summary such as: Artifact Signing Individual validation: CosmosDB resource already exists during Verified ID presentation
    4. In Problem details, provide:
      • Current and previous identity-validation identifiers.
      • Artifact Signing account and Azure region.
      • UTC timestamps of both Face Check attempts.
      • Current status: Action Required.
      • Exact Authenticator and webpage error text.
      • Authenticator version, mobile OS/version, and browser.
      • The sequence: initial FaceCheck failure → old Azure request deleted → replacement request created → existing or newly issued Verified ID presented.
      • Whether the Verified ID associated with the first request was removed before creating the replacement.
      • A request to inspect the current transaction for duplicate or stale Verified ID presentation state and advise whether it can be recovered or must be reset.
      Azure recommends including when the problem began and reproducible steps, but not confidential information in the initial description.^2^
    5. Until Support responds, keep the current request and credential unchanged:
      • Do not retry the presentation link.
      • Do not create additional identity-validation requests.
      • Do not delete the current validation or Verified ID unless Support directs that recovery sequence.

    Artifact Signing documentation states that creating more requests while one is in progress does not help and requests cannot be expedited.^1^

    Share diagnostics securely

    Do not post government-ID images, QR codes, presentation URLs, tenant/subscription identifiers, or validation identifiers in Q&A.

    After creating the case:

    1. Open Help + support → All support requests.
    2. Select the case → Upload file.
    3. Upload sanitized screenshots or logs. The portal supports up to five files after case creation, with a 5-MB limit per file.^3^
    4. If Support needs sensitive material, ask the assigned engineer to initiate Secure File Exchange. Access is restricted to Microsoft Support professionals actively working on the case, and files are permanently deleted 90 days after case closure or sooner on request.^4^

    Record screenshots, identifiers, and UTC timestamps before making any later changes.

    Conditional recovery path

    The documented recovery for an Individual validation error involving FaceCheck fail is a complete reset:

    1. Delete the existing identity-validation request.
    2. Remove its associated Verified ID from Microsoft Authenticator.
    3. Submit a new identity-validation request.
    4. Create and present a new Verified ID, checking that the submitted information is accurate and lighting is adequate.^1^

    Deleting only the earlier Azure request was not the complete documented reset if its associated Verified ID remained in Authenticator. However, because the replacement transaction now reports a CosmosDB conflict and has been deliberately preserved, perform this reset only after Support confirms that the current transaction cannot be recovered or has captured what it needs. Similar Artifact Signing reports describe Face Check or presentation failures followed by an “already exists” conflict and an Action Required state.^5^

    References

    1. Artifact Signing FAQ
    2. Create an Azure support request
    3. Manage an Azure support request
    4. How to securely transfer files to Microsoft Support
    5. Artifact Signing identity validation repeatedly fails at Face Check
    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.