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

Scott LaFond 20 Reputation points
2026-06-15T20:48:58.53+00:00
  1. Resource Name: MUDClientSigning
  2. Subscription ID: PII
  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."
Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-06-15T20:49:09.8366667+00:00

    The certificate profile is in a terminal Failed provisioning state. For Artifact Signing certificate profiles, provisioningState is a read-only status field that can be Succeeded, Failed, Canceled, Updating, Deleting, or Accepted and indicates the status of the current operation on the certificate profile. Once it is in Failed, this reflects that the resource failed to provision.

    Because the state is terminal and the platform is returning ResourceOperationFailure with UnknownError, and the profile cannot be deleted or recreated, this is a platform-side issue that cannot be resolved through client changes (such as identity validation or configuration) alone.

    The only viable next step is to contact Azure support with the following details so the backend team can investigate and, if needed, force-complete or remove the stuck resource:

    1. Resource type and name: Artifact Signing certificate profile PublicTrustProfile under Artifact Signing account MUDClientSigning.
    2. Subscription ID: 76e40cb4-7e67-4b21-adf8-9d14a1630958.
    3. Current provisioningState: Failed.
    4. Activity Log details: operation name, ResourceOperationFailure, error code UnknownError, and correlation ID 51230ba1-5c92-48d3-8ae8-b9376e105907.

    Support can use the correlation ID and subscription details to trace the failed operation in the backend and remediate the stuck certificate profile.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.