A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing organization validation: CosmosDB conflict after Face Check; verification link consumed
We are completing Azure Artifact Signing Public Organization identity validation for FreeChat Inc., a Canadian corporation.
Environment:
- Artifact Signing account: FreeChat
- Region: East US
- Signing tier: Basic
- Azure support plan: Basic
- Verified ID issuer: AU10TIX
What happened:
- An AU10TIX Verified ID from a previous identity-verification attempt is still present in Microsoft Authenticator.
- We opened the current organization identity-validation link and scanned the Present your Verified ID QR code.
- The live face check passed, but sharing the existing Verified ID returned a server-conflict error: The targeted resource in CosmosDB already exists.
- The verification webpage subsequently said: Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request.
- Azure's identity-validation list still showed Action Required. The request details pane showed In Progress and continued to display the verification link.
Please engage the Artifact Signing identity-validation team to inspect and reconcile the existing verification transaction. Can the current request be recovered? If recovery is not possible, please provide a confirmed safe reset procedure. We want to preserve the current request and existing Verified ID while the issue is investigated.
This appears similar to this reported issue:
We can provide the identity-validation ID, Azure subscription/tenant/resource details, and gateway request ID through a Microsoft-approved private support channel. The phone error's diagnostic Request ID, Correlation ID, and timestamp were not captured. Please advise how to provide the available identifiers privately and whether an Authenticator diagnostic incident would help.