A woman reviews a digital staff scheduling dashboard on her laptop in a modern office.
Dynamics 365 Workforce Engagement Management (WEM) now lets supervisors and contact-center agents handle scheduling requests by chatting with Copilot. They don't have to open the workforce app. Microsoft's roadmap entry (ID 581992) describes the feature as launched. It lists preview availability as June 2026 and general availability as July 2026, for the web in the Worldwide multi-tenant cloud. We couldn't independently confirm those dates in the roadmap page, so treat them as Microsoft's listing rather than verified rollout facts.

A woman reviews a digital staff scheduling dashboard on her laptop in a modern office. What the feature does​

WEM Model Context Protocol (MCP) tools provide standardized workforce actions that AI experiences can use to retrieve and manage scheduling requests. They connect a conversational experience such as Service Agent with Dynamics 365 Customer Service and Dataverse. Users don't typically call MCP tools directly. They talk to Service Agent. Behind the scenes, Service Agent picks the right tool and shows the result in the chat.

Microsoft's own example is a supervisor who asks for pending time-off requests, reviews a specific request, and approves or rejects it without navigating to the workforce management application.

Microsoft's September announcement adds that version 1 ships three WEM MCP tools, accessible to supervisors and customer service representatives through Service Agent. The tools are:

ToolWhat it does
list_wem_requestsLists and filters time-off, shift-swap and shift-bid requests within the user's authorized scope
get_wem_request_detailsOpens one request with its details and scheduling context
decide_wem_time_off_requestApproves or rejects a pending time-off request, records the reviewer and review time, and saves a rejection reason

Who can do what​

Supervisors

  • They can list and filter requests for their planning group.
  • They can open a request to see its details and scheduling context.
  • With the required reviewer permission, they can approve or reject pending time-off requests.
  • A rejection must include a reason. It is saved as the reviewer note.

Customer service representatives

  • They can list their own time-off, shift-swap and shift-bid requests.
  • They can check a request's status and open its details.
  • They can't see other people's records.

The detail view is matched to the request type. Microsoft's tool reference says time-off requests show the type, whether it's a full day, start and end, hours and notes. Shift-swap requests show both sides of the swap, with dates, times and hours. Per the roadmap entry, request lists and details appear as interactive app-in-chat experiences. Approvals and rejections return a text confirmation.

The limits that matter​

  • Decisions cover time-off only. The decision capability applies only to time-off requests. It doesn't approve or reject shift swap or shift bid requests. Those two types can be listed and reviewed, but a supervisor still has to decide them in the regular WEM experience.
  • Decided requests stay decided. Microsoft's documentation says the decision tool doesn't overwrite an existing decision.
  • Security is inherited. Access follows existing Dynamics 365 and Dataverse security. Tool responses are limited to the records and actions the signed-in user is authorized to access. So there's no separate permissions framework to build, and no standalone mobile app is needed for these scenarios.
  • Reading and approving need different rights. The reference for the detail tool says WEM must be enabled and the signed-in user must have read access to WEM requests. Approving or rejecting additionally requires reviewer permission.

Setup caveats​

"No separate permissions framework" doesn't mean "no setup." Microsoft's Service Agent documentation says Service Agent is also a Microsoft 365 Copilot agent. It also says an administrator must set it up first. That includes installing the Service app and enabling Microsoft 365 Copilot for the Customer Service environment or applicable model-driven apps. The WEM tools are registered as part of the Service Agent tool catalog and accessed through the Microsoft Agent 365 Tooling Gateway, the same management layer used for Service Agent's other MCP tools.

The sources I reviewed don't give licensing requirements, a tenant enablement checklist, or any measurement of time saved. I'm not going to guess at those.

Analysis​

This is a narrow feature, and it's more useful for being narrow. Approving leave is the kind of small task that eats a supervisor's day. Making it a conversation is a reasonable fit for AI, as long as access control holds. By tying the tools to existing Dataverse roles, Microsoft sidesteps the worry that a chatbot becomes a back door into scheduling data.

Some caution is still warranted:

  • Test with real roles. Administrators should check with accounts at different permission levels. Confirm that a supervisor sees only their own planning group and that a representative sees only their own requests.
  • Review the audit trail. The tool records the reviewer and review time, which helps. Make sure it meets your HR and compliance expectations.
  • Expect a mixed workflow. Supervisors will approve time off in chat but still go back to the WEM app for swaps and bids.
  • More is planned. Future capabilities are planned for schedule visibility, leave balances, and clock in/out experiences. For now, that is Microsoft's stated direction, not shipped functionality.

For IT admins running Dynamics 365 Customer Service, the practical next step is to check that Service Agent is configured. Then pilot the three tools with a small group of supervisors and representatives before wider rollout.

 

References

  1. Manage workforce requests in Microsoft 365 Copilot Microsoft 365 Roadmap 2026-11-21T02:55:45.391708Z
  2. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com
  3. Overview of Dynamics 365 Workforce Management MCP tools learn.microsoft.com