Artifact Signing validation failed: no document upload option — requesting a secure review channel

A failed validation no longer has a self-service document-upload step; request a moderator-assisted private escalation on this Q&A thread so the Artifact Signing validation team can review the existing validation ID and provide a protected document-submission method.

What to provide privately

Do not post the certificate, NIF, tenant ID, subscription ID, or validation ID publicly. In the thread, ask a Microsoft moderator to enable the private-message/details workflow and provide only the following there:

• Identity Validation ID and current status
• Artifact Signing account/resource name
• Azure subscription and tenant IDs
• Approximate submission and failure timestamps
• Confirmation that Microsoft Credentials verification completed
• Screenshot or exact text requesting additional documents
• Confirmation that the validation blade never changed to Action Required and exposed no upload control
• The document available: recent AEAT Certificado de situación censal
• A request to determine whether the existing failed validation can be reopened/reviewed or must be replaced

Moderator-assisted cases have been escalated to the validation team and resolved after account and validation details were collected privately, although this requires case-by-case backend review rather than guaranteeing that a failed request can be reopened.^1^ ^2^

Why no upload control appears

For organization validation, Microsoft documents this sequence:

1. The request enters In Progress.
2. If more documents are needed, Microsoft sends an email and changes the request to Action Required.
3. The request then exposes the instructions for supplying the documents.
4. The final status becomes Completed or Failed.^3^

Therefore, a request already showing Failed, rather than Action Required, is not in the documented upload phase. There is no documented general-purpose email address or public upload portal for sending identity evidence outside that workflow.

Since the phone-based identity check already completed, repeating Authenticator troubleshooting would not address the missing organization-document upload step.

Basic-support limitation

The portal behavior is expected: Azure technical support requires a support plan. Basic support does not include technical break/fix tickets.^4^ The Artifact Signing FAQ identifies Azure Support and Microsoft Q&A with the Artifact Signing tag as the supported assistance channels, so this Q&A escalation is the available documented route when a technical ticket cannot be created.^5^

Do not try to bypass this through the Support REST API; creating technical tickets through that API also requires an eligible technical support plan, along with the required subscription role.^6^

If there is an unused Visual Studio, partner, Unified, Premier, or other support entitlement available to the account, it can be linked under:

Azure portal → Help + Support → Support Plans → Link support benefits

Otherwise, obtaining a qualifying Azure support plan is the direct private technical-support option.

Spanish sole-trader eligibility

Spain is in the European Union, and Public Trust is available to organizations in the EU. The separate Individual Developer route is limited to individuals in the United States and Canada, so a Spanish applicant must use Organization validation rather than Individual validation.^3^

A closely matched accepted Q&A answer treats a registered Spanish autónomo with an AEAT census registration and NIF as using the organization route and identifies the AEAT registration as the sole-proprietor equivalent of business-registration evidence.^7^ However, the official documentation does not explicitly guarantee acceptance of a Certificado de situación censal or define every Spanish sole-trader form. Final eligibility and document sufficiency must therefore be confirmed by the validation team.

For any replacement request authorized by that team, the submitted values should match the legal business record exactly:

• Legal business/trading name
• Registered business address
• Recognized business identifier
• Website owned by the business
• Monitored primary email on the business-owned domain
• Representative’s name exactly as shown on government identification

Microsoft also advises keeping public records for the legal business entity current.^3^

Do not create repeated replacement validations while seeking review. Microsoft states that duplicate requests do not help and cannot be expedited; where extra-document attempts have been exhausted, onboarding cannot continue through further attempts.^5^

References

1. Artifact Signing Account Organization Identity validations failed - Microsoft Q&A
2. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
3. Quickstart: Set up Artifact Signing
4. Create an Azure support request
5. Artifact Signing FAQ
6. Azure Support REST API Reference
7. Organization identity validation for a Spanish self-employed individual (autónomo) — which business identifier and documents? - Microsoft Q&A