Skip to main content
The Microsoft Viva Engage connector allows Glean to index messages from public and private communities, making them searchable within Glean. The connector supports instances running in Native Mode and uses the Data Export API to keep content up to date. To ensure data integrity and security, all data remains within your cloud environment, and Glean strictly enforces user permissions during search.

​
Supported objects

The Microsoft Viva Engage connector indexes public and private community messages.

​
Supported API endpoints

For information on supported API endpoints, see the Microsoft Viva Engage Data Export API documentation.

​
Limitations

The Microsoft Viva Engage connector indexes community messages and has the following limitations:
  • Direct Messages: Private messages between individual users are not crawled or indexed.
  • Real-time Updates: The connector relies on scheduled crawls for updates and does not support webhooks or near-realtime activity tracking.
  • Files: Files are not indexed by this connector, as they are handled by the SharePoint connector.
  • Reactions: Likes and reactions to posts cannot be acquired from the Data Export API.
  • Deployment: The connector is designed for cloud-hosted Microsoft Viva Engage instances in Native Mode and does not support on-premise variants.

​
Requirements

To enable the Microsoft Viva Engage connector, you must meet the following requirements:
  • Your Microsoft Viva Engage instance must be running in Native Mode.
  • You must have a Microsoft Viva Engage Verified Administrator account and permissions to register applications in Azure Active Directory.
  • You must obtain the following from your Azure AD application:
    • Client secret
    • Application (client) ID
    • Directory (tenant) ID
  • The connector app must be granted the following delegated permissions in Azure AD:
    • Microsoft Viva Engage:
      • access_as_user
      • user_impersonation
    • Microsoft Graph:
      • User.Read
      • offline_access
      • email
      • openid
      • profile

​
Set up instructions

To connect Glean to Microsoft Viva Engage, you need to gather the following credentials from the Azure portal: Client ID, Client Secret, and Directory (tenant) ID. These credentials are used to configure the connector in the Glean Admin Console.

​
Step 1: Register a new application in Azure AD

  1. Sign in to your Azure portal as an administrator.
  2. Select Microsoft Entra ID, and navigate to Manage > App registrations > New registration.
  3. On the Register an application page, enter the following details:
    • Name: Glean Viva Engage Application
    • Supported account types: Accounts in this organizational directory only (Single tenant)
    • Redirect URI: Select Web and enter the URL: https://[your-domain]-be.glean.com/instance/viva-engage/oauth/verify_code Note: Replace [your-domain] with your company’s unique Glean domain.
  4. Click Register.

​
Step 2: Configure API permissions

Grant the Glean application the necessary permissions to access Microsoft Viva Engage data.
  1. On the left side navigation on the Overview page, click Manage > API Permissions.
  2. Click Add a permission and select Microsoft Graph.
  3. Choose Delegated permissions and add the following permissions:
    • User.Read
    • offline_access
    • email
    • openid
    • profile
  4. Click Add a permission again and select Viva Engage.
  5. Choose Delegated permissions and add access_as_user and user_impersonation.
  6. Click the Grant admin consent button to finalize the permissions.

​
Step 3: Generate client secret and copy Application (client) ID and Directory (tenant) ID details

  1. Navigate to Microsoft Entra ID > Manage > App registrations and click on the application that you created earlier.
  2. From the left-hand navigation pane, select Manage > Certificates & secrets.
  3. Under Client secrets, click New client secret.
  4. Enter a descriptive name and select a recommended expiry time, such as 24 months, then click Add. For more information, see Certificates & secrets.
  5. Copy the Value of the new secret. This is your client secret, and it will not be displayed again after you leave this page.
Note: It is important that you save the secret value, not the secret ID.
  1. After copying the secret, navigate back to the Overview page for your application.
  2. Copy the Application (client) ID and the Directory (tenant) ID from the Essentials panel. For more information, see Register an application.

​
Step 4: Connect in Glean

With all three credentials in hand, you can now complete the setup in the Glean Admin Console.
  1. In the Glean Admin Console, navigate to Data Sources and select Add Data Source, and select Yammer.
  2. Enter a Name for your data source. This name will appear to all teammates in search results.
  3. Enter the following values into their corresponding fields:
    • Client secret
    • Application (client) ID
    • Directory (tenant) ID
  4. Click the Authorize button and follow the generated link to sign in with your Verified Administrator account.
Upon successful authorization, your connection to Microsoft Viva Engage is complete, and Glean will begin the initial crawl.

​
Permissions & security

  • Permission propagation: The connector honors Microsoft Viva Engage’s permission model. It uses community/group membership to determine access, ensuring users only see messages from communities they are members of.
  • Privileges: The connector uses OAuth 2.0 delegated authentication and only requests the specific scopes required for its operation, ensuring access is limited.
  • Data privacy: Data extraction is performed by Glean within the customer’s cloud environment. All indexed data respects source system permissions and does not leave the customer’s environment.