A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Trusted Signing: certificate profile creation always fails with UnknownError despite Completed Public Trust identity validation
I'm unable to create a certificate profile on a Trusted Signing /
Artifact Signing account. Every attempt fails with a generic backend error.
Environment
- Account: idea41signing (Microsoft.CodeSigning/codeSigningAccounts)
- Region: East US
- SKU: Basic
- Provider Microsoft.CodeSigning: Registered
- Account provisioningState: Succeeded
- Public Trust Organization identity validation: COMPLETED (validation id 62aab5b5-5d5d-4bbb-8b3e-a08327dba3a0); it appears selectable in the certificate-profile form.
What I'm doing
Creating a PublicTrust certificate profile (profileType=PublicTrust,
identityValidationId set to the completed validation) — tried via both
the Azure Portal "Certificate profile" form and the ARM REST API
(api-version 2025-10-13). Street address / postal code unchecked,
Program type = None.
What happens
The PUT is accepted (201, provisioningState=Accepted), then the async
operation ends in Failed with:
code: UnknownError
message: "Some error occured. Correlation id - <id>. Timestamp - ..."
No actionable detail is returned. 8 attempts over ~100 minutes; failure
time varied from ~8s to ~110s. A delete attempt also failed the same way.
Correlation IDs
11dee72b-ab02-405c-a39b-1fc94f476195
3190c14c-7ccf-4de0-864d-1c3835369ccf
263d81de-6622-4530-aa82-d3463b5dc4ec
4bd88bca-7073-495c-8306-f2ef3e6e3f6e
ecbf451e-fe54-4a87-b651-4932b8201bb1
1479ab9e-a6eb-4358-9249-0e54e6154c71
delete failed: 63b5377e-b6c0-468e-90dc-223d7b6ca92c
Question
The identity validation is Completed and all prerequisites appear met, so
why does certificate profile issuance fail with UnknownError, and how do I
resolve it? Can someone trace these correlation IDs on the backend?