A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
For Artifact Signing, document upload is available only when the identity validation request status is Action Required. If the request is already Failed, the documented path is to start a new identity validation request rather than reopen the same one.
Relevant points for this scenario:
- If more documents are required, the request status changes to Action Required, and documents can be uploaded in the Azure portal.
- There are only three attempts for documentation upload.
- If identity validation ultimately fails and the validation team can’t determine the request from the information provided, onboarding can’t continue on that request.
- For questions or assistance with identity validation, the supported channels are Azure Support or Microsoft Q&A with the artifact-signing tag.
- Creating more identity validation requests for the same entity while one is already in progress does not help.
For the document itself, the stated requirements are that submitted documents must be:
- issued within the previous 12 months, and
- have an expiration date at least two months in the future, when applicable.
A practical path is:
- In the Azure portal, open the Artifact Signing account and check the identity validation status.
- If the status is Failed and there is no upload control, create a new organization identity validation request.
- Re-enter the organization details exactly as they appear on the official business record.
- Monitor for Action Required status and the related email, because that is the stage where additional documents are requested and uploaded.
- If another identity validation already exists for the same organization with a different primary email address, contact support to continue onboarding.
- If assistance is needed during the process, open an Azure Support ticket or post on Microsoft Q&A using the artifact-signing tag.
References: