FaberCAM LLC Azure Artifact Signing organization validation failed without a reason

ahmet KAYUR 0 Reputation points
2026-09-29T13:39:18.1833333+00:00

Hello,

We are trying to complete Public Trust organization identity validation for FaberCAM LLC, a US company, for Azure Artifact Signing. The Azure portal currently shows the validation as Failed, but the validation details do not provide a specific reason or corrective action.

The primary and secondary contacts on the failed request used public email addresses. We have now set up a monitored address on the company’s own domain. The Artifact Signing FAQ says to contact support when another identity validation for the same organization requires a different primary email address.

Could the Artifact Signing team advise how we can have the failed request reviewed and continue onboarding with a company-domain primary email?

Thank you.

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: Most helpful
  1. AI answer

    2026-09-29T13:39:36.43+00:00

    For this scenario, the supported path is to contact Azure support to continue onboarding.

    Relevant facts for this case:

    1. If another identity validation is needed for the same organization with a different primary email address, support must be contacted to continue onboarding.
    2. For organization validation, the primary email should be a monitored address on a domain owned by the legal business entity, and the secondary email must be different from the primary email.
    3. If organization identity validation failed because email verification was missed or the link expired after seven days, a new identity validation request must be created.
    4. If the validation failed for other reasons, the validation team could not determine the request from the submitted information. If additional documents were requested, there are only three upload attempts.
    5. Azure support can be reached by creating a support ticket in the Azure portal.

    Recommended next steps:

    1. In the Azure portal, create a support ticket for Artifact Signing onboarding.
    2. In the ticket, include that the failed organization validation used public email addresses and that a monitored company-domain mailbox is now available for the primary contact.
    3. Ask support to help continue onboarding because a new identity validation for the same organization requires a different primary email address.
    4. If the original failure was caused by a missed email verification link, create a new identity validation request and use the company-domain primary email. The verification link sent to the primary email expires in seven days.
    5. When creating or recreating the request, ensure the organization details exactly match the legal business entity records and that the mailbox can receive messages and links from external senders.

    For the new or corrected organization request, use:

    • Primary Email: monitored mailbox on a domain owned by the legal business entity
    • Secondary Email: different from the primary email, with the same domain for organization validation
    • Organization information: legal business entity name, website, business identifier, and business address matching official records

    If more documentation is requested during review, upload it in the Azure portal. The documents must be current and meet the stated requirements, including being issued within the previous 12 months when applicable.


    References:

    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.