A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Open an Azure Support request for the existing identity validation and ask for backend investigation by the Artifact Signing validation team; do not create, renew, or delete the current request while it remains In Progress.
Submit the escalation
- In the Azure portal, select Help + support.
- Select Create a support request.
- Choose the affected subscription and an Artifact Signing/technical issue category where available.
- Use a title such as: Artifact Signing identity validation stuck In Progress — certificate profile reports “System could not find identity validation id”
- Include:
- Artifact Signing account name and Azure region.
- Subscription ID and tenant ID.
- Identity validation ID copied from Artifact Signing account → Objects → Identity validations → affected entity.
- Validation submission date and current In Progress status.
- Exact certificate-profile error text.
- Certificate profile type being created, such as Public Trust or Private Trust.
- Timestamp, time zone, and correlation ID from the failed operation, if displayed.
- Screenshots showing the validation record and failure, with unrelated identifiers redacted.
- Confirmation that no duplicate request was created and that investigation of the existing record is required.
Azure documents support-request creation through the portal; technical support requires an applicable support plan.^1^ The Artifact Signing FAQ explicitly directs identity-validation issues to Azure Support or Microsoft Q&A with the artifact-signing tag and states that duplicate requests do not help and validation cannot be expedited.^2^
If no technical support plan is available, keep this Q&A post under the Artifact Signing tag and provide the non-sensitive details above. Do not post subscription IDs, tenant IDs, full validation IDs, or correlation IDs publicly; provide them only through a moderator-approved private collection method or the support case.
Why profile creation cannot proceed yet
A completed identity-validation request is a prerequisite for creating a certificate profile.^3^ Although the portal displays the record, an In Progress request does not meet that prerequisite. The profile operation also requires the identity-validation ID associated with the entity.^4^
Artifact Signing documentation gives the identity-validation review process a 1–20 business-day window. Identity validation itself can be completed only through the Azure portal, not through Azure CLI.^5^ If the request is still within that window and has no Action Required state, monitor it; if it has exceeded the window—or profile creation consistently cannot resolve its ID—attach those facts to the escalation.
Matching stalled In Progress cases required intervention from the engineering or validation team before the request became verified.^6^^7^
Do not delete this request
Artifact Signing does not permit deletion of an identity validation while it is In Progress. For other states, deletion is irreversible and can stop certificate renewal for linked profiles.^5^ Therefore, deletion or another submission is not an appropriate workaround for this case unless Microsoft Support specifically directs it after investigating the existing record.
References