Individual identity verification succeeded, but Azure shows Action Required and the link is already used

Preserve the existing In Progress request and open an Azure Support case to have its backend state reconciled; do not reuse the consumed link or create duplicate requests while this one remains active.

Open the support case

1. In the Azure portal, go to Help + support → Create a support request. If the navigation differs, open the Azure Help + Support blade.
2. Select the closest available service/problem classification for Azure Artifact Signing → Identity validation.
3. Use a title such as:

   Public Trust individual verification succeeded, but request remains Action Required/In Progress and verification link is already used

4. Include:
   • Artifact Signing account and Azure region (West US 2).
   • Identity Validation ID.
   • Subscription and tenant IDs.
   • Approximate verification completion time and time zone.
   • A screenshot of “Verification successful.”
   • Screenshots showing the list status, detail status, and “this link has been used already.”
   • Any transaction or correlation ID displayed on the provider/error page.
5. Ask support to:
   • Confirm whether the successful verification result reached Artifact Signing.
   • Reconcile the list/detail status with the provider result.
   • Determine whether the existing request should be completed, reset, or replaced.
   • Preserve the current request unless replacement is required.

Microsoft directs identity-validation issues to Azure Support and states that creating additional requests for the same entity while one is in progress does not help.^1^ Similar cases required backend investigation using the validation ID and Artifact Signing account details rather than further browser-side troubleshooting.

Do not repeat the completed flow

The used-link message is consistent with a one-time verification action that has already been consumed. A matching Artifact Signing report showed the same Action Required → used link loop, which Microsoft acknowledged as a service-side verification issue.^2^

Because verification already reached “Verification successful”:

• Do not keep reopening the link.
• Do not clear Authenticator or repeat device/browser/network troubleshooting.
• Do not delete the request before support captures its backend state.
• Do not post the validation, subscription, tenant, transaction, or correlation IDs publicly; provide them only in the private support case.

The portal normally changes a newly created request to In Progress, then presents Action Required for the external verification step.^3^ Your mismatched list/detail states after successful completion require service-side confirmation; the portal alone cannot establish whether the result was ingested.

Recreate only if support instructs it

A new request is appropriate under documented conditions such as an expired email link or an explicit mismatch/Face Check error. Those conditions have not been reported here. If support determines that this request cannot be reconciled, have them confirm that it is safe to delete and replace it first.

Before replacement, verify that the selected billing account has Account Type = Individual, and that its legal name and sold-to address exactly match the government ID. These are requirements for Public Trust individual validation.^3^ The United States is supported for individual developers, and West US 2 is a supported Artifact Signing region.^3^

References

1. Artifact Signing FAQ
2. Terrible Identity validation experience - Microsoft Q&A
3. Quickstart: Set up Artifact Signing | Microsoft Learn