# Record threads per core separately from an Azure VM’s available vCPUs

> DSE recommends writing both requested settings into the deployment specification alongside the exact VM size.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:34:24+00:00
- Modified: 2026-09-17T16:35:04+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: IT
- Reading time: 1 minutes

## What you need to know

DSE recommends writing both requested settings into the deployment specification alongside the exact VM size.

## Potentially affected

This guide is for a team requesting CPU customization during Azure VM creation and preparing to validate what the guest operating system receives.

## DSE recommendation

DSE recommends writing both requested settings into the deployment specification alongside the exact VM size.

## Article

## Source facts

Microsoft describes separate settings for threads per core and the available vCPU count. Setting threads per core to one disables simultaneous multithreading. The portal presents valid available-vCPU values for the selected VM size. Microsoft states that the base VM price is unchanged by these CPU configuration options. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/vm-customization)

## Applicability

This guide is for a team requesting CPU customization during Azure VM creation and preparing to validate what the guest operating system receives.

## DSE recommendation

DSE recommends writing both requested settings into the deployment specification alongside the exact VM size. Have the workload owner explain the operational reason for each choice and define a representative performance test before deployment. Keep any software-license assessment separate and obtain the relevant owner’s interpretation rather than promising savings from a lower CPU count. Review the valid values shown for the selected size before submitting the request.

## Verification

Compare the deployed hardware profile with the specification and inspect the processors visible to the guest. Run the agreed workload checks and retain the configuration with the results. If the observed CPU presentation differs from the request, investigate that mismatch before using the VM as the basis for performance or licensing conclusions.

## Official references

- [Microsoft: VM vCore Customization – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/vm-customization)

## Primary reference

- Name: VM vCore Customization - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/vm-customization
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Record threads per core separately from an Azure VM’s available vCPUs,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.