Microsoft Configuration Manager
General

Cost

In brief

For version 2609 and version 2603 with KB39169655, CMG tiers now use D2ads_v6, D4ads_v6, and D8ads_v6 VM sizes. Earlier versions retain the previous sizes, and existing deployments migrate automatically when the update is installed.

What Intune admins need to know

Use the new VM sizes when estimating costs for updated deployments; the Small tier remains intended for lab and proof-of-concept use.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

  • In version 2107 and later, you can configure the VM size:

    • Starting in version 2609 and version 2603 with the update rollup (KB39169655): Small (Standard_D2ads_v6), Medium (Standard_D4ads_v6), or Large (Standard_D8ads_v6).
    • Earlier versions without this update rollup: Lab (B2s)
    • , Standard (A2_v2)
    • , or Large (A4_v2).

    Existing deployments are automatically migrated to the corresponding new VM size when you install either update. Use the new VM sizes when estimating costs for updated deployments. For the size mapping and upgrade requirements, see Size and scale for CMG.

    Important

    The Small tier (previously Lab (B2s) size VM) is only intended for lab testing and small proof-of-concept environments. It isn't intended for production use with the CMG. The B2s VMs are low cost and low performing.

    You can change the VM size after you deploy the CMG. This action updates the Azure service to use a new VM.

  • In version 2103 and earlier, the CMG uses a Standard A2_v2 VM. The VM size isn't configurable. To change the VM size, you need to Redeploy the service.

Daily Intune.Admin.News

Get daily email updates

Get a concise summary of the latest Microsoft Intune updates delivered straight to your inbox.

Loading the secure signup form…