What changed

Microsoft announced general availability on 19 August 2026, stating support across all Azure public regions and for Virtual Machine Scale Sets in Uniform orchestration mode. The commercial case Microsoft gives is software licensed per core, naming SQL Server, Oracle and SAP. Configuration is available through ARM templates, the Azure CLI and PowerShell.

The operational risk is easy to miss because the service can continue to look healthy. The control becomes visible only when a capacity request fails, an unsupported runtime is removed, or an extension blocks an enforced ERP update. Waiting for that moment transfers a planned decision into an incident.

What the term means in plain language

VM vCore Customization covers two related controls. Disabling simultaneous multithreading runs one thread per physical core instead of two. Configurable Constrained Cores lets a VM present fewer active vCPUs than its size normally provides, while keeping the memory, storage and network bandwidth of the full size. The point is to align the core count the operating system reports with the cores a customer has actually licensed.

This distinction matters because product status is not the same as business readiness. Availability, support and compatibility are separate questions. A service can be available but unsupported, supported but capacity-constrained, or technically updated while a customer-specific process has stopped working.

Why this matters to a South African organisation

South African teams often operate with tight specialist capacity, rand-sensitive budgets and business processes that cannot be paused while a replacement is sourced. Localisation, regional cloud capacity and long procurement lead times can narrow the recovery options. The practical response is to use the available test window before it becomes an emergency window.

The consequence belongs to the business process, not only the technology team. Finance month-end, customer transactions, data pipelines and ERP extensions all cross technical and operational ownership. A change should therefore be accepted only when the service owner and the business owner can see the same evidence.

The hidden exposure

Azure VM vCore Customization is generally available, letting a large virtual machine present fewer active cores to per-core licensed software. Microsoft’s own documentation states the Azure price does not change, and that the SQL Server Marketplace image is not supported.

Normal operation is weak evidence. It proves only that yesterday’s combination of platform, configuration and workload completed. It does not prove that the next capacity allocation, lifecycle enforcement or major release will preserve the same result. An owner needs an inventory, a representative test and a dated decision.

Decision path

The first decision is financial and it is narrower than the announcement suggests. Microsoft’s concept page states that there is no extra charge for the CPU options and that the base VM price remains the same as if the full-size machine had been deployed with default settings. The Azure invoice therefore does not fall; the saving exists only in per-core licensed software, and only where the licence terms recognise the reduced count. The second decision is a deployment one: Microsoft’s page states that specialised Marketplace offerings, including SQL Server on Virtual Machines, are not supported, so a customer pursuing a SQL saving must build from a first-party Windows Server or custom image rather than the SQL Server Marketplace image. The third is regional and currently unsettled, which is addressed below.

Record the alternatives that were rejected and why. That prevents the next reviewer from reopening the entire question without context. Where the preferred path cannot be completed inside seven days, approve a time-bound exception with a responsible owner, expiry date and compensating control.

Technical test plan

Retrieve the supported configurations for the chosen size and region with az vm list-skus and read the vCPUsConstraintsAllowed field; the portal returns the valid options as an error when an unsupported count is requested. Set vCPUsAvailable to the licensed core count where per-core licensing or Azure Hybrid Benefit applies. On hyperthreaded sizes the value must be an even number, and it can only be reduced below the size default, never raised. CPU options can be set at creation or during a resize only: an allocated VM must be deallocated, and any resize reboots the machine. Where SQL Server is involved, review MAXDOP and the cost threshold for parallelism after constraining cores, and validate the result with Task Manager and sys.dm_os_sys_info.

Use production-representative conditions without exposing production data unnecessarily. Capture the starting configuration, exact version, time of test and expected result. A pass requires evidence from the real workflow, not only a successful login or an unchanged dashboard.

Primary owner

Primary owner: Infrastructure lead with FinOps and the software asset owner.

The named owner coordinates platform, application, commercial and business-process decisions. Contributors may perform the work, but accountability cannot be distributed across a meeting invite. The owner closes the test, exception and evidence record.

Action within seven days

Action within seven days: Inventory Azure VMs carrying per-core licences, identify one memory-bound or I/O-bound candidate, confirm the supported vCPU options for your own region with az vm list-skus, and model the licence saving without changing production.

Start with the highest-consequence workload. Assign the people, date and pass criteria before the test begins. If the first test fails, record the failure as evidence and open remediation with a deadline rather than hiding it behind a general project status.

Evidence to retain

Evidence to retain: Current vCPU count, licensed core entitlement, vCPUsConstraintsAllowed output for the region, a performance baseline and the cost model.

Store the evidence with the platform or change record. Include source exports and machine-readable results where possible. The next reviewer should be able to reproduce the conclusion without rebuilding it from email, chat or memory.

Frequently asked questions

Does the Azure bill go down?

No. Microsoft’s page states there is no extra charge for the options and that the base VM price remains the same as the full-size deployment. The saving is in per-core licensed software.

Can this be used with the SQL Server Marketplace image?

Microsoft’s concept page states that specialised Marketplace offerings, including SQL Server on Virtual Machines, are not supported. First-party images and custom images are.

Is it available in South Africa North?

Microsoft’s announcement states all Azure public regions. The SQL Server guidance page, last updated 27 May 2026 before general availability, still lists four regions and does not include South Africa North. Confirm against your own region with az vm list-skus before planning.

Can the setting be changed on a running machine?

No. Microsoft states the options are set at creation or resize only, that an allocated VM must be deallocated, and that a resize triggers a reboot.

The Braintree view

Microsoft’s announcement supplies the platform fact. The customer control begins after that fact: identify the exposed process, name the owner, test the real dependency and retain a decision that can survive audit or staff turnover. Braintree can help structure the inventory, build the representative test and translate the result into a controlled implementation plan.

Use the seven-day action as the entry point. Do not wait for a renewal, support refusal or enforced update to reveal work that can be measured now.