OnePlan’s November Release Puts Your Portfolio Inside Your AI Assistant. Here’s How to Get Ready.
OnePlan’s November 2026 release is live, and the headline feature is a preview of the OnePlan MCP Server. It connects AI assistants such as Microsoft Copilot and Claude directly to your OnePlan data, so your team can ask questions about plans, resources, and financials in plain language and make updates without leaving the chat.
As a OnePlan partner, we have spent time with the release. Below is our take on what matters most for PMO leaders and IT teams, where we would slow down, and what we would put in place before switching it on.
The headline: your portfolio, in the conversation
The MCP Server uses the Model Context Protocol, an open standard for linking AI assistants to business systems. In practice, a resource manager can type “Who on the design team has capacity in March?” and get the answer from OnePlan in the same chat window they already use for email drafts and meeting summaries.
“Who on the design team has capacity in March?”Ask it in Copilot or Claude. Get the answer from OnePlan.
It covers five areas: portfolio, resource management, financial management, work plans, and My Work. In most of them, users can make changes as well as look things up. That includes creating plans, moving a plan to its next stage, editing resource allocations, and adjusting budget and forecast values. Every request runs within the user’s existing OnePlan permissions.
Now in previewThe feature is in preview now. Customers who want to try it can reach out to their OnePlan Customer Success Manager.
Why it matters
Portfolio data has always lived one step removed from where people do their daily work. Getting a single answer often means opening several views and clicking through screens. Fewer handoffs and faster answers are useful on their own.
The bigger opportunity, in our view, is adoption. Every PMO has stakeholders who rarely log into the PPM tool. If they can get what they need by asking a question in Copilot or Claude, the portfolio data becomes something more of the organization actually uses.
Where we would slow down: governance
AI access to your portfolio is only as safe and as accurate as the setup underneath it. Before rolling it out widely, we would look hard at four things.
01It writes, not just reads.An allocation change made in a chat can ripple across several projects. OnePlan shows a preview before anything is saved, which helps, but your organization still needs clear rules about who should be making which changes this way.
02Permissions carry over exactly as they are.The MCP Server respects each user’s OnePlan permissions. That is the right design, but it also means any role that is loosely configured today becomes easier to exploit tomorrow. If nobody has reviewed your security model since go-live, now is the time.
03Answers are only as good as your data.An assistant will confidently report stale allocations or outdated forecasts. Clean resource and financial data before you invite people to ask questions of it.
04Start with a pilot.OnePlan itself recommends beginning with a small group, such as resource managers or PMO leads. We agree, and we would add: define up front what success looks like so you know when to expand.
Other updates worth your attention
The MCP Server gets the attention, but several other changes in this release deserve a look.
Strategic Execution Management templateA new solution template for defining strategic objectives, aligning initiatives and investments to them, tracking goals and OKRs, and measuring business benefits. This is a strong fit for organizations trying to show leadership what their portfolio is actually delivering.
Private plansSensitive plans can now be restricted to their plan teams.Important caveat: private plan permissions apply only inside OnePlan. They are not enforced in external reports or integrations. If you feed OnePlan data into Power BI, a data warehouse, or another system, you will need to filter private plans by plan type and adjust those integrations yourself.
Status report historySubmitted status reports now keep the layout they were submitted with, even if the report design changes later. That gives you a reliable historical record for audits and executive reviews.
Authentication key controlsKeys now support expiry dates and granular scopes. Existing keys default to never expiring with all scopes, so nothing breaks, but we recommend reviewing and tightening them.
Azure DevOps integration changeThe integration moves to the OneConnect 2.1 connector infrastructure, which changes the IP address range used. If you restrict Azure DevOps access by IP, open a OnePlan support ticket for the new range and update your allow list.
Everyday improvementsCopy Plan and Create Plan automations now carry over plan hierarchy, roadmaps can be printed from saved views, timesheets get saved views, financial plans get a Combine Costs option, and Portuguese language support is new.
A readiness checklist before you enable AI access
1Review roles and permissions in OnePlan, especially for anyone who can edit allocations or financials.
2Clean up resource assignments, capacity data, and forecasts.
3Choose a pilot group and define what success looks like.
4Decide which updates should happen through an AI assistant and which should stay in OnePlan.
5Check downstream reports and integrations for private plan exposure.
6Confirm your Azure DevOps IP allow list if you use one.
7Review authentication keys and set expiry dates and scopes.
How PPM Works can help
PPM Works has spent more than 20 years helping mid size and enterprise organizations get real value from their PPM investments, with more than 600 implementations completed. As a OnePlan partner, we can help you assess readiness for the MCP Server, review your permissions model, clean up portfolio data, and plan a pilot that sets your team up for success.Want to talk through what this release means for your organization?Contact our team
