Organization identity validation remains In Progress since November 2

PeterJohn Fox 0 Reputation points
2026-11-20T15:05:22.42+00:00

Our Fox Innovations LLC organization identity validation was submitted on November 2, 2026, and remains In Progress as of November 20. Email verification was completed, and the portal confirms our domain documentation was uploaded on November 2. We have received no subsequent requests for information.

We understand the published processing window is up to 30 business days. Could Microsoft confirm whether this request is awaiting review or whether any additional action is required from us?

Our Azure Basic support plan prevents opening a technical support ticket. We can provide the identity validation ID and subscription details privately to Microsoft support staff.

Artifact Signing
Artifact Signing

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


1 answer

Sort by: Oldest
  1. AI answer

    2026-11-20T15:06:04.63+00:00

    An In Progress status after email verification and document upload indicates that validation is continuing; it does not expose whether the request is queued or actively being reviewed, and no additional action is documented unless the status changes to Action Required or Microsoft sends a request by email.

    From November 2 to November 20, the request remains within the stated 30-business-day window. Microsoft documents this status sequence:

    • In Progress after submission.
    • Action Required when individual verification or additional documents are needed.
    • Back to In Progress after the requested action is completed.
    • Completed or Failed when review finishes, with an email reporting the outcome. ^1^

    What to do now

    1. In the Azure portal, open Artifact Signing account → Objects → Identity validations.
    2. Open the validation—not only the overview—and verify that it still says In Progress with no embedded instruction or link.
    3. Monitor both primary and secondary email addresses, including junk folders, for an Action Required, Completed, or Failed notification.
    4. Keep the existing request. Do not create another validation for the same organization while this one remains active. Microsoft states that duplicate requests do not help and identity-validation requests cannot be expedited. ^2^
    5. If it remains In Progress after the published processing window, continue this Microsoft Q&A case under the Artifact Signing tag and request service-side investigation. The documented assistance channels are Azure Support and Microsoft Q&A. ^2^

    Include these details in the escalation:

    • Submission date
    • Current status and a screenshot
    • Date email verification was completed
    • Date documents were uploaded
    • Artifact Signing account region
    • Whether the validation is Public or Private

    Provide the identity validation ID, subscription ID, tenant details, and other account identifiers only through a private channel requested by Microsoft staff, not in the public Q&A thread.

    Do not delete and recreate the request merely because it is pending. Deletion and resubmission are documented for correcting request information, expired or missing email verification, or specific validation failures—not for an ordinary In Progress review. Similar prolonged or unexplained Artifact Signing validation cases have required an internal team to inspect the validation ID and account details, but that does not establish the current backend state of this request. ^3^


    References

    1. Quickstart: Set up Artifact Signing
    2. Artifact Signing FAQ
    3. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
    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.