A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
For an existing Artifact Signing organization identity validation request, there is no documented resend action for the email verification link on the same request. If the email verification link was missed or expired, the supported action is to start a new identity validation request. A new link can’t be resent on the same request, and the link expires after seven days.
To determine whether the email step is still the blocker, use the request status and the detail pane together:
- In the Azure portal, open the Artifact Signing account.
- Go to Objects > Identity validations.
- Open the existing organization validation request.
- If the detail pane still shows Please complete your email verification, treat the email verification as still pending for that request, even if the overall status shows In Progress.
Before replacing the request, verify the mailbox conditions required for the primary email:
- Confirm the primary email address can receive messages from external senders.
- Confirm messages containing links are not being filtered.
- Check Junk or Spam.
- Ask the email administrator to confirm firewall, security, or mail filtering policies are not blocking the message.
- For organization validation, ensure the primary email is a monitored address on a domain owned by the legal business entity.
For recovery of the existing request:
- If the verification email cannot be found, the documented recovery is to delete the current identity validation request and submit a new one.
- If the link expired, the documented recovery is also to start a new identity validation request.
- Creating additional in-progress requests for the same entity does not help.
- The accepted Microsoft Q&A guidance for this exact situation states that an in-progress request can be deleted and recreated, and that the three-attempt limit applies to document upload attempts requested by the validation team, not to deleting and recreating this email-verification request.
About waiting for alias propagation:
- The documented guidance does not provide a Microsoft-supported “wait for propagation” recovery path for a missing organization email-verification link on an existing request.
- The practical prerequisite is that the mailbox must already be able to receive external messages with links before the new request is created.
If assistance is still needed, the documented support paths are:
- Azure Support
- Microsoft Q&A with the artifact-signing tag