Azure Artifact Signing identity validation rejected with generic error: need specific reason

Miguel Acevedo 0 Reputation points
2026-05-13T04:06:48.82+00:00

We're trying to get public organization identity validation for Azure Artifact Signing. Our latest rejection message stated to "provide documents within 12 months" but the Mercury banking statement we provided is one month old. We're not sure what's actually deficient; could someone from the validation team provide specific feedback on what's failing?

Happy to share documents privately if needed. We have double-checked that everything else matches up.

Validation ID: <PII REMOVED>

@Meha-MSFT @Marilee Turscak-MSFT

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-05-13T04:07:06.6533333+00:00

    The specific reason for a rejection can't be retrieved or reviewed here, and documents can't be reviewed privately through this channel.

    For Artifact Signing public organization identity validation, the documented guidance is:

    1. Ensure all required fields in the identity validation request are accurate and match the supporting documents exactly (organization name, address, website, business identifier, etc.). If any information needs to be changed after creation, a new identity validation request is required.
    2. Confirm that the primary and secondary email addresses meet the requirements:
      • Primary email must belong to the legal business entity and be able to receive external emails with links.
      • Secondary email must be different from the primary and, for organizations, must share the same domain as the primary.
    3. Verify that the documents meet the age and validity requirements:
      • All documents must be issued within the previous 12 months.
      • The expiration date must be at least two months in the future.
    4. If more documentation is requested, upload the most current official business documents (for example, business registration, charter, or articles of incorporation) that show the company name and address exactly as entered in the identity validation request.
    5. Ensure domain-related documentation (domain registration or invoice) lists the same entity and contact name and includes all domains referenced in the request.
    6. If email verification failed at any point, a new identity validation request must be initiated; failed email verification cannot be retried on the same request.
    7. If all three documentation attempts have been exhausted or the validation team still cannot verify the information, onboarding cannot proceed and the recommendation is to delete the Artifact Signing account to avoid charges for unused resources.

    To obtain case-specific feedback or have the validation team review the situation, open a support ticket in the Azure portal under the Artifact Signing resource, or use Microsoft Q&A with the artifact-signing tag as documented. For scenarios where another identity validation is needed for the same organization with a different primary email, support must also be contacted to continue onboarding.


    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.