A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
If the initial verification email still cannot be found after mailbox and filtering checks, delete the current identity-validation request and submit a new one; if email verification was already completed, keep the existing request and escalate it to Azure Support.
If the verification email was never received
- Check the Junk/Spam folder for the primary email address entered in the request.
- Confirm that the mailbox:
- Accepts messages from external senders.
- Permits emails containing links.
- Is not blocked by a mail gateway, firewall, or security policy.
- Ask the email administrator to search message traces and filtering logs.
- If the email still cannot be located, delete the current identity validation and create a new request. The verification link expires after seven days and cannot be resent for the same request.^1^
In the Azure portal:
- Open the Artifact Signing account.
- Under Objects, select Identity validations.
- Select the existing request and delete it.
- Select Organization → New Identity, choose Public or Private, and submit the corrected request.
- Monitor both primary and secondary mailboxes and open the verification link promptly.
Deletion and creation require the Artifact Signing Identity Verifier role.^2^ Before deleting, review any associated certificate profiles. Deleting a completed validation stops certificate renewal for associated profiles and can eventually interrupt signing; your request is currently still In Progress, but checking associations first is the safe approach.^1^
When recreating an organization request, use:
- A monitored primary mailbox on a domain owned by the legal entity.
- A different secondary mailbox whose domain matches the primary mailbox’s domain.
- Mailboxes that accept external messages containing links.
- The legal entity’s current organization, website, business-registration, address, and representative information.^3^
If email verification was already completed
Do not create duplicate requests. After individual/email verification is completed, the request legitimately returns to In Progress while validation continues. If documents are needed, its status changes to Action Required and Microsoft sends instructions by email; the final status becomes Completed or Failed.^3^
For a verified request that has remained In Progress:
- Open Artifact Signing account → Objects → Identity validations and record:
- Request name or ID
- Current status
- Submission date and UTC time
- Subscription and resource identifiers
- Primary email domain, without posting the complete address publicly
- Create an Azure Support request from the Azure portal and select the Artifact Signing/identity-validation issue.
- Include a screenshot of the status and state explicitly that verification was completed but no Action Required, completion, or failure email arrived.
Identity-validation requests cannot be expedited, and creating more requests for the same entity while one is undergoing review does not help.^1^
Do not send identity documents through Microsoft Q&A. Provide them only through the workflow specified in an Action Required notification or through instructions supplied in the Azure Support case.
References