You finish a quarterly upgrade review and a stakeholder asks which release wave features actually need work this cycle versus which are marketing slides. The honest answer requires reading the wave notes against your environment, not from a vendor blog. The 2026 waves are dense with Copilot wiring and quiet Dataverse plumbing; both matter, but for different teams.
Copilot Everywhere
More Copilot surfaces per module: Sales deal acceleration, Service case analyzer, Field Service work-order assistant. Enablement is still per-module and per-license tier, which means a single tenant can have Copilot lit up in Sales and dark in Service, and users will not understand why their colleague has the button.
Audit your license SKUs against the wave note feature table before promising a date. The Sales Premium SKU unlocks deal acceleration; the base Sales SKU does not. Build a Power BI page that joins user license assignments to feature availability so the support team can answer the question without escalating.
Dataverse
Performance improvements, increased file column sizes, faster dual-write with F&O. Behind-the-scenes work that accumulates. The file column lift to 128MB unlocks attaching scanned contracts directly to records instead of routing through SharePoint, but it also raises storage cost. Model the storage delta before flipping the column maximum.
Dual-write latency between Dataverse and Finance and Operations drops in this wave, which matters for inventory-aware quoting and credit checks at quote time. If your sales-to-finance round trip was budgeted at 8 seconds, retest after the wave hits your region.
Customer Insights
Cross-product segment sharing between Journeys and Data matures. Real-time journey triggers from behavioral events expand. The new event grid integration lets a Customer Insights segment fire on a clickstream event from your website within seconds, which finally makes the cart-abandonment journey live up to the demo. Set up the event grid topic before the wave hits, otherwise the journey designer will show triggers your environment cannot fulfill.
Power Platform Alignment
D365 and Power Platform development models continue to converge. Fewer D365-specific customization patterns; more build-on-Power-Platform patterns. The practical effect is that new makers should learn Power Apps before they learn the model-driven app classic patterns, because the tooling investment is going one direction. Update your maker onboarding to lead with Power Fx and modern designer skills.
Old onboarding: classic form designer, JavaScript web resources, classic workflows
New onboarding: modern designer, Power Fx, Power Automate flowsDeprecations
Legacy web UI retires further. Classic workflows slowly retire. Plan migration off deprecated features before forced retirement. Microsoft is publishing 12-month deprecation notices in the wave docs; bookmark the deprecation page and assign one admin to read it monthly. Surprises here are expensive.
Deprecated this wave:
- Classic workflow designer (read-only on creation)
- Legacy mobile client offline mode
- Two older form rendering pathsReading the Wave Notes Effectively
The wave notes are 800 pages. Nobody reads them cover to cover. The working method is to filter to your modules, sort by GA date in your region, and triage features into Need Now, Watch, and Skip. Need Now goes on your sprint board. Watch goes on the quarterly review. Skip gets archived.
What to do this week
Pull the wave notes for the modules you own, build the three-bucket triage, and book a two-hour review with your business owners to confirm the Need Now list. Update the license-to-feature Power BI page so support can answer the inevitable Copilot questions without you.
