A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Check the primary email address for the separate individual identity-validation message and complete its verification link if it is still valid; this step can be pending even when no additional-document request has arrived.
Check the existing request
- Search the primary mailbox, Junk/Spam, quarantine, and link-filtering systems for the Artifact Signing identity-validation email.
- In Azure portal → Artifact Signing account → Objects → Identity validations, open the request itself and look for any email or individual-verification instruction not exposed in the summary status.
- If the verification link exists and remains valid, complete it using the named organization representative’s details.
For public organization validation, the verification link is sent to the primary email address. After individual verification, the status returns to In Progress while organization review continues. Requests for additional documents are separate: those produce an email and an Action Required status.^1^ A same-symptom case was resolved by completing the primary-email verification link.^2^
Escalate the existing validation
If no verification step is visible and the request has remained In Progress for several weeks:
- Create an Azure support request from the Azure portal and select Artifact Signing / identity validation as closely as the available issue categories permit.
- Include:
- Validation type: Public Organization
- Submission date and elapsed business days
- Current status: In Progress
- Whether the request details show any pending verification
- Whether a verification-link email was received and completed
- Confirmation that no additional-document request was received
- Provide the subscription, tenant, Artifact Signing account, and validation identifiers only through the private support case or a private-information request from an identifiable Microsoft moderator. Do not post them in the public Q&A thread.
Azure Support and Microsoft Q&A with the artifact-signing tag are the documented assistance channels.^3^ Previous weeks-long cases were completed after details were privately passed to the validation team, but only Microsoft support or the validation team can inspect whether this particular request is awaiting manual review.^4^
Do not create a concurrent duplicate request: Microsoft states that duplicates for the same entity do not help and that validation cannot be expedited.^3^
If the verification email is missing or expired
After checking filtering and asking the mail administrator whether external messages containing links were blocked, the documented recovery is to delete the current validation and submit a new one; an expired link cannot be resent on the same request.^3^ Because this request may already be under review, contact support first and preserve its validation ID before deleting it.
A certificate profile cannot be created until at least one identity validation reaches Completed, so there is no supported certificate-profile workaround while this review remains pending.^5^
References