← Back
Dynamics 365 Contact Center – Privileges and role-based access
MC1420635 · build prod-20251231-200323
Category
stayInformed
Severity
normal
Major change
False
Last modified
2026-07-08 14:33:15
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
Action by (AI)
2026-07-24 00:00:00
Services
Dynamics 365 Apps
Tags
New feature
Master tags
User, Admin, Security
Roadmap IDs

One-line summary

Role-based access for Entra ID agents in Dynamics 365 Contact Center is generally available July 24, 2026; admins can assign security roles at the team level via Entra security groups.

Similar updates

More like this

Details

Body (from Message Center)

We are announcing the ability to use role-based access for agents and customer service representatives using Microsoft Entra ID within Dynamics 365 Contact Center. This feature will reach general availability on July 24, 2026.

How does this affect me?
With this feature, admins can link a Microsoft Entra security group to a Dataverse team of the type Microsoft Entra ID Security Group and assign the required security roles once at the team level, such as Basic User, Customer Service Representative, and Omnichannel Agent. Every member of the linked group inherits those roles automatically, so agents get full functionality with no per-user role assignment, including Queue participation, Presence, and Conversation handling. When an agent belongs to more than one team, they receive the combined privileges of all their teams. Existing persona-based assignments continue to work, so current configurations continue to function without changes.

This feature is not enabled by default. To enable it:
  1. Create a Microsoft Entra security group and add your users as members.
  2. In the Power Platform admin center, create a Dataverse team, set its team type to Microsoft Entra ID Security Group, and link it to that security group.
  3. Assign the user security roles to the team rather than to individual users. After setup, adding a user to the Entra group provisions them into the Dataverse team automatically on first sign in, and removing them revokes access. Existing persona-based users remain supported, so you can adopt this model gradually for new users while leaving current users unchanged.
What action do I need to take?
This message is for awareness, and no action is required.

Raw JSON (for debugging)

Expand/collapse the full payload below.
Show/hide raw
{
  "snapshot_item": {
    "action_required_by": null,
    "ai_action_required_by": "2026-07-24T00:00:00Z",
    "ai_actions": [],
    "ai_master_tags": [
      "User",
      "Admin",
      "Security"
    ],
    "ai_model": "gpt-4.1",
    "ai_summary": "Role-based access for Entra ID agents in Dynamics 365 Contact Center is generally available July 24, 2026; admins can assign security roles at the team level via Entra security groups.",
    "ai_topics": [
      "Dynamics 365 Apps",
      "Dynamics 365",
      "Entra"
    ],
    "category": "stayInformed",
    "details_map": {},
    "id": "MC1420635",
    "importance": 4,
    "is_major_change": false,
    "last_modified": "2026-07-08T14:33:15Z",
    "ms_products": [
      "Dynamics 365 Apps"
    ],
    "platforms": null,
    "roadmap_ids": [],
    "services": [
      "Dynamics 365 Apps"
    ],
    "severity": "normal",
    "tags": [
      "New feature"
    ],
    "title": "Dynamics 365 Contact Center \u2013 Privileges and role-based access"
  }
}