Quote_v7_FINAL_REAL.xlsx while trying not to wreck the gross margin. Microsoft is trying to pull that messy financial modeling back inside the application with What-if Analysis on estimates for Dynamics 365 Project Operations, tracked on the Microsoft 365 AI at Work Roadmap under ID 576878.Designed for web deployments in Worldwide (Standard Multi-Tenant) cloud instances, the capability gives Sales Managers, Project Managers, and Functional Consultants an isolated simulation workspace directly inside a project quote. Instead of exporting quote line details to Excel or creating throwaway quote revisions just to see how a rate change behaves, teams can tweak quantities and pricing dimensions, compare multiple saved models against their baseline estimates, and apply the winning scenario directly to the draft quote when the numbers make sense.
Rollout Status and Timeline Shifts
If you are tracking deployment schedules for enterprise ERP and CRM environments, the release calendar for Roadmap ID 576878 warrants a closer look. According to the current Microsoft 365 Roadmap entry, the feature entered public preview in March 2026, remains listed as In development, and now projects general availability for April 2027.
That April 2027 target represents a notable shift from earlier scheduling. Microsoft’s archived 2025 Release Wave 2 plan on Microsoft Learn (last updated in August 2026) and early September 2026 administrative tracking notices on M365 Admin and MWPro (referencing message center post MC1465314) previously pointed toward a September 2026 general availability window following the March 31, 2026 preview. As Microsoft’s release plan documentation explicitly notes, delivery timelines are projections that can shift before general release. Meanwhile, Microsoft’s prerelease documentation on Microsoft Learn and an April 2, 2026 Dynamics 365 blog post by Senior Product Manager Pooja Fandan confirm that the feature is currently accessible in Preview for both Project Operations Core (Lite deployment) and Project Operations Integrated with ERP. Because it remains a preview capability, Microsoft recommends evaluating it in a non-production environment first.
Summary: Rollout Snapshot
- Roadmap ID: 576878 (Dynamics 365 Project Operations, Web, Worldwide Standard Multi-Tenant).
- Supported Deployments: Project Operations Core (Lite) and Project Operations Integrated with ERP.
- Current State: Available in Public Preview (since March 2026) when enabled by administrators or makers via an environment feature flag.
- Projected General Availability: Listed as April 2027 on the active Microsoft 365 Roadmap, superseding earlier September 2026 release-plan estimates.
Inside the Simulation Workspace: KPIs and Pricing Dimensions
What makes native scenario modeling useful isn't just being able to change a number; it is seeing what that change breaks—or fixes—across the rest of the deal. When a user opens a scenario in What-if Analysis, Project Operations uses the quote’s current estimates as a baseline and tracks four primary financial key performance indicators (KPIs) in real time, displaying both the new scenario total and the delta against the original quote:
| Financial KPI | What It Measures | Illustrative Delta Example |
|---|---|---|
| Total estimated revenue | The total extended sales amount of the quote under the simulated changes. | Up 5% revenue vs. baseline |
| Total estimated cost | The projected delivery cost required to fulfill the work in the scenario. | Down $12,000 vs. baseline |
| Gross margin (%) | Recalculated profitability percentage based on scenario revenue and cost, compared against baseline and target goals. | Margin increased from 15% to 18% (+3 pts) |
| Budget variance | How the scenario's financials compare against the quote's original budget. | Under budget by 4% |
To drive those calculations, the simulation workspace aggregates quote line details by pricing dimensions—such as Resourcing unit (for example, US, India, or Canada), Role (such as Developer, Architect, or Project Manager), or custom pricing dimensions configured in the environment. Users can group by a single dimension or combine them by dragging an additional dimension to the top bar, such as isolating the billing rate or hours for Consultants specifically within the US resourcing unit.
Within the scenario grid, Project Operations exposes key columns that can be customized or expanded to full screen:
- Group by / Dimension columns: Displays one row per unique value of the selected dimension (such as each organizational unit or resource role).
- Proposed Quantity: The planned work volume (typically measured in a primary time unit like hours) after simulation adjustments.
- Proposed sales price (avg): The billing rate for that row. When grouped by Role, it shows the role's proposed sales price; when grouped by Resourcing unit, it shows the blended average sales rate across all roles in that unit.
- Proposed sales amount & Proposed cost amount: The calculated revenue and delivery cost for each row, which sum up to the scenario's top-level revenue and cost KPIs.
Users can adjust price, quantity, or both at an aggregated level using interactive sliders or manual percentage/value input fields, while hovering over a slider reveals the profitability associated with that dimension value. When broad strokes aren't enough, selecting View line details allows granular, line-by-line edits to specific quote line details.
Summary: Modeling Mechanics
- Four Real-Time KPIs: Tracks Total estimated revenue, Total estimated cost, Gross margin (%), and Budget variance against the baseline quote.
- Dimension Grouping: Aggregates estimates by Resourcing unit, Role, or custom pricing dimensions, with support for multi-dimension filtering.
- Granular or Broad Control: Supports high-level slider adjustments across entire delivery units or line-by-line edits on individual quote line details.
Step-by-Step: Running and Applying a What-If Scenario
According to Microsoft Learn’s preview documentation, setting up and executing a simulation follows a strict lifecycle inside the quoting interface:
- Enable the Preview Feature Flag: An administrator or maker must first turn on the What-if Analysis preview feature flag in the environment so the What-if analysis tab appears on eligible quotes.
- Open an Eligible Draft Quote: Navigate to a quote in Draft status that contains at least one quote line with estimates. Activated or closed quotes are read-only and cannot be used.
- Create a Scenario: Select the What-if analysis tab and click Create scenario. Enter a title and optional description. The current quote is linked automatically, and the Time transaction class is selected by default (meaning adjustments target quote line details using the Time transaction class). Select Save.
- Model Adjustments: Use the Adjust by control in the simulation workspace to modify price, quantity, or both across your chosen pricing dimensions, or open View line details for specific line items.
- Save Variations and Compare: Use Save As to store distinct named strategies (for example, Aggressive Discount, Balanced Tradeoff, or High-Margin). Switch to the comparison view to evaluate multiple scenarios against each other and the baseline quote in a side-by-side KPI table or visual chart.
- Apply to Quote: Once a preferred model is chosen, select it on the What-if analysis tab, click Apply to quote, and confirm the prompt.
Summary: Workflow Lifecycle
- Eligibility: Requires the environment feature flag and a Draft quote containing at least one estimated quote line.
- Default Scope: Defaults to the Time transaction class when creating a new scenario.
- Side-by-Side Evaluation: Multiple named scenarios can be saved via Save As and compared in a table or chart before committing changes.
Critical Operational Quirks Every Admin and PM Should Know
While the pitch for What-if Analysis is straightforward—fewer spreadsheets, faster pricing decisions—Microsoft’s technical documentation highlights several concrete architectural behaviors that project managers and functional consultants need to understand before using it on live proposals:
- No Automatic Rebalancing Across Dimensions: When you adjust quantities using the dimension sliders, each dimension value operates independently. If you reduce hours in the US resourcing unit, the system does not automatically add those hours to India or Canada to keep total effort at 100%. Total allocation across values can rise above or drop below 100% during experimentation, and quantity changes are distributed proportionally across all quote line details tied to that specific dimension value.
- Editing the Base Quote Invalidates Existing Scenarios: Scenarios are tightly bound to the snapshot of the quote from which they were generated. If someone modifies the underlying Draft quote directly, all existing what-if scenarios for that quote become invalid and must be recreated.
- Applying a Scenario Updates the Draft Quote In Place: Traditional quote revisions in Project Operations typically close the original quote and spin up a new quote record. Applying a what-if scenario works differently: it overwrites the same Draft quote in place, updating modified quote line details, automatically generating any necessary price override records for adjusted prices, and locking that scenario as Applied. As long as the quote remains in Draft status, teams can then create fresh scenarios using the newly updated quote as their baseline.
- Unit Conversion Rounding and Refresh Resets: For Time-based work that mixes multiple units across quote line details, Project Operations converts values into the primary unit (such as hours), which Microsoft notes can introduce minor rounding approximations during exploratory analysis. Additionally, while the scenario grid supports undo and redo actions during a session, refreshing the scenario resets unsaved grid changes.
For organizations standardizing on Dynamics 365 Project Operations, keeping margin and staffing simulations inside the quote record removes one of the most error-prone handoffs in professional services sales. By testing rate adjustments and delivery-center mixes directly against live cost and billing structures—while keeping an eye on how in-place updates and manual allocation totals behave—teams can stress-test their proposals long before a client ever sees a final number.