Azure Artifact Signing organization identity validation failed with no rejection reason

The exact rejection reason cannot be determined from the Azure portal status alone. For Artifact Signing, the portal can show only Failed without exposing the reason, and backend investigation requires Azure Support.

Based on the documented behavior:

1. Exact reason for failure
   • If the failure was caused by a missed email verification, the verification link sent to the primary email expires after seven days, and a new identity validation request is required.
   • If the failure was not caused by missed email verification, the Microsoft validation team was unable to validate the request from the information provided.
   • If more documentation was needed, the request status changes to Action Required and documents can be uploaded in the Azure portal. There are three attempts for documentation upload.
   • For Public Trust onboarding, public records for the legal business entity should be up to date. Recent or not-yet-propagated public business records can affect validation.
2. Whether the existing validation can be reviewed or reopened
   • If the email validation link expired, a new link cannot be resent on the same request.
   • The guidance is to start a new identity validation request rather than reopen the existing one.
   • If another identity validation is needed for the same organization with a different primary email address, support must be contacted to continue onboarding.
3. Whether to submit a new validation
   • Submit a new request if:
     • the email verification link was missed or expired,
     • the verification email was never received and cannot be found after checking Junk/Spam and mail filtering,
     • the current request is failed and no document-upload step was presented.
   • Before resubmitting, verify that the primary email can receive messages from external senders and that emails containing links are not blocked.
   • Do not create multiple in-progress requests for the same entity, because that does not help and requests cannot be expedited.
4. Whether recent company formation affects Public Trust eligibility
   • Public Trust certificates are available only in supported countries and regions.
   • For Public Trust organization validation, onboarding is faster when public records for the legal business entity are up to date. A recently formed company can therefore be affected if public records are not yet sufficiently available or current for validation.
5. How to provide supporting documents securely/private to Microsoft
   • If documentation is required, the documented path is through the Azure portal after the request status changes to Action Required.
   • If the request failed without exposing a reason or upload option, use Azure Support for investigation and next steps.
   • Microsoft Q&A can also be used for guidance, but Azure Support is the documented route for account-specific investigation.

Practical next steps:

1. In the Azure portal, confirm whether the request ever entered Action Required.
2. Check the primary mailbox, Junk/Spam, and mail filtering for the verification email.
3. If no verification email was received or the link expired, delete the failed request and submit a new identity validation.
4. Ensure the primary email uses the company domain and can receive external messages with links.
5. If the request failed without any visible reason or upload workflow, open an Azure Support case and provide the Artifact Signing account name and identity validation ID there for backend review.

• Artifact Signing FAQ
• Artifact Signing FAQ
• Artifact Signing FAQ
• Quickstart: Set up Artifact Signing
• Quickstart: Set up Artifact Signing
• Artifact Signing resources and roles