A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Azure Artifact Signing / Microsoft.CodeSigning backend failure creating PublicTrust certificate profile
Andrew Lindemulder
0
Reputation points
I’m unable to create a PublicTrust certificate profile after completed Public identity validation.
Environment:
- Subscription type: Pay-As-You-Go
- Region: eastus
- SKU: Basic
- Microsoft.CodeSigning provider: Registered
- Artifact Signing account provisioningState: Succeeded
- Azure CLI: 2.87.0
- artifact-signing extension: 1.0.0
- API version shown in Activity Log: 2025-10-13
- Identity validation status: Completed
- Profile type: PublicTrust
Observed behavior:
The certificate profile PUT is accepted with HTTP 201 Created, then the async provisioning operation transitions to terminal Failed.
Activity Log:
- Operation: Microsoft.CodeSigning/codeSigningAccounts/certificateProfiles/write
- Error: ResourceOperationFailure
- Detail: The resource operation completed with terminal provisioning state 'Failed'
- Nested error: UnknownError
- Timestamp: 2026-06-16T20:02:58.0264410Z
Two failed profiles are now stuck
This appears to match other recent Artifact Signing backend provisioning failures where create/delete operations fail after ARM accepts the request.
Can the Microsoft.CodeSigning / Artifact Signing backend team investigate and clean up the failed certificateProfiles?
Artifact Signing
Artifact Signing
Sign in to answer