Azure Artifact Signing certificate profile creation fails with ResourceOperationFailure UnknownError

Question

Azure Artifact Signing certificate profile creation fails with ResourceOperationFailure UnknownError

Juan Diego Urdaneta 0

I am unable to create any certificate profile in Azure Artifact Signing / Microsoft.CodeSigning.

The Code Signing account is provisioned successfully, but every certificate profile transitions from Creating/Created to Failed with ResourceOperationFailure / UnknownError / "Some error occurred". This affects both Public Trust and Public Trust Test profiles, so I cannot sign a Windows application installer.

Environment:

Service: Azure Artifact Signing / Microsoft.CodeSigning
Region: East US
SKU: Basic
Resource provider: Microsoft.CodeSigning is Registered
Subscription: paid/enabled subscription
Code Signing account provisioningState: Succeeded
Identity validation: Individual / Public, Completed

RBAC confirmed:

Owner at subscription scope
Artifact Signing Identity Verifier on the Code Signing account
Artifact Signing Certificate Profile Signer on the Code Signing account
No conditions on the role assignments

What fails:

Public Trust certificate profile creation fails shortly after provisioning starts
Public Trust Test certificate profile creation also fails
Multiple unique profile names were tried
Deleting failed profiles also fails with the same UnknownError pattern

Activity Log examples:

Public Trust profile creation

Operation: Microsoft.CodeSigning/codeSigningAccounts/certificateProfiles/write
Correlation ID: eaa3f4b4-f674-4062-920a-1f9b45f4d3b3
Activity log time: 2026-06-17T17:02:16.7776397Z
Status timestamp: 2026-06-17T17:02:09.4065593Z
Error: ResourceOperationFailure / UnknownError / Some error occurred

Public Trust Test profile creation

Operation: Microsoft.CodeSigning/codeSigningAccounts/certificateProfiles/write
Correlation ID: 971fa539-d395-4599-8506-61ff1f6075db
Activity log time: 2026-06-17T17:04:23.2762866Z
Status timestamp: 2026-06-17T17:04:15.1057024Z
Error: ResourceOperationFailure / UnknownError / Some error occurred

Question: Can the Artifact Signing / Microsoft.CodeSigning team check whether this account or identity validation is stuck in a backend provisioning state? Is there a backend repair/reset required, or is there a recommended way to recreate the account/identity validation without losing the completed validation?

0 comments

2 answers

Your answer

Answer 1

Hi Meha-MSFT / Jaxel — this same East US backend issue is happening again as of June 16–17. I have the identical setup and symptoms.

Environment:

Region: East US (endpoint https://eus.codesigning.azure.net/)
Account: DSSigncode, SKU Basic, provisioningState Succeeded
Microsoft.CodeSigning: Registered
Identity validation: Completed
RBAC: Owner + Artifact Signing Identity Verifier + Artifact Signing Certificate Profile Signer (all assigned, no conditions)

Every certificate profile creation (Public Trust) fails shortly after with ResourceOperationFailure / UnknownError / "Some error occurred", and failed profiles cannot be deleted normally.

Correlation IDs:

f50bca51-5f24-4bb3-83be-45cd1aa66444 (2026-06-16T23:58:50Z)
7c0f35c8-558a-4005-88fd-9a0d1fcb71ac (2026-06-16T23:42:29Z)
456812ba-ad4a-474a-83b2-9f017fe0390f
56702c97-6274-46ce-b989-24a1d5250e83

This looks like the same ongoing East US backend problem also reported in questions 5915640, 5920966, 5921136, and 5923041 — all within the past 10 days, all East US / Basic, all the same error. Could the team check whether my account (DSSigncode) is stuck server-side and apply the same backend fix that resolved this case? I'd prefer not to delete and recreate, since that would force me to redo the completed identity validation.

Thank you.

Answer 2

Artifact Signing resources, including certificate profiles, currently cannot be migrated or repaired by changing subscription or tenant. If there is a backend issue with the existing account or identity validation, the supported mitigation is to recreate the Artifact Signing resources.

The documented behavior is:

Artifact Signing resources cannot be migrated across subscriptions, tenants, resource groups, or resources.
If any change is needed to subscription ID or tenant ID, all Artifact Signing resources must be created again.

There is no documented mechanism to “reset” or “repair” a stuck identity validation or certificate profile from the customer side beyond deleting and recreating the Artifact Signing resources. Since deletion of failed profiles is also returning UnknownError, and there is no public API or guidance for backend repair, the next step is to:

Delete the Artifact Signing account and its resources (if the portal/ARM allows it), and
Recreate the Artifact Signing account, redo identity validation, and then create new certificate profiles (for example, via PowerShell New-AzArtifactSigningCertificateProfile or Azure CLI az artifact-signing certificate-profile create) using the documented parameters.

If deletion of the Artifact Signing account itself fails with similar ResourceOperationFailure / UnknownError, this indicates a platform-side issue that cannot be resolved with documented self-service steps. In that case, open an Azure support ticket with the correlation IDs from the Activity Log so the service team can investigate and fix the stuck backend state.

There is no supported way to preserve and “rebind” an existing completed identity validation to a new account if the platform-side state is corrupted; the documented guidance is to recreate Artifact Signing resources when such changes are needed.

References: