Artifact Signing identity validation failed for a new UK company (no reason given)

Question

Artifact Signing identity validation failed for a new UK company (no reason given)

Richard Vitola-Jones 0

My Artifact Signing organization identity validation (Public) has moved to Failed. The portal and the notification email only say "Validation Fail", with no reason or required action.

Organization: JAM WAVE LTD, UK company number 17550195 (incorporated 29 October 2026).

Country: United Kingdom. A D-U-N-S number is registered for the company and the name matches Companies House.

Primary email is on the company's own domain, and the company website is live.

Identity validation ID: 1fcd4d45-66c6-4eeb-b496-682c7ce34b5b

Subscription: pay-as-you-go. Artifact Signing account in North Europe, Basic tier. The Identity Verifier role is assigned.

Questions:

Q1) Is there a minimum company age or other eligibility rule that could cause this for a newly incorporated UK company?

Q2) Is there any way to see the specific reason for the failure?

Q3) What should I correct before submitting a new validation? I understand the number of attempts is limited, so I would like to know the cause first.

Thank you.

0 comments

1 answer

Your answer

Answer 1

Q1) No minimum company age is stated in the available Artifact Signing guidance. For Public Trust certificates, organizations in the United Kingdom are supported for onboarding. For public identity validation, the documented requirement is that public records for the legal business entity are up to date. If Microsoft can’t validate the information provided, onboarding can fail.

Q2) There is no documented portal experience that exposes the detailed failure reason. The guidance says that if organization identity validation fails, the Microsoft validation team wasn’t able to make a determination based on the information provided. Assistance is through Azure Support or Microsoft Q&A using the artifact-signing tag.

Q3) Before submitting a new validation, check these items:

Confirm all public business records are current and match the request exactly.
- Legal entity name
- Business address
- Business identifier
- Company website
- Primary and secondary email domains
Ensure the primary email is a monitored mailbox on a domain owned by the legal business entity and can receive links from external senders. The verification link expires after seven days.
Ensure the secondary email is different from the primary email. For organizations, its domain must match the primary email domain.
If any email verification was missed or expired, a new identity validation request is required. A new link can’t be resent on the same request.
If more documentation is requested on a future attempt, upload current official documents only. The guidance states documents must be issued within the previous 12 months, and any expiration date must be at least two months in the future.
If the organization details need correction after submission, create a new identity validation request. The guidance states changes after creation require a new request.
If another identity validation already exists for the same organization with a different primary email address, support must be contacted to continue onboarding.

Given the failed status with no reason shown, the supported next step is to open an Azure Support ticket before using another attempt. That is also the documented path when another identity validation is needed for the same organization with a different primary email address.

References: