New-AzVM failing with VMCustomization' is not enabled for the Subscription.

[wsucoug69]

Description

We are running into an issue where the New-AzVm powershell cmdlet has stopped working. This was working a week ago without any issues, however we tried to run this today and are getting the following response:

Following this basic this example produces the issue:

New-AzVM: 'VMCustomization' is not enabled for the Subscription. Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

example-1--create-a-virtual-machine

Anybody else seeing this?

Issue script & Debug output

PS > New-AzVm -ResourceGroupName 'thisrg' -Name 'thisvm' -Location 'westus'

cmdlet New-AzVM at command pipeline position 1
Supply values for the following parameters:
Credential
User: thisuser
Password for user thisuser: blah

No Size value has been provided. The VM will be created with the default size Standard_D2s_v3.
New-AzVM: 'VMCustomization' is not enabled for the Subscription. Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Module versions

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     2.7.3                 Az.Accounts                         {Add-AzEnvironment, Clear-AzContext, Clear-AzDefault, Connect-AzAccount…}
Script     4.24.0                Az.Compute                          {Add-AzImageDataDisk, Add-AzVhd, Add-AzVMAdditionalUnattendContent, Add-AzVMDataDisk…}
Script     5.4.0                 Az.Resources                        {Export-AzResourceGroup, Export-AzTemplateSpec, Get-AzDenyAssignment, Get-AzDeployment…}

Error output

No response

[davmhelm]

Seeing this in Azure Cloud Shell as well for Az.Compute module version 4.24.0.

Seems to be working fine in module version 4.23.0, which I forcefully loaded to test using these commands:

# This downloads the working version of the module into your cloud shell session
Install-Module -Name Az.Compute -Force -RequiredVersion 4.23.0 

# this starts a new PowerShell session that will allow the Az.Compute assembly version to be loaded
pwsh 

# you should now see version 4.23.0 as loaded
Get-Module -Name Az.Compute 

# Run your New-AzVM command as normal

# to return your cloud shell to the previous state running the latest version of Az.* modules, run these commands
# otherwise new instances of cloud shell will continue to use the older version of the module you manually installed
Uninstall-Module -Name Az.Compute -Force -RequiredVersion 4.23.0
exit

[Naveenn12]

I got into similar issue, there seems to be some issue with powershell 7.2.1 version, I have installed PowerShell 7.3.0-preview.2 to fix the error.

[IsmaelJCarlo]

This is also happening in the Microsoft Learn environment sandbox which is running PowerShell 7.2.1.

Thank you for your feedback. This has been routed to the support team for assistance.

[dingmeng-xue]

Compute team,

I can reproduce this issue. I believe there is problem on new API version.

DEBUG: ============================ HTTP REQUEST ============================

HTTP Method:
PUT

Absolute Uri:
https://management.azure.com/subscriptions/9e223dbe-3399-4e19-88eb-0975f02ac87f/resourceGroups/thisrg/providers/Microsoft.Compute/virtualMachines/thisvm?api-version=2021-11-01

Headers:
x-ms-client-request-id        : 640453d1-d4e5-4fe7-9424-c3745d90ca30
Accept-Language               : en-US

Body:
{
  "properties": {
    "hardwareProfile": {
      "vmSize": "Standard_D2s_v3",
      "vmSizeProperties": {}
    },
    "storageProfile": {
      "imageReference": {
        "publisher": "MicrosoftWindowsServer",
        "offer": "WindowsServer",
        "sku": "2016-Datacenter",
        "version": "latest"
      }
    },
    "additionalCapabilities": {},
    "osProfile": {
      "computerName": "thisvm",
      "adminUsername": "dixue",
      "adminPassword": "dixue",
      "windowsConfiguration": {}
    },
    "networkProfile": {
      "networkInterfaces": [
        {
          "id": "/subscriptions/9e223dbe-3399-4e19-88eb-0975f02ac87f/resourceGroups/thisrg/providers/Microsoft.Network/networkInterfaces/thisvm"
        }
      ]
    }
  },
  "location": "westus2"
}

DEBUG: ============================ HTTP RESPONSE ============================

Status Code:
BadRequest

Headers:
Cache-Control                 : no-cache
Pragma                        : no-cache
x-ms-ratelimit-remaining-resource: Microsoft.Compute/PutVM3Min;239,Microsoft.Compute/PutVM30Min;1199
Strict-Transport-Security     : max-age=31536000; includeSubDomains
x-ms-request-id               : be35b85d-e86b-4ef8-a917-9afa90e1b8e0
Server                        : Microsoft-HTTPAPI/2.0,Microsoft-HTTPAPI/2.0
x-ms-ratelimit-remaining-subscription-writes: 1199
x-ms-correlation-request-id   : 1fc4cc06-3d9a-4a51-9e33-189c92859f56
x-ms-routing-request-id       : SOUTHEASTASIA:20220306T133226Z:1fc4cc06-3d9a-4a51-9e33-189c92859f56
X-Content-Type-Options        : nosniff
Date                          : Sun, 06 Mar 2022 13:32:26 GMT

Body:
{
  "error": {
    "code": "BadRequest",
    "message": "'VMCustomization' is not enabled for the Subscription. Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature."
  }
}

Besides API version is changed, it contains an empty property vmSizeProperties in the latest version. Please look into it with priority.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv.

Issue Details

---

Description

We are running into an issue where the New-AzVm powershell cmdlet has stopped working. This was working a week ago without any issues, however we tried to run this today and are getting the following response:

Following this basic this example produces the issue:

New-AzVM: 'VMCustomization' is not enabled for the Subscription. Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

example-1--create-a-virtual-machine

Anybody else seeing this?

Issue script & Debug output

PS > New-AzVm -ResourceGroupName 'thisrg' -Name 'thisvm' -Location 'westus'

cmdlet New-AzVM at command pipeline position 1
Supply values for the following parameters:
Credential
User: thisuser
Password for user thisuser: blah

No Size value has been provided. The VM will be created with the default size Standard_D2s_v3.
New-AzVM: 'VMCustomization' is not enabled for the Subscription. Please register the Subscription for 'Microsoft.Compute/VMCustomizationPreview' to use the feature.

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Module versions

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     2.7.3                 Az.Accounts                         {Add-AzEnvironment, Clear-AzContext, Clear-AzDefault, Connect-AzAccount…}
Script     4.24.0                Az.Compute                          {Add-AzImageDataDisk, Add-AzVhd, Add-AzVMAdditionalUnattendContent, Add-AzVMDataDisk…}
Script     5.4.0                 Az.Resources                        {Export-AzResourceGroup, Export-AzTemplateSpec, Get-AzDenyAssignment, Get-AzDeployment…}

Error output

No response

Author:	zapadoody
Assignees:	-
Labels:	Compute - VM, Service Attention, bug, customer-reported, P0, CXP Attention
Milestone:	-

[lowestbassnote]

This is also happening in the Microsoft Learn environment sandbox which is running PowerShell 7.2.1.

Yes - I have this same problem running in the sandbox when trying out https://docs.microsoft.com/en-us/learn/modules/automate-azure-tasks-with-powershell/6-exercise-create-resource-interactively