Azure Artifact Signing: Certificate profile stuck in terminal 'Failed' provisioning state.

Question

1. Resource Name: MUDClientSigning
2. Subscription ID: 76e40cb4-7e67-4b21-adf8-9d14a1630958
3. Identity Validation Status: Completed
4. The Issue: Terminal ResourceOperationFailure during certificate profile creation.
5. Correlation ID: 51230ba1-5c92-48d3-8ae8-b9376e105907
6. Error Code: UnknownError
7. Description: "My certificate profile PublicTrustProfile is stuck in a terminal 'Failed' provisioning state. I cannot delete or recreate it. I have attached the correlation ID 51230ba1-5c92-48d3-8ae8-b9376e105907 from the Activity Log, which shows a ResourceOperationFailure with an UnknownError."

Answer 1

The certificate profile is in a terminal Failed provisioning state, which means the current operation on that profile has completed but did not succeed. For Artifact Signing / Trusted Signing certificate profiles, the provisioningState reflects the status of the current operation and is read-only; once it is Failed, it cannot be changed in place.

For certificate profiles, the provisioning state is exposed as a status field such as provisioningState (for example, via SDKs or PowerShell properties like ProvisioningState) and can take values including Succeeded, Failed, Canceled, Updating, Deleting, and Accepted. A terminal Failed state indicates that the platform could not complete creation or update of the profile.

Because the profile is stuck in Failed and cannot be deleted or recreated from the client side, and the error code is UnknownError with ResourceOperationFailure, this requires backend investigation with the correlation ID and subscription details. There is no supported self-service operation in the provided context to force-reset or override a terminal Failed provisioning state for an Artifact Signing certificate profile.

Recommended next steps:

1. Capture the key details already available:
   • Subscription ID: 76e40cb4-7e67-4b21-adf8-9d14a1630958.
   • Resource name: MUDClientSigning and certificate profile name PublicTrustProfile.
   • Correlation ID: 51230ba1-5c92-48d3-8ae8-b9376e105907.
   • Error code: UnknownError and ResourceOperationFailure.
   • Current provisioningState value (Failed).
2. Open a support case with Azure Support for Artifact Signing / Trusted Signing and provide the above details, including the correlation ID from the Activity Log. The support team can:
   • Inspect backend logs for the UnknownError associated with the correlation ID.
   • Clear or remove the stuck certificate profile resource if appropriate.
   • Advise whether a new certificate profile needs to be created under the same or a different name.
3. After support has either removed or corrected the stuck profile, re-create the certificate profile and confirm that its provisioningState transitions to Succeeded.

If subsequent signing attempts return HTTP 403 errors, use the Artifact Signing FAQ guidance to verify:

• The certificate profile status is active and provisioningState is Succeeded.
• The identity used for signing has the Artifact Signing Certificate Profile Signer role.
• The subscription is in Registered state and identity validation is Completed.

---

References:

• CertificateProfile Interface
• Artifact Signing FAQ
• ICertificateProfile.ProvisioningState Property
• CertificateProfileProperties interface
• CertificateProvisioningState.Failed Field
• Deployed Claude and getting API deployment resource is not ready even though it has been an hour - Microsoft Q&A