A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Because the request is already Failed and never presented a document-upload control, request case-specific validation-team review through this existing Artifact Signing Q&A thread before deleting it or creating another request; Q&A is the documented no-cost assistance channel, but escalation, private document collection, reopening, and approval are not guaranteed. ^1^
What to request in this thread
Add a reply containing only non-sensitive details:
- The request status is Failed, not In Progress or Action Required.
- Microsoft requested a document issued within the past 12 months.
- No upload control or secure submission link ever appeared.
- The primary email uses the organization’s own domain, if applicable. Microsoft specifically documents that this can cause the upload option not to appear, but publishes no user-side workaround. ^1^
- Ask a moderator or Microsoft representative to request validation-team review and determine:
- whether the failed request can be returned to Action Required;
- whether Microsoft can provide a secure private document channel; or
- whether the request must be deleted and recreated.
- Ask Microsoft to confirm that no document attempt was consumed because no upload opportunity was provided.
Do not post the validation ID, tenant/subscription identifiers, tax records, certificate, or business documents publicly. Provide them only if authorized Microsoft personnel supply a private channel.
Internal intervention has resolved some superficially similar Artifact Signing validation cases, but that is an example rather than a published or guaranteed escalation process. ^2^
Whether to create a new request
Preserving the current failed request until Microsoft gives its disposition is a cautious recommendation, not a documented requirement.
The normal workflow changes to Action Required when more documents are needed; Microsoft then sends an email with instructions. The final status becomes Completed or Failed. ^3^
The FAQ is more restrictive once a request has failed:
- If failure was caused by a missed or expired email-verification link, create a new request.
- For a non-email-related failure, Microsoft says the validation team could not make a determination and onboarding might not be possible.
- If all three document attempts were exhausted, onboarding cannot continue. ^1^
Your case is different from the documented missed-email scenario: Microsoft requested documentation, but the portal offered no way to submit it. No public documentation confirms that a Failed request can be restored to Action Required. The validation team must decide whether this request is recoverable or whether a replacement request is appropriate.
Delaware documents
The Artifact Signing documentation does not specifically confirm that either of these is acceptable:
- Delaware Franchise Tax Payment Acknowledgement
- Delaware Certificate of Good Standing
It also does not specify whether separate address evidence must accompany either document. Therefore:
- Keep both documents available.
- Ensure each displays the exact legal entity name used in the validation request.
- Ask the validation team to confirm which document it requires and whether it must also show the submitted business address.
- Do not assume that being dated within 12 months guarantees acceptance; that satisfies only the stated age requirement.
Microsoft recommends ensuring that public records for the legal business entity are current and that the legal name, business identifier, and address entered in the request are accurate. Changes require a new identity-validation request. ^3^
Basic support plan
Azure requires an eligible paid support plan for technical support requests; unlimited no-cost support covers subscription-management matters such as billing, quota, and account transfers, not Artifact Signing identity-validation investigation. ^4^
For Artifact Signing identity validation, the official alternatives are:
- Azure Support, when the subscription has an eligible technical support plan.
- Microsoft Q&A using the Artifact Signing tag—which you have already done. ^1^
Reclassifying this as a billing request would not provide a documented route to the validation team. With Basic support, the practical next action is to keep this Q&A thread active and explicitly request private, case-specific review because the required upload opportunity was never supplied.
References