Artifact Signing organization validation failed after successful identity verification

PRZME 0 Reputation points
2026-10-24T04:21:12.9733333+00:00

Hello Microsoft Artifact Signing Team,

We are registering a South Korean business for Artifact Signing Public Trust. The representative’s identity verification displayed “Verification successful!”, but organization validation now shows “Failed” with no reason in the Azure portal.

Could the validation team confirm:

  1. The failure reason.
  2. Whether the identity verification result was received and linked to the organization validation request.
  3. What supporting documents are required and how to submit them securely.
  4. Whether the existing request can be reviewed before we delete it or submit a new request.

Our Basic support plan prevents opening a technical support case. Please provide a secure channel where we can share the validation ID and account details privately.

Thank you.

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-10-24T04:22:30.52+00:00

    First check whether the separate verification link sent to the organization’s primary email address was completed within seven days; if it was missed or expired, the documented resolution is to create a new identity validation request.^1^

    Distinguish the two validation steps

    “Verification successful!” confirms completion of the representative’s individual identity verification. Organization validation then continues separately: the request returns to In Progress, may become Action Required if documents are needed, and ultimately becomes Completed or Failed.^2^

    1. Check the primary mailbox, including Junk/Spam, for any additional Artifact Signing verification message.
    2. Confirm with the mail administrator that messages containing external links were not filtered.
    3. If the organization/email verification link was missed or expired after seven days, create a new request; the link cannot be resent for the existing request.^1^
    4. If that link was also completed, preserve the failed request while attempting escalation. The portal does not provide a documented self-service method to retrieve the internal rejection reason or confirm that the successful individual result was correlated with the organization request.

    Documents and the existing request

    Do not send identity or company documents through Microsoft Q&A; questions and replies are public.

    When Microsoft requires supporting documents, the supported workflow is:

    • Microsoft sends an email.
    • The request changes to Action Required.
    • The email directs you to the Azure portal to upload the requested documents securely.
    • The documentation does not publish a generic document list because the requested evidence depends on what the validation team needs to establish.^2^

    A failed request cannot be edited: if organization details need correction, a new identity validation request is required. Before resubmitting, compare the request with the public business record:

    • Exact registered legal entity name and business address
    • Current business identifier
    • Website belonging to the legal entity
    • Primary email on a domain owned by the business
    • Secondary email on the same domain
    • Representative’s name exactly matching the government-issued ID

    Public records should be current. The primary address must be monitored and able to receive links from external senders.^2^

    The FAQ’s three-attempt limit applies specifically when additional documents were requested and all three attempts were exhausted. Separately, if the validation team cannot determine the organization from the supplied information, onboarding might not be possible.^1^

    Private escalation with a Basic support plan

    The documented channels are Azure Support and Microsoft Q&A.^1^ Because Q&A is public, only Azure Support is suitable for confidential identifiers:

    1. Azure portal → Help + support → Create a support request.
    2. Select whichever support category the portal makes available for the subscription.
    3. State that this is an Artifact Signing Public Trust organization identity-validation failure requiring validation-team review.
    4. Include this non-secret diagnostic checklist in the private case:
      • Azure subscription and Artifact Signing resource names
      • Identity validation ID
      • UTC timestamps for submission and individual-verification completion
      • Current status and screenshot of the failed record
      • Primary business domain
      • Confirmation that the organization/email link was completed, if applicable
      • Confirmation that individual verification displayed “Verification successful!”

    A Basic plan might not expose a technical support case, and the documentation does not list a dedicated private Artifact Signing email address. Nontechnical categories shown by the portal are not guaranteed to route to the validation team. If no private case option is offered, post only a sanitized Q&A follow-up under the artifact-signing tag asking a moderator for an approved private handoff—do not publish the validation ID, subscription ID, account details, personal identity data, or documents.


    References

    1. Artifact Signing FAQ
    2. Quickstart: Set up Artifact Signing
    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.