Artifact Signing public identity validation still In Progress after October 27 document upload

Devin Heitmueller 0 Reputation points
2026-11-21T00:15:08.83+00:00

My Azure Artifact Signing public identity validation is still In Progress. I uploaded the two requested documents on October 27, 2026. Both show as uploaded in the Azure portal, and the validation record shows no Action Required prompt.

This is blocking publicly trusted code signing for my Windows releases. Could a Microsoft support engineer check whether any verification or documentation is still outstanding? If you need the identity validation ID to look up the request, please let me know how to share it 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: Most helpful
  1. AI answer

    2026-11-21T00:16:00.7+00:00

    Escalate the existing validation through an Azure support request and provide the Identity Validation ID only in the private ticket, because Artifact Signing documentation lists Azure Support as the assistance path and states that duplicate in-progress requests cannot expedite validation.^1^

    Open the private support request

    1. In the Azure portal, open the affected Artifact Signing account.
    2. In its resource menu, select Support + Troubleshooting.
    3. Complete the guided diagnostics. If they do not resolve the issue, select Create a support request.^2^
    4. Describe the issue as Artifact Signing public identity validation stuck In Progress after requested documents were uploaded.
    5. Include:
      • Identity Validation ID
      • Artifact Signing account and subscription
      • Validation type: Organization or Individual, and Public
      • Document-upload date: October 27, 2026
      • Current portal status
      • Confirmation that both requested documents appear uploaded
      • Confirmation that no current Action Required prompt appears
      • Business impact: publicly trusted Windows code signing is blocked
      • Approximate timestamps and screenshots, with unrelated personal data removed

    The support form’s Additional details section accepts diagnostic information and a file attachment. Avoid including confidential document contents unless the assigned engineer requests them through the support case.^2^

    Do not post the validation ID, subscription ID, documents, or other account identifiers in this public Q&A thread. A Q&A moderator might request details through an appropriate private channel, but an Azure support request is the documented private route. Technical support availability and response severity depend on the subscription’s support plan.^2^

    Check for a hidden pending email step

    Before submitting the ticket, open the validation itself rather than relying only on the account overview:

    Artifact Signing account → Objects → Identity validations → select the in-progress validation

    Also check the primary email address and its junk/quarantine folders. Artifact Signing sends individual identity-verification links and requests for additional documents to that address. The primary mailbox must accept external messages containing links; verification links expire after seven days.^3^

    If the detailed record requests email verification but no usable message exists, state that explicitly in the ticket. An expired verification link cannot be resent for the same request; the documented recovery in that specific condition is a new validation request.^1^ That fallback does not apply merely because review remains in progress with no email-verification prompt.

    Avoid deleting or duplicating this request

    Do not delete or recreate the current validation while support investigates unless Microsoft confirms that an expired or failed email-verification step requires it. The FAQ states that creating additional requests for the same entity while one remains in progress does not help, and identity validation cannot be expedited.^1^

    Microsoft’s public setup documentation describes the status transitions—In Progress, Action Required, and then Completed or Failed—but does not publish a fixed completion SLA after documents are uploaded.^3^ Since the request has remained unchanged since October 27, a private support investigation is the appropriate next step rather than repeating the document upload.


    References

    1. Artifact Signing FAQ
    2. Create an Azure support request
    3. Quickstart: Set up Artifact Signing | Microsoft Learn
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was 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.