A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Email [Email] with the Identity Validation ID and request clarification before creating another validation; this address was provided by an accepted Microsoft Q&A answer for Artifact Signing identity-validation clarification, although the officially documented support routes remain Azure Support and Microsoft Q&A.^1^^2^
What to send initially
Send only non-sensitive case metadata:
- Identity Validation ID/reference
- Artifact Signing account name
- Azure region
- Organization’s exact registered legal name and country
- Approximate submission and failure timestamps
- Current status: Failed
- Confirmation that neither the email nor portal displayed a specific reason
- Whether email verification and individual identity verification were completed
- Whether Microsoft requested documents and, if so, how many submission attempts were used
- A request for:
- Any rejection detail that can be disclosed
- Confirmation whether the existing record can be reviewed
- Confirmation whether a new request is required or permitted
- An approved private mechanism for submitting documents, if more evidence can be accepted
Suggested message:
Subject: Artifact Signing organization validation failed without reason – review request
Our Public Trust organization identity validation for a Poland-based legal entity has status Failed, but neither the notification email nor the Azure portal identifies the unmet requirement.
Identity Validation ID: [reference]
Artifact Signing account: [account name]
Failure date/time: [UTC time]Please advise whether any permissible rejection details can be provided, whether the existing request can be reviewed, and whether we should create a new request. If additional evidence can be accepted, please provide a Microsoft-approved private upload method. No identity documents are attached to this email.
Do not attach identity documents, government records, or personal identification to the initial email. Send them only through a private submission method explicitly supplied by Microsoft.
Whether to create a new request
The correct action depends on the failure stage:
- Missed or expired email-verification link: Create a new identity validation request. Verification links expire after seven days and cannot be resent for the same request.^2^
- Incorrect information must be changed: A created validation cannot be corrected in place; the setup documentation says changes require a new identity validation request.^3^
- Different primary email is needed for the same organization: Contact support before continuing; the FAQ specifically directs this case to support.^2^
- Generic failure after completing verification: Do not assume that resubmission will resolve it. The FAQ states that a non-email-related organization failure means the validation team could not make a determination from the supplied information, so onboarding might not be possible. A clarification request does not guarantee reopening or reconsideration.^2^
- Three requested-document submissions already used: The FAQ states that onboarding cannot proceed after all three document-submission attempts are exhausted.^2^
Avoid creating multiple concurrent requests for the same entity; Microsoft states that doing so does not help and that validation cannot be expedited.^2^
Support options with a Basic plan
The Artifact Signing FAQ documents two routes:
- Azure Support
- Microsoft Q&A with the
Artifact Signingtag^2^
The Basic plan does not include technical-support investigation; Azure requires a paid support plan for technical cases, although subscription-management support remains available without one.^4^ Do not classify this as billing or subscription management merely to bypass that restriction.
Additional available routes are:
- The Artifact Signing support-options link surfaced in validation messaging: https://aka.ms/tssupportoptions
- The Trusted Signing contact supplied in the accepted Q&A answer: [Email]
- This existing Q&A post for public guidance, while keeping the validation reference and all documents out of the public thread
Only Microsoft’s validation or support team can inspect the private validation record and determine what rejection information may be disclosed.
References