It is the first week of October 2026, and the Power Platform release wave calendar says this is when Wave 2 lands. Except it didn't. On August 25, 2026, Microsoft announced there will be no September 2026 Release Wave 2 announcement. The twice-yearly wave model that governance teams have anchored their planning on since 2016 is being retired in favor of continuous disclosure through the AI at Work roadmap. The twist for Center of Excellence (CoE) leads: features are still arriving in your tenant this week. They just arrived without an announcement. That is the Power Platform 2026 Release Wave 2 tenant rollout verification problem in its sharpest form yet.

What Actually Changed on August 25, and What Didn't

Microsoft was explicit that this is a communications change, not a product change. Release Plans on Microsoft Learn stop publishing in September 2026 and remain archived for historical reference. The Release Planner app retires by November 15, 2026. Dynamics 365, Power Platform, and Dataverse roadmap content now flows through the renamed AI at Work roadmap as always-on disclosure.

Nothing else moved. Product release schedules, deployment processes, Microsoft 365 Message Center notifications, and Microsoft Learn product documentation are unchanged. Semi-annual channel environments still receive their October build. Monthly channel environments still receive weekly builds. Advanced Connector Policies (ACP), which went generally available on June 4, 2026, still enforces default-deny the moment a new connector appears in your catalog.

The forcing function is gone. The deployments are not.

Why the First-Week Verification Problem Survives the End of Waves

Microsoft documents the release channel mechanics clearly. The semi-annual channel turns on GA-ready features twice a year, in April and October, using build names in the YY09.3 format (2609.3 for this October). The monthly channel delivers GA-ready features each month in YYMM.W builds. Each build is then gradually rolled out to regions over roughly five weeks, starting with the first release region and reaching production regions in groups on successive weekends.

Translated for a multi-region tenant: your environments do not light up at the same time, your channels do not light up at the same time, and now no announcement tells your stakeholders when any of it should have landed. Makers still ask "is it live yet?" They just no longer have a Microsoft calendar date to point at. The CoE has to answer with evidence from the tenant itself.

The BabyBots Tenant Verification Pyramid

Across the Power Platform governance work we see at BabyBots, the organizations that handle release weekends well treat verification as a hierarchy of signal authority, not a scan of blog posts. We codify this as the Tenant Verification Pyramid. Governance decisions must be sourced from the top two tiers. The bottom two are context, not evidence.

Tier 1: Ground Truth (environment-level)

The Settings > About dialog in a model-driven app shows the current release channel and build number for that environment. This is what your users are actually running. It is the only tier that answers the question "what code is live for us right now." Appending &channelrelease=next to the URL previews the next channel's behavior for validation.

Tier 2: Tenant-Authoritative (notification-level)

Microsoft 365 Message Center is the authoritative source for planned, tenant-specific changes. The Status for your org field tracks each item as Scheduled, Rolling out, or Launched. Power Platform admin center Notifications (preview) complement this with tenant-specific operational alerts.

Tier 3: Portfolio-Directional (roadmap-level)

The AI at Work roadmap, filtered views, and RSS feeds tell you what is coming across the portfolio. They do not tell you what has arrived in your tenant. Useful for planning, insufficient for governance decisions.

Tier 4: Narrative-Contextual (blog-level)

The Power Platform Blog, MVP posts, and community recaps explain intent, design rationale, and best practice. They prove nothing about your tenant. Treat them as reading, not as evidence.

Govern the tenant you have, not the roadmap you read.

A Monthly Cadence That Replaces the Retired Twice-Yearly Review

Microsoft itself now recommends monthly or quarterly roadmap reviews built on saved AI at Work filters and RSS. For most CoEs, monthly is the right floor. The twice-yearly wave review was never really twice-yearly work; it was the week of concentrated attention that produced the governance artifacts. That attention now has to be scheduled.

A workable monthly routine covers four moves. Pull the Message Center items with Status for your org = Launched since the last review. Confirm the current build and channel on each representative environment via Settings > About. Reconcile that list against the AI at Work roadmap items you were tracking. Record the delta, with evidence, in a running verification log that survives staff turnover and audit.

Every Verified Arrival Triggers a Governance Move

Verification is not the end of the routine. It is the trigger for the governance work that only the CoE can do. For each newly-arrived capability, three questions follow.

First, does ACP need to change? ACP's strict allowlist blocks every connector that is not explicitly allowed. A new connector in your tenant catalog is implicitly blocked until policy review. Silence is a decision.

Second, does the risk register need an entry? Features that touch data egress, agent tool access, or cross-environment calls deserve an explicit entry with the build number and arrival date as evidence.

Third, what do makers need to hear? Communicate verified state, not plan state. Say what is live in which environments, what remains blocked by policy, and what is coming on the roadmap but has not arrived. The specificity is what builds trust.

Frequently Asked Questions

If Microsoft isn't publishing release waves anymore, what do we plan around?

Plan around verified tenant state and the AI at Work roadmap as a directional input. Message Center and Settings > About are now the primary planning anchors. The roadmap tells you what is coming across the portfolio; Message Center tells you what is coming to your tenant.

How do we know which Power Platform features have actually reached our tenant this week?

Triangulate three signals: Message Center items with Status for your org = Launched, the current build number shown in Settings > About for a representative environment per channel, and Power Platform admin center Notifications. Blog posts and roadmap entries do not count as evidence.

What review cadence should replace twice-yearly wave planning?

Monthly for most enterprises, quarterly at the minimum. The retired wave review was really a concentrated week of attention; that attention must now be scheduled as a standing meeting with a verification log as its artifact.

What does ACP require every time a new connector arrives?

Because ACP is default-deny, any newly-cataloged connector is implicitly blocked until it is explicitly allowed. The governance move is to review the connector against your allowlist policy, decide allow or deny, and record the decision with the arrival date and build number as evidence.

Who owns verification now that there is no fixed wave moment?

The CoE or platform governance team. With no Microsoft-driven forcing function, verification becomes a standing CoE capability. BabyBots recommends naming a single owner for the monthly verification log, the same way you would name an owner for the DLP policy or the environment strategy.

Sources

• One always-on roadmap: Dynamics 365, Power Platform, and Dataverse join the AI at Work roadmap, Microsoft Dynamics 365 Blog, August 25, 2026.
• Business Applications release plans move to the AI at Work roadmap, Microsoft Partner Blog, August 25, 2026.
• Release channel for your model-driven app, Microsoft Learn.
• Change release channels for model-driven apps, Microsoft Learn.
• Advanced connector policies are generally available, Microsoft Power Platform Blog, June 4, 2026.
• Advanced connector policies, Microsoft Learn.
• Power Platform admin center notifications and announcements (preview), Microsoft Learn.
• Prepare for Microsoft 365 updates with Message center, Microsoft Learn.

From Wave Review to Standing Capability

The organizations that handled Wave 2 well in prior years were not the ones who read the release notes fastest. They were the ones who used the concentrated week of attention to produce real governance artifacts: a verified feature inventory, an updated ACP policy, a maker communication, an audit entry. That week is gone. The deployments are not. Elevate verification from a twice-yearly scramble to a standing monthly capability, run it with the same discipline as the financial close, and the retirement of release waves becomes an advantage. The firms that keep planning around announcements will drift. The firms that plan around their tenant will not. Visit BabyBots for more on operating Power Platform governance in the always-on era.