Artifact Signing account creation fails with ResourceCreationValidateFailed (persistent, since May 2026)

Question

Artifact Signing account creation fails with ResourceCreationValidateFailed (persistent, since May 2026)

Michael Economou 0

Hello,

I'm trying to create an Azure Artifact Signing (Trusted Signing) account and it consistently fails during deployment with:

Error code: ResourceCreationValidateFailed

Message: "The resource validation failed."

This has been happening since 18 May 2026, with 10+ failed attempts through 21 July 2026, all with the same generic error and no further detail in the Error details, Raw Error, or Activity Log JSON.

Setup details: Subscription "Azure subscription 1" (Pay-as-you-go "Azure Plan", not free/trial); Resource group oncut-codesigning (West Europe); Account name oncut-signing; Region West Europe; Pricing tier Basic.

Things I already checked per the FAQ and troubleshooting docs: the Microsoft.CodeSigning resource provider is already registered on the subscription; the subscription is a paid "Azure Plan", not free/trial/sponsored (which I understand is unsupported); the business is an individual/sole proprietorship registered in Greece (EU), with business identifier ELGEMI.171173703000.

Could someone help identify why the validation is failing and what additional information you would need from me (for example correlation or activity IDs) to investigate further?

Thank you.

Khairy Zhafran H. Kastella 80 Reputation points

2026-07-21T11:11:47.7633333+00:00
Hi Michael,

The "ResourceCreationValidateFailed" error is a generic validation error that usually means the request failed one of the service-side validation checks before the Trusted Signing account could be created.

Since you've already confirmed that the Microsoft.CodeSigning resource provider is registered, you're using a supported paid subscription, you're deploying to West Europe, and the issue has persisted across multiple attempts over several months, it doesn't appear to be a temporary deployment issue.

A few additional things you can check are:

Verify there are no Azure Policies or resource locks on the subscription or resource group that could prevent resource creation.

Try creating the Trusted Signing account with a different resource name and, if possible, in another supported region to rule out a region- or name-specific issue.

Confirm that your Microsoft Entra account has sufficient permissions (such as Owner or Contributor) on the subscription and resource group.

Because the deployment fails during validation and no detailed diagnostics are available in the Activity Log, this will most likely require investigation by the Azure Trusted Signing service team.

I recommend opening an Azure Support request and including your Subscription ID, Tenant ID, Resource Group name, resource name, region, the approximate UTC time of the failed deployment, and any Correlation ID, Operation ID, or Activity ID available from the deployment or Activity Log. Also include the deployment operation details or ARM deployment error output if available.

These details will help Microsoft engineers locate the backend validation logs and determine why the validation is failing. Since the issue has been reproducible since May 2026, it may require investigation on the service side.
Meha-MSFT 2,125 Reputation points Microsoft Employee Moderator

2026-07-21T17:34:35.67+00:00

It's unclear from your question what is failing: resource creation as in Artifact Signing account creation or cert profile creation or identity validation. Identity validation and cert profile creation happens after Artifact Signing account is created.
Michael Economou 0 Reputation points

2026-07-21T19:09:34.8966667+00:00

Thank you for the clarification. To be precise: the failure happens at the very first step - creating the Artifact Signing Account resource itself in the Azure portal. The deployment fails immediately with error code ResourceCreationValidateFailed / message "The resource validation failed.", with no further details provided. We never reach identity validation or cert profile creation, since the account resource itself is never successfully created. We've tried this in both West Europe and North Europe regions with identical results. We've also verified: no resource locks or deny policies on the subscription/resource group, correct RBAC permissions (Owner), an active subscription, a verified custom domain matching our company's registered domain, and complete/consistent company and billing profile information. Could you advise what additional validation happens at this initial resource-creation step, and how we can get more detail on why it's failing?
Meha-MSFT 2,125 Reputation points Microsoft Employee Moderator

2026-07-21T19:32:39.2066667+00:00

can you share the correlation id?
Michael Economou 0 Reputation points

2026-07-21T20:01:05.5633333+00:00

Yes, here it is: Correlation ID: 5039df1d-e869-40dc-98a6-53e427418537 (deployment "CreateAccount-20260721220015", resource group "oncut-codesigning", attempted 7/21/2026 10:02:09 PM UTC). Let me know if you need a fresh correlation ID from a specific region (we've reproduced this in both West Europe and North Europe).
Vishwas Srivastava 0 Reputation points

2026-07-22T07:33:42.92+00:00

Hi Michael,

Thanks for sharing the details.

The "ResourceCreationValidateFailed" error is a generic validation error, typically indicating that the request failed one of the service-side validation checks before the Trusted Signing account could be created.

This appears to be an intermittent issue. I'd suggest retrying the request, or alternatively, trying with a different account name — either approach should resolve it.

Thanks,
Jyotishree Moharana 1,945 Reputation points Microsoft External Staff Moderator

2026-07-28T08:46:27.3633333+00:00

Hello @Michael Economou,

Following up to check if the issue is still persisting and the validation is failing, kindly let us know so we can check further.
Jyotishree Moharana 1,945 Reputation points Microsoft External Staff Moderator

2026-07-30T06:57:01.2+00:00

Hello @Michael Economou,

Following up to check if the issue is still persisting and the validation is failing, kindly let us know so we can check further.

Your answer

Khairy Zhafran H. Kastella 80 Reputation points

2026-07-21T11:11:47.7633333+00:00

Hi Michael,

The "ResourceCreationValidateFailed" error is a generic validation error that usually means the request failed one of the service-side validation checks before the Trusted Signing account could be created.

Since you've already confirmed that the Microsoft.CodeSigning resource provider is registered, you're using a supported paid subscription, you're deploying to West Europe, and the issue has persisted across multiple attempts over several months, it doesn't appear to be a temporary deployment issue.

A few additional things you can check are:

Verify there are no Azure Policies or resource locks on the subscription or resource group that could prevent resource creation.

Try creating the Trusted Signing account with a different resource name and, if possible, in another supported region to rule out a region- or name-specific issue.

Confirm that your Microsoft Entra account has sufficient permissions (such as Owner or Contributor) on the subscription and resource group.

Because the deployment fails during validation and no detailed diagnostics are available in the Activity Log, this will most likely require investigation by the Azure Trusted Signing service team.

I recommend opening an Azure Support request and including your Subscription ID, Tenant ID, Resource Group name, resource name, region, the approximate UTC time of the failed deployment, and any Correlation ID, Operation ID, or Activity ID available from the deployment or Activity Log. Also include the deployment operation details or ARM deployment error output if available.

These details will help Microsoft engineers locate the backend validation logs and determine why the validation is failing. Since the issue has been reproducible since May 2026, it may require investigation on the service side.
Meha-MSFT 2,125 Reputation points Microsoft Employee Moderator

2026-07-21T17:34:35.67+00:00

It's unclear from your question what is failing: resource creation as in Artifact Signing account creation or cert profile creation or identity validation. Identity validation and cert profile creation happens after Artifact Signing account is created.
Michael Economou 0 Reputation points

2026-07-21T19:09:34.8966667+00:00

Thank you for the clarification. To be precise: the failure happens at the very first step - creating the Artifact Signing Account resource itself in the Azure portal. The deployment fails immediately with error code ResourceCreationValidateFailed / message "The resource validation failed.", with no further details provided. We never reach identity validation or cert profile creation, since the account resource itself is never successfully created. We've tried this in both West Europe and North Europe regions with identical results. We've also verified: no resource locks or deny policies on the subscription/resource group, correct RBAC permissions (Owner), an active subscription, a verified custom domain matching our company's registered domain, and complete/consistent company and billing profile information. Could you advise what additional validation happens at this initial resource-creation step, and how we can get more detail on why it's failing?
Meha-MSFT 2,125 Reputation points Microsoft Employee Moderator

2026-07-21T19:32:39.2066667+00:00

can you share the correlation id?
Michael Economou 0 Reputation points

2026-07-21T20:01:05.5633333+00:00

Yes, here it is: Correlation ID: 5039df1d-e869-40dc-98a6-53e427418537 (deployment "CreateAccount-20260721220015", resource group "oncut-codesigning", attempted 7/21/2026 10:02:09 PM UTC). Let me know if you need a fresh correlation ID from a specific region (we've reproduced this in both West Europe and North Europe).
Vishwas Srivastava 0 Reputation points

2026-07-22T07:33:42.92+00:00

Hi Michael,

Thanks for sharing the details.

The "ResourceCreationValidateFailed" error is a generic validation error, typically indicating that the request failed one of the service-side validation checks before the Trusted Signing account could be created.

This appears to be an intermittent issue. I'd suggest retrying the request, or alternatively, trying with a different account name — either approach should resolve it.

Thanks,
Jyotishree Moharana 1,945 Reputation points Microsoft External Staff Moderator

2026-07-28T08:46:27.3633333+00:00

Hello @Michael Economou,

Following up to check if the issue is still persisting and the validation is failing, kindly let us know so we can check further.
Jyotishree Moharana 1,945 Reputation points Microsoft External Staff Moderator

2026-07-30T06:57:01.2+00:00

Hello @Michael Economou,

Following up to check if the issue is still persisting and the validation is failing, kindly let us know so we can check further.