Clarification Required - Azure VM and Storage Pricing Update from 1 February 2027

Everyone is talking about digital sovereignty these days. Yet businesses continue to depend on cloud providers that control pricing, capacity and where their workloads can run.

We were told that Microsoft’s data centres in Norway are facing capacity constraints. On one occasion, we had to choose a data centre in Sweden instead. We also heard that Microsoft is no longer investing in its Norwegian data centres, although we haven’t independently confirmed that.

Against that backdrop, these Azure price increases are frustrating - especially when customers have to ask which resources are actually affected. What is Microsoft trying to achieve here?

In my view, it’s time to start moving workloads out of the cloud, particularly Microsoft Azure. If digital sovereignty matters, we need to take control of our infrastructure, data and budgets.

For predictable, long-running workloads, businesses should seriously consider their own infrastructure or independent hosting. Migration, staffing, security and resilience all need to be included in the comparison. But it’s time to develop an exit plan.

We should choose providers because they continue to deliver value, not because leaving has become too difficult.

Hi @$@chin ,

Services excluded from the regional pricing update

The pricing adjustments described above do not apply to the following Azure Virtual Machine series and Azure Storage services: Azure Virtual Machines

• v1: Bv1, D, Ds, F, Fs, G, Gs, L, NP, HCS
• v2: Av2, Amv2, Dv2, Dsv2, Fsv2, Lsv2
• v7: Dsv7, Ddsv7, Dlsv7, Dldsv7, Esv7, Edsv7

Your question:

For example, would VM series such as Dv4/Dsv4, Dv5/Dsv5, Ev4/Esv4, Ev5/Esv5, and other v4/v5/v6 series be impacted by the pricing increase?

The VM SKUs you listed are affected by the price increase if they are deployed in the Southeast Asia (Singapore) Azure region. As they are not listed in the exclude list.

Your question:

Is there an official list of all VM series/SKUs that will be impacted by this pricing update?

All VM series/SKUS that are not excluded by the list above in the email.

A full list of Azure VM series/SKUs you can find here: Sizes for virtual machines in Azure

Your question:

Is there a way to identify the impacted resources in a subscription through the Azure Portal, Azure Resource Graph, Cost Management, or another Azure API?

In the Azure portal you can list all VMs and filter on Azure region and VM SKU (location and size).With PowerShell, Azure Resource Graph such a query should be possible as well.

Just an example to get started with PowerShell. But the command needs some more filter (Where-Objects):

 Get-AzComputeResourceSku | Where-Object { $_.Locations -contains "southeastasia" }

Your question:

Will Azure provide a more detailed Service Health notification identifying the impacted resources/SKUs before the pricing change takes effect?

I am pretty sure there will be further notification and updates on this topic. But no idea when and which details.

Your question:

Is there a list of the specific Azure Storage services/SKUs affected?

All Azure storages/services that are not listed in the excluded list.

Excluded are the following Azure storage services:

• Azure Container Storage
• Azure Managed Lustre
• Azure NetApp Files – Cross Region Replication SKU
• Blob Features
• Change Feed
• General Block Blob
• Import/Export
• Queues
• Queues v2
• Standard Page Blob
• Storage Actions
• Storage Bandwidth
• Storage Discovery
• Tables
• Transaction Optimized SKU

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten

I think the exclusion list alone doesn't mean every unlisted VM or Storage SKU will get the increase. The affected billing meters aren't clear from the notification either. Get-AzComputeResourceSku lists available SKUs, not ur deployed VMs.

For ur Singapore VMs, select the relevant subscriptions in Resource Graph Explorer and run:

Resources

| where type =~ 'microsoft.compute/virtualmachines'

| where location =~ 'southeastasia'

| project subscriptionId, id, name, vmSize = tostring(properties.hardwareProfile.vmSize)

Also check the Service Health advisory's Impacted Resources tab, if available. Then send ur Singapore VM and Storage cost details (ResourceId, MeterId, PricingModel) and the advisory ID to Azure billing support. Ask which meters will increase on 1 February 2027, whether PAYG, existing reservations and savings plans are affected, and if a more detailed notice is planned.