Monitoring Office 365 with System Center Operations Manager 2012

Standard

In this blogpost I am going to take you true the steps that I took to implement the Office 365 Management pack for System Center Operations Manager. You can download the Office 365 management pack from here

I took the following steps to import and configure the management pack:

  • Configure a cloud user account
  • Install the Office 365 Management pack
  • Import the Office 365 Management pack
  • Configure the Office 365 Subscriptions

When you want to monitor the Office 365 we need to create a Office 365 user account with Global Administrator permissions. Take the following steps to create a Office 365 user

  1. Go to https://portal.microsoftonline.com 
  2. Login with a account that has the Global Administrator right.
  3. On the “Admin Center” page, in the “Users” block click “Add a user
    Create Monitoring Account in Office 365
  4. In the “Create User Screen” enter the following data:
    • First name: Office365Monitoring
    • Display name: Office365Monitoring
    • Expand “Roles” and select “Global Administrator
    • Expand “Product licenses” and select “Create user without product license
    • Click “Add
      Create Monitoring Account in Office 365
  5. In the “Create User Screen” enter the email address where you want to sent the user password to  and click “Send email and close

When you create the above account login to office365 management portal to change the password. If you don’t change the password you can get the following error:

Authorization Failed

Before we can import the management pack we need to install the management pack

  1. Click “System Center Management Pack for Office 365.msi
  2. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “License Agreement” page, select “I accept” and click “Next
    System Center Management Pack for Office 365
  3. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “Select Installation Folder” page, select “Everyone” and click “Next
    System Center Management Pack for Office 365
  4. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “Confirm Installation” page, click “Install
  5. In the “System Center Management Pack for Office 365 – Installer” wizard, on the “Installation Completed” page, click “Close

After installing the Office 365 Management pack we need to import the management pack into System Center Operations Manager

  1. Start the "Operations Manager Console"
  2. In the “Operations Manager Console” click “Administration
  3. Right click “Management Packs”, and the click “Import Management Packs
    Import Microsoft Office 365 Management Pack
  4. The “Import Management pack wizard” opens. Click “Add”, and the click “Add from Disk
    Import Microsoft Office 365 Management Pack
  5. The Select Management Packs to import dialog box appears. If necessary, change to the directory that holds your management pack file. Select the following files:
    • Microsoft.SystemCenter.O365.mpb 
      Import Microsoft Office 365 Management Pack 
  6. In the “Import Management Pack” wizard, Click “Install
  7. In the “Import Management Pack” wizard, Click “Close

Know that the Office 365 management pack is imported it is time configure the management pack

  1. Start the “Operations Manager Console
  2. In the “Operations Manager Console” click “Administration
  3. On the “Administration” page click “Office 365Configure Office 365 Management Pack 
  4. On the “Office 365” page, click “Add Subscription
    Configure Office 365 Management Pack
  5. In the “Add Subscription” wizard, on the “Subscription Configuration” page enter the following data “Subscription Name”, “User Name”, “Password” and click “Next
    Configure Office 365 Management Pack
  6. In the “Add Subscription” wizard, on the “Server Pool” page, select the “All Management Servers Resource Pools” and click “Add Subscription
    Configure Office 365 Management Pack
  7. In the “Add Subscription” wizard, on the “Completion" page, click “Finish

The end result should look something like this:

Configuration Completed

12 thoughts on “Monitoring Office 365 with System Center Operations Manager 2012

  1. Kasun

    Hi,

    I’m also get this error “Authentication Failed”.

    I created a Global admin account in O365 tenant.
    Then I reset the password and enter the password i usually use.
    I install the MP and add the subscriptions using admin panel in SCOM.

    But still i get the above error.

    • Hi Kasun,

      Thanks for the comment.

      To resolve this issue, make sure that there are no network restrictions that are prohibiting a connection between the Management server and the Office 365 portal endpoint. Most connections use TCP 443, or else they first connect over TCP 80 and are redirected.

      Also make sure that the credentials for the Office 365 subscription’s account are correct and that you have granted access to the Office 365 API Endpoint. You can test your access to https://office365servicehealthcommunications.cloudapp.net/ from the Management server. When you do this, you may encounter an “access denied” error, but this indicates that there are no restrictions to the Office 365 API Endpoint.

      More information can be found here

      Hope it helps

      Greetings Roel Knippen

  2. Chris

    I had previously added the MP and removed it however I’ve now re-added it back in however when I go to configure the subscription, I receive the following message;

    Could not create Subscription object
    A discovery data item was rejected because the item has already been inserted by another user or process.

  3. Chris

    I’ve just tried again and this is what shows in the log file (doesn’t make a lot of sense to me):

    An exception was thrown while processing ProcessDiscoveryData for session ID uuid:3561c1a0-de80-475a-8128-57fa4b8a0944;id=13.
    Exception message: A discovery data item was rejected because the item has already been inserted by another user or process.
    Full Exception: Microsoft.EnterpriseManagement.Common.DiscoveryDataInsertionCollisionException: A discovery data item was rejected because the item has already been inserted by another user or process.
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.SingleUpsertInstance(DiscoveryDatabaseApi dbApi, DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData)
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.SingleAddUpdate(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.Write(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithNoRetryUnauthorized(DiscoveryDatabaseApi dbApi, Boolean useProcessContext)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.ProcessIncrementalDiscoveryData(DatabaseConnection databaseConnection)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.Process()
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithRetry(HandleProcessing handleProcessing, RetryPolicy retryPolicy)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.ProcessDiscoveryDataWithRetry(DatabaseConnection dbconnection, Guid discoverySourceId, IList1 sdkEntityInstances, IDictionary2 streams, IContext context)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryData(Guid discoverySourceId, IList1 entityInstances, IDictionary2 streams, ObjectChangelist`1 extensions)

    • Hi Chris,

      Do you have any notification subscription running regarding Office 365. I did the same steps ass you described. Removed the office management pack. And then reimported it. I Didn’t get the errors you are talking about.

      greetings Roel Knippen

  4. Chris

    Hi Roel,

    I only have 1 subscription running which is used to email our service desk generated alerts.

    Notify on all alerts
    of a ‘Critical’ severity
    and of a ‘Medium or High’ priority
    and with ‘New (0)’ resolution state

    • Hi Chris,
      Can you disable all the descriptions that are running on you system center operations manager deployment and then import the management pack.
      Greetings Roel Knippen

  5. Chris Cundy

    Hi Roel,
    I’ve done this – the only subscription I have is an email subscription that goes to our Service Desk. We’re due to install a fresh SCOM 2016 instance in the next couple of weeks which should resolve this anyhow.

Leave a Reply

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