Artifact Signing organization validation stays on Action Required after Verified ID succeeds

Windows App Publisher 0 Reputation points
2026-11-17T21:28:56.0466667+00:00

I’m setting up a Public Trust certificate profile in Azure Artifact Signing. The organization identity validation requested a personal Verified ID check. I followed the verification link and the Microsoft Verified Credentials page displayed “Verification successful.”

After refreshing and reopening Azure, the organization request still shows “Action Required” and points to the verification step. The portal shows no separate document request, and the Public Trust profile form has no eligible verified identity. Azure’s built-in troubleshooter found no specific cause.

What can cause this status to persist after Verified ID succeeds? Is there a way to verify that the credential presentation reached the existing organization request? If a Microsoft moderator needs the request details to investigate, how can I share them privately?

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-11-17T21:31:08.86+00:00

    Reopen the existing organization identity-validation request and repeat its verification link through the final confirmation; if it remains Action Required, preserve the evidence and have Microsoft Support verify the service-side correlation rather than creating duplicate requests.

    Retry the existing request once

    1. In the Azure portal, open Artifact Signing account → Objects → Identity validations.
    2. Select the existing organization validation showing Action Required.
    3. Open its verification link and complete the entire Verified ID presentation.
    4. As a practical recovery measure, keep the browser session open until the final success page appears. This is not a documented requirement, but it avoids interrupting the browser-to-Authenticator handoff.
    5. Record:
      • Identity Validation ID
      • UTC date and time
      • Screenshot of the final success page, with personal information removed

    After successful individual validation, the documented organization workflow should change from Action Required back to In Progress while organization processing continues. Only Completed validations become eligible for a matching certificate profile.^1^ ^2^

    Do not create parallel requests while the current one is still active; Microsoft states that additional requests for the same entity do not help. If a retry encounters a technical error, fully close and reopen Authenticator, update it, clear the browser cache or use another browser/device, and avoid VPNs, proxies, or unstable connectivity.^3^

    What the persistent status means

    “Verification successful” confirms that the user-facing Verified ID operation completed. It does not, by itself, prove that Artifact Signing correlated and processed that presentation against this particular Identity Validation ID.

    The expected Artifact Signing transition did not occur, so possible categories include:

    • The browser/Authenticator completion was not processed by the existing Artifact Signing request.
    • The presentation succeeded, but its request correlation or subsequent workflow update stalled.
    • A separate validation condition remains outstanding, although Artifact Signing normally changes the request to Action Required and sends an email when additional documents are needed.^1^

    The portal status alone cannot identify which category applies. Similar unexplained Artifact Signing validation states have required Microsoft to inspect or correct the request on the service side.^4^

    Evidence available to you

    You can confirm credential activity, but there is no documented customer-facing view that conclusively maps it to an Artifact Signing Identity Validation ID.

    • Authenticator: Open the credential and select Recent Activity. This can show recent credential operations.^5^
    • Entra audit logs, if available in your tenant: Go to Microsoft Entra admin center → Entra ID → Monitoring & health → Audit logs and filter for Verified ID. Relevant activities can include Verified ID verification completed or Verifiable Credential Presented.^6^

    These records might not contain the Artifact Signing validation ID, and their absence does not prove that presentation failed. Microsoft Support must check whether service-side telemetry links the Verified ID presentation/request ID to the existing Artifact Signing request.

    Also submit Authenticator diagnostics:

    1. Open Microsoft Authenticator.
    2. Select Send feedback → Having trouble?
    3. Send the logs and retain the resulting incident ID.^7^

    Escalate securely

    Open the Artifact Signing resource and select Support + Troubleshooting → Create a support request. Include:

    • Identity Validation ID
    • Artifact Signing account and Azure region
    • Exact UTC verification time
    • Current status and expected transition
    • Authenticator incident ID
    • Sanitized screenshots and relevant audit entries
    • A request to check the Verified ID presentation/request correlation and the workflow update for the existing validation

    Creating technical support requests requires an appropriate subscription role and may require a support plan.^8^

    On Microsoft Q&A, do not post tenant, subscription, validation, correlation, or incident identifiers publicly. Ask a Microsoft moderator to initiate a private message. Only the question author and Microsoft moderators can view that exchange, and attachments are supported; private conversations are deleted 30 days after the moderator’s first message.^9^


    References

    1. Quickstart: Set up Artifact Signing | Microsoft Learn
    2. Artifact Signing resources and roles
    3. Artifact Signing FAQ
    4. Artifact Signing organization validation (Poland): verification link signs in to the Microsoft Accounts tenant and shows You need permission - Microsoft Q&A
    5. Configure Microsoft Entra Verified ID verifier
    6. Microsoft Entra audit log categories and activities
    7. Send Microsoft Authenticator logs and get an incident ID
    8. Create an Azure support request
    9. Private messages on Microsoft Q&A
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.