A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
The current In Progress request should be escalated to Azure Support for transaction review rather than deleted or duplicated, because Artifact Signing does not support deleting an identity validation while it remains In Progress.^1^
Is the failed personal identity check blocking validation?
Potentially, yes. Public organization validation includes an individual identity-validation step. After that step succeeds, the request returns to In Progress while organizational validation continues; Microsoft may then request additional documents.^2^
However, In Progress alone does not show whether the current blocker is the 409 transaction, review of the document uploaded on October 21, or another backend state. The 409 and “already used” response requires the Artifact Signing validation team to inspect the existing request; repeatedly opening the consumed link is not a documented recovery method.
Recommended escalation
- In the Azure portal, open Help + support → Create a support request.
- Select the affected subscription and Artifact Signing resource.
- Describe the issue as an Artifact Signing identity-validation/onboarding problem, not a billing issue.
- Include:
- Identity Validation ID.
- Artifact Signing account and Azure region.
- Validation type: Organization – Public.
- Primary email domain, but avoid posting the complete address publicly.
- Timeline: link failed with HTTP 409 on October 20; additional document uploaded October 21; status remains In Progress.
- Screenshot or exact text of the 409 response.
- Correlation/incident ID and Microsoft Authenticator logs, if available.
- The existing billing case number only as background.
- Ask specifically for escalation to the Artifact Signing identity-validation/vetting team to determine whether the individual Verified ID transaction must be reset or whether the organizational document review is still pending.
Microsoft lists Azure Support and Microsoft Q&A with the artifact-signing tag as the supported assistance channels. It also states that creating additional requests for the same entity while one is in progress does not help and that validation cannot be expedited.^3^
Do not post the validation ID, email address, tenant details, or documents in a public reply. Provide them only through the support case or a private information-request mechanism initiated by authorized Microsoft personnel. Similar stuck In Progress cases on Microsoft Q&A were completed after the validation team received the request details.^4^
Should the request be deleted and recreated?
Not while it is In Progress:
- The documented portal deletion operation applies only when the identity validation is not in the In Progress state.^1^
- Artifact Signing explicitly advises that another request for the same entity while the existing one is in progress does not help.^3^
- Deletion is irreversible and can affect renewal of linked certificate profiles.
If Microsoft changes the current request to Failed, or support instructs you to replace it, then create a new request. A new request is the documented recovery when an email-validation link expired after seven days or email validation failed; a new link cannot be resent on that same request.^3^ That guidance does not establish that self-service recreation is appropriate for this still-In Progress 409 case.
References