Applies To: Human Resources on the stand-alone infrastructure
Starting July 2022, new Human Resources environments can't be provisioned on the stand-alone Human Resources infrastructure, and new Microsoft Dynamics Lifecycle Services (LCS) projects can't be created on it. Customers can deploy Human Resources environments on the finance and operations infrastructure. For more information, see Provision Human Resources in the finance and operations infrastructure.
The update and hotfix process on the finance and operations app infrastructure differs from the Human Resources stand-alone update and hotfix process. For more information about the update process, see Process for moving to the latest update of finance and operations. For more information about hotfixes, see Download updates from Lifecycle Services (LCS).
Microsoft Dynamics 365 Human Resources is a true software as a service (SaaS) that provides continuous, touchless service updates. These updates contain both application and platform changes that often provide critical improvements to the service, including regulatory updates.
Updates are released on a regular cadence to all environments. Human Resources is supported according to the Microsoft Lifecycle policy, which provides consistent and predictable guidelines for the availability of support.
Human Resources updates are applied to all environments automatically. Human Resources provides two types of releases:
Service updates: Service updates include applicable platform updates when they are released. In addition to exception-based updates, regular service updates occur following the General Availability (GA) of Dynamics 365 Finance platform updates. For more information about platform releases, see What's new or changed in Platform updates. Updates have a staged global rollout across regions. For more information about updates, see What's new or changed in Dynamics 365 Human Resources.
Dataverse solution updates: These updates occur approximately every six weeks, as needed. They include new entities and changes to existing entities in Dataverse. These updates are released to the same regions as the biweekly updates, and they take about six weeks to replicate through all data centers. Solution updates may or may not align with biweekly service updates.
Solution updates are available on all data centers once they're released. If you don't want to wait for the updates to replicate automatically, you can manually apply these updates on any environment in any data center.
When needed, Human Resources provides the following types of fixes:
Revision (hotfix): Bug fixes that can occur either with or apart from a biweekly service update release
Emergency fix: Proactive and reactive hotfixes that are standalone in nature, can include configuration-only or code changes to resolve live site issues, and can occur apart from a biweekly service update release
Releases are reviewed, tested, and validated on an internal environment. After builds are signed off, they're then deployed to production.
You can find out what's in the works for Human Resources and what we've released in the following locations:
Issue search in Lifecycle Services (LCS) (for Platform-related bugs only)
Preview features in a sandbox environment
You can validate preview features in a sandbox environment before enabling them in your production environment. For more information about enabling features, see Feature management overview.
All new features remain in preview for at least 30 days, and typically 30-60 days. Major features are generally available in October and April of each year following the preview period. As soon as you see new capabilities in the Feature management workspace, you can turn them on. Some features may be on by default.
At times, an integral feature will be on by default and can't be turned off (for example, the Feature management workspace).
Once a feature is generally available, it may be turned on or off in production environments. The Feature management workspace indicates when a preview feature will become mandatory. This date is usually on October 1 or April 1 to align with the semiannual release plans. You can't turn off mandatory features. Until it becomes mandatory, you can turn a feature on and off in all environments.
We highly recommend previewing features in a sandbox or trial environment. It's best to create a copy of your current production environment or database into a sandbox environment so you can get the complete experience of the new features with your data.
While testing preview features or trying new capabilities, you might find items that don't work as expected. Please report any bugs through Microsoft Dynamics 365 support.
Submit and view feedback for