A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Escalate the existing identity-validation request through Azure Support and ask for backend reconciliation or a reset; do not delete it, create a duplicate request, or repeat the already-completed Verified ID flow.
Open the support request
- In the Azure portal, open Help + support and select Create a support request.
- Select the affected subscription and route the request to Azure → Security → Azure Artifact Signing where those choices are available.
- Use a title such as: Artifact Signing organization validation stuck at Action Required after Verified ID succeeded — one-time link already used
- Include:
- Artifact Signing account name and region
- Identity Validation ID
- Subscription ID
- Validation type: Public Trust Organization
- Current portal state: Action Required
- Exact link error: “No Access — Sorry, this link has been used already”
- Approximate UTC time when AU10TIX/Authenticator verification completed
- Microsoft Authenticator Incident ID
- Confirmation that the Verified ID credential appears in Authenticator
- Confirmation that the request was not deleted or duplicated
- Screenshots with unrelated identifiers redacted
- Ask support to:
- Reconcile the completed Verified ID transaction with the existing validation request.
- Reset or re-trigger the verification step if reconciliation is not possible.
- Confirm whether Authenticator logs are required and provide a secure upload channel.
Microsoft’s Artifact Signing guidance directs identity-validation issues to Azure Support or Microsoft Q&A and warns that creating additional requests for the same entity while one is in progress does not help.^1^ A closely matching report—Action Required after Verified ID succeeds, with the link subsequently marked used—also identifies support escalation because no portal-side reset or link-regeneration procedure is documented.^2^
About private messages on Microsoft Q&A
A moderator may request information privately, but a private-message exchange cannot be assumed or initiated from an answer. Do not post the validation ID, subscription ID, incident ID, tenant details, or Authenticator logs publicly. The Azure support case is the appropriate secure channel for those identifiers.
Since an Authenticator Incident ID already exists, there is no need to repeat the FAQ’s browser, device, cache, VPN, or Authenticator troubleshooting steps. If support requests diagnostic evidence, submit the Authenticator logs associated with that incident ID through the secure method they provide; the FAQ specifically recommends supplying logs and an incident ID when contacting support.^1^
Do not delete the current request unless support explicitly directs that action. Identity validation can only be completed in the Azure portal, not repaired or completed through the Azure CLI.^3^
References