Artifact Signing organization identity validation failed after successful identity verification

Question

Artifact Signing organization identity validation failed after successful identity verification

Bostjan Zemljic 0

I am trying to complete Public Organization Identity Validation for an Azure Artifact Signing account.

I am a legally registered sole proprietor in Slovenia. The organization name, business address and other organization information entered in the validation request match the official Slovenian Business Register.

I completed the Microsoft-requested identity verification process, including identity document and face verification, and the verification page showed that the verification was successful.

Shortly afterward, however, the Artifact Signing organization identity validation status changed to Failed. The Azure portal and the notification email do not provide a specific reason for the failure.

I have reviewed the organization information shown in the failed validation request and compared it with my official business registration document. The organization name and address match the official records.

The primary email address used for the validation is valid and I successfully received Microsoft's verification messages. I understand that Microsoft may have additional requirements regarding organization email domains or newly established businesses, but the failed validation does not indicate which requirement caused the rejection.

Could a Microsoft Artifact Signing engineer please clarify which organization validation requirement could not be verified and advise whether the existing validation request can be reviewed/reset, or whether I need to create a new validation request?

I can provide the Identity Validation ID, Azure Subscription ID and official Slovenian business registration documentation through a private support channel, but I will not post those details publicly.

0 comments

4 answers

Your answer

Answer 1

The organization is a Slovenian sole proprietorship registered on December 1, 2025, so it is less than one year old.

However, the current Artifact Signing documentation does not appear to state a three-year minimum organization age requirement. The Azure troubleshooter nevertheless lists “Check Organization's Age” as its first possible cause, while also stating that it could not pinpoint a specific issue.

Could you please confirm whether the three-year organization-age requirement is actually enforced for EU Public Trust organization validation under the current Artifact Signing GA service?

Answer 2

Bostjan Zemljic 0

Thank you for the clarification.

In my case, it was very fast. Approximately 10 minutes passed between the individual identity verification page showing Success and the organization identity validation changing to Failed.

This is why I was surprised by the result. The personal document and face verification completed successfully, and shortly afterwards the organization validation failed without providing any reason.

Since you mentioned that the vetting review normally takes 1–20 business days, could this mean that my request failed during an automated organization check before it reached the actual Vetting Operations review?

If so, is there any way to have Microsoft/Vetting Operations review the exact failure reason or reset the existing validation request? I can provide the validation ID, subscription ID, and official Slovenian business registration documentation through a private support channel if required.

SHOUMIK CHAKRAVARTY 660 Reputation points

2026-09-16T01:43:15.48+00:00

Hi @Bostjan Zemljic - I dont see in the Quickstart / FAQ there is any mention about the organization age at all. If it were current policy you'd expect it in the prerequisites. The three-year figure does appears in community threads and seems to date from the Trusted Signing preview, with some claims it was relaxed at GA. Neither version is stated by Microsoft anywhere which I can find. With that said, Azure troubleshooter naming "Check Organization's Age" first is Microsoft's own tool pointing at it, and an automated age check would explain a rejection arriving in 10 minutes with no reason.

Worth putting those together for a moderator picking up the thread : registered December 2025, failed 10 minutes after verification succeeded, troubleshooter flagging organization age. That's something specific to be confirmed.
Bostjan Zemljic 0 Reputation points

2026-09-16T16:22:54.9466667+00:00

Azure ARM Diagnostic Workflow is now reporting that the root cause of my Organization Identity Validation failure is that there are zero Certificate Profiles configured on the Artifact Signing account.

However, the current Artifact Signing Quickstart documents the sequence as:

Artifact Signing Account → Identity Validation → Certificate Profile.

The Certificate Profile creation process also requires an Identity Validation ID / Verified CN and O.

My Organization Identity Validation is currently in Failed status.

Could you please confirm whether a Public Trust Certificate Profile is actually expected to exist before Organization Identity Validation can complete?

I do not want to create or modify resources until this dependency is clarified, because the current diagnostic recommendation appears to conflict with the documented onboarding sequence.
SHOUMIK CHAKRAVARTY 660 Reputation points

2026-09-17T01:28:34.23+00:00

No. A Public Trust certificate profile is not expected to exist before organization identity validation completes. Your reading of the sequence is right.

The Artifact Signing FAQ states

"Why is the CN/O dropdown empty when I create a certificate profile? You need at least one completed identity validation request that matches the certificate profile type you are creating."

So with your validation in Failed status, the CN/O dropdown would be empty and the certificate profile couldn't be created at all. A missing certificate profile can't be the cause of the validation failing, because creating one depends on the validation having already completed.

You're right not to create anything on the strength of that recommendation.

Answer 3

Passing the document and face verification doesn't tell you the organization check passed. That may be a reason you see the Success and then the failure. From the Quickstart: "Once Individual Identity Validation is successfully completed, the status changes back to In Progress and the validation process continues." It confirms you're the person you say you are. The organization check comes after, and that's the one which might have failed.

The failure reason isn't surfaced in the portal or the notification email. It sits with Vetting Operations and isn't exposed outside that team.

The FAQ says to create a new request when the failure was a missed email verification link. For the other causes it says Microsoft can't proceed, which isn't the same as inviting a retry.

One question: how long was it between the verification page showing success and the status changing to Failed? The Quickstart puts the vetting review at 1 to 20 business days, so a rejection arriving much faster than that didn't come from that review.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

Answer 4

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more