A platform owner reads the Wave 1 announcement, screenshots three slides, and forwards them to the team with the subject “what does this actually mean for us”. The answer is module-specific, region-specific, and license-specific, and the slides do not say so. Here is the operator’s read on what to actually plan for.
Timing
Release Wave 1 announced March 18, 2026. Rollout April through September 2026. Features deploy in stages; consult each feature’s target date. Not all land simultaneously. Microsoft publishes a per-feature target date in the release planner; treat that as the planning anchor, not the wave keynote.
Apr 2026: General availability for early-deploy features
Jun 2026: Mid-wave wave of releases
Sep 2026: End of wave; remaining features go GASubscribe to the message center filter for D365 in M365 admin so the dates land in your inbox automatically. Do not rely on internal communication to surface them.
Sales Agent Expansion
Command-center positioning — daily primary interface for sellers. Conversational data access via Copilot. Mobile and in-context experiences. Deeper config and governance at scale. The sales agent now has a structured handoff pattern from Copilot to the underlying Sales hub form, which means the rep can ask a question, see the answer, and be one click from editing the source record.
The governance change matters. Admins can now scope which entities the sales agent can read at the role level, which closes a long-standing concern about agents leaking data across territories. Map your existing security roles to the new agent scopes before enabling.
Service Agent Maturity
Agentic capabilities in case management, email, customer intent, quality, knowledge. AI-infused admin and supervisor help. End-to-end orchestration strengthens. The big shift is that the service agent can now close low-complexity cases without human review when configured to do so, with a confidence threshold the admin sets.
agent_autoclose:
enabled: true
threshold: 0.92
intents: [password_reset, order_status, account_lookup]
fallback: escalate_to_tier_oneStart the threshold conservative, measure misroutes for two weeks, then loosen. Going aggressive on day one creates a class of customer complaints that is hard to recover from.
Contact Center and BC
Contact Center advances agentic operations — self-service, assisted service, operational intelligence. Business Central accelerates toward agentic ERP in sales and purchase scenarios. The Contact Center self-service deflection metric finally has a measurable definition that excludes abandoned calls, which means quarter-over-quarter comparisons stop lying.
Business Central agents handle purchase order creation from supplier emails, with the standard checks for budget, vendor approval, and SKU validity. The integration with Dataverse means a sales quote on the D365 Sales side can pull live inventory from BC without a custom dual-write configuration.
What to Pilot vs Defer
Not every feature deserves a pilot. Use a simple two-by-two: business value high or low, deployment risk high or low. High value low risk goes to pilot in May. High value high risk waits for the mid-wave bugfix pass in July. Low value features are a Watch List entry and nothing more.
Cross-Tenant Coordination
If you operate multiple tenants for different business units, the wave hits each one on its own schedule based on region. Coordinate the pilot tenant ahead of production by 30 days so any breaking change is visible before it lands in the revenue-bearing environment.
What to do this week
Pull the per-feature target dates for your region, build the two-by-two, and book the pilot environment for the May features. Subscribe to the message center filter and assign one admin to triage the inbox. The waves do not slow down for unprepared teams.
