Onboard an Office 365 App to SSPM Using OAuth 2.0

Onboard an Office 365 App to SSPM Using OAuth 2.0

1. 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 configuration scan of your Office 365 instance, and will then run scans at regular intervals.

      When you onboard Office 365, SSPM gives you an option to connect with read-only permissions or with read and write permissions. The onboarding screen lists the API scopes that SSPM requires for each type of scan that it can run. The onboarding screen also lists the API scopes that SSPM requires to perform certain actions on your behalf. For example, if SSPM is granted permission to certain scopes, you can revoke a user's access to a third-party plugin through SSPM. After establishing a connection, SSPM will notify you if it is unable to run certain scans, or complete certain actions, because the account did not have the permissions to grant access to certain scopes.

      Onboarding Office 365 with read-only permissions will enable SSPM to perform configuration scans, risky account scans, and third-party plugin scans.

      Connecting with read and write permissions enables additional SSPM features, including the following features:

      • The ability to revoke a user's access to a third-party plugin.
      • Scans for MFA enrollment issues, which SSPM reports on the Identity Security dashboard.
      • Scans for user sign-in activities, which SSPM displays on the Identity Security dashboard.
      • The ability to force a user out of their current SaaS application sessions from the Identity Security dashboard.

      Required Permissions: To grant SSPM access to either the read-only scopes only or access to read and write scopes, the account must be assigned to the Global Administrator role.
   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.
2. 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 SecurityApplicationsAdd Application), click the Office 365 tile.
   2. On the Posture Security tab, Add New instance.
   3. Specify whether you want SSPM to connect with Read Permissions only or with Read and Write permissions.

      The onboarding page lists the API scopes that SSPM will access to complete basic scans and to perform advanced scans and actions.
   4. Connect with Office 365

      SSPM redirects you to the Office 365 login page.
   5. Enter the credentials for the Microsoft account that you identified earlier, and sign in to Office 365.

      Microsoft displays a consent form that details the access permissions that SSPM requires.
   6. Review the consent form and allow the requested permissions.

      SSPM connects to your Office 365 instance, and displays whether it was able to access the API scopes that it requires for its scans and other actions. If SSPM is unable to access necessary scopes, it indicates which scans and actions it will not be able to perform.