A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
The failure reason cannot be confirmed from the portal or notification email. For Artifact Signing, failed identity validation requests often do not expose the reason in the portal, and backend investigation requires Azure Support.
Relevant next steps:
- Do not create additional in-progress requests for the same entity just to troubleshoot. That does not help and requests cannot be expedited.
- If the earlier request used an outdated legal name, submit a new public identity validation using the current legal business entity name and all matching legal business details.
- Ensure the information is exact for public identity validation. If changes are needed after creation, a new identity validation request is required.
- Make sure public records for the legal business entity are up to date, because that helps public identity validation succeed more quickly.
- Monitor the primary email address used in the request. The verification link expires in seven days, and if email verification fails or the link expires, a new request is required.
- If more documentation is requested, upload current documents in the Azure portal. Submitted documents must be issued within the previous 12 months, and documents with expiration dates must still be valid for at least two more months.
- For confirmation of the actual failure reason on the first request, contact Azure Support. Microsoft Q&A with the artifact-signing tag is also listed as a support option for identity validation questions.