Microsoft Configuration Manager

Setup Cloud Management Gateway

26 October 2026Doc update+4 / −4 lines

In brief

The setup instructions now link to VM sizing guidance by Configuration Manager version, capacity, and upgrade requirements. The Lab (B2s) size is now called the Small tier and remains intended only for lab or proof-of-concept use.

What Intune admins need to know

Review the updated sizing guidance when configuring a CMG and avoid using the Small tier for production.

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

Documentation change

View full page diff

View on Microsoft Learn

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

    - If you choose **Use existing**, then select an existing resource group from the list. This resource group needs to already exist in the same region you selected for the CMG. If you select an existing resource group, and it's in a different region than the previously selected region, the CMG will fail to deploy.
    - If you choose **Create new**, then enter the new resource group name.
4. By default,Select the **VM Size** is **Standard (A2\_V2)**. Select another option as your design specifies. For example,VM sizes by Configuration Manager version, client capacity, and upgrade requirements, see [Size and scale for CMG](perf-scale#size-and-scale-for-cmg).

    Important

    The **Large (A4\_v2)*Small** for increased client capacity per VM, ortier (previously **Lab (B2s)** in a small test environment.

    Important

    The **Lab (B2s)** size VM) is only intended for lab testing and small proof-of-concept environments. For example, withenvironments, such as the Configuration Manager technical preview branch. The B2s VMs arenIt isn't intended for production use with the CMG. They are low cost and low performing.
5. In the **VM Instance** field, enter the number of VMs for this service. The default is one, but you can scale up to 16 VMs per CMG.
6. If you're using client authentication certificates, select **Certificates** to add trusted root certificates. Add all of the certificates in the trust chain.

@@ -38,13 +38,13 @@ monikers: [] item_type: Content source_path: intune/configmgr/core/clients/manage/cmg/setup-cloud-management-gateway.md cmProducts:+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/4c50f262-d533-4ba4-9d4a-08899ec3a3d1 - https://authoring-docs-microsoft.poolparty.biz/devrel/68ec7f3a-2bc6-459f-b959-19beb729907d - https://authoring-docs-microsoft.poolparty.biz/devrel/96f6b0a2-2fd7-4de1-936d-89ad6e0eb7cc-- https://authoring-docs-microsoft.poolparty.biz/devrel/486161dc-fa28-4625-9b1c-1a21d690bc8d spProducts:+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/6a8c83be-f1de-4e90-bde0-bd097999a60c - https://authoring-docs-microsoft.poolparty.biz/devrel/90370425-aca4-4a39-9533-d52e5e002a5d - https://authoring-docs-microsoft.poolparty.biz/devrel/ef8b0a5a-ba0a-4ec0-8636-48246ccd954f-- https://authoring-docs-microsoft.poolparty.biz/devrel/5dd28c86-729c-4723-ab5a-57e26fcec2a8 platformId: c1a25ad2-51d4-46a6-eeff-53b1bd56581c --- @@ -111,11 +111,11 @@ Do this procedure on the top-level site. That site is either a standalone primar 
         - If you choose **Use existing**, then select an existing resource group from the list. This resource group needs to already exist in the same region you selected for the CMG. If you select an existing resource group, and it's in a different region than the previously selected region, the CMG will fail to deploy.
         - If you choose **Create new**, then enter the new resource group name.
-    4. By default, the **VM Size** is **Standard (A2\_V2)**. Select another option as your design specifies. For example, **Large (A4\_v2)** for increased client capacity per VM, or **Lab (B2s)** in a small test environment.
+    4. Select the **VM Size** as your design specifies. For VM sizes by Configuration Manager version, client capacity, and upgrade requirements, see [Size and scale for CMG](perf-scale#size-and-scale-for-cmg).
 
         Important
 
-        The **Lab (B2s)** size VM is only intended for lab testing and small proof-of-concept environments. For example, with the Configuration Manager technical preview branch. The B2s VMs aren't intended for production use with the CMG. They are low cost and low performing.
+        The **Small** tier (previously **Lab (B2s)**) is only intended for lab testing and small proof-of-concept environments, such as the Configuration Manager technical preview branch. It isn't intended for production use with the CMG.
     5. In the **VM Instance** field, enter the number of VMs for this service. The default is one, but you can scale up to 16 VMs per CMG.
     6. If you're using client authentication certificates, select **Certificates** to add trusted root certificates. Add all of the certificates in the trust chain.