A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Keep the existing validation request: do not delete it, create a duplicate, or retry the one-time email link while its status remains In Progress and the uploaded document is still attached.
For an organization request, Microsoft documents this sequence:
- The request starts as In Progress.
- It changes to Action Required when the applicant must complete verification or provide documents.
- After individual identity validation completes, it returns to In Progress while validation continues.
- Further documents produce another Action Required state and email.
- The final state becomes Completed or Failed, with an email notification.^1^
Therefore, the current In Progress status, uploaded document, and absence of a new Action Required or failure notification are consistent with continued review. The “link has been used already” page indicates that the link cannot be used again, but the public documentation does not establish that this message alone proves the email-verification result was successfully recorded. The remaining “complete email verification” text could be delayed UI state or a validation-state inconsistency requiring account-specific inspection.
Correct next step
Continue this Microsoft Q&A case under the Artifact Signing tag and request escalation for the existing validation ID. The Artifact Signing FAQ identifies Azure Support and Microsoft Q&A with this tag as the supported assistance routes, and explicitly says that creating more requests for the same entity while one is in progress does not help.^2^
Ask a Microsoft moderator or product representative to confirm privately:
- Whether email verification was recorded successfully.
- Whether the request is currently queued for document review.
- Whether another applicant action is pending but not reflected correctly in the portal.
- How to transmit the subscription ID, Artifact Signing account name, validation ID, and timestamps through a Microsoft-authorized private exchange.
Continue withholding identifiers, verification URLs, and documents from the public thread. Microsoft Q&A does not document a general user-initiated private case channel, so a moderator must provide or initiate an approved private handoff if the product team needs those details. A public reply claiming to be support is not sufficient unless it comes through an authenticated Microsoft mechanism.
Azure Support limitation
Azure’s documentation confirms that technical support requires an eligible support plan; Basic support does not provide ordinary technical support tickets. Subscription-management support is unlimited, but that does not make an Artifact Signing validation investigation a subscription-management issue.^3^
If an eligible support plan becomes available, open the request from:
Azure portal → Artifact Signing account → Support + Troubleshooting → Create a support request
Select the affected subscription and Artifact Signing service, then include:
- Validation type: Public organization
- Current status and exact portal message
- Document-upload timestamp
- Verification-link usage timestamp and exact resulting message
- Validation ID and Artifact Signing account/resource details
- Screenshots with sensitive values redacted where appropriate
Creating a support request requires subscription-level Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission.^3^
When a new request would be appropriate
Only replace the request if it changes to a state covered by the documented restart rules—for example:
- Email verification expired: the link was not selected within seven days.
- Email validation explicitly says Failed.
- Microsoft support instructs you to recreate it.
A new link cannot be resent for an expired request.^2^ None of those documented conditions currently matches an In Progress request whose link reports that it was already used.
References