Configure Microsoft 365 Yammer for the Next Generation API Data Protection

Configure Microsoft 365 Yammer for the Next Generation API Data Protection

To configure Microsoft 365 Yammer for the Next Generation API Data Protection, follow the instructions below.


Before configuring Microsoft 365 Yammer for the Next Generation API Data Protection, review the prerequisite.

  • A global administrator account is required to grant access to Netskope.

    • Netskope-Yammer integration relies on delegated permissions. Netskope recommends to create a dedicated service account (with global administrator role) exclusively for the Netskope integration. Revoking access to this service account will break the integration with Netskope. Creating a dedicated service account will ensure that the integration with Netskope will not break due to an exiting employee, and consequently a deactivation of the account.
    • The way permissions work in Azure/Office 365 is that Netskope requires an administrator to grant enough privileges for Netskope to perform specific actions. Note that the Netskope app does not receive global admin permissions. It only receives permissions for the scope Netskope requests.
  • Make sure the Microsoft 365 account has Yammer admin access. Check your organizations’ Yammer page to make sure your account has Yammer admin access:

    1. Log in to<replace with your-domain-name>/admin/set_admins.

    2. On the left navigation, click Admins and under Current Admins, ensure that the account you logged in with is displayed in the list.

      Microsoft 365 Yammer Current Admin List
  • You must turn on audit logging in Microsoft 365 admin center. To enable audit logging, follow the steps below:

    1. Log in to the left navigation, click Audit.

      If auditing is not turned on for your organization, a banner is displayed prompting you to start recording user and admin activity.

      Enable Audit Logging In Microsoft 365 Admin Center
    2. Click the Start recording user and admin activity banner.

      It may take up to 60 minutes for the change to take effect. After enabling, the first application event contents can take up to 12 hours to show up in Skope IT.
  • If you have guest or external users in your SaaS environment belonging to domains considered internal, you must set the appropriate internal domains for Netskope to classify exposure accurately. To set up internal domains, follow this article.

Configure Netskope to Access your Microsoft 365 Yammer Account

To authorize Netskope to access your Microsoft 365 Yammer account, follow the steps below:

  1. Log in to the Netskope tenant UI: https://<tenant hostname> and go to Settings > Configure App Access > Next Gen > CASB API.

  2. Under Apps, select Yammer and click Setup CASB API Instance.

    The Setup Instance window opens.

  3. Under Administrator Email, enter the email address of the user who will receive an email notification when a policy violation or event triggers. This step is optional.

  4. Under Instance Name, enter a name of the SaaS app instance. This step is optional and if left blank, Netskope will determine the name of the app instance post grant.

  5. Click Grant Access.

    The Microsoft Login window opens.

  6. Enter the global administrator username and password.

  7. Keep Consent on behalf of your organization unchecked and Accept the permissions.

    Microsoft 365 Yammer Permissions

    The Netskope CASB API app is installed in Azure AD with additional permissions once you grant access to the Microsoft 365 Yammer app.

Refresh your browser, and you should see a green check icon next to the instance name.

Next, you can can view the Next Generation API Data Protection Inventory page to get deep insights on various entities on your Microsoft 365 Yammer account. For more information on the Inventory page, see Next Generation API Data Protection Inventory.

You can receive audit events and standard user behavior analytic alerts in Skope IT. To know more: Next Generation API Data Protection Skope IT Events.

Next, you should configure a Next Generation API Data Protection policy. To do so, see Next Generation API Data Protection Policy Wizard.

Share this Doc
In this topic ...