SaaS Security
Onboard a Microsoft Teams App to SSPM
Table of Contents
Onboard a Microsoft Teams App to SSPM
Connect a Microsoft Teams instance to SSPM to detect posture risks.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
Or any of the following licenses that include the Data Security license:
|
To detect posture risks in your Microsoft Teams instance, SSPM connects to the
instance by using information that you provide. Once SSPM connects, it scans the
Microsoft Teams instance for misconfigured settings and will continue to run scans
at regular intervals.
There are two ways to onboard a Microsoft Teams app, depending on how you want SSPM
to scan your Microsoft Teams instance. Review the following information about these
two methods of scanning to decide which one you want SSPM to use. Before you onboard
Microsoft Teams to SSPM, there are certain actions you must take and certain
information you must gather. These actions will differ depending on the method you
choose.
- You can onboard a Microsoft Teams App for scans that use the Microsoft Graph
API. To enable SSPM to access the Microsoft Graph API, you create a client
application in Azure Active Directory (AD) with the necessary permissions, and
allow access to the application to users in your organization. During
onboarding, you will supply SSPM with Microsoft credentials for a user in the
organization with the necessary permissions. You will also supply the Client ID
of the Azure AD application. SSPM uses this information in a PowerShell call to
connect to the Microsoft Graph API. The account that you use for onboarding
cannot require MFA.This approach uses a published API.
- You can onboard a Microsoft Teams App for scans that use data extraction (also
known as web scraping). To perform this data extraction, SSPM logs in to
Microsoft Teams by using an administrator account. You can have SSPM access the
account directly or through the Okta or Microsoft Azure identity providers. If
SSPM will be logging in to the administrator account directly, then the account
cannot be configured for MFA. If SSPM will be accessing the account through Okta
or Microsoft Azure, then MFA is required. During onboarding, you will provide
SSPM with the administrator credentials. If SSPM will connect to the account
through an identity provider, you will also specify the information that SSPM
needs for MFA.This data-extraction approach scans more Microsoft Teams settings compared to the Microsoft Graph API approach.
Onboard a Microsoft Teams App for Scans That Use Data Extraction
Connect a Microsoft Teams instance to SSPM to detect posture risks.
High-level configuration scanning across Office 365
products is available by onboarding the Office 365 app. Adding the
Microsoft Teams app individually gives you greater visibility into Microsoft Teams
settings.
For SSPM to detect posture risks in your Microsoft Teams instance with more detail
than the Office 365 app scan, you must onboard your Microsoft Teams instance to
SSPM. Through the onboarding process, SSPM logs in to a Microsoft administrator
account. SSPM uses this account to scan your Microsoft Teams instance for
misconfigured settings. If there are misconfigured settings, SSPM suggests a
remediation action based on best practices.
There are two ways in which SSPM can scan your Microsoft Teams instance. The
following instructions describe how to enable SSPM to use data extraction techniques
(also known as web scraping) to perform its configuration scans. You can follow
alternative instructions that enable SSPM to use the Microsoft Graph
API to perform its configuration scans.
During the onboarding process, you will supply Microsoft Teams account credentials to
SSPM. SSPM can access the account directly or through the Okta or Microsoft Azure
identity providers. Having SSPM access the account through one of these identity
providers requires MFA, which adds an extra layer of security.
To onboard your Microsoft Teams instance, you complete the following actions:
Collect Information for Connecting to Your Microsoft Teams Instance
To access your Microsoft Teams instance, SSPM requires the following information,
which you will specify during the onboarding process.
| Item | Description |
|---|---|
| User | The username or email address of the
administrator account. The format that you use can depend on
whether SSPM will be logging in directly to your account or
through an identity provider. Required Permissions:
The user must be assigned to the Microsoft Global Admin
role. |
| Password | The password for the administrator account. |
If you are using Okta as your identity provider, you must provide SSPM with the
following additional information:
| Item | Description |
|---|---|
| Okta subdomain | The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization. |
| Okta 2FA secret | A key that is used to generate one-time passcodes for MFA. |
If you are using Azure Active Directory (AD) as your identity provider, you must
provide SSPM with the following additional information:
| Item | Description |
|---|---|
| Azure 2FA secret | A key that is used to generate one-time passcodes for MFA. |
As you complete the following steps, make note of the values of the items
described in the preceding tables. You will need to enter these values during
onboarding to access your Microsoft Teams instance from SSPM.
- Identify the Microsoft administrator account that SSPM will use to access your Microsoft Teams instance. The administrator must be assigned to the Microsoft Global Admin role.Determine whether you want SSPM to log in to the administrator account directly, or through an identity provider.Using an identity provider adds an extra layer of security by requiring MFA using one-time passcodes. You can use Okta or Microsoft Azure as the identity provider for accessing the administrator account. However, if you use an identity provider, SSPM requires more information for MFA.
- (For Okta log in) To access the administrator account through Okta:
- (For Microsoft Azure log in) To access the administrator account through Microsoft Azure:
Connect SSPM to Your Microsoft Teams Instance
By adding a Microsoft Teams app in SSPM, you enable SSPM to connect to your Microsoft Teams instance.- From the Add Application page ( ), click the Microsoft Teams tile.Under posture security instances, Add Instance or, if there is already an instance configured, Add New instance.Specify how you want SSPM to connect to your Microsoft Teams instance. SSPM can Log in with Credentials, Log in with Okta, or Log in with Azure.When prompted, provide SSPM with the administrator credentials. If SSPM is connecting to the account through an identity provider, specify the information that SSPM needs for MFA.Connect.
Onboard a Microsoft Teams App for Scans That Use the Microsoft Graph API
Connect a Microsoft Teams instance to SSPM to detect posture risks.High-level configuration scanning across Office 365 products is available by onboarding the Office 365 app. Adding the Microsoft Teams app individually gives you greater visibility into Microsoft Teams settings.For SSPM to detect posture risks in your Microsoft Teams instance with more detail than the Office 365 app scan, you must onboard your Microsoft Teams instance to SSPM. Through the onboarding process, SSPM connects to a Microsoft API and, through the API, scans your Microsoft Teams instance for misconfigured settings. If there are misconfigured settings, SSPM suggests a remediation action based on best practices.There are two ways in which SSPM can scan your Microsoft Teams instance. The following instructions describe how to enable SSPM to use the Microsoft Graph API to perform its configuration scans. You can follow alternative instructions that enable SSPM to use data extraction techniques to perform its configuration scans. To onboard your Microsoft Teams instance, you complete the following actions:Collect Information for Connecting to Your Microsoft Teams Instance
To access your Microsoft Teams instance, SSPM requires the following information, which you will specify during the onboarding process.Item Description Username The login email address for a Microsoft account. The account must not require multi-factor authentication (MFA).Required Permissions: The user must be assigned to one of the following roles.- Global Reader
- Teams Administrator
- Global Administrator
Password The password for the Microsoft account.Client ID SSPM will access a Microsoft API through an Azure AD application that you create. During the onboarding process, SSPM prompts you for a Client ID that uniquely identifies the application. As you complete the following steps, make note of the values of the items described in the preceding table. You will need to enter these values during onboarding to access your Microsoft Teams instance from SSPM.- Identify the Microsoft account that SSPM will use to access your Microsoft Teams instance.Account requirements:
- The account must have Global Reader, Teams Administrator, or Global Administrator permissions.
- The account must not require MFA.
After SSPM establishes the connection, it will perform an initial scan of your Microsoft Teams 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 Microsoft Teams again.Register an Azure AD Client ApplicationDuring onboarding, SSPM will access a Microsoft API through an Azure AD client application that you create. Follow the instructions to register a an Azure AD client application, and note the Client ID that Azure AD generates for the client app.If you have already onboarded another Microsoft application that requires an Azure AD client application, you can use that same Azure AD client app to onboard Microsoft Teams. If necessary, ask the administrator who registered the Azure AD client app for its Client ID.Do not continue to the next step unless you have obtained the Client ID. You will provide this information to SSPM during the onboarding process.Connect SSPM to Your Microsoft Teams Instance
By adding a Microsoft Teams app in SSPM, you enable SSPM to connect to your Microsoft Teams instance.- From the Add Application page ( ), click the Microsoft Teams Powershell tile.Under posture security instances, Add Instance or, if there is already an instance configured, Add New instance.Log in with Credentials.When prompted, provide SSPM with the Microsoft user credentials and the Client ID of the Azure AD application.Connect.
