Artifact Signing organization verification stuck at Action Required; verification link already used after mobile verification

Question

Artifact Signing organization verification stuck at Action Required; verification link already used after mobile verification

kunihiro yamada 0

I am setting up Azure Artifact Signing for a registered organization in Japan.

Environment:

Artifact Signing Basic SKU
Japan East region
Pay-As-You-Go Azure subscription
Organization / Public identity validation

The representative completed the identity verification flow on a mobile device, but the Azure portal still displays Action Required. Opening the verification link from the existing request displays:

No Access

Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request.

Earlier in the flow, Microsoft Authenticator displayed VerifiableCredential / Card missing. We subsequently progressed through the mobile process, but I cannot confirm whether the verified credential presentation result reached Artifact Signing.

We have refreshed the portal and confirmed that the Identity Verifier role is assigned. We have not deleted the existing request or created duplicate requests.

Could a Microsoft moderator advise how to check whether the verification result was received, and how to safely recover the existing request when the verification link cannot be reused? If a backend reset is needed, please advise a private support channel for providing the request identifiers.

I have intentionally omitted email addresses, subscription/tenant/request IDs, verification URLs, tokens, and identity documents from this public post.

kunihiro yamada 0 Reputation points

2026-10-30T15:52:21.84+00:00

Update (31 October 2026, Japan time): The existing organization/Public identity-validation request now shows "In Progress" in the Azure portal. Previously it showed "Action Required" after the mobile verification, and the verification link reported that it had already been used. We have not deleted the request or created a duplicate.

We attempted to open an Azure technical support request for Artifact Signing > Identity validation - Organization. At the Additional details step, the portal blocks submission under our Basic support plan and asks us to purchase a paid support plan.

Could a Microsoft moderator or the Artifact Signing identity-validation team please confirm whether the verification result has been received and the existing request is now proceeding normally, advise whether any additional action is required, and provide a private escalation route if investigation is needed? Our Windows application release is waiting for signing. We prefer a no-additional-cost route for this onboarding issue. We can supply request identifiers privately if requested. No personal documents, verification links, or identifiers are included in this public comment.

1 answer

Your answer

kunihiro yamada 0 Reputation points

2026-10-30T15:52:21.84+00:00

Update (31 October 2026, Japan time): The existing organization/Public identity-validation request now shows "In Progress" in the Azure portal. Previously it showed "Action Required" after the mobile verification, and the verification link reported that it had already been used. We have not deleted the request or created a duplicate.

We attempted to open an Azure technical support request for Artifact Signing > Identity validation - Organization. At the Additional details step, the portal blocks submission under our Basic support plan and asks us to purchase a paid support plan.

Could a Microsoft moderator or the Artifact Signing identity-validation team please confirm whether the verification result has been received and the existing request is now proceeding normally, advise whether any additional action is required, and provide a private escalation route if investigation is needed? Our Windows application release is waiting for signing. We prefer a no-additional-cost route for this onboarding issue. We can supply request identifiers privately if requested. No personal documents, verification links, or identifiers are included in this public comment.

Answer 1

Open an Azure Support request for review and reset or re-triggering of the existing identity-validation transaction; the consumed one-time link cannot be reused, and another validation request for the same in-progress entity will not resolve the state.^1^

Submit the private support request

In the Azure portal, open the affected Artifact Signing account.
From its resource menu, select Support + Troubleshooting.
If the suggested solutions do not apply, select Create a support request.^2^
Select:
- Issue type: Technical
- Service: Azure Artifact Signing
- Problem area: Identity validation/onboarding, or the closest available choice
- Subscription: The Pay-As-You-Go subscription containing the request
Use a title such as:

Artifact Signing organization validation stuck at Action Required after Verified ID presentation; one-time link already consumed
Ask support to:
- Confirm whether the Verified ID presentation result was received and associated with the existing validation request.
- Inspect the current backend transaction state.
- Reset or re-trigger the existing validation flow/link if the callback was not committed.
- Preserve the existing organization validation request rather than creating a duplicate.
- Confirm the next portal action after remediation.

Provide these details only inside the private support case:

Subscription and tenant IDs
Artifact Signing account resource ID and region
Identity-validation/request ID
UTC timestamps of the mobile verification and subsequent link attempt
Correlation or transaction ID, if displayed
Screenshot of Action Required
Screenshot of “No Access—this link has been used already”
Microsoft Authenticator and mobile OS versions
A concise note that Authenticator initially showed VerifiableCredential / Card missing, followed by completion of the mobile flow

Do not include the verification URL, tokens, identity documents, or personal identifiers in the public Q&A thread. The support form permits diagnostic attachments and private case details.^2^

Why this requires support review

The same Artifact Signing state—Action Required followed by “this link has been used already”—has been reported as an identity-validation issue rather than a reusable-link workflow.^3^ Artifact Signing identity validation can be completed only through the Azure portal; Azure CLI cannot complete or recover it.^4^

There is no documented customer-facing operation that shows whether the Verified ID presentation callback reached the Artifact Signing backend. Portal state plus backend support investigation is therefore the applicable check.

Japan is supported for Public Trust organization onboarding, and Japan East is a supported Artifact Signing resource region, so those facts do not require changing the account or region.^4^

Avoid changing the existing request for now

Because the request remains Action Required, rather than explicitly Failed or expired:

Do not reuse the consumed URL.
Do not create duplicate validation requests.
Do not delete the current request unless Azure Support directs that recovery requires replacement.
Do not recreate the Artifact Signing account merely to restart validation.

Microsoft’s FAQ specifically says that creating more requests for the same entity while one is in progress does not help. It directs identity-validation assistance to Azure Support or Microsoft Q&A; account-specific inspection and reset should use Azure Support.^1^

If the support-request option is unavailable

Creating a subscription-scoped support request requires Owner, Contributor, Support Request Contributor, or a custom role containing the necessary Microsoft.Support/* permissions. Technical support also requires an eligible support plan.^2^

Ask a subscription administrator to either grant Support Request Contributor at subscription scope or open the case on the organization’s behalf. A Microsoft Q&A moderator may help route a public discussion, but request identifiers and backend transaction data should remain in the private Azure Support case.

References