Azure Artifact Signing organization validation closed after third appeal — eligibility and reapplication path?

Question

Azure Artifact Signing organization validation closed after third appeal — eligibility and reapplication path?

Aymane S 0

Hello,

We submitted an Organization / Public identity validation for a UK private limited company. After the third documentation appeal, the Azure portal changed the request to Failed and displayed:

We've reviewed your appeal for verification. Based on the information you have provided to date, we have determined that your organization does not currently meet the requirements to pass verification. As this is your third appeal, we have closed your application.

The portal does not identify which requirement could not be verified.

Relevant facts:

The legal entity is active and was incorporated in the UK in 2025.
The legal name and registered-office address submitted to Azure match the public Companies House record.
The primary and secondary mailboxes are different addresses on the same organization-controlled domain and can receive external email.
The requested documentation submitted across the validation process included current domain-registration evidence and an authorization/assignment letter.
The Azure subscription uses the Basic support plan, so the portal does not permit us to open a private technical support request.

Could a Microsoft moderator or Artifact Signing engineer please clarify:

Does Organization / Public validation currently require a minimum period of verifiable operating history, such as three years?
If so, from which date is that period measured, and should the organization wait until it reaches that age before applying again?
If company age is not the blocker, can Microsoft provide a private channel where we can supply the subscription, tenant, and validation IDs so the failed verification category can be checked?
After a third appeal is closed, should we avoid using New identity until Microsoft authorizes another request?
What exact evidence is accepted to establish the link among the legal entity, its domain, and the authorized representative?

We will not post any tenant, subscription, validation, email, or document identifiers publicly, but we can provide them privately to verified Microsoft staff.

Thank you.

0 comments

1 answer

Your answer

Answer 1

Hi,

Since the validation has already reached Failed after the third documentation appeal, I would avoid creating another identity validation request until Microsoft confirms the next supported step.

I would suggest the following:

Confirm that the legal organization name, registered address, website/domain, and email details exactly match the organization's official records.

Review the documentation submitted during the validation process and make sure the documents are current and clearly establish the relationship between the legal entity, its domain, and the authorized representative.

Regarding the three-year business-history requirement, I would recommend asking Microsoft to confirm this specifically. Earlier public-preview guidance referenced a three-year verifiable history requirement for certain organizations, but the current Artifact Signing documentation does not clearly state that this is a universal requirement for today's Organization/Public identity validation process.

Since this is already the third appeal and the application has been closed, I would not continue creating new validation requests without confirmation from Microsoft. It would be better for the Artifact Signing validation/support team to review the failed validation category first.

Ask Microsoft to review the validation request ID and backend verification result and clarify which specific verification requirement was not satisfied.

If Microsoft confirms that the organization is eligible to reapply, you can then submit a new validation request with the required evidence rather than repeatedly submitting appeals against the closed request.

For privacy, I would not post the Tenant ID, Subscription ID, Validation ID, email addresses, or identity documents publicly. These details can be provided through an official Microsoft support channel or private communication with a verified Microsoft moderator if requested.

My recommendation: At this stage, don't create another request. First get confirmation from Microsoft on whether the issue is related to the organization's operating history, documentation, domain/organization relationship, or another verification category.

Microsoft Learn references:

https://learn.microsoft.com/en-us/azure/artifact-signing/quickstart⁠

https://learn.microsoft.com/en-us/azure/artifact-signing/faq⁠

https://learn.microsoft.com/en-us/answers/questions/2262308/submitting-a-new-identity-validation⁠

Hope this helps clarify the next steps.