Trusted Signing (Artifact Signing) organization identity validation failed with no reason given - how to find out why?

Calu Andrei 0 Reputation points
2026-08-02T22:59:12.1433333+00:00

I submitted an organization identity validation for a Trusted Signing / Artifact Signing account (Basic tier, East US) about two weeks ago. It sat in "Action Required" until I completed the Verifiable Credentials presentation, after which the status changed to "Validation Fail".

The portal shows only "Failed" with no detail, and the notification email says only that the status was updated to Validation Fail. The Renew button is disabled, so the request cannot be retried in place.

The organization is a US LLC registered in January 2026. It is properly registered with the state and I have the Articles of Organization, but it is new and does not yet have a D-U-N-S number.

Questions:

  1. Is there any way to see the specific reason an organization identity validation failed?
  2. Is there a minimum business age or public-records requirement for organization validation? If a ~6 month old entity is disqualifying, is that documented anywhere?
  3. Would obtaining a D-U-N-S number before resubmitting materially improve the chances?
  4. Should I submit a new validation request via "+ New identity", or does a failed request need to be cleared first?

Happy to share the identity validation ID and subscription ID privately with an engineer.

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: Most helpful
  1. Oliver Bennett 0 Reputation points
    2026-08-03T00:48:49.03+00:00

    It looks like the validation failed because Microsoft doesn’t show the actual reason in the portal. Usually the only way to find out is by opening a support ticket so they can check the backend logs. New LLCs often don’t have enough public records yet, and not having a D‑U‑N‑S number can make verification harder. Once a request is marked failed, you generally have to submit a new identity instead of retrying the same one. Getting a D‑U‑N‑S and making sure your business info is publicly verifiable should help before trying again.

    Was this answer helpful?

    0 comments No comments

  2. Allan Solomon Mejia 1,460 Reputation points
    2026-08-02T23:56:55.1033333+00:00

    Hello @Calu Andrei

    Unfortunately, the Azure portal doesn't expose the specific reason when an organization identity validation fails for Trusted Signing. The detailed validation results are only available internally to Microsoft, so the most practical next step is to open an Azure Support request and provide your Validation Request ID, Subscription ID, and Tenant ID so the backend logs can be reviewed.

    Based on your description, two things stand out:

    • Your LLC is relatively new (registered in January 2026). Microsoft doesn't publish a minimum business age requirement, but identity verification relies on multiple trusted data sources, and newly formed organizations may not yet have sufficient public records for automated verification.
    • Not having a D-U-N-S number could also be a contributing factor. While it isn't a documented requirement for Trusted Signing, having an active D-U-N-S record with matching legal name and address can improve verification confidence.

    Once a request reaches Validation Fail, it generally can't be retried in place, so after addressing any verification gaps, you'll likely need to submit a new organization validation.

    Based on Microsoft's documentation, it's also important to ensure your organization's public records are up to date, as public identity validation relies on information that can be verified externally. If any information changes, you'll need to submit a new identity validation request, since existing requests can't be edited after submission.

    One additional consideration is your organization's age. Microsoft moderators have indicated that Public Trust organization validation currently requires a minimum of three years of verifiable operating history, which may be established through business registration records, tax records, D-U-N-S, or other third-party validation sources. If your LLC was registered in January 2026, that may explain the validation failure.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    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.