CollabPoint
← Insights
Adoption

The Microsoft 365 roadmap is not your roadmap: turning it into a 12-month plan for 2027

How to read Microsoft's roadmap, turn it into a 12-month plan in five steps, and decide which items should honestly wait.

8 min read
Quick answer

The Microsoft 365 roadmap, now called the Microsoft Copilot Roadmap, lists the features Microsoft is building and rolling out. Your own 12-month plan lists what your organization will do, in what order, with one owner per item, tied to your renewal, budget and end-of-support dates.

Every November, someone in IT opens Microsoft's roadmap, scrolls through a few hundred features and calls it a 2027 plan. It isn't one. Microsoft's roadmap tells you what Microsoft is building. Your roadmap has to say what your organization will do, in what order, who owns each item, how people will hear about the changes that affect their work, and how it lines up with the renewal and budget dates you already have.

This guide covers how to read Microsoft's roadmap, how to turn it into a 12-month plan in five steps, and which items should honestly wait.

What the Microsoft 365 roadmap is now

Microsoft's public roadmap has a new name. Microsoft Learn now calls it the Microsoft Copilot Roadmap, formerly known as the Microsoft 365 Roadmap and the AI at Work Roadmap. The purpose hasn't changed: it is a public list of features Microsoft is building and rolling out across Microsoft 365.

You can filter it by product, status, release phase, platform and cloud instance (government tenants on GCC, GCC High or DoD have their own filter), and download the results as a CSV. Each feature has one of three statuses:

  • In development: being built and tested. Features in public preview stay in this status and might change before release.
  • Rolling out: reaching the first customers, but not yet all of them.
  • Launched: available to all applicable customers.

That is useful input. It is not a plan. The roadmap doesn't know which licences you hold, what still runs on your own servers, when your renewal falls or who on your team has time.

Read it next to Message center

The roadmap is the long view. For changes that will land in your own tenant, Microsoft points admins to Message center in the Microsoft 365 admin center. Microsoft says major updates are communicated at least 30 days in advance when action is required, and Message center can sync posts into Planner as tasks.

A practical habit: filter the roadmap to the products you own, skim it once a quarter, and treat the Message center items that need action as your real to-do list. An item marked In development is a signal, not a date.

Step 1: List what you own

Start with an inventory, not with features. Licences and add-ons, by plan and seat count. Anything still on premises: servers, SQL databases, file shares, line-of-business apps. The integrations people depend on every day. A roadmap item only matters if it touches something on this list.

Step 2: Anchor to the dates you already have

Put the fixed dates on the calendar before any project: licence renewals, the date your 2027 budget gets locked, audit dates, and end-of-support dates for the systems you run.

Check every end-of-support date on Microsoft's own lifecycle pages, not from memory. Microsoft's Ending Support in 2027 page, for example, lists Windows Server 2016 at January 12, 2027, SQL Server 2017 at October 12, 2027, and the end of servicing for Windows 11 Enterprise and Education, version 24H2, at October 12, 2027. If any of those are on your list from step 1, they go on the plan first.

Two colleagues compare two printed documents side by side on a white conference table.

Step 3: Decide the order and the owner

Now fit the work around the dates. Two rules keep the order sensible: anything tied to a hard date comes first, and foundations come before the features that depend on them. Copilot works with the access people already have, so cleaning up SharePoint permissions and sharing belongs ahead of a wider Copilot rollout.

Every item gets one owner, by name, and a reason that points to a date. A simple grid is enough:

QuarterItemTied toOwnerWho noticesStatus
Q1Decide the path for remaining Windows Server 2016 workloadsEnd of support, January 12, 2027Infrastructure leadUsers of the apps on those servers, during any moveDoing
Q1Review licence mix and seat countsLicence renewalIT directorAnyone whose plan or features changeNext
Q2Tighten SharePoint permissions and sharingCopilot pilotSecurity leadAnyone who shares files; some people lose access they hadNext
Q3Upgrade SQL Server 2017 databasesEnd of support, October 12, 2027Database adminUsers of the apps on those databases, at cutoverNext
None yetMicrosoft FabricNo clear data owner yetNone yetNone yetNot yet

Step 4: Give the plan an owner and a review rhythm

Most roadmaps go stale the week after the planning meeting, because nobody owns the review. Name one person who owns the plan itself, separate from the item owners. Then put the rhythm on the calendar: a short monthly check against Message center, and a fuller review each quarter when budget and renewals come up.

Keep each review to four questions. What moved? What is blocked? What changed in Microsoft's plans that affects ours? What do people need to hear about before next month?

Step 5: Plan what people will notice, not just what IT switches on

For IT, a roadmap item is a setting, a migration or a licence change. For everyone else it is a change to their working day: a new button in Outlook, a Teams meeting that behaves differently, Copilot appearing in Word, a shared folder they can no longer open. If nobody tells them first, they find out from a help desk ticket or a confused call on a busy morning. That is not an IT problem. It is a business one.

For every item on the plan that people will see, add three things:

  • Who notices: Which teams or roles, and how much their day changes. The same change lands differently for a front-line team, a finance analyst and a department manager.
  • What they need to know, and when: A short note before the change lands, in plain words: what is changing, when, what they need to do, and where to ask. Not a forward of Microsoft's announcement. Message center gives you lead time on many changes; use it to tell people before, not after.
  • How they learn it: Match the effort to the size of the change. A small update might need two lines in a team channel. A bigger one might need a five-minute demo in an existing team meeting, a one-page guide, or a champion in each department who has used it first.

This is where the plan needs people from outside IT. Department leads know the weeks to avoid, such as month end or audit season. HR or internal communications know which channels people actually read. For any change that touches daily work, name a business owner next to the IT owner. Our guides to sustainable Microsoft 365 adoption and why Copilot adoption stalls go deeper on champions and role-based training.

Say "not yet" out loud

A good plan is as clear about what waits as about what happens. Mark an item "not yet" when:

  • It is still In development on Microsoft's roadmap, so you would be planning around a feature that might change.
  • It depends on a foundation you don't have yet, such as clean permissions or sensitivity labels.
  • Nobody can own it this year, including the communication and training it needs.

Write the reason next to it. That stops the same debate coming back every quarter. Data platforms are a common example: our Microsoft Fabric readiness check explains when the honest answer is not yet.

If you don't have a Microsoft architect

Plenty of 200 to 2,000 person organizations run Microsoft 365 and Azure without a dedicated architect. Two ways CollabPoint helps:

  • Journey Lite is a senior Microsoft advisor on retainer: Microsoft 365 and Azure monitoring, a living 12-month roadmap, monthly guidance and a 24-hour response. It is advisory and monitoring, not a help desk.
  • Journey.ai is our managed strategy, roadmap and support service. With Journey.ai, your roadmap sits in Orbit, our secure client portal, next to live health, subscriptions, requests and documents.

Start your 2027 plan

If your 2027 budget is being set now and nobody owns the roadmap, talk to us about Journey.ai, our managed strategy, roadmap and support service.

Talk to CollabPoint

Want a second set of eyes?

Our team works with mid-market IT leaders to capture the upside of AI and the Microsoft cloud without the compounding risk. Start with a focused conversation.

Frequently asked questions

What is the Microsoft 365 roadmap?

It is Microsoft's public list of features being built and rolled out across Microsoft 365. Microsoft now calls it the Microsoft Copilot Roadmap. Each item shows a status: In development, Rolling out or Launched.

Is the Microsoft 365 roadmap the same as Message center?

No. The roadmap is public and covers features in general. Message center sits in your Microsoft 365 admin center and is where Microsoft posts planned changes and announcements for your organization.

Who should own end-user communication for Microsoft 365 changes?

IT should know what is changing and when, but it works best when a business owner shares the job. Department leads know how a change affects their teams and which weeks to avoid, and HR or internal communications know which channels people read. Put both names on the plan for any change people will notice.

How often should we review our own roadmap?

A short check each month and a fuller review each quarter works for most mid-market teams. What matters most is a fixed rhythm and one owner, so the plan doesn't stop at the planning meeting.

We use cookies for analytics and to measure our ads. You can accept or decline.