A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Do not close or duplicate the current request yet; open a private Azure Support case and ask Microsoft to reconcile, reset, or re-trigger the existing identity-validation transaction.
The exact Action Required → “No Access—this link has been used already” loop has been reported as a known Artifact Signing verification issue ^1^. Microsoft’s FAQ also states that creating additional identity-validation requests while the same entity has a request in progress does not help ^2^.
Open a private support case
- In the Azure portal, open Help + support: https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade
- Select Create a support request.
- Route it under Azure → Security → Azure Artifact Signing, or the closest available Artifact Signing/identity-validation category.
- Use a title such as: Artifact Signing Public Trust organization validation stuck at Action Required—Verified ID link already consumed
- Ask support to:
- Check whether the Verified ID presentation reached the Artifact Signing backend.
- Reconcile the portal status if verification was received.
- Otherwise reset or re-trigger the existing verification transaction.
- Confirm explicitly if the existing request must be deleted before a replacement is submitted.
Azure Support is the documented private support channel for Artifact Signing identity-validation assistance ^2^. A similar immediate “No access” case was resolved through support escalation requesting a reset or re-trigger rather than by recreating local resources ^3^.
Information to include privately
Provide these fields in the support ticket, not in Microsoft Q&A:
- Azure subscription ID
- Microsoft Entra tenant ID
- Artifact Signing account name and Azure region
- Resource group
- Identity validation ID
- Validation type: Organization / Public Trust
- Current status: Action Required
- Approximate UTC time when Verified ID was presented
- Exact error text and a screenshot with unrelated personal data redacted
- Any transaction, correlation, or request ID displayed on the error page
- Primary contact address, entered only in the private case
Do not attach the live verification URL, QR code, tokens, government-issued ID, or identity documents unless the assigned support engineer requests them through an approved secure upload mechanism.
Why the existing state needs investigation
After individual identity validation succeeds, the documented workflow says the request should return from Action Required to In Progress while organization validation continues ^4^. A consumed link combined with a portal status that remains Action Required therefore needs backend reconciliation rather than another attempt to open that one-time link.
When deletion and a new request are appropriate
Delete and recreate only if:
- Microsoft Support instructs you to do so after checking the current transaction; or
- The request changes to Failed because the email-verification link expired. Email links expire after seven days, and a new link cannot be issued for that same request ^2^; or
- The portal reports a specific Verified ID name, address, or Face Check mismatch. For those errors, the documented recovery is to delete the validation, remove its Verified ID from Microsoft Authenticator, and submit a new request ^2^.
The current link already used symptom alone does not establish one of those failure conditions.
References