CMG Connection Point Status Disconnected | SCCM | ConfigMgr

In Configuration Manager (SCCM/ConfigMgr), you may encounter a situation where the Cloud Management Gateway (CMG) Connection Point status shows as Disconnected. This issue typically indicates a communication or configuration problem between the CMG and the on‑premises site system. In this guide, we’ll walk through the common causes, log file analysis, and step‑by‑step troubleshooting methods to restore connectivity and ensure smooth client communication through CMG.

Issue:

After configuring a new Cloud Management Gateway (CMG) in SCCM/Configuration Manager, you may notice that the CMG Connection Point status shows as Disconnected. This typically indicates a communication or configuration issue between the CMG and the site system. The following error is logged in the SMS_CLOUD_PROXYCONNECTOR.log file, which provides critical details for troubleshooting.

ERROR: Failed to build HttpV2 connection 711c3af4-a0a8-44bd-a8dd-01572a7b276c with server xxxCMG.CLOUDAPP.NET:443. Exception: System.Net.WebException: The remote name could not be resolved: 'xxxcmg.cloudapp.net'~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.HttpConnectionV2.SendInternal(HttpMethod method, String path, String payload, Int32& statusCode, Byte[]& responsePayload)~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.HttpConnectionV2.SendInternal(HttpMethod method, String path, Byte[] payload)~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.HttpConnectionV2.Online()~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.ConnectionBase.Start()~~   at Microsoft.ConfigurationManager.CloudConnection.ProxyConnector.ConnectionManager.MaintainConnections()

Cause:

The logs indicate that the remote name could not be resolved, which occurred because Microsoft changed the way Cloud Management Gateway (CMG) service names are registered with Azure.

Starting with ConfigMgr version 2010, when you deploy CMG to a Virtual Machine Scale Set (VMSS), the deployment name format is different. With VMSS, the service name uses the cloudapp.azure.com domain along with the Azure region. For example: GraniteFalls.EastUS.CloudApp.Azure.Com for a deployment in the East US region.

In the above setup, the service name was configured with the Prefix.Cloudapp.net domain, which is no longer valid for VMSS‑based CMG deployments. This mismatch caused the connection point to show as Disconnected.

Solution:

Option 1: Keep the Service name the same as the Deployment name.

Examples:

Service Name: Prefix.Region.CloudApp.Azure.Com

e;g: techuisitivecmg.EastUS.CloudApp.Azure.com

Deployment Name: Prefix.Region.CloudApp.Azure.Com

e:g: techuisitivecmg.EastUS.CloudApp.Azure.com

Option 2: Another option is to use your own domain address for the CMG service name and create a DNS CNAME to route the traffic to the CMG deployment name. Microsoft recommends this method.

Example:

Service Name: techuisitivecmg.techuisitive.com

Deployment name: techuisitivecmg.EastUS.CloudApp.Azure.com

DNS CNAME: Create a DNS CNAME in public DNS (Your DNS registrar) to route the request coming for the Service name address to the CMG Deployment address.

The Configuration Manager client policy includes the CMG service name. The client resolves the service name via the CNAME alias to the deployment name.

The CNAME for the above example will be:

HostName: techuisitivecmg

Value: techuisitivecmg.EastUS.CloudApp.Azure.com

Related Posts:

Subscribe to Techuisitive Newsletter

Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.

Scroll to Top