A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Preserve the current In Progress / Action Required validation and request a Microsoft moderator to escalate it for service-side investigation; only Microsoft can determine whether the consumed transaction can be reset or recovered, and creating another request while this one remains in progress does not help.^1^
The matching 409/Cosmos DB and already-used-link reports do not establish a customer-accessible repair or guarantee that the existing transaction can be recovered. They indicate that the validation state needs backend review. A completed identity validation is also required before a certificate profile can be created, so the missing profile is expected at this stage.^2^
Request escalation on this Q&A thread
Add a comment or update containing only non-sensitive information and ask for:
Please escalate this preserved Public/Individual identity-validation transaction to the Artifact Signing validation team for backend review. The Verified ID presentation returned HTTP 409 with a Cosmos DB “resource already exists” detail, after which the one-time link became consumed while Azure continued to show Action Required / In Progress. Please enable a Microsoft Q&A private message if account-specific identifiers or files are required.
A moderator may open a private-message conversation, but Q&A does not guarantee private-message availability, escalation routing, or recovery of the transaction. Microsoft Q&A private messages are visible to the question author and Microsoft moderators and are approved for support IDs, logs, scrubbed traces, subscription IDs, and tenant IDs. Messages are retained for 30 days from the moderator’s first message.^3^
Do not post validation, subscription, tenant, transaction, or correlation identifiers publicly.
Prepare the private diagnostic package
Collect the following without changing or deleting the validation:
- Artifact Signing account name, resource group, region, and validation type.
- Identity Validation ID.
- Azure subscription ID and tenant ID.
- Current portal status and details status:
-
Action Required -
In Progress
-
- Exact UTC time of the failure, if available. Otherwise provide November 8, 2026, the local time, and timezone.
- The complete
409error text, correlation/request/incident IDs, and screenshots. - Screenshot of the consumed-link message.
- Microsoft Authenticator version and mobile OS version.
- Confirmation that the Verified ID remains present and unexpired.
- The failed Azure Support request result showing
InvalidSupportPlan; exclude access tokens and unrelated account data.
Also submit Authenticator diagnostics:
- Open Microsoft Authenticator.
- Select Send feedback from the top menu.
- Select Having trouble?
- Submit the form and logs.
- Record the resulting incident ID and provide it privately to the moderator or support engineer.^4^
The Artifact Signing FAQ specifically requests Authenticator logs and an incident ID when escalating Verified ID technical errors.^1^
Do not recreate it yet
Deletion and recreation is documented for failed or expired links and for specific identity mismatch/Face Check scenarios. Your validation instead remains In Progress, and the failure occurred after presenting an existing Verified ID. Therefore, keep the request and Verified ID intact until the Artifact Signing team confirms whether it can recover the backend transaction.
If Microsoft determines that recovery is impossible and explicitly directs recreation, then:
- Delete the existing identity-validation request.
- Remove the associated Verified ID from Authenticator only if instructed.
- Create a new Public/Individual validation in the Azure portal.
- Present a newly issued, valid Verified ID.
Identity validation can be completed only through the Azure portal, not Azure CLI.^5^
References