Add Community Member
Add one Microsoft Entra user to a Viva Engage community by adding the user to its associated Microsoft 365 group. Requires group_id from community.groupId, not the Viva Engage community ID.
Manage Viva Engage communities, members, owners, and engagement role discovery and assignments through Microsoft Graph.
Add one Microsoft Entra user to a Viva Engage community by adding the user to its associated Microsoft 365 group. Requires group_id from community.groupId, not the Viva Engage community ID.
Atomically add up to 20 users to a Viva Engage community's associated Microsoft 365 group. If any user reference is invalid, no users are added.
Make one Microsoft Entra user a Viva Engage community admin by adding the user as an owner of the community's associated Microsoft 365 group. This grants administrative privileges: confirm the target user and group before calling. Add the owner as a member separately if member capabilities are also required. Requires group_id from community.groupId, not the Viva Engage community ID.
Assign one predefined Viva Engage administrative or corporate communication role to a Microsoft Entra user. This changes the user's privileges; confirm both the role and target user before calling. Retain the returned member ID for safe removal; Graph currently uses the target user ID as that member ID when this route returns 204.
Start asynchronous creation of a Viva Engage community. This provisions Microsoft 365 tenant resources and returns an operation reference; poll the operation separately before treating the community as created.
Permanently delete a Viva Engage community and all associated Microsoft 365 content, including its connected group, OneNote notebook, and Planner plans. This destructive action cannot be undone.
Get one Viva Engage community by community ID, including its distinct associated Microsoft 365 group ID.
Get the status and resulting resource reference for a Viva Engage asynchronous operation such as community creation. Make separate calls more than 30 seconds apart while polling.
List Viva Engage communities in the tenant, one Microsoft Graph page at a time, including each community ID and associated Microsoft 365 group ID.
List direct members of a Viva Engage community's associated Microsoft 365 group, one Microsoft Graph OData page at a time. Requires group_id from community.groupId, not the Viva Engage community ID. Hidden members are visible only when the connection also has Member.Read.Hidden.
List owners of a Viva Engage community's associated Microsoft 365 group, who are community admins, one Microsoft Graph OData page at a time. Requires group_id from community.groupId, not the Viva Engage community ID.
List Viva Engage roles assigned to the signed-in work or school user, one Microsoft Graph page at a time.
List Viva Engage roles assigned to a specified Microsoft Entra user, one Microsoft Graph page at a time.
List users assigned to one predefined Viva Engage role and return the selected assignment properties. Include id for later removal and userId for identity correlation. Requires a role_id from List Viva Engage Roles and a native-mode Viva Engage network; legacy and external networks are unsupported.
List the predefined administrative and corporate communication roles that can be assigned in Viva Engage, one Microsoft Graph page at a time. Custom roles cannot be created, and this API supports only native-mode Viva Engage networks with a work or school account.
Remove one user from a Viva Engage community's associated Microsoft 365 group, revoking community membership without deleting the user object. Dynamic-group memberships cannot be changed with this action. The request always retains the safety-critical /$ref suffix.
Remove a user's community admin status by removing the user as an owner of the Viva Engage community's associated Microsoft 365 group. This is destructive to admin access: verify another user owner remains because Microsoft Graph does not allow removal of the last user owner. The request always retains the safety-critical /$ref suffix.
Revoke one user's Viva Engage role assignment. This can remove administrative or corporate communication privileges: confirm the role and assignment before calling. Use the role_member_id returned by listing or assigning role members; Graph currently uses the target user ID as this member ID on assignment.
Update a Viva Engage community's name, description, or privacy by community ID. Provide at least one field; omitted fields remain unchanged.
The Microsoft Viva Engage integration connects your Dench AI CRM directly to Microsoft Viva Engage, so agents can read and act on your Microsoft Viva Engage data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
19 actions are available for agents to invoke on your behalf. Every call runs through Microsoft Viva Engage's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Microsoft Viva Engage and click Connect — you'll authorize access through Microsoft Viva Engage's own sign-in flow. No API keys or code required.
Ask an agent to use Microsoft Viva Engage in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Microsoft Viva Engage integration connects your AI CRM to Microsoft Viva Engage, so AI agents can work with your Microsoft Viva Engage data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Microsoft Viva Engage integration currently exposes 19 actions, including Add Community Member, Add Community Members in Bulk, Add Community Owner, Assign Engagement Role Member, Create Community, and Delete Community. Agents invoke them on your behalf from chat or from automations.
No. You connect Microsoft Viva Engage from your Dench workspace using Microsoft Viva Engage's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Microsoft Viva Engage's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Microsoft Viva Engage connection from your workspace settings at any time.