With ConfigMgr 1606, you can now connect Configuration Manager collections to the Microsoft Operations Management Suite (OMS) in Azure. The OMS Connector is currently a prerelease feature. As so, this is done in a lab. This blog will go through the steps on how to add the connector in ConfigMgr and the preqreuisite steps to take in Azure.
This blog post assumes you have a running ConfigMgr 1606 environment and a subscription in Azure.
The first step is to configure your ConfigMgr 1606 site to consent to use Pre-Release features.Make sure you read the disclaimer.
After this is done, we will turn on the “Pre-release Microsoft Operations Management Suite (OMS) Connector”
Click Yes to the dialogue box (make sure to read the disclaimer)
Log in to the Azure Classic portal https://manage.windowsazure.com an go into your Azure AD, select Applications. Click on Add down the bottom.
Enter in the name you would like to use and select web application and/or web API and click next.
Enter in sign on URL and APP ID URI. I added in my ConfigMgr server name (http://configmgr.domain.com) for both.
Next we will log into the Azure Resource Manager https://portal.azure.com and create our OMS Workspace. Click on Browse then go to “Log Analytics (OMS)” then click on Add
Once this is created, we will go back in the Azure Classic Portal and go into our Azure AD then Application we created earlier to make a note of our Client ID and generate a key.
Next we will create our connection to OMS back in the ConfigMgr console:
This is the part that Technet did not tell us. The part with the red box around it is misleading. We actually need to give our application we created earlier access to our Resource Group in the Azure Resource Manager Portal (portal.azure.com). This is probably because Operation Insights was moved from Azure Classic Portal to Azure Resource Manager. Without doing this, I will show you what happens:
I will type in my tenant name and Client ID and secret key from before, click Verify, then click Next.
ConfigMgr is unable to pull any information about the subscription or Resource Group or the OMS Workspace
To fix this, we need to log back into https://portal.azure.com and go into our Resource Group with our OMS workspace and give our Application we created earlier access.
Go to Settings, then click Users
Click on Add, and type in the name of the Application you created in the classic portal https://manage.windowsazure.com I gave mine Contributor role for testing.
Now if we go back and try and add the Operations Management Suite Connection again, you will see that ConfigMgr can pull the information from our Resource Group and OMS Workspace.
There we go. This looks better! It pulled the information now that it has access.
You can view the OMS Connector here. You can also right click on it and go to properties to view the properties and add collections.
Once the connector is set up, it should install the Microsoft Monitoring Agent.
Next we will log into the Azure Resource Manager portal https://portal.azure.com and enable the ConfigMgr collections. Once you’re in the Azure portal, go to Log Analytics (OMS) then click on OMS Portal
Once in the OMS Portal, go to Settings
Go to the COMPUTER GROUPS tab, and click on SCCM, then click “Import Configuration Manager collection memberships” and save.
After it updates you should see the collections (I added some more)
You can click on the links to view more information