Azure Artifact Signing – Organization Identity Validation Failed after successful identity verification

Giampaolo La Terza 0 Reputation points
2026-10-14T16:36:53.7733333+00:00

Hello Microsoft Support Team,

We are configuring Azure Artifact Signing (Public Trust) for our Italian company, Medisoft Sistemi Informatici Srls.

We submitted an organization identity validation request through the Azure portal.

During the validation process, we were asked to complete identity verification using Microsoft Authenticator. We successfully completed this procedure and received the message "Verification successful!".

However, shortly afterwards, we received an email stating that our organization identity validation had been updated to "Validation Fail".

The Azure portal currently displays the status "Not submitted", without providing any explanation or additional details about the failure.

We noticed that the organization name entered in the validation request was "Medisoft Sistemi Informatici", whereas our full registered legal company name is "Medisoft Sistemi Informatici Srls".

We would appreciate clarification on the following points:

Could the difference between the entered organization name and the full registered legal name have caused the validation failure?

Is there a way to obtain the specific reason for the rejection?

Can the existing identity validation request be corrected or resubmitted, or must we create a new one?

Is there a dedicated support channel for identity validation issues that does not require a paid Azure technical support plan?

Our goal is to complete the organization validation and create a Public Trust certificate profile to digitally sign our Windows desktop applications.

Thank you for your assistance.

Best regards, Medisoft Sistemi Informatici Srls

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

1 answer

Sort by: Most helpful
  1. AI answer

    2026-10-14T16:37:15.6466667+00:00

    Yes. For public identity validation, the organization name must be the legal business entity to which the certificate is issued. If incorrect information was submitted, changes can’t be made on the existing request; a new identity validation request must be created. The documentation also states that if email verification fails, a new request is required, and if organization identity validation fails, the validation team was unable to determine the request based on the information provided.

    Supported facts for this case:

    1. The legal name matters for Public Trust validation
      • For public identity validation, Organization Name must be the legal business entity.
      • The guidance explicitly says to provide the correct information for public identity validation.
      • If changes are needed after creation, a new identity validation request must be completed.
    2. The existing failed request can’t be corrected in place
      • The documented path is to create a new identity validation request when the submitted information needs correction.
      • If the portal now shows Not submitted, the practical next step is to submit a new request using the full registered legal company name exactly as it should appear.
    3. How to get the reason for the failure
      • Status updates are sent by email, and the status can also be checked in the Azure portal.
      • If more documentation is required, email is sent and the request status changes to Action Required.
      • If the request already shows Failed without enough detail, the available support channels for identity validation questions are Azure Support or Microsoft Q&A with the artifact-signing tag.
    4. No-expedite / duplicate request caution
      • Creating more identity validation requests for the same entity while one is already in progress doesn’t help, and requests can’t be expedited.
      • Since this request appears to have failed rather than remaining in progress, the documented correction path is a new request.
    5. Support without a paid technical support plan
      • Microsoft Q&A with the artifact-signing tag is listed as a support option for identity validation questions.

    Recommended next submission details:

    • Enter the full legal entity name exactly as registered: Medisoft Sistemi Informatici Srls.
    • Ensure the Website url belongs to that legal entity.
    • Ensure the Primary Email is on a domain owned by the legal business entity, is monitored, accepts messages from external senders, and can receive links.
    • Ensure the Secondary Email is different from the primary email and uses the matching domain for organization validation.
    • If additional documents are requested, upload current official business documents that match the company name and address used in the request.

    If the verification email or status details were unclear, also check Junk/Spam and confirm that mail filtering is not blocking messages with links.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.