Dynamics 365 Weekly Updates: Release Planner Retires and Project Operations Adds Investment Projects
- Maria Delia Proteasa
- 2 days ago
- 6 min read
Updates of the week - August 31, 2026
Two announcements landed in the Microsoft 365 admin center this week that, on paper, have nothing to do with each other. One retires a tool. The other adds a project type. Put them side by side, though, and they tell the same story about where Microsoft is taking Dynamics 365 in 2026: less static documentation, more continuous, granular disclosure, whether that's roadmap items or financial transactions.
What to find in this article:
What Changed
Release Planner is going away, and so is the twice-a-year release wave
Release Planner — the site most Dynamics 365 and Power Platform admins have bookmarked to track what's coming — is retiring on November 15, 2026. Its content is moving into the AI at Work roadmap, a single roadmap Microsoft now uses across Dynamics 365, Power Platform, Dataverse, Copilot, and the rest of its business applications and productivity portfolio.
That part is a consolidation. The bigger change is underneath it: Microsoft is retiring the twice-yearly release wave model itself. New roadmap items start publishing directly to the AI at Work roadmap in September 2026. Existing items with a Public Preview or General Availability date on or after June 1, 2026 migrate over from Release Planner this fall. Release Plans on Microsoft Learn stop getting new content in September, though the historical archive stays up. And the September 2026 Release Wave 2 announcement — the one most admins schedule their planning cycle around — simply will not happen.
What replaces it is continuous disclosure: features get published to the roadmap as they become committed, rather than batched into a document twice a year. Saved views from My Release Plans don't carry over, so anyone with curated filters built up over the years starts from zero. Filtering, CSV export, RSS subscriptions, and a new Release Communications MCP Server are the tools Microsoft is offering in exchange.
Nothing about how features are actually built, tested, or rolled out is changing.
Deployment schedules, upgrade timelines, preview programs, and Message Center as the source of tenant-specific notices all stay exactly as they are.
Also worth flagging: Project Operations gets a real Investment Project type
Separately — and unrelated to the roadmap changes above — Dynamics 365 Project Operations is getting the ability to designate a project as an Investment Project, reaching general availability on September 25, 2026.
This is aimed at internal capital work: infrastructure builds, R&D, asset creation, anything a finance team would normally track outside the customer-billable project model. A project manager can classify a project as an investment, attach estimates and budgets by transaction type, and the system blocks investment projects from being attached to a customer contract, keeping them structurally separate from billable work. Costs accumulate as work in progress (WIP) throughout the project, and at completion, the organization chooses between capitalizing the WIP into a fixed asset or transferring it to another ledger account.
Microsoft is also shipping a companion capability slightly ahead of that: multiple eliminations per investment project, reaching public preview on September 11, 2026 — two weeks before the Investment Project feature itself goes GA. Today, Project Operations allows one elimination transaction per investment project. This removes that restriction, letting finance and project accountants post staged eliminations against a single project instead of one all-or-nothing transaction. If your organization is planning to adopt Investment Projects, that preview window is worth testing before the GA feature it depends on even ships.
Why This Matters
The Release Planner retirement matters less because of the URL changing and more because of what it says about how Microsoft expects organizations to plan going forward. A twice-yearly release wave, whatever its flaws, gave IT teams a predictable planning rhythm: read the notes in spring and fall, brief stakeholders, schedule sandbox testing, move on. Continuous disclosure doesn't have a rhythm. It has a feed. That's more current information, but it also means the planning cadence your organization built around release waves — the review meeting, the change-advisory cycle, the "we'll look at this in October" habit — has nothing left to anchor to unless someone rebuilds it around the new model.
The Investment Project feature matters for a narrower but higher-stakes reason: it's a financial governance decision wearing a project-management feature's clothes. Once a project is classified as an investment and WIP starts accumulating against it, the choice at completion — capitalize into a fixed asset versus transfer the ledger balance — has real accounting consequences. That's not a decision project managers should be making unsupervised, and it's not one IT should configure without finance in the room from day one.
Watch List
Governance of the roadmap-review process itself. Whoever owns your internal change-advisory or roadmap-review cadence needs to know the twice-yearly checkpoint they've relied on is disappearing. This is a process gap, not a technical one, and it's easy to miss until the September Release Wave 2 announcement quietly doesn't arrive.
Saved views and bookmarks. My Release Plans' personalized filters don't migrate. Anyone with a curated saved view is starting over on the AI at Work roadmap.
Documentation and training materials that reference Release Planner. Internal wikis, onboarding guides, and even ticket templates that point people to Release Planner or Learn's release-plans page need updating before November 15, or they'll quietly point to a dead end.
RSS/CSV/MCP tooling adoption. If your organization wants roadmap data flowing into its own planning tools rather than checked manually, someone needs to own configuring the new export and MCP options — that's not something that happens by default.
Investment Project classification is a one-way door in practice. Once WIP has accumulated and eliminations have posted, reclassifying a project or unwinding the financial treatment gets complicated fast. Get the classification decision right before go-live, not after.
Chart of accounts and ledger mapping. The choice between generating a fixed asset and transferring WIP to another ledger account depends entirely on how your finance team's chart of accounts is structured. This needs finance sign-off, not just a project manager's toggle.
Contract-restriction behavior in mixed environments. If your organization runs both billable and internal projects through the same Project Operations instance, confirm the system's block on attaching investment projects to contracts doesn't collide with how your team currently structures internal-to-external project conversions.
Practical Recommendations
Bookmark the AI at Work roadmap now and start using it as your primary planning reference in September, in parallel with Release Planner until it retires.
Audit internal documentation, SharePoint pages, and onboarding materials for references to Release Planner, Release Plans on Learn, or "release wave" announcements, and update or redirect them before mid-November.
Rebuild your internal roadmap-review cadence around continuous disclosure rather than a twice-yearly checkpoint — a monthly or bi-weekly filtered pull from the AI at Work roadmap, rather than waiting for a wave announcement that won't come.
If your organization integrates roadmap data into internal planning tools, evaluate the Release Communications MCP Server and the roadmap's CSV/RSS export options before your team defaults back to manual checking.
Before enabling Investment Projects, get finance and Project Operations administrators in the same room to agree on classification criteria, WIP-to-ledger mapping, and which projects qualify — don't let this default to whoever sets up the first project.
Test the elimination workflow in sandbox during the September 11 public preview window, ahead of the feature's own September 25 GA date, so your finance team isn't learning the transaction flow for the first time on a live project.
When to Seek Support
Neither of these changes is disruptive on its own, but each creates a decision point that's easy to underestimate. If your organization's roadmap planning has always run through Release Planner and nobody currently owns rebuilding that process around the AI at Work roadmap, that's worth a short internal conversation before November — and if you'd like a second set of eyes on how to structure it, our team can help review your current roadmap-tracking workflow and set up something durable around continuous disclosure.
If you're evaluating Investment Projects in Project Operations, particularly the classification rules, WIP treatment, or how it should interact with your existing chart of accounts, that's exactly the kind of configuration decision worth validating with someone who's set it up before rather than adjusting after costs have already accumulated. We're glad to help review the setup before you flip it on for a live project.
Need a Second Opinion?
Microsoft explains what changed. ASG, the team behind d365apps.support, helps you figure out what to do about it — from rebuilding your roadmap-review process to configuring Investment Projects correctly the first time.
