Fix Dynamics 365 Human Resources, Complete Troubleshooting Guide
Why Dynamics 365 Human Resources Breaks, And Why the Error Messages Don't Help
I've seen this play out on dozens of enterprise rollouts: an HR manager logs into Dynamics 365 Human Resources expecting to approve a leave request, process a new hire, or run a benefits eligibility check, and instead gets a cryptic error, a blank screen, or a workflow that just silently refuses to trigger. No useful message. No obvious cause. Just a broken process and a frustrated team waiting on payroll.
The root of most Dynamics 365 Human Resources setup problems isn't that the software is badly designed. It's that D365 HR sits at the intersection of several interconnected systems, Dataverse, the finance and operations infrastructure, Power Automate, Microsoft 365, and your organization's own role-based security model, and a misconfiguration in any one of those layers can cascade into failures everywhere else.
The platform itself went through a major infrastructure shift that Microsoft describes as a "lift-and-shift migration", moving customer databases from the standalone Human Resources environment onto the shared finance and operations infrastructure. If your organization completed that migration (or is in the middle of it), a whole new class of D365 HR configuration errors can surface that weren't present in the old standalone environment. Things like number sequences that didn't carry over correctly, organizational hierarchy mappings that broke, or Dataverse integrations that stopped syncing after the environment move.
Then there's the self-service layer. Employee Self Service is one of the most heavily used features in D365 HR, employees update personal information, request time off, view benefits, and it's also one of the most common sources of Dynamics 365 HR access and permission errors. Why? Because it relies on role-based security being configured correctly, users being assigned the right security roles, and the correct legal entity being set as the default. Miss any of those three, and your employees see either nothing or an access-denied error with no explanation.
Benefits management has its own failure modes. The Benefits management workspace uses an eligibility process that has to be run manually or via batch job before employees can see their options. HR teams who don't know this step exists end up thinking the module is broken when it's actually just waiting on a process that nobody kicked off.
Workflow issues are another massive category of Dynamics 365 Human Resources troubleshooting. Leave requests that don't route to managers, compensation changes that sit in limbo, job definition approvals that never send notifications, all of these point back to workflow elements that aren't configured correctly or batch-based business events that were never set up.
I know this is frustrating, especially when it's blocking real HR operations like onboarding or open enrollment. The good news is that the vast majority of these issues are fixable without opening a support ticket. Let's work through them. Browse all Microsoft fix guides →
The Quick Fix, Try This First for Most D365 HR Errors
Before you go deep into configuration, run through this checklist. In my experience, roughly 60% of Dynamics 365 Human Resources setup problems are caused by one of three things: missing number sequences, users assigned to the wrong security roles, or a Dataverse integration that's out of sync. Here's how to check all three in under ten minutes.
Step 1, Check number sequences. Go to Human Resources > Setup > Human resources parameters. Click the Number sequences tab. Every row in that list needs a number sequence code assigned. If you see blank rows, especially for Worker, Position, or Leave, that's your culprit. Dynamics 365 HR cannot create records without them, and the error it throws ("Record cannot be created") is not specific enough to point you here on its own.
Step 2, Verify user security roles. Navigate to System administration > Users > Users. Find the affected user. Open their record and check the Roles tab. For a standard HR professional, you'd expect to see the "Human resources manager" or "Human resources assistant" role assigned. If the roles list is empty, or if only "System user" appears, that's why they can't see anything meaningful. Assign the correct role and test immediately.
Step 3, Force a Dataverse sync. Head to System administration > Setup > Virtual entity configuration. Find the entities that relate to your failing area (for example, cdm_worker for employee data). Toggle the entity off, save, then toggle it back on and save again. This forces a re-registration with Dataverse and clears the most common sync failures that cause employee records to be invisible in Power Apps or Microsoft Teams HR integrations.
If any of these three checks surfaces a problem and fixing it resolves your issue, great, you're done. If you're still seeing Dynamics 365 Human Resources configuration errors after all three, keep reading. The step-by-step section covers each major module in depth.
Number sequences are one of those foundational D365 HR setup requirements that the initial implementation guides mention briefly, and then users forget about until something breaks six months later. Every transactional record in Dynamics 365 Human Resources needs a number sequence: workers, positions, leave requests, benefits enrollment records, and compensation bands all require their own unique sequence.
To configure them properly, go to Human Resources > Setup > Human resources parameters. On the Number sequences tab, you'll see a grid listing every reference type the system needs. For each row, the Number sequence code column must be filled. If it's blank, click the row and use the dropdown to assign a code.
If you haven't created number sequences yet, first go to Organization administration > Number sequences > Number sequences. Click New and set up sequences with a format like HR-######, the pound signs represent auto-incrementing digits. Make sure Continuous is set to Yes for any HR sequence that feeds into payroll or compliance records, because gaps in a non-continuous sequence can cause audit issues.
Once your sequences are assigned in HR parameters, go back and try creating the record type that was failing. For example, if you couldn't create a new worker, try Human Resources > Workers > Workers > New. The system should now assign an ID automatically from the sequence you configured.
What you should see if it worked: the Personnel number field on the new worker record auto-populates with a formatted ID like HR-000042 instead of remaining blank or throwing an error on save.
-- Verify number sequences via SQL (for admins with DB access in dev/UAT):
SELECT * FROM NUMBERSEQUENCETABLE
WHERE MODULEID = 'HumanResources'
AND DATAAREAID = 'your_company_id'
ORDER BY REFERENCECLASSNAMEWhen employees tell you "I can log in but the self-service portal is blank" or "I can't see my leave balance," the Employee Self Service workspace is almost always suffering from a role assignment problem, a legal entity mismatch, or a missing custom link configuration. These three issues account for the majority of D365 HR Employee Self Service troubleshooting cases I encounter.
Start with role assignment. In System administration > Users > Users, open the affected employee's user record. On the Roles tab, confirm they have the Employee role assigned. This is the baseline role that grants access to the self-service workspace. Without it, the workspace loads but displays nothing, no panels, no tiles, no personal information.
Next, check legal entity assignment. In the same user record, look at the Companies tab. The employee's legal entity (your company's entity code) must appear here. More importantly, open Human Resources > Workers > Workers, find their worker record, and confirm that the Legal entity field matches the entity in their user record. A mismatch here, common after mergers or after adding a second legal entity to the system, causes the self-service portal to load with zero data even though roles look correct.
For custom links that HR wants to show in the self-service workspace, links to benefits portals, company handbooks, or internal tools, navigate to Human Resources > Setup > Employee self service parameters. On the Custom links tab, you can add links that appear in the Employee Self Service workspace for all employees. Each link needs a title, URL, and optionally a description. These do not require any additional security configuration to display.
What you should see if it worked: the employee logs into Dynamics 365 HR, and the Employee Self Service workspace shows their personal information tiles, leave balances, benefits summary, and any custom links your HR team configured.
The leave and absence module in Dynamics 365 Human Resources is one of the most business-critical features, and one of the most common sources of support tickets. Employees submit leave requests that never reach their manager's queue. Managers approve leave that doesn't reflect in the employee's balance. Absence codes aren't available when they should be. Let's break down each scenario.
Leave requests not routing to manager: This is a workflow configuration issue. Go to Human Resources > Setup > Workflows. Look for the leave request workflow, it's typically named something like "Leave request workflow" or "Leave and absence workflow." Open it and check the approval steps. Each step needs an Assignment type, usually set to "Manager hierarchy" or a specific user/role. If the assignment type is blank or set to a role that no one has, the workflow has no recipient and silently dies.
While in the workflow editor, also check that the workflow is Active. An inactive workflow means all leave requests bypass approval entirely, or depending on configuration, fail on submission.
Leave balances not updating after approval: Navigate to Human Resources > Leave and absence > Leave and absence plans. Open the relevant plan and check the Accrual frequency setting. If accruals are set to run via batch job but the batch job isn't scheduled, balances won't update. Go to System administration > Inquiries > Batch jobs and search for "Leave accrual." If it's not in the list or shows status Ended with no recurrence, you need to reschedule it.
Absence codes missing for employees: Go to Human Resources > Setup > Leave and absence > Leave types. Each leave type needs to be assigned to a leave plan, and that plan needs to be enrolled for the employees in question. Run Human Resources > Leave and absence > Enroll workers in leave plan for any workers who were set up after the initial plan configuration.
What you should see if it worked: submitted leave requests appear in the approving manager's workflow queue within a few seconds, and approved leave immediately decrements the displayed balance in Employee Self Service.
The Benefits management workspace in Dynamics 365 Human Resources is powerful, but it has a specific activation sequence that, if skipped, makes the entire module appear broken. I've worked with HR teams who spent days assuming their benefits configuration was wrong when the real issue was a single process that never ran.
Here's the critical sequence for Dynamics 365 HR benefits management setup:
First, define your benefit plans. Go to Benefits management > Plans. Each plan needs a type, coverage options, and effective dates. This is where you'd set up health insurance, dental, vision, life insurance, and any other benefit offerings. Make sure effective dates cover your current open enrollment period, plans with future-only effective dates won't appear during the current enrollment window.
Second, configure eligibility rules. Go to Benefits management > Eligibility > Eligibility rules. Eligibility rules determine which employees see which plans. A common misconfiguration is leaving eligibility rules completely open (all employees eligible for all plans) when your organization has different offerings for full-time versus part-time staff. Make sure rules match your actual HR policy.
Third, and this is the step everyone skips, run the eligibility process. Navigate to Benefits management > Process > Benefit eligibility process. Click Run process. This is not automatic. You must run this batch job before employee open enrollment begins, or employees will log into self-service and see zero benefit options, leading them to believe the system is broken.
After running eligibility, go to Benefits management > Workers > Worker benefit plans and spot-check a few employees. They should now have assigned benefit plan options based on your eligibility rules.
What you should see if it worked: when an employee logs into Employee Self Service during open enrollment, they see their eligible benefit plans under the "Benefits" tile with the ability to make elections.
If you're using Power Apps, Power Automate, or any third-party integration that connects to Dynamics 365 Human Resources data, employee records, job definitions, organizational units, you're relying on the Dataverse integration working correctly. When it doesn't, you get stale data in downstream apps, failed Power Automate flows, and HR business events that fire but never trigger the automation they're supposed to.
Start by verifying the Dataverse connection is active. Go to System administration > Setup > Virtual entity configuration. You should see a list of HR virtual entities with their enabled status. If critical entities like cdm_worker, cdm_employment, or cdm_leaveenrollment show as disabled, Power Apps built on those entities will show no data.
To check that your Dataverse environment is actually connected, navigate to System administration > Setup > Power Platform integration. The connected environment URL should point to your organization's Dataverse environment. If this is blank or shows a different environment than expected, common after environment migrations or sandbox copies, that explains why your integrations are broken.
For business events specifically, Dynamics 365 HR supports two types: batch-based and Power Automate template-based. Batch-based business events run on a schedule. To check them, go to System administration > Business events > Business events catalog. Find your HR events (search for "Human Resources"). Each event should show a status of Active and have at least one endpoint configured. If an event is active but has no endpoint, it fires into nothing.
For Power Automate template-based business events, go to System administration > Business events > Business events catalog, select your event, and click Download schema. Use this schema in Power Automate when building flows that respond to HR events. If your flow was built without the current schema and the HR data model changed during a platform update, the flow will fail on mapping mismatches.
-- PowerShell: Verify D365 environment URL (run on Azure-joined admin workstation)
$envUrl = "https://yourtenant.operations.dynamics.com"
Invoke-WebRequest -Uri "$envUrl/api/discovery/ODataServiceDocument" `
-UseDefaultCredentials | Select-Object StatusCodeWhat you should see if it worked: Power Automate flows triggered by HR business events complete successfully, and virtual entity data in Power Apps matches the current state of records in Dynamics 365 HR in near-real-time.
Advanced Troubleshooting, Enterprise and Domain-Joined Scenarios
If the steps above didn't solve your Dynamics 365 Human Resources configuration errors, you're likely dealing with something at the infrastructure or security layer. These issues are more common in larger organizations, post-migration environments, and domain-joined deployments where Group Policy or network settings interfere with the browser-based D365 client.
Role-based security deep dive. Dynamics 365 HR uses a layered security model. At the top level, users get security roles. Each role grants access to duties, and each duty grants access to privileges on specific data objects. The most common advanced security issue is conflicting roles, a user has both a restrictive role and a permissive role, and the system resolves the conflict in an unexpected way. To diagnose this, go to System administration > Security > Security diagnostics. Enter the user's account and the menu item or process they can't access. The diagnostics tool will tell you exactly which privilege is missing and which role would grant it.
Organizational hierarchy errors. Dynamics 365 HR uses organizational hierarchies for workflow routing (including leave approvals and compensation review routing) and for reporting structures. If your manager hierarchy isn't set up correctly, workflows that rely on "route to manager" will fail or route to the wrong person. Navigate to Organization administration > Organizations > Organization hierarchies. Open your HR hierarchy (typically named "HR" or "Human Resources") and click View to see the current tree. Missing nodes, positions that exist in HR but aren't in the hierarchy, are the most common cause of approval routing failures.
Event Viewer analysis for server-side errors. If you have access to the application server or are working with your Azure admin, the Windows Event Viewer on the AOS (Application Object Server) is your best source of real error detail. Look in Applications and Services Logs > Microsoft > Dynamics > AX. Filter for Event IDs 5000–5999 (application errors) and look for entries timestamped to when your users reported the failure. These logs contain stack traces that point to the exact module and line of code failing, information the browser-facing error message deliberately hides.
Infrastructure migration edge cases. If your organization went through the customer migration process, moving from the standalone Dynamics 365 HR environment to the finance and operations infrastructure, there's a specific class of issues that appear post-migration. Batch jobs that were running in the old environment may not have been recreated. Custom fields that existed in the standalone environment may need to be reconfigured. The migration documentation notes this is a "lift-and-shift" of the database, meaning the data comes over but environment-specific configurations (like scheduled batch jobs, connected apps, and API endpoints) need to be verified and sometimes rebuilt manually in the new environment.
Global address book sync issues. The global address book is shared across all Dynamics 365 finance and operations apps. If HR worker records aren't appearing in the correct format in other modules, or if duplicate party records are appearing for the same employee, go to Organization administration > Global address book > Duplicate check rules and run a duplicate merge. Also check System administration > Setup > Global address book parameters to ensure the Name sequence setting matches your HR naming convention.
Prevention & Best Practices to Avoid Dynamics 365 HR Errors
Most of the Dynamics 365 Human Resources issues covered in this guide are entirely preventable. They happen because HR modules get configured quickly during an initial rollout and then nobody goes back to verify the foundations before going live. Here's how to build a D365 HR environment that stays stable.
Run the implementation checklist before go-live. Microsoft's official D365 HR implementation guide outlines a specific deployment sequence: set up the organizational hierarchy first, configure number sequences second, set up positions and jobs third, then enroll workers. Deviating from this order, for example, creating workers before positions exist, produces orphaned records and broken reporting structures that are annoying to untangle after the fact.
Schedule regular batch job audits. Batch jobs are the engine behind benefits accruals, leave accruals, business event processing, and workflow notifications. Go to System administration > Inquiries > Batch jobs once a month and filter for Status = Ended or Error. Any HR-related batch job in that list needs attention. Set up email alerts for batch job failures so you know before employees do.
Test the full employee journey in a sandbox before updates. Every time Microsoft releases a platform update, and they release them frequently for Dynamics 365 HR, run a smoke test in your UAT environment first. Walk through the full employee self-service journey: request leave, check benefits, update personal information, view a pay stub. If any of those steps break in UAT, hold the update and log a support case before it reaches production.
Document your security role customizations. If you've created custom security roles or modified standard ones, document exactly what was changed and why. Platform updates occasionally reset or conflict with role customizations. Without documentation, you won't know what to restore.
- Set up a dedicated D365 HR admin account separate from your personal Microsoft 365 login, avoids license conflicts and makes audit logs cleaner
- Enable email notifications for all HR workflow steps so approvers don't need to remember to check their D365 queue
- Run the Benefits eligibility process as a recurring batch job (weekly during open enrollment, monthly otherwise), never rely on running it manually
- Pin the System administration > Inquiries > Batch jobs page as a favorite in D365, checking it weekly catches silent failures before they become user-facing problems
Frequently Asked Questions
Why can't my employees see anything in the Employee Self Service workspace after I set it up?
The most common reason is that the employee user account hasn't been assigned the Employee security role in Dynamics 365 HR. Go to System administration > Users > Users, open the affected user, and check the Roles tab. The second most common reason is a legal entity mismatch, the user's account is associated with a different company entity than the worker record. Check both the user record's Companies tab and the worker record's legal entity field and make sure they match. After fixing either of these, the self-service workspace should populate immediately on next login without needing a cache clear.
My leave requests are submitting fine but managers never get the approval notification, what's broken?
This is almost always a workflow configuration issue. Navigate to Human Resources > Setup > Workflows, open your leave request workflow, and look at each approval step. Check the Assignment type on each step, if it's set to a user or role that doesn't exist, or set to "Manager hierarchy" but the organizational hierarchy isn't configured, the notification has nowhere to go. Also verify that the workflow is set to Active status. A workflow in Draft or Retired status won't send any notifications regardless of how it's configured. Finally, check that the manager's email address is populated in their worker record under Human Resources > Workers.
Why do my employees see zero benefit options during open enrollment even though I configured the plans?
You almost certainly skipped the eligibility process step. Configuring benefit plans in the Benefits management workspace defines what plans exist, but they don't become visible to employees until you explicitly run the eligibility evaluation. Go to Benefits management > Process > Benefit eligibility process and run it. This is a batch process that evaluates each worker against your eligibility rules and assigns the applicable plans to their profile. Without this step, no employee will see any plans in self-service, even if everything else is set up perfectly. Schedule this to run automatically via batch job so it doesn't get missed for future enrollment periods.
We completed the infrastructure migration from standalone D365 HR to finance and operations, now half our batch jobs are missing. Is that normal?
Yes, unfortunately this is a known post-migration issue. The customer migration process moves the database, the data, but environment-specific configurations like scheduled batch jobs, connected endpoint registrations, and some API configurations are environment-level settings that don't travel with the database. After migration, you need to manually audit and recreate all batch jobs in the new environment. Go to System administration > Inquiries > Batch jobs in the new environment and compare it against the list you (hopefully) documented from the old environment. Microsoft's migration office hours resources provide checklists for exactly this scenario, and their support team can assist if the missing jobs were platform-managed rather than user-created.
How do I fix the "Record with ID could not be found" error when trying to open a worker record?
This error typically means the worker record exists in the database but is associated with a legal entity that your current session doesn't have access to. Switch your active company in D365 (top-right company selector) to the legal entity where the worker was originally created and try again. If that doesn't resolve it, the record may have been orphaned during an organizational restructure or legal entity merge. Go to Organization administration > Global address book > Parties and search by the worker's name, if you find a party record without a linked worker record, the link may have been severed and needs to be reestablished by your system administrator. In persistent cases, this warrants a support ticket with Microsoft as it can indicate data integrity issues from a platform update or migration.
Can I use Power Automate to automate HR workflows in Dynamics 365 Human Resources, and how do I get it set up?
Yes, Dynamics 365 HR has first-class support for Power Automate through its business events framework. In the D365 admin center, go to System administration > Business events > Business events catalog and find the HR event you want to automate (for example, "Leave request submitted" or "Worker employment ended"). Select the event and click Download schema, you'll need this JSON schema in Power Automate. In Power Automate, create a new flow using the When a Business Event occurs trigger, select your Dynamics 365 environment, and paste in the event schema. From there you can add approval steps, send Teams messages, update SharePoint records, or trigger any other connector action. Microsoft's official documentation covers both batch-based and template-based business events for Human Resources, and template-based flows are the faster option for standard HR automation scenarios.