Artifact Signing organization validation fails after successful FaceCheck: HTTP 504, then 409 CosmosDB conflict, link already used

I am completing organization identity validation for Azure Artifact Signing in West Europe using Microsoft Authenticator on iOS.

On 12 October 2026, the flow reported FaceCheckStatus=success and AppIntegrityStatus=success. Submitting the presentation response then failed with HTTP 504. Retrying failed with HTTP 409 and the error chain conflict -> tokenError -> Entity already exists, with this message: "The targeted resource in CosmosDB already exists."

The original verification link now displays: "No Access. Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request."

The portal initially remained at Action required. About eleven minutes after the technical error, an email reported Validation Fail, and the portal now confirms Failed. I cannot determine whether the technical error caused the validation failure. No detailed rejection reason appears in the validation details.

Could the Artifact Signing team investigate whether the initial submission was processed before the timeout, explain the failure reason, and advise how to recover the existing request or obtain a fresh verification link? I have retained the existing request and any associated Verified ID.

I can provide the validation ID, Request-ID, correlation vectors, screenshots, and diagnostic log privately through an official support channel. Please advise how to do so securely.