A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Open the identity validation’s detail page to distinguish a normal In Progress review from Action Required; if it remains In Progress and no email action is outstanding, keep the existing request and ask a Microsoft Q&A moderator for an approved private method to collect its identifiers.
Check the customer-visible status
- In the Azure portal, open Artifact Signing Accounts.
- Select the relevant Artifact Signing account.
- Under Objects, select Identity validations.
- Open the organization validation itself rather than relying on the account overview.
- Record:
- Current status
- Submission date
- Whether the page displays instructions or Action Required
- Whether email and any Verified ID steps have been completed
Identity validation must be completed before a certificate profile can be created, so signing cannot proceed while the request remains In Progress.^1^ The documentation describes how to access the validation under Objects → Identity validations, but it does not identify a more granular customer-visible review stage.^2^
Also check the primary contact mailbox, including junk/spam, for verification or document requests. Confirm with the mail administrator that messages from external senders and messages containing links are not being filtered.^3^
Keep or replace the request
- In Progress with no missing email step: Do not create another request merely to accelerate review. Microsoft states that duplicate requests for the same entity do not help and that identity validation cannot be expedited.^3^
- Verification email never arrived: After checking spam and mail filtering, if the email still cannot be found, delete the current validation and submit a new one.
- Verification link expired: If it was not used within seven days, create a new validation request; Microsoft cannot resend a link for the same request.
- Action Required: Supply only the documents requested through the validation workflow. Do not post documents or sensitive identifiers in Q&A.
The recreate action is specifically for missing or expired email-verification cases. It should not be used for an ordinary In Progress review.^3^
Request an account-specific review privately
Because the Basic support plan does not include Azure technical support, the portal blocking a technical case is expected; Azure provides subscription-management support without a paid plan, but technical support requires one.^4^ The Artifact Signing FAQ identifies Microsoft Q&A with the artifact-signing tag as an official assistance channel, so this post is the appropriate public escalation route.^3^
Add a comment requesting that a Microsoft employee or moderator:
- Confirm whether the request is awaiting internal review or customer action.
- Provide an approved private collection method, if available.
- Confirm whether any account-specific completion estimate can be given.
Do not place validation IDs, subscription IDs, tenant IDs, screenshots containing identifiers, or identity documents in the public thread. If private collection is offered, the following information may help the review:
- Identity validation request ID
- Artifact Signing account name
- Azure subscription ID
- Organization legal name and country/region
- Submission date and current portal status
- Confirmation of completed email/Verified ID steps
- Redacted screenshot of the validation detail page
There is no guaranteed published completion date for an individual request. Similar Q&A cases show that Microsoft staff may need the request details to verify a prolonged In Progress state, but those outcomes do not establish a standard timeframe.^5^
Given the conference deadline, maintain a separate release contingency; the validation itself cannot be expedited.^3^
References