VM deployment: Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

Question

VM deployment: Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

Ronny Forberger 45

I wanted to deploy a VM usig Bicep and Azure DevOps, but I get the ollowing error message:

ERROR: {"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/REDACTED/resourceGroups/vmapp/providers/Microsoft.Resources/deployments/main","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see 
##[error]Script failed with exit code: 1

Looks like the feature

Microsoft.Compute/VMCustomizationPreview

is not enabled in the preview features in my subscription, but when I want to add the feature in 'Preview features' in the subscription, I do not find it in the drop down list in the portal.

I am using az cli version 2.51.0 script type pscore.

What can be wrong?

kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-12T17:42:30.55+00:00

Hello, @Ronny Forberger !

Just to confirm, you're getting the VM Customization error along with DeploymentFailed? There was a bug in the CLI that was similar to this a while back that we may need to investigate.

Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

https://learn.microsoft.com/en-us/answers/questions/727655/vmcustomization-is-not-enabled-for-the-subscriptio
Ronny Forberger 45 Reputation points

2023-08-12T18:10:45.1066667+00:00

Hi @kobulloc-MSFT ,

I am seeing this error when trying to run my Bicep code on Azure DevOps, which deploys a public IP, NSG, vnet, Nic and a virtual machine,

I am using a recent version of az cli (2.51.0) as per the default agent in Azure DevOps.

The bug in az cli from the bug should not affect this version?

Should I use a newer az cli version than 2.51? (Using a custom built agent).
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-13T18:48:54.8+00:00

Thank you for the additional information, @Ronny Forberger ! This is perfect.

The bug I linked shouldn't affect that version but I want to look into the possibility of a regression. I might try a different CLI version just to see if that affects the result before I'm able to follow up with the virtual machine team. What size VM were you attempting to deploy?
Ronny Forberger 45 Reputation points

2023-08-14T06:05:37.4+00:00
Standard_D1_v2

Thanks.
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-14T13:46:22.0966667+00:00

Thank you, @Ronny Forberger ! I've reached out to the virtual machine team and will let you know when I have an update.
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-15T18:05:55.5733333+00:00

Hello, @Ronny Forberger !

One more point of clarification: Did you use the Azure Cloud Shell or a local shell to execute deployment?
Ronny Forberger 45 Reputation points

2023-08-15T22:08:05.9366667+00:00

I used the az cli from the Azure DevOps agent.
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-16T04:35:28.0233333+00:00

Hello, @Ronny Forberger !

It doesn't sound like you are using VMCustomizationPreview but the product group would like to see if the following command unblocks you:

az feature register --namespace Microsoft.Compute --name VMCustomizationPreview

Ronny Forberger 45

OK, enabling the feature I get the following error:

az feature register --namespace Microsoft.Compute --name VMCustomizationPreview                                                  
Once the feature 'VMCustomizationPreview' is registered, invoking 'az provider register -n Microsoft.Compute' is required to get the change propagated
(FeatureRegistrationUnsupported) The feature 'VMCustomizationPreview' does not support registration.
Code: FeatureRegistrationUnsupported
Message: The feature 'VMCustomizationPreview' does not support registration.

kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-16T16:40:16.1166667+00:00

Thank you, @Ronny Forberger ! I suspected that was the case but this helps in narrowing down the cause. I'll update you as I learn more.

Accepted answer

1 additional answer

Your answer

kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-12T17:42:30.55+00:00

Hello, @Ronny Forberger !

Just to confirm, you're getting the VM Customization error along with DeploymentFailed? There was a bug in the CLI that was similar to this a while back that we may need to investigate.

Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

https://learn.microsoft.com/en-us/answers/questions/727655/vmcustomization-is-not-enabled-for-the-subscriptio
Ronny Forberger 45 Reputation points

2023-08-12T18:10:45.1066667+00:00

Hi @kobulloc-MSFT ,

I am seeing this error when trying to run my Bicep code on Azure DevOps, which deploys a public IP, NSG, vnet, Nic and a virtual machine,

I am using a recent version of az cli (2.51.0) as per the default agent in Azure DevOps.

The bug in az cli from the bug should not affect this version?

Should I use a newer az cli version than 2.51? (Using a custom built agent).
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-13T18:48:54.8+00:00

Thank you for the additional information, @Ronny Forberger ! This is perfect.

The bug I linked shouldn't affect that version but I want to look into the possibility of a regression. I might try a different CLI version just to see if that affects the result before I'm able to follow up with the virtual machine team. What size VM were you attempting to deploy?
Ronny Forberger 45 Reputation points

2023-08-14T06:05:37.4+00:00

Standard_D1_v2

Thanks.
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-14T13:46:22.0966667+00:00

Thank you, @Ronny Forberger ! I've reached out to the virtual machine team and will let you know when I have an update.
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-15T18:05:55.5733333+00:00

Hello, @Ronny Forberger !

One more point of clarification: Did you use the Azure Cloud Shell or a local shell to execute deployment?
Ronny Forberger 45 Reputation points

2023-08-15T22:08:05.9366667+00:00

I used the az cli from the Azure DevOps agent.
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-16T04:35:28.0233333+00:00

Hello, @Ronny Forberger !

It doesn't sound like you are using VMCustomizationPreview but the product group would like to see if the following command unblocks you:

az feature register --namespace Microsoft.Compute --name VMCustomizationPreview
Ronny Forberger 45 Reputation points

2023-08-16T08:52:10.52+00:00

OK, enabling the feature I get the following error:

az feature register --namespace Microsoft.Compute --name VMCustomizationPreview Once the feature 'VMCustomizationPreview' is registered, invoking 'az provider register -n Microsoft.Compute' is required to get the change propagated (FeatureRegistrationUnsupported) The feature 'VMCustomizationPreview' does not support registration. Code: FeatureRegistrationUnsupported Message: The feature 'VMCustomizationPreview' does not support registration.
kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-16T16:40:16.1166667+00:00

Thank you, @Ronny Forberger ! I suspected that was the case but this helps in narrowing down the cause. I'll update you as I learn more.

Answer 1

kobulloc-MSFT 26,626 Microsoft Employee

Hello, @Ronny Forberger !

(Edit: Updated with solution)

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Why is my DevOps VM deployment failing with an VMCustomization error?

Solution provided by Ronny Forberger (thank you!):

The problem was the vmSizeProperties hash in my bicep code. I didn't know you cannot set it when deploying a specific vmSize. Also I had to set another vmSize, since for Generation 2 hypervisors, the above mentioned SKU seems not to be supported.

Thank you for helping to improve Microsoft Q&A!

User's image

Ronny Forberger 45 Reputation points

2023-08-21T18:41:05.83+00:00

Hi @kobulloc-MSFT ,

ok, thanks for your effort so far. I will reach out to AzCommunity@microsoft.com. Maybe the problem also resides in my bicep code, but I am not really sure where. Would be ideal if Microsoft could verify the API requests sent to ARM, I guess you do, but maybe not deeply enough yet? Just as a suggestion :) But maybe the problem sits somewhere in azure cli and its libraries, I have no insight here.

Answer 2

Ronny Forberger 45

Ah, sorry, I fixed it.

I was silly, the problem was the vmSizeProperties hash in my bicep code. I didn't know you cannot set it when deploying a specific vmSize.

Also I had to set another vmSize, since for Generation 2 hypervisors, the above mentioned SKU seems not to be supported.

Sorry for the effort, but I am still learning Azure and Bicep.

Thanks again.

kobulloc-MSFT 26,626 Reputation points Microsoft Employee

2023-08-21T20:41:40.91+00:00

Thank you for the update, @Ronny Forberger !

No worries! I really appreciate the update--the goal here is to find the solution so this is perfect. I'll update the other answer in case you want to accept it to help increase the visibility for this thread (unfortunately you can't accept your own answer yet so this is a temporary workaround).

Thank you again!

Share via

VM deployment: Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

1 additional answer

Your answer