The problem Microsoft is trying to fix
Microsoft names three routine jobs that project managers do during subcontract management:
- Modifying subcontract lines.
- Tracking subcontract usage.
- Monitoring billing progress on subcontracts.
Today these tasks sit behind multiple forms and interfaces. The roadmap says the complexity grows when one manager handles vendors and subcontracts across several projects. This is a usability fix. It is not a new accounting engine.
What is already documented and shippable
Microsoft Learn already documents an opt-in experience. It applies to Project Operations Integrated with ERP and to Project Operations Core. The improved experience sits behind a feature flag called "Enable Subcontracting UX enhancements for smoother navigation and insights".
According to Microsoft Learn, the redesigned subcontract main form changes three things:
- General tab: fields are organized into sections for subcontract details, vendor information and contracting unit details.
- Subcontract Price Lists tab: a new tab for handling and managing price lists.
- Insights tab: a new tab showing actuals logged against the subcontract, subcontract line consumption, and vendor invoice details related to the subcontract.
The Insights tab maps most directly to the roadmap's complaint about tracking usage and billing progress. The documentation does not claim that every task now fits on a single screen. It also gives no figures for time saved, so treat any efficiency claims as unproven.
How to turn it on
The Learn procedure follows these steps:
- Sign in to Project Operations.
- In the left navigation, switch the area to Settings.
- In the General section, select Parameters.
- Double-tap or double-click the Organization Units row, on the columns that aren't links.
- On the Project Parameters page, select Feature Control in the top ribbon.
- Select the enable option for the subcontracting UX enhancements.
- Select Enable in the confirmation dialog.
You can undo it. To revert to the previous experience, choose the matching Disable option under Feature Control. Because the change is reversible, an admin can pilot it with project managers before committing.
One caveat from Microsoft's September 2025 Project Operations Core release notes concerns preproduction. Enabling a different preview feature there required a support ticket. That note should not be read as a general requirement for the subcontracting flag. Check your own environment before assuming either way.
A later addition: the Hierarchy view
Microsoft's March 2026 release notes add a Hierarchy view on the Subcontracts list page. It lays out subcontracts, their lines and the linked project in a hierarchical structure. This makes relationships easier to follow and navigation between related records easier. It sits behind the same feature flag. That is evidence the redesign is still being extended, not proof the roadmap item is complete. The March 2026 notes also list a subcontracting quality fix, for a vendor invoice field not defaulting from the subcontract line. The relevant item appears to be 6000962 in the Integrated with ERP notes.
What does not change
Microsoft's subcontract management overview shows why the interface matters, and where its limits are:
- Project managers create subcontracts with vendors, and lines can be for time, expenses or products.
- Pricing is adjusted through purchase price lists attached to the subcontract.
- Vendor invoice lines can optionally reference a subcontract line. The system then associates matching cost actuals to support a three-way match.
- The improvements concern the user experience and visibility, not the purchasing rules.
Existing constraints also stay in place:
- Fixed-price subcontracts are not supported for resource/non-stocked scenarios.
- Work-based subcontract lines, which map to a body of work on a single project, are not currently supported.
- When a team member is linked to a subcontract line, the system re-costs their task assignments using the subcontract's purchase price list. For named contract workers, the worker's vendor must match the subcontract's vendor, and the role must match the time line.
Practical advice for admins
- Check the flag, don't assume. The documentation describes an explicit enablement step. It does not say the feature is on by default.
- Pilot before rollout. Let a few project managers try the Insights and Price Lists tabs on real subcontracts. Then confirm the reorganized form matches your process, and train users on the new layout.
- Keep expectations realistic. The sources give no minimum build number and no licensing change. They also do not confirm that general availability has happened. Verify against your tenant and release plan.
- Watch the roadmap. The August 2027 GA estimate could move. If your team depends on this, track the roadmap entry and the monthly "What's new" notes.
Bottom line
This is a modest but useful change for project-based services firms. It does not change how subcontracts are costed or billed. It consolidates where managers see price lists, consumption, actuals and vendor invoices. Finance teams will probably care less about the new layout than about the visibility into invoice and actuals data. For now, the safest course is to enable it in a test environment, check it against your subcontract scenarios, and plan around the roadmap's stated, non-guaranteed timing.