Artifact Signing organization identity validation failed without a reason

Question

Jakub Różycki 0

Hello,

Our Polish company, LiberUp sp. z o.o., submitted an

Organization / Public identity validation for Azure

Artifact Signing. Its status changed to Validation Fail.

The notification email and Azure portal provide no reason.

I cannot confirm whether email verification was completed.

Our Artifact Signing account is in Poland Central.

Azure AI support found no failed management-plane operations,

but this does not explain the identity validation rejection.

Our Basic support plan prevents submitting a technical ticket.

Could a Microsoft moderator help route this case to the

Artifact Signing Identity Validation team and clarify:

Whether email verification was completed.
Whether the failure concerns organization verification or a technical error.
Whether we should submit a corrected request and what information needs correction.

I can provide the validation ID through a private channel

if required.

Thank you.

0 comments

1 answer

Answer 1

What can be confirmed from the documented behavior:

If the email verification link was not completed within seven days, the request fails and a new identity validation request is required. The verification link cannot be resent for the same request.
If no verification email was received, check Junk/Spam, confirm the mailbox accepts messages and links from external senders, and ask the mail administrator to verify that firewall, security, or filtering policies did not block the message. If the message still cannot be found, delete the current request and submit a new one.
For Organization / Public identity validation, the primary email must be a monitored mailbox on a domain owned by the legal business entity, and the secondary email must be different from the primary email. The service sends status updates by email, and the portal can also be used to check status.
Public identity validation can also fail when the validation team cannot determine the request from the information provided, or when additional documentation was requested and the three upload attempts were exhausted. For public validation, public records for the legal business entity should be up to date.
Creating more identity validation requests for the same entity while one is already in progress does not help, and requests cannot be expedited.
For assistance with identity validation, the supported path is Azure Support or Microsoft Q&A with the artifact-signing tag.

Based on that, the practical next steps are:

In the Azure portal, open the Artifact Signing account and review Identity validations to confirm whether the request ever moved to Action Required before it failed.
Check whether the primary mailbox used in the request is on the company-owned domain, can receive external mail, and did not filter the verification message.
If email verification cannot be confirmed, delete the failed request and submit a new Organization / Public identity validation.
When resubmitting, ensure the legal entity name, website, business identifier, business address, and contact details exactly match current public business records.
If another identity validation already exists for the same organization with a different primary email address, support is required to continue onboarding.

References: