A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Open the validation’s detail page to check for Action Required; if it remains In Progress after completing email and Verified ID verification, the request is undergoing validation and no further submission is required unless Microsoft requests documents.
Check the customer-visible stage
- In the Azure portal, open Artifact Signing Accounts.
- Select the relevant account.
- Under Objects, select Identity validations.
- Open the organization validation itself rather than relying only on the account overview.
- Check its status:
- In Progress: validation is continuing.
- Action Required: follow the instructions shown and check the primary email for the requested action or documents.
- Completed or Failed: review is finished, and Microsoft sends the updated result by email.
After individual identity validation succeeds, the documented workflow returns the organization request to In Progress. If documents become necessary, Microsoft changes the status to Action Required and sends an email.^1^
Microsoft documents these portal statuses but does not document a more granular customer-visible stage, such as “registry review” or “manual document review.” Artifact Signing validation requests also cannot be expedited, and creating another request for the same entity while this one remains in progress does not help.^2^
Contact the validation team
For a private, request-specific status check:
- The officially documented channels are Azure Support and Microsoft Q&A with the
artifact-signingtag.^2^ - An accepted Microsoft Q&A answer also directs identity-validation inquiries to the Azure Trusted Signing support team at [Email].^3^
Include:
- Identity Validation request ID
- Azure subscription ID
- Artifact Signing account name
- Organization’s legal name and country/region
- Submission date
- Current status
- Confirmation that email verification and Verified ID were completed
- A screenshot of the validation details with unrelated identifiers redacted
Ask them to confirm whether the request is awaiting internal review or customer action. Do not attach identity documents unless the validation team specifically requests them through an official channel.
With the Basic support plan, Azure technical support generally requires a paid support plan; subscription-management support is available without one.^4^ If the portal does not permit a technical ticket, use the Trusted Signing email above or continue through the existing Microsoft Q&A thread. Q&A is public, so post no request IDs or account details unless a Microsoft moderator provides a private collection method.
Do not delete or recreate the current request merely because it remains In Progress. That fallback applies to missed or expired email-verification links, which does not match this case because email verification was already completed.^2^
References