Enable multiple deployment types in a single legal entity
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | Mar 2025 | Jun 2025 |
Business value
This feature enables users to take advantage of our modern architecture with our resource/non-stocked scenarios using the Dataverse platform. Users benefit from the great user experiences, the deep functionality in project planning using Microsoft Project for the Web, and resource management using Unified Resource Management.
Feature details
The enhancements introduced with this feature will work toward parallel use of projects from both deployment types. This is a large effort that won't have all functionality delivered at once.
This feature is for customers who are using our stocked/production order deployment type, but using scenarios that don't involve inventory. The changes made allow customers who have used Microsoft Project in the past to enable the resource/non-stocked deployment type without having to reimplement their existing legal entity.
Changes include:
The existing validation in the Global project management and accounting parameters form will be relaxed to allow legal entities with existing project data to be enabled for resource/non-stock deployment types.
Business processes will be evaluated to ensure proper restrictions are in place for the appropriate deployment types. For example, invoices for Dataverse-based projects can only be created from Dataverse.
We will remove access or make read-only the legacy functions that exist in both deployment types. For example, resource management and project work breakdown structures will no longer be editable in the finance and operations user interface for both stocked and resource/non-stocked deployment mode with this feature enabled. For projects created in resource/non-stocked deployment mode, users are able to use Unified Resource Scheduling experiences for resource scheduling, and Project for the Web experiences for project planning.
Some experiences may change. For example, we may introduce independent forms to manage projects for each deployment type or show both types of projects in the same list page.
Example experience: Managing existing stocked projects along with non-stocked projects in the same form.
