A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Open the identity-validation record itself to check for a pending email-verification action; if no action is shown, keep the existing request and escalate it through an Artifact Signing Q&A post rather than creating a duplicate request.
1. Check the detailed validation state
In the Azure portal:
- Open Artifact Signing Accounts → threebc-signing.
- Under Objects, select Identity validations.
- Open the organization validation submitted on October 20.
- Look for either:
- Complete your email verification
- Action Required
- Instructions requesting another document or individual identity validation
The overview can remain In Progress while processing continues. When more documents are needed, the documented workflow changes the request to Action Required and sends instructions to the primary email address. After an action is completed, it can return to In Progress for continued review.^1^
2. If it says “Complete your email verification”
Check the primary email address entered in the validation request, including:
- Inbox and Junk/Spam
- Mail quarantine
- Corporate firewall and mail-security logs
- Rules that block external messages or messages containing links
Open the verification link if it remains valid. A closely matching Artifact Signing case was resolved by completing that primary-email verification.^2^
Verification links expire after seven days. If the message cannot be found after those checks, or the link has expired, Microsoft documents that the link cannot be resent for the same request: delete that validation and submit a new one.^3^
Do not delete and recreate the request merely because review is taking longer than expected. Microsoft states that additional requests for an entity already being processed do not help and that identity-validation requests cannot be expedited.^3^
3. If no action is pending
Because the requested documents were uploaded on October 22 and the request has remained unchanged, this needs validation-team follow-up rather than more portal troubleshooting. The approximately seven-day response period mentioned in a similar Q&A answer is an informal estimate, not a documented SLA.^4^
Since the Subscription Management request was already redirected to technical support that the current plan cannot open, update this Microsoft Q&A question with:
- Identity validation request ID
- Submission date: October 20, 2026
- Additional-document upload date: October 22, 2026
- Current detailed status and whether any action is displayed
- Confirmation that the primary mailbox, spam, quarantine, and filtering were checked
- The existing Azure support-request number
- A request for moderator escalation to the Artifact Signing validation/vetting team
Do not post tenant IDs, subscription IDs, invoices, registration documents, email addresses, or other sensitive data publicly. Provide those only through a private channel if Microsoft staff initiates one.
Microsoft identifies Azure Support and Microsoft Q&A with the Artifact Signing tag as the supported assistance channels.^3^ Similar stalled requests have been completed after validation-team follow-up, but a Q&A escalation does not guarantee a manual review or faster completion.^5^
References