There is an important availability distinction, however. Microsoft Learn lists Preboarding (preview) in Human Resources version 10.0.50. That release is scheduled for December 2026 self-update availability and January 2027 automatic updates—not a simultaneous production rollout to every customer.
What the planned workflow covers
Microsoft’s roadmap entry 578897, titled “Dynamics 365 Human Resources: Streamline the preboarding experience,” describes a configurable candidate journey rather than a fixed checklist.
The planned scope includes:
- Guided steps for personal information, document uploads, right-to-work verification, tax and banking details, background verification, and first-day preparation.
- Progress tracking with consistent navigation and task states.
- Conditional requirements based on country, role, or worker type.
- Administrator controls for templates, validation rules, required documents, dependencies, and conditions that must be met before proceeding.
- Worker-record mapping to carry collected information into worker records.
- Program-based assignment, with administrators deciding which steps are active for candidates assigned to a program.
These are intended capabilities, not a guarantee that every element is already usable in the preview. Microsoft explicitly describes roadmap dates and functionality as estimates subject to change.
Microsoft Learn independently confirms the candidate-facing model: HR sends an invitation from Dynamics 365 Human Resources, and the candidate signs in to the careers site to complete a guided form. Its documented categories include contact and identification information, education, experience, skills, screenings, and documents.
The practical attraction is consistency. Instead of leaving candidates to work out which attachment or information request comes next, the proposed workflow would make the sequence explicit. Whether that reduces delays will depend on configuration and adoption; Microsoft has not supplied measured results in the reviewed material.
December is a target, not an all-clear
The roadmap identifies the capability as In development, with an October 2026 preview target and December 2026 general availability target. October has passed, but a roadmap month alone does not establish availability in a particular customer environment.
The supporting release documentation provides a more useful planning distinction:
| Human Resources 10.0.50 milestone | Microsoft’s schedule |
|---|---|
| Release preview | October 2026 |
| General availability through self-update | December 2026 |
| General availability through automatic updates | January 2027 |
Microsoft still labels Preboarding as a preview feature in that release’s documentation. Administrators should therefore distinguish the application update schedule from the feature’s production-readiness status.
The preview warning matters here
Preboarding is an especially sensitive place to confuse “available to test” with “ready for real candidates.”
Microsoft’s general Human Resources feature-management guidance says preview features are available only in sandbox environments, have limited support, and fall outside the Human Resources service-level agreement. It also warns that previews may have fewer privacy and security measures and should not process personal data or information subject to legal or regulatory requirements.
For evaluation, the sensible approach is synthetic candidate information—not real identification documents or banking details. That recommendation follows directly from Microsoft’s preview restrictions, rather than implying a newly discovered vulnerability.
What administrators can prepare now
The roadmap describes enablement through Feature management and Human resources parameters. Microsoft Learn corroborates Feature management as the enabling mechanism, but the reviewed release note is not a complete preboarding configuration guide. Exact fields and setup sequences should not be guessed.
A useful preparation exercise is to define acceptance tests before configuring the workflow:
- Separate requirements by candidate group. Decide which information is necessary for each country, role, or worker type.
- Identify dependencies. Establish which incomplete items should prevent progression and which can wait.
- Test the candidate journey. Using synthetic records, assess whether required actions and completion states are understandable.
- Validate the handoff. Check collected information against the intended worker-record destinations before approving production use.
- Review data handling. Establish who should access candidate information and what organizational retention requirements apply.
These are implementation recommendations, not documented product menu steps.
The opportunity is a clearer bridge between a hiring decision and day-one readiness. The corresponding responsibility is careful configuration: a guided process can organize requirements, but a tidy progress indicator is not, by itself, proof that every requirement has been correctly verified.