How to solve this subscription spending limit issue

I also have a MSDN Subscription, and it is not working for all the newest VM types:

• Windows 11 Pro, version 23H2 - x64 Gen2 > not possible
• Windows 11 Pro, version 22H2 - x64 Gen2 > possible
• Windows 11 Pro, version 21H2 - x64 Gen2 > possible
• Windows 11 Enterprise, version 23H2 - x64 Gen2 > not possible
• Windows 11 Enterprise, version 22H2 - x64 Gen2 > possible
• Windows 11 Enterprise N, version 23H2 - x64 Gen2 > not possible
• Windows 11 Pro N, version 23H2 - x64 Gen2 > not possible

This virtual machine requires a subscription without any spending limit or temporary payment method set. Use a different subscription or update your subscription (requires account administrator privileges) at Account Center to continue.

All,

I created a support request for Microsoft to look into this issue and here is the summary:

TL;DR - They are offering that VM only to Visual Studio subscribers, but they want those users to add a credit card.. The $150 (for Ent subscribers, for example) 'free credits' will not be applicable if you want to create this specific VM (bizzare, but that's their official position). Read on....

We explained you that to deploy the Visual studio 2022 Virtual machine (Marketplace Product) in Azure portal using the Visual studio credits you need to remove the spending limit and add credit card to the account.

• We worked with our engineering team multiple times internally and with technical advisory team regarding the VS 2022 VM deployment using script. 
• By design in terms of how the publisher has currently configured their offer/plan.
• If publisher doesn’t provide the option for Azure Free credits, then no credit-based subscription cannot be deployed the Virtual machine.
• You can also create paid subscription (Pay-As-You-Go | Microsoft Azure) to deploy the VS 2022 Virtual machine.
• The publisher came back and explained that this is by design, this Marketplace offer needs a paid subscription.
• Since there is a gap in the system through CLI and they will be working on closing this gap soon.

Hi There,

I am still getting the issue with my MSDN subscription in creating a SQL2022/RHEL VM. The error is

"This virtual machine requires a subscription without any spending limit or temporary payment method set. Use a different subscription or update your subscription (requires account administrator privileges) at Account Center to continue.". Is there a way to progress without removing the spending limit? I just need a test SQL Linux VM for a short time.

Thanks & regards, Irene

I got the same issue today and tried with command lines, then it worked

param (
    [string]$ResourceGroup = "YourResourceGroupName",
    [string]$VmName = "YourVmName",
    [string]$VnetName = "YourVnetName",
    [string]$SubnetName = "YourSubnetName",
    [string]$Location = "southeastasia",
    [string]$AdminUsername = "YourAdminUsername",
    [string]$AdminPassword = "YourPassword123!",
    [string]$AddressPrefix = "10.0.0.0/16",
    [string]$SubnetPrefix = "10.0.0.0/24",
    [string]$PublisherName = "MicrosoftWindowsDesktop",
    [string]$Offer = "windows-11",
    [string]$Skus = "win11-24h2-pro",
    [string]$Version = "latest",
    [string]$VmSize = "Standard_B2s"
)

# Create a virtual network
New-AzVirtualNetwork -ResourceGroupName $ResourceGroup -Location $Location -Name $VnetName -AddressPrefix $AddressPrefix -Subnet @{"Name" = $SubnetName; "AddressPrefix" = $SubnetPrefix}

# Create a public IP address with Static allocation and DNS name
$PublicIp = New-AzPublicIpAddress -ResourceGroupName $ResourceGroup -Location $Location -Name "${VmName}PublicIP" -AllocationMethod Static -Sku Standard -DnsName $VmName

# Create a network security group
$Nsg = New-AzNetworkSecurityGroup -ResourceGroupName $ResourceGroup -Location $Location -Name "${VmName}NSG"

# Create a network security group rule to allow RDP
$NsgRule = New-AzNetworkSecurityRuleConfig -Name "AllowRDP" -Protocol "Tcp" -Direction "Inbound" -Priority 1000 -SourceAddressPrefix "*" -SourcePortRange "*" -DestinationAddressPrefix "*" -DestinationPortRange 3389 -Access "Allow"
$Nsg.SecurityRules.Add($NsgRule)
$Nsg | Set-AzNetworkSecurityGroup

# Create a virtual network interface and associate with public IP address and NSG
$Nic = New-AzNetworkInterface -ResourceGroupName $ResourceGroup -Location $Location -Name "${VmName}NIC" -SubnetId (Get-AzVirtualNetwork -ResourceGroupName $ResourceGroup -Name $VnetName).Subnets[0].Id -PublicIpAddressId $PublicIp.Id -NetworkSecurityGroupId $Nsg.Id

# Create a virtual machine without boot diagnostics
$VmConfig = New-AzVMConfig -VMName $VmName -VMSize $VmSize | `
    Set-AzVMOperatingSystem -Windows -ComputerName $VmName -Credential (New-Object PSCredential -ArgumentList $AdminUsername, (ConvertTo-SecureString -String $AdminPassword -AsPlainText -Force)) | `
    Set-AzVMSourceImage -PublisherName $PublisherName -Offer $Offer -Skus $Skus -Version $Version | `
    Add-AzVMNetworkInterface -Id $Nic.Id | `
    Set-AzVMOSDisk -CreateOption FromImage -ManagedDiskId $null -StorageAccountType "Standard_LRS" | `
    Set-AzVMBootDiagnostics -Disable

New-AzVM -ResourceGroupName $ResourceGroup -Location $Location -VM $VmConfig

# Open port 3389 to allow RDP traffic
Get-AzNetworkSecurityGroup -ResourceGroupName $ResourceGroup -Name "${VmName}NSG" | Add-AzNetworkSecurityRuleConfig -Name "AllowRDP" -Protocol "Tcp" -Direction "Inbound" -Priority 1000 -SourceAddressPrefix "*" -SourcePortRange "*" -DestinationAddressPrefix "*" -DestinationPortRange 3389 -Access "Allow" | Set-AzNetworkSecurityGroup