{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/", "slug": "dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus", "url": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/" }, "title": "Record threads per core separately from an Azure VM’s available vCPUs", "summary": "DSE recommends writing both requested settings into the deployment specification alongside the exact VM size.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-17T16:34:24+00:00", "modified_at": "2026-09-17T16:35:04+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 210, "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.", "primary_source": { "name": "VM vCore Customization - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/vm-customization", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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

\n

Applicability

\n

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

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n", "content_text": "Source facts\nMicrosoft 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\nApplicability\nThis guide is for a team requesting CPU customization during Azure VM creation and preparing to validate what the guest operating system receives.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\n\nMicrosoft: VM vCore Customization – Azure Virtual Machines | Microsoft Learn", "content_markdown": "## Source facts\n\nMicrosoft 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)\n\n## Applicability\n\nThis guide is for a team requesting CPU customization during Azure VM creation and preparing to validate what the guest operating system receives.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nCompare 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.\n\n## Official references\n\n- [Microsoft: VM vCore Customization – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/vm-customization)" }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/", "url": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Record threads per core separately from an Azure VM’s available vCPUs", "item": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/", "url": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/", "headline": "Record threads per core separately from an Azure VM’s available vCPUs", "description": "DSE recommends writing both requested settings into the deployment specification alongside the exact VM size.", "abstract": "DSE recommends writing both requested settings into the deployment specification alongside the exact VM size.", "articleBody": "Source facts\nMicrosoft 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\nApplicability\nThis guide is for a team requesting CPU customization during Azure VM creation and preparing to validate what the guest operating system receives.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\n\nMicrosoft: VM vCore Customization – Azure Virtual Machines | Microsoft Learn", "datePublished": "2026-09-17T16:34:24+00:00", "dateModified": "2026-09-17T16:35:04+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260917-036-record-threads-per-core-separately-from-an-azure-vms-available-vcpus/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Record threads per core separately from an Azure VM’s available vCPUs" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 210, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "VM vCore Customization - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/vm-customization" } } ] } }