SCCM – Integrate OMS with your SCCM infrastructure

The latest update of System Center Configuration Manager 2012 R2 (build 5.00.8412.100 published on August 2016) has added a prerelease feature to use OMS to synch your monitoring logs.

Off course, to take advantage of this feature, you need to have an Operations Management Suite tenant (

Enable Prerelease Features

To take advantage of this prerelease feature, you first need to enable the activation of prerelease from the Administration\Site Configuration\Sites\Hierarchy Settings



Enable Microsoft OMS Connector

From the SCCM administration console, access the Administration\Cloud Services\Updates and Servicing\Features and turn on the Pre-release – Microsoft Operations Management Suite (OMS) feature


Once activated, close the console and re open it to see the OMS Connector



Register your SCCM infrastructure

You need to perform this step ONLY if you did not already have registered your SCCM infrastructure; you may already have done this to integrate your Windows Store for Business store. You will need anyway to configure the permission to grant the correct rights (next step).

To be able to continue the configuration process, you need to register your SCCM infrastructure on Azure Active Directory

Connect to your Azure portal ( and access the Applications section your Azure AD tenant to Add a new application


Choose to add an Application my organization is developing


Name the application (like SCCM for example) and select the Web Application type


Define the sign in and app ID url’s – the values you defined do not really matter as these will no be really used; this needed to complete the process and then be able to get a key


Finally, configure the added application to generate a key using the keys section on then select the duration of the key


Once the key has been generated, stay on this page until you complete the next steps. If you do, you will not be able to get the key after.


Create the OMS workspace on Azure

Connect to your Azure management portal ( and add a resource; if you already have an OMS workspace, just search for it and go to the step to grant the permission

Search for Log Analytics (OMS) and create the workspace


Create or link an existing OMS workspace


Then fill the additional settings like resource group, location…


Grant Permission to Connect to the OMS Workspace

Open the Log Analytics (OMS) blade and open your workspace


Click on the Access management


Add a contributor role and add the user – which is the application name you created on your Azure AD



Configure OMS Connector

From the administration console, browse to Administration\Cloud Services\OMS Connector and right click to create the connector – from the top tier site in your hierarchy


Just follow the wizard to configure the tenant, client ID and key for the application added previously


Click the Verify button to ensure everything is correct; this will show Successfully verified


During the next step, you need to define your Azure subscription, the Azure resource group and the OMS workspace; you need to manually fill these fields (as this is a prerelease, we can expect this could be prepopulated at a later stage). If you have multiple Azure subscription, it is recommended to use the one you are already using with OMS (you can check it from the OMS portal, Settings\Accounts\Azure Subscription section) and select the device collection you want to synch with OMS – you can change it anytime later


The collection will then be shown in the OMS portal helping you monitoring your device collections.

Install the OMS Agent on the SCCM Server with the Connection Point

You must install the OMS agent on the server hosting the connection point to OMS



Import the collection on OMS

Connect to your OMS workspace portal ( and go to the Settings

You should see an SCCM tab as part of the Computer Groups section and activate the Import Configuration Manager collection membership


Leave a Comment

Your email address will not be published. Required fields are marked *

The reCAPTCHA verification period has expired. Please reload the page.