: Onboard an Office 365 App to SSPM
Focus
Focus

Onboard an Office 365 App to SSPM

Table of Contents

Onboard an Office 365 App to SSPM

Connect an Office 365 instance to SSPM to detect posture risks.
For SSPM to detect posture risks in your Office 365 instance, you must onboard your Office 365 instance to SSPM. Through the onboarding process, SSPM connects to a Microsoft API and, through the API, scans your Office 365 instance at regular intervals for misconfigured settings. If there are misconfigured settings, SSPM suggests a remediation action based on best practices.
Connecting to Office 365 enables SSPM to scan settings at a high level based on Microsoft's Secure Score. For greater visibility into a particular application in the Office 365 product family, onboard the individual product app. By adding an individual product app, you enable SSPM to scan more settings for the particular product. To scan more settings for Microsoft Word, Microsoft PowerPoint, and Microsoft Excel, onboard Office 365 - Productivity Apps. Other products in the Office 365 product family have their own tiles on the Applications page, and you can onboard these apps separately.
SSPM gets access to your Office 365 instance through OAuth 2.0 authorization. During the onboarding process, you are prompted to log in to Office 365 and to grant SSPM the access it requires.
To onboard your Office 365 instance, you complete the following actions:

Identify the Account for Granting SSPM Access

During the onboarding process, SSPM redirects you to log in to Office 365. After you log in, Office 365 will prompt you to grant SSPM the access it needs to your Office 365 instance.
  1. Identify the Office 365 account that you will use to log in to Office 365 during onboarding.
    SSPM will use this account to establish a connection to your Office 365 instance. After SSPM establishes the connection, it will perform an initial scan of your Office 365 instance, and will then run scans at regular intervals of approximately 30 minutes. For SSPM to run these scans, the administrator account that you use to establish the initial connection must remain available. For this reason, we recommend that you use a dedicated service account to grant SSPM access. If you delete the service account, the scans will fail and you will need to onboard Office 365 again.
    Required Permissions:
    To grant SSPM the access it needs to connect to your Office 365 instance and to perform configuration, risky user, and third-party plugin scans, the account must be assigned to all of the following roles:
    • Global Administrator
    • Security Administrator
    • User Administrator
  2. Log out of all Microsoft accounts.
    Logging out of all Microsoft accounts helps ensure that you log in under the correct account during the onboarding process. Some browsers can automatically log you in by using saved credentials. To ensure that the browser does not automatically log you in to the wrong account, you can turn off any automatic log-in option or clear your saved credentials. Alternatively, you can prevent the browser from using saved credentials by opening the Cloud Management Console in an incognito window.

Connect SSPM to Your Office 365 Instance

By adding an Office 365 app in SSPM, you enable SSPM to connect to your Office 365 instance. You must consent to specific permissions when adding the Office 365 app.
  1. From the Add Application page (
    Posture Security
    Applications
    Add Application
    ), click the Office 365 tile.
  2. Under posture security instances,
    Add Instance
    or, if there is already an instance configured,
    Add New
    instance.
    SSPM redirects you to the Office 365 login page.
  3. Enter the credentials for the administrator account that you identified earlier, and sign in to Office 365.
    Microsoft displays a consent form that details the access permissions that SSPM requires.
  4. Review the consent form and allow access.

Recommended For You