Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | 
Jun 6, 2025 |
Oct 3, 2025 |
Business value
With this feature, you can use the modern architecture for resource and nonstocked scenarios on the Dataverse platform. You get great user experiences and deep functionality in project planning with Microsoft Project for the Web and resource management with Unified Resource Management.
Feature details
The enhancements in this feature enable parallel use of projects from both deployment types. With this change, you can enter transactions and create invoices for long-running projects. These enhancements support the transition to the modern architecture. This change is part of a larger effort. You won't see all the functionality delivered at once. With these enhancements, you can try the modern architecture in a test environment. If you want, you can move from the stocked deployment type to the resource and nonstocked deployment type.
Use this feature if you're using the stocked deployment type and don't need production orders or manufacturing. With this feature, you can enable the resource and nonstocked deployment type for customers who previously used the Project Management and Accounting module without reimplementing your existing legal entity. If you want to continue using the capabilities in the stocked deployment type, you aren't impacted by this feature.
Changes include:
The existing validation in the Global project management and accounting parameters form is relaxed to allow legal entities with existing project data to enable resource and nonstock deployment types.
The Global project management and accounting parameters validation checks that all projects are closed. Initially, you can close all existing projects and create new projects in Dataverse.
You evaluate business processes to make sure they restrict the appropriate deployment types. For example, you can create invoices for Dataverse-based projects only from Dataverse.
We remove access or make read-only the legacy functions that exist in both deployment types. For example, when you enable this feature, you can't edit resource management and project work breakdown structures in the finance and operations user interface for the resource/non-stocked deployment mode. For projects you create in resource/non-stocked deployment mode, use Unified Resource Scheduling experiences for resource scheduling, and Project for the Web experiences for project planning.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.
Related Content
Configure Project Operations integration per legal entity (docs)