Azure Artifact Signing: Does "In Progress" confirm successful Face Check despite contradictory verification results?

I am attempting Public Trust organization identity validation for a registered Danish software company using a paid Azure Artifact Signing account in North Europe.

After multiple validation attempts, I have encountered three contradictory outcomes during the Microsoft Verified ID presentation process.

Steps to reproduce

Create a Public organization identity validation.

Complete the government ID verification and obtain a Verified ID.

Open the verification link and present the Verified ID using Microsoft Authenticator.

Complete the requested Face Check.

Actual results

Across multiple attempts, I have experienced the following:

Retrying the presentation in Authenticator produces:

Error code: tokenError

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

Reopening the verification link produces:

"Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request."

At this point, Azure can still display Action Required, despite the verification link being unusable. It subsequently changes to In Progress.

Expected behaviour

The customer should receive a consistent, definitive result indicating whether credential presentation and Face Check succeeded, failed, or encountered a technical error.

Instead, all three outcomes — success, explicit failure, and no result — lead to the same In Progress status.

This is particularly misleading because In Progress suggests that the application has advanced to organization verification, even when the desktop website explicitly reported that Face Check failed.

The CosmosDB conflict occurs on retry, suggesting that the original submission may have reached the backend despite Authenticator reporting an error. However, there is no way to confirm whether the existing record represents a successful or incomplete verification.

Troubleshooting performed

Repeated identity validation using new requests.

Verified Azure resource configuration through Azure CLI.

Confirmed the signing account provisioning state is Succeeded.

Checked Azure activity logs, which contain no failed management operations or identity verification events.

Azure's automated troubleshooting recommended creating a Public Trust certificate profile. However, completed identity validation is a prerequisite for creating that profile, making this recommendation circular and unusable.

Question

Does the transition from Action Required to In Progress definitively confirm that Verified ID presentation and Face Check succeeded?

If not, how can a customer determine whether personal verification actually succeeded before waiting up to 20 business days for organization validation?

My current request is In Progress following another Authenticator error and no desktop verification result.

I previously deleted an In Progress request because I could not determine whether verification had succeeded. That request may have been processing normally.

The current workflow effectively forces customers to choose between abandoning a potentially successful application and waiting weeks for a potentially inevitable rejection.

I am not requesting expedited validation or assistance configuring Azure. I am requesting confirmation that the mandatory personal verification steps have actually succeeded.

I can provide my validation ID and diagnostic information privately.

Please refer this to the Artifact Signing or Microsoft Entra Verified ID team if backend investigation is necessary.
Additional context

This is not an isolated issue. Other Artifact Signing customers have reported the same combination of Authenticator timeouts, CosmosDB conflicts and contradictory Face Check results:

https://learn.microsoft.com/en-us/answers/questions/6034952/artifact-signing-organization-validation-failed-af

https://learn.microsoft.com/en-us/answers/questions/6034996/artifact-signing-individual-validation-cosmosdb-re

I am already paying for Artifact Signing, but Azure's automated support cannot diagnose these failures, and direct technical support requires an additional paid subscription.

If the current verification transaction has failed, is there a supported way to recover the existing validation request without deleting it and repeating the entire process?

At a minimum, the portal should expose separate statuses for Verified ID presentation, Face Check and organization verification, rather than collapsing every possible outcome into "In Progress".