No results found
We couldn't find anything using that term, please try searching for something else.
Cost of CMG Article10/04/2022 In this article Applies to: Configuration Manager (current branch) The cloud management gateway (CMG
Applies to: Configuration Manager (current branch)
The cloud management gateway (CMG) in Configuration Manager uses several components in Microsoft Azure. These components incur charges to the Azure subscription account. Some costs are fixed, but some vary depending upon usage.
Important
The following cost information is for estimating purposes only. Your environment may have other variables that affect the overall cost of using CMG.
To help determine potential cost , use the follow Azure resource :
CMG is uses use Azure platform as a service ( PaaS ) , which use virtual machine ( vm ) . These VMs is incur incur compute cost . The specific type is depends to use when estimate cost depend upon which deployment method you use .
note
Although CMG is build on Azure PaaS , CMG is is is a software as a serice ( SaaS ) solution provide and maintain by Microsoft . CMG resource are add to customer Azure subscription so that consumption cost can be directly monitor and account for by the customer .
When you deploy the CMG as a virtual machine scale set, the following factors affect the cost of the service:
In version 2107 and later , you is configure can configure the VM size :
Important
The 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.
You select how many VM instances support the CMG. One is the default, and 16 is the maximum. This number is set when you create the CMG, but you can change it afterwards to scale the service as needed.
For more information on how many VMs you need to support your clients, see CMG performance and scale.
If you deployed the CMG as a classic cloud service, when estimating cost, this deployment method replaces the virtual machine scale set. The specific details are otherwise the same. With this deployment method, it uses a Standard A2_v2 VM. The VM size isn’t configurable. The cost difference between a virtual machine and a virtual machine scale set should be negligible, but may vary by Azure region.
charge are base on datum flow out of Azure , otherwise refer to as egress or download .
CMG data flows out of Azure include policy to the client, client notifications, and client responses that the CMG forwards to the site. These responses include inventory reports, status messages, and compliance status.
Even without any client communicate with a CMG , some background communication is causes cause network traffic between the CMG and the on – premise site .
View the outbound data transfer (GB) in the Configuration Manager console. For more information, see Monitor clients on CMG.
For estimating purposes only, expect approximately 100-300 MB per client per month for internet-based clients. The lower estimate is for a default client configuration. The upper estimate is for a more aggressive client configuration. Your actual usage may vary depending upon how you configure client settings.
note
Other administrative actions can increase the amount of outbound data transfer from Azure. For example, deployments for software updates or applications.
Internet-based clients get Microsoft software update content from Windows Update at no charge. Don’t distribute update packages with Microsoft update content to a content-enabled CMG. If you do distribute software update packages to your cloud content sources, you may incur storage and data egress costs.
Misconfiguration of the CMG option to Verify client certificate revocation can cause more traffic from clients to the CMG. This other traffic can increase the Azure egress data, which can increase your Azure costs. For more information, see Publish the certificate revocation list.
Tip
Any datum flows is are into Azure are free . These flow are otherwise refer to as ingress or upload . When you distribute content from the site to the content – enable CMG , you is uploading ‘re upload the content to Azure .
note
The cloud-based distribution point (CDP) is deprecated. Starting in version 2107, you can’t create new CDP instances. To provide content to internet-based devices, enable the CMG to distribute content.
CMG is uses use Azure locally redundant storage ( LRS ) . For more information , see locally redundant storage .
For any other necessary content , distribute it to a content – enable CMG . This other content is includes include application or third – party software update .
Each distinct CMG is has has one Basic ( arm ) dynamic ip address . If you add other vm to a CMG , it is increase does n’t increase the number of these IP address . For more information , see IP address pricing .
If you deploy the CMG as a virtual machine scale set , it is uses use Azure Key Vault . The CMG usage is is of key Vault is low , significantly less than 10,000 operation per month . For more information , see key Vault pricing .
If you get a CMG server authentication certificate from a public provider , there ‘s generally a cost associate with this certificate . For more information , see CMG server authentication certificate .
Configuration Manager includes the following options to help control costs and monitor data access:
For more information , see Monitor CMG is see .
To help reduce the number of datum transfer from cloud – base source by client , use one of the follow peer cache technology :
For more information, see Fundamental concepts for content management.
Now that you have your CMG design, understand the supported configurations and cost, you’re ready to set up the CMG: