A Dynamics 365 Human Resources infographic outlines a coordinated employee offboarding workflow and team responsibilities.
Microsoft has put a sizeable offboarding overhaul for Dynamics 365 Human Resources on its AI at Work roadmap. It is planned, not shipped. The roadmap lists the item as in development. It gives an estimated public preview in March 2027 and general availability in June 2027. The scope is the Web platform and the Worldwide (Standard Multi-Tenant) cloud. Microsoft says roadmap dates and descriptions can change.

The pitch is simple. When someone leaves, HR, the manager, IT, facilities and payroll each have work to do. In practice, the termination action often isn't tied to the request that started the exit, or to the follow-up work. Microsoft's description says manual coordination can leave access open, property unreturned and final pay incomplete. The feature aims to connect these pieces into one governed, visible exit journey. That is Microsoft's own framing, and no one has independently verified it.

A Dynamics 365 Human Resources infographic outlines a coordinated employee offboarding workflow and team responsibilities. What exists today​

Dynamics 365 Human Resources already has offboarding tools. Task management creates the tasks needed to hire, terminate and transfer employees, and it uses checklists. Checklists group tasks and assign them to individuals or groups.

Microsoft Learn describes the current Offboarding tab. It lists exiting and already-exited employees. It also has an all-tasks list, an overdue list and a list of tasks assigned to you. On all three tabs, HR assistants and managers can apply a checklist to an employee, reassign a task and update a task's due date. Per Microsoft's terminate-workers guidance, the current process also depends on pre-configured offboarding setup, offboarding checklists, reason codes and personnel action types.

The roadmap item builds on that base. It does not say these capabilities are already shipped, and I can't confirm that any of the new elements below exist today.

What the roadmap says is coming​

The description covers a lot of ground. Here it is by area:

  • Separation requests: Employees can resign and managers can request separations in self service. Approval and policies vary by company and worker type.
  • Safer termination: Notice details, configurable checks, bulk termination and moving direct reports.
  • Rule-based checklists: Templates apply automatically when conditions match. They support due-date anchors and predecessor tasks.
  • Property and access: Return tasks for loaned items such as laptops and badges. Dynamics 365 access can be deactivated on a schedule.
  • Task evidence: Attachments, exit questionnaires, generated or signed documents, verification and task history.
  • Follow-up: Reminders, business events and legal hold for overdue tasks and connected systems.
  • Workspaces: An "Offboarding control tower" for HR, "Exiting workers" for managers and "My exit" for leavers.
  • Final settlement worksheet: Open expenses, advances, timesheets, leave and unreturned property, surfaced for payroll.
  • Rehire guard: Warns or blocks rehiring based on eligibility. An approved override is possible.
  • Roles and integration: Coordinator roles, a segregation-of-duties rule and public data entities.

Where the edges are​

Read the description carefully before you plan around it.

  • Access deactivation covers Dynamics 365 only. The roadmap names scheduled deactivation of Dynamics 365 access. It doesn't say the feature disables Entra accounts, Microsoft 365 licences, mailboxes or third-party apps. Microsoft Learn's general guidance lists those steps: disable sign-in credentials, remove network access, revoke software licences and collect badges. They are things an organisation should do. They are not things this feature is promised to do. IT teams should keep their existing identity and device offboarding processes in place until they have tested the new feature.
  • The settlement worksheet is a view, not a payroll engine. It is described as showing open items for payroll. Microsoft's termination guidance lists the work around an exit: final pay, accrued leave, outstanding loans or advances, tax withholding, benefit deductions and records. The roadmap doesn't claim the worksheet calculates or processes any of that, or that it ensures legal compliance. Rules vary by jurisdiction.
  • Integration details are missing. The record lists business events, legal hold and public data entities. It doesn't say which external systems are supported, how legal hold behaves or what the entity schema looks like.
  • Several implementation details are unstated. The roadmap doesn't give approval flows, permission models or supported legal entities. It doesn't say whether every capability works in every environment.

What admins will have to do​

This is not a single-toggle feature. The roadmap says to turn on 12 offboarding features in Feature management. After that, you configure Human resources shared parameters, separation policies, checklist rules, coordinator roles and batch jobs. The roadmap also says turning a feature off keeps existing data. It doesn't list the 12 switches or explain what happens to in-flight processes when one is disabled. Don't assume a rollback undoes completed actions.

A sensible way to prepare now:

  1. Review your current offboarding checklists. Note which tasks are really conditional on worker type, location or role. Those are candidates for rule-based templates.
  2. Map who owns each exit task across HR, IT, facilities and payroll. Coordinator roles and the segregation-of-duties rule will need that mapping.
  3. Decide how scheduled Dynamics 365 deactivation fits with your wider identity offboarding.
  4. Write down your rehire-eligibility policy and who may approve an override.
  5. Plan to test in the March 2027 preview before relying on any of this in production.

Analysis​

Much of this fits a long-standing complaint about HR systems. Exits are handled by people across departments, and a single missed task can leave access open or property unreturned. Tying the request, termination, tasks and settlement together should help with that. The evidence fields, task history and segregation-of-duties rule suggest Microsoft expects auditors to care.

The counterpoint is that a roadmap entry is a promise to deliver, not proof of it. Much depends on details the entry doesn't give, such as how deep the integrations go. Dates have slipped on roadmaps before. Organisations that run most of their identity and device lifecycle outside Dynamics 365 should expect this to complement their existing offboarding process, not replace it. Those are my own judgments from general industry experience, not statements from Microsoft.

Microsoft has said it is moving Dynamics 365 roadmap content onto the AI at Work roadmap. So check that roadmap and Microsoft's release communications again before committing deployment dates.

 

References

  1. Dynamics 365 Human Resources: Streamline the employee offboarding experience Microsoft 365 Roadmap 2026-11-20T23:20:27.871175Z
  2. Task management - Human Resources | Dynamics 365 | Microsoft Learn learn.microsoft.com
  3. Overview of the Terminate workers business process - Dynamics 365 | Microsoft Learn learn.microsoft.com