Artifact Signing organization identity validation stuck on Action Required — no document upload option

Kelly Norris 0 Reputation points
2026-09-11T02:17:05.64+00:00

I am setting up Azure Artifact Signing for a Public organization identity for NORRISSTAND LLC.

The identity validation is currently in Action Required state.

I successfully completed the Microsoft credential/face verification flow using the one-time verification link and received a green success check.

After that, Microsoft sent an email stating that additional organization documents are required and should be uploaded in the Azure portal.

However:

  • the Artifact Signing portal does not show any document upload control,
  • the only verification link redirects to credentials.microsoft.com,
  • that page now says the one-time link has already been used,
  • and the validation remains in Action Required.

I have the requested supporting documents ready, including current Kentucky formation documents for NORRISSTAND LLC.

Please either:

  1. enable the document upload option for the existing identity validation, or
  2. provide a secure/private upload path for the requested documents.

I do not want to delete or recreate the existing validation unless instructed to do so, because the identity verification step has already completed successfully.

Artifact Signing account: norrisstandsigning2026 Organization: NORRISSTAND LLC Country/Region: United States

I can provide the Identity Validation ID, Subscription ID, screenshots, and supporting documents privately to authorized Microsoft staff.

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

2 answers

Sort by: Newest
  1. Meha-MSFT 2,365 Reputation points Microsoft Employee Moderator
    2026-09-11T16:08:22.6633333+00:00

    User's image

    Was this answer helpful?

    0 comments No comments

  2. Rukshan edirisinghe 165 Reputation points
    2026-09-11T03:25:45.7866667+00:00

    Hi @Kelly Norris

    Your instinct not to recreate is right, so let's keep that request alive. Creating additional identity validation requests for the same entity doesn't help and can't be expedited, and you'd have to redo the face check.

    Two things to clear up, then the fix.

    First, the credentials.microsoft.com link saying "already used" is expected and not a problem. That one-time link only covers the Microsoft Verified ID / face check step, which you passed with the green check. The document upload never happens through that link. It's a separate step that happens inside the Azure portal, within the identity validation request itself, and it only becomes available while the request status is Action Required, which yours is.

    Second, when the status is Action Required but you still see no upload control, the most common cause is a missing role. The upload option only renders if your signed-in user holds the Identity Verifier role on the Artifact Signing account. So:

    1. Open the norrisstandsigning2026 account, go to Access control (IAM), and check whether your user has the Artifact Signing Identity Verifier role. If not, have someone with Owner or User Access Administrator rights on the account assign it, then sign out and back in.
    2. Then go to the account, Identity validations, and click into the NORRISSTAND LLC request itself. The upload control lives inside that request view, not on the account overview and not in any email link. If it still doesn't render after the role fix, try a fresh incognito window, since stale portal cache has caused this exact symptom before.
    3. When the upload does appear, be deliberate: there are only three upload attempts per request. Submit the Kentucky formation documents together with everything else Microsoft's email listed in one go, and make sure the legal name and address on the documents match the request exactly.
    4. If the role is confirmed and the control still won't show while the status reads Action Required, that mismatch has to be checked on Microsoft's side. Reply on your thread stating you've verified the Identity Verifier role, and a moderator can take your Identity Validation ID via private message to look at the request internally. Azure Support is the parallel channel. And you're already doing the right thing keeping the IDs and documents off the public post.

    Reference: https://learn.microsoft.com/en-us/azure/artifact-signing/quickstart

    Was this answer helpful?

    0 comments No comments

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.