Hi I am currently doing a CMG deployment on 2010 release of MECM.

The pre-reqs have been completed to the best of my knowledge and the deployment of Azure services/MECM integration and CMG has gone well. Client settings have been updated and I can see the cloudapp.net CMG in the network tab of the client.

The client when flicked to internet however doesnt seem to be able to connect to management point.

The MECM environment is primarily on-prem with 1 VM as IaaS in Azure. This was a DP however it was nominated to also become the CMG Connection point as well. It wasn’t an MP either so I enabled MP.

The environment is enabled to use EHHTP and all client machines are Azure Hybrid joined.

When running the CMG validation checker All checks are successful except the last one and it reports the following error:

Succeed to get ConfigMgr token with Azure AD token.

Failed to refresh MP location. Status code is ‘500’ and status description is ‘CMGConnector_InternalServerError’.

A possible reason for this failure is the CMG connection point failed to forward the message to the management point. Internal server error. For more information, see the management point logs for more details to see why internal server error returns.

I believe the issue is because this new MP isnt able to connect to the SQL database based on what I see in the logs. My question is after this is resolved do I need to do anthing with regards to DNS? I tryed to ping the cloudapp.net FQDN but it doesnt respond, I assume this is by design because when I check name resolution it is able to resolve the name to the correct IP address allocated.

Any help on this would be most appreciated.

Thanks