The Microsoft Azure Management pack for SCOM 2012 R2 requires a
little different configuration than the commercial cloud. I am going to
write down some of the configurations that have to be done.
Link to download the mp:
Install the management pack and import the
mp’s in your scom environment.
The management pack documentation does a
fairly good job in explaining the configuration. If you have an user who
has read permissions to your Azure active directory and subscription
then you can add your Azure subscription using the credentials for the
user. But if you have an environment where dual authentication is
“enforced” you can use the steps given below. Because apps may not be able receive calls or enter the code in the messages :D
Creating the App for login:
Click Azure Active Directory–App Registrations
Click Add in the top pane and fill up the following parameters for your app.
Name: AnyName [Make a note of this name.]
Application Type: Web App/API
Sign-on URL:
http://anyurl This url does not have to be a working url.
Then click create.
Now select your app under App Registration and in the next blade that opens select Keys.
There is no add button here. If you enter a description for your key then the next values are populated.
Select the expiry duration. As of now the values are 1 year,2 years and Never expires.
Once you hit save then the key value will be displayed.
Important Note:
This will be shown only once so make sure that you copy this key value somewhere safe.
If you have exited then go back to Active directory–App registrations
select your app and copy the Application ID from the portal.
Click Active Directory–Domain Names and copy the Name of your domain if you don’t already know it.
These three values App id,domain name,Key will be required when you add your subscription in SCOM.
Now in the portal click on subscriptions.
Select the subscription you wish to monitor.
Click Access Control in the next blade.
Click Add,select role
Reader,Click add users if not already populated.
In the search under Add
users your app would not show up as it shows only users.
Enter the name
of your app and click select.Click ok and your app should have reader
permissions on your subscription.
Next open the SCOM Operations Console and create a new resource pool in
Administration– -Resource Pools called “Azure monitoring resource pool”.
Add the server that you want to be a member of this pool.
This is recommended because the operations are very resource
intensive and if you have a dedicated management server for this pool
you will not load the management group.
Navigate to Administration-Microsoft Azure.
Click Add subscription and click the radio button for Service Principal Name.
Remember the three values that i had asked your to copy. You will need them here.
Enter your domain name
Enter the Application ID in the Client ID field.
Enter the key in the password.
Click the advanced box and enter the following values. The forward slash “/” is also required in the ARM Management URI.
Storage Service DNS Suffix: core.usgovcloudapi.net
Your subscription should be populated in the next screen. Select the Azure monitoring server pool.
Next is self explanatory.
After this is done you should be able to see the subscription in
Monitoring–Microsoft Azure–Subscription State.
Now click Authoring and select Microsoft Azure Monitoring Template to configure the resources that you want to monitor.
More about that next time….
Export the management pack and open it in any text editor. You have to change the write action to powershell write action. Locate the enrty for write action and replace it with a powershell write action ID.
