Artifact Signing: reopen document upload on existing In Progress organization review and confirm ETA

Keep the existing In Progress validation request open and request case-specific escalation through this Artifact Signing Q&A thread; the portal does not document a self-service way to reopen document upload while the request remains In Progress.

Supplying the complete certificate

The documented organization-validation workflow is:

1. After representative identity validation succeeds, the request returns to In Progress.
2. If the validation team requires more documents, Microsoft sends an email and changes the request to Action Required.
3. The upload instructions then become available for that request.
4. After review, the status changes to Completed or Failed, and Microsoft sends another email. ^1^

Because the request is presently In Progress, there is no documented customer-side control or CLI command to reopen or replace its attachments. Identity validation can only be completed in the Azure portal, not through Azure CLI. ^1^

For this case:

• Do not create a duplicate request. Microsoft specifically states that additional requests for the same entity while one is in progress do not help.
• Continue monitoring the primary mailbox, including filtered mail, and the validation details page for an Action Required transition.
• Ask a Microsoft moderator on this thread to escalate the existing validation and initiate private contact so the validation request ID and corrected 12-page document can be collected securely.
• Do not publish the request ID, subscription ID, certificate, or other organization-specific details in the public thread.

The FAQ identifies Azure Support and Microsoft Q&A with the Artifact Signing tag as the supported assistance channels. It does not publish a separate general-purpose secure-upload address or portal for this situation. ^2^

Review stage and completion date

Only the validation team can determine the internal review stage, whether the incomplete attachment is blocking the review, and whether anything else is outstanding. In Progress only establishes that validation is continuing; it does not expose the internal review stage.

Microsoft publishes no completion SLA in the supplied Artifact Signing guidance and explicitly states that identity-validation requests cannot be expedited. Therefore, a completion date cannot be confirmed from the portal status or through public Q&A. ^2^

Basic-support limitation

Azure technical support requires an eligible support plan, which explains why the Basic plan blocks completion of a technical-support request. Subscription-management support remains available without a paid technical plan, but it is not a substitute for Artifact Signing identity-validation investigation. ^3^

When a support request cannot be opened because of entitlement or subscription coverage, Microsoft’s published fallback is to use Microsoft Q&A for the public technical question while withholding confidential and tenant-specific data. If technical-support access should exist through the organization, the tenant administrator or support-agreement owner should verify whether a support benefit can be linked to the subscription. ^4^

A moderator escalation should request these specific actions privately:

• Associate the follow-up with the existing validation request.
• Confirm whether the submitted incorporation document is considered incomplete.
• Reopen Action Required document collection or provide an authorized private transfer mechanism.
• Confirm any other outstanding validation action.
• Provide a status update, recognizing that no expedited or guaranteed completion date is documented.

References

1. Quickstart: Set up Artifact Signing
2. Artifact Signing FAQ
3. Create an Azure support request
4. Microsoft Cloud Portals: Self-Help When a Support Request Cannot Be Opened