Updated recently
Last updated:
Quick Answer: This dynamics 365 human resources guide covers what the product is: a Dataverse-backed HR system of record for workers, positions, hierarchies, compensation, benefits, time and absence, recruiting, performance and learning, with an employee self-service surface in Dynamics 365 and inside Teams. The most important thing to understand is what it is not — there is no native payroll, and that decision shapes most Indian implementations. If you are new to the platform, our broader Dynamics 365 complete guide covers the wider suite first.
Dynamics 365 Human Resources Guide: The Modules That Matter
Microsoft groups the functionality into named areas. The names are not bureaucracy — interview questions and scoping documents use these exact terms, and buying a licence for the wrong area is expensive.
| Area | What it actually does | Who touches it |
|---|---|---|
| Core HR | Employee records: person, worker, employment, employment history, bank details, dependents, personal details, contact and emergency information. The base layer everything else sits on. | HR operations, HRIS team, data migration |
| Organizational management | Legal entities, departments, job functions, positions, cost centres, and the organisational hierarchies that define reporting lines and the chain of command. | HR leadership, org design, reporting |
| Compensation management | Compensation structures, grade bands, fixed and variable compensation, earning statements, and compensation events that change what someone is paid. | Compensation and benefits, HR leadership |
| Benefits | Benefit plans, eligibility rules, benefit programs and the link between a benefit and the employee records who qualify for it. | Benefits administration |
| Time and absence | Leave types, leave requests, leave balances, absence requests, calendars, work patterns and shift templates — the module Indian clients care about most because of statutory leave. | Every employee, payroll, HR ops |
| Recruiting | Hiring managers, recruiting requests, job postings, candidate applications, interview scheduling and offers, feeding into Core HR on hire. | Talent acquisition |
| Onboarding and offboarding | Structured onboarding steps and tasks, checklist-driven offboarding, and equipment or access hand-offs tied to an employee record. | HR ops, IT, facilities |
| Performance | Performance review templates, review cycles, goals and ratings, stored against the employee record. | Managers, HR business partners |
| Learning (training) | Training courses, course catalogues, attendance and completion, with the data model hosted in Dataverse and delivery often handled in Teams or SharePoint. | L&D, HR |
| Employee self-service | The Employee Self-Service app plus the Employee Hub experience in Microsoft Teams — request leave, view balances, update details, see org context. | Every employee |
Two structural facts do most of the explanatory work. First, the record model separates the person from the employment and the position. A person is the human being. An employment is that person’s relationship with a legal entity — dates, type, cost centre. A position is a slot in the org chart carrying the reporting line and job function, and it can exist with nobody in it. That three-way split is why one individual can hold two employments, why a contractor can sit on the org chart, and why vacancies are not bugs.
Second, the whole model lives in Dataverse — the Power Platform data store Dynamics 365 applications use. That is why Power Apps, Power Automate and Power BI can reach HR data directly, why the entity framework lets you add custom fields, and why the “Microsoft Dynamics 365 Human Resources” license is really a Power Platform license with an HR app on top.
The Org Backbone: Positions, Hierarchies and Legal Entities
Most implementations go wrong in the first month, and they go wrong in the org model. Get this right and the rest of the project mostly configures itself.
Conceptual illustration — Dynamics 365 HR org setup (not a UI script)
Legal entity: Acme India Pvt Ltd
Department: Engineering
Job function: Software Engineering
Position: Senior Software Engineer (position id P-1043)
Reports to: Engineering Manager (position id P-1012)
Worker: W-00982 Priya Raman
Employment: E-00982 full time, legal entity = Acme India,
cost centre = ENG-BLR-01, start 12-Aug-2021
Employment history: prior employment 2019-2021, employer = Beta Systems
Compensation: fixed = grade band B3, variable = 10% of target,
effective 01-Apr-2026
Rules the model enforces for you:
- a position with no incumbent is a vacancy, not an error
- a person can hold more than one employment, so a rehire is a new
employment record, not an edit of the old one
- reporting lines live on positions, so a reorg is a position update
and not 900 employee record edits
Three decisions drive everything downstream. Do you model the org by position or by job title? Position, always — titles are a data attribute, positions are the structure, and building on titles makes every reorganisation a mass data edit. Do you allow multiple reporting hierarchies (a dotted line to a project manager)? It is a real requirement in matrixed organisations and it doubles the org-design work. And do you allow an employee to hold a position they do not occupy, or do you create a vacancy? Indian clients routinely want “open positions” visible in the org chart, so vacancies become positions with no incumbent, and headcount reporting has to exclude them.
The legal entity layer is what makes a multi-country implementation hard. The employee record is global; the employment is local. Leave, compensation currency, statutory benefits and payroll attach to the employment, not the person. A single Indian entity inside a global parent with 3,000 employees elsewhere is a very different project from one entity with 300 employees — and the second is what most Indian Dynamics 365 HR deals are.
Time and Absence: The Module Indian Clients Actually Care About
Ask an Indian HR team what they want from an HRMS and you hear about leave before anything else. Earned leave, sick leave, casual leave, maternity leave, loss of pay, and entitlement tables that change with tenure. Most Indian private-sector leave also accrues monthly rather than as a flat annual grant.
Here is the trap: Dynamics 365 Human Resources models leave entitlement as a leave plan plus a leave request against an employee, with balances derived from the plan and the calendar. The plan holds the entitlement rules; the employee holds the balance. It works when the plan mirrors the Indian accrual pattern and the calendar reflects the April-to-March financial year, with different holidays in every plant.
The second trap is attendance. Indian clients often want attendance and shift management — biometric output, shift rosters, overtime, present/absent marking. That is not leave management, and it typically arrives as a third-party attendance integration or a custom build. If attendance is the real requirement, say so during scoping, because that is a separate product conversation and pretending otherwise is how timelines slip.
Employee Self-Service: Where the Project Value Actually Lives
For many Indian clients, “implement Dynamics 365 Human Resources” really means “give employees self-service and stop the HR inbox”. That framing changes the build order: employee self-service is not a phase-two nice-to-have, it is the deliverable the business sponsor is funding.
The mechanics are straightforward once you know them. The Employee Self-Service app is a model-driven app over the same Dataverse tables, secured by role and row-level security so a person sees their own records and their team’s, and nobody sees a peer’s salary. The Employee Hub in Microsoft Teams is the surface most employees will use, because it lives where they already work — approve leave, check a balance, update a phone number. Behind it, Power Automate flows handle notifications and escalations: leave approval routing, reminders, joining-letter triggers, and the alert to IT that a leaver needs access revoked.
The real engineering challenge is not the app. It is the data protection and audit story. Employee records are among the most sensitive data an employer holds, and “who can see what” is a hard question. Security roles, business units and organisational-hierarchy access must be designed together with the org model, not bolted on at the end. A self-service app that exposes compensation data is a career-ending incident, and it is the most common thing I see go wrong in review.
What Dynamics 365 Human Resources Does Not Do
Being precise about the gaps is more useful than a feature tour, because the gaps are where projects fail.
- No native payroll. Indian payroll, statutory compliance, payslips and filings come from a partner ISV or a separate payroll product. In most deals the client already has payroll running and Dynamics 365 HR feeds it, or runs alongside it. Either way, you are integrating, not replacing.
- No attendance device management. Biometrics, shift rosters and overtime are typically a third-party integration or a custom build.
- Learning content authoring is limited. The training module manages course catalogues, enrolment and completion records; it is not a full authoring and video platform, and clients often pair it with SharePoint or a dedicated LMS.
- Recruiting is a module, not an ATS. It covers requisitions, postings, applications and interviews. High-volume campus hiring and sourcing usually needs a separate applicant tracking system.
- Performance is a lightweight framework. Review templates, cycles, goals and ratings. Clients wanting 360-degree feedback, continuous performance or calibrated talent reviews end up building on top.
Say all of this out loud during scoping. The most common cause of a Dynamics 365 HR cost surprise is a client believing the product includes payroll and discovering in month four that it does not. If you are sizing a role rather than a project, our HR salary guide sets out what these implementations are worth.
How It Connects to Dynamics 365 Finance
Many Indian clients who adopt Dynamics 365 Human Resources also run Dynamics 365 Finance, and the pairing is useful: employee cost lands in the cost centre that consumed the effort, and Power BI gives one view of headcount, cost and delivery. But the two applications have separate data models and separate postings, and the “one integrated view” is something you build with Power BI and Power Automate, not something you switch on.
That framing also explains why the Dynamics 365 HR job market is thinner than the Finance one. An HR-only project is usually mid-sized with a mid-sized budget. A combined Finance-plus-HR programme is a larger engagement with a larger team, and it opens a second revenue line for the same consultant. Being comfortable in both is worth a lot of money.
What Actually Happens at Work: The Migration That Failed Twice
A Chennai engineering services firm with 4,200 employees was moving from three separate regional HRMS instances — one bought in 2013, one in 2017, one a spreadsheet-driven workaround for a business unit acquired in 2021 — into Dynamics 365 Human Resources, with a plan to retire all three within nine months.
The first migration attempt failed on data quality and everyone expected that; the surprise was the second attempt, which failed on structure after the data had been cleaned. The cleaned extract keyed employee records on a legacy code that was unique per regional instance — and the three instances had each issued codes in the same numeric range, so “EMP-1042” existed three times for three different people. The load job deduplicated on that code and silently dropped 340 real employees, discovered in a steering meeting three weeks later.
Worse, the org structure had been built on region. Each regional instance had its own department hierarchy with overlapping names, and a single “Accounts Payable” department existed in all three with different cost-centre mappings. Loading them into one Dynamics 365 department tree would have produced three Accounts Payable departments, each partially real, each with a different manager, and a hierarchy no finance system could reconcile.
What they did instead took a month and is the pattern to steal. They rebuilt the mapping from the finance cost-centre master, not from HR, because finance was the system of record for cost. They created a surrogate person key in the migration layer and kept legacy codes as a lookup table, so no legacy identifier was ever used as a join key. Then they ran a parallel month with the legacy systems still authoritative, reconciling headcount, leave balances and position counts weekly until the counts matched.
Cost of the delay: about two months, one extra full-time resource, and a lot of political capital with the finance team. The go-live succeeded, but the project was re-baselined twice, and the internal lesson — HR systems are never the source of truth for structure, and legacy codes are never safe join keys — is now in that firm’s delivery methodology.
Training Resources
Most of the value in a Dynamics 365 Human Resources implementation sits in the Power Platform layer, so build it deliberately with SkilBrill Power Platform Functional Consultant Training — Dataverse modelling, security roles, Power Apps, Power Automate and Power BI, with labs on Dynamics 365 Human Resources objects such as positions, workers, leave requests and employee self-service. The MB-330 certification guide covers the exam that goes with this product.
FAQ
What is Dynamics 365 Human Resources used for?
It is the HR system of record for employees, organisation structure, compensation, benefits, time and absence, recruiting, performance and learning, with an employee self-service app and a Teams-based Employee Hub. It sits in the same Dynamics 365 family as Finance and runs on the Power Platform model.
Does Dynamics 365 Human Resources include payroll?
No. Payroll is not native to Dynamics 365 Human Resources and comes from a partner ISV or a separate payroll product. Indian statutory payroll — PF, ESI, PT, TDS, payslips and filings — stays in the client’s existing payroll system in most projects.
How is the employee record structured in Dynamics 365 HR?
As three separate concepts: a person (the human being), an employment (their relationship with a legal entity, with dates, type and cost centre), and a position (a slot in the org chart carrying the reporting line). Separating them allows multiple employments, rehires and open vacancies.
What is the Employee Hub in Teams?
It is the employee self-service experience published into Microsoft Teams, so staff can request leave, check balances, see who is out and update their details without opening a Dynamics app. The underlying app is model-driven and secured by role and hierarchy access.
Is Dynamics 365 Human Resources hard to learn compared to Workday?
The configuration is easier, and that is part of why the market is smaller and pays less. The data model, security design and Power Platform build are where the difficulty lives, and those skills transfer to every other Dynamics 365 app.
