OnePlan’s November 2026 Release: What Matters for Your PMO

OnePlan’s November 6, 2026 release is one of its more substantial updates this year. Two headline additions, a Strategic Execution Management solution and a preview of the OnePlan MCP Server, point to where the platform is heading: tighter alignment between strategy and delivery, and AI assistants that work directly with your portfolio data.

Below is our summary of what’s new, plus the items we’d put on a PMO or IT leader’s radar before the release goes live.

The headline: Strategic Execution Management

The new Strategic Execution Management (SEM) solution template gives organizations a structured way to connect strategic objectives to the initiatives, investments, and outcomes meant to deliver them. It covers goals and OKRs, benefits tracking, roadmaps, and performance dashboards.

Why it matters: Most PMOs can tell you what’s in flight. Far fewer can show leadership which initiatives are moving a strategic objective and which are consuming budget without a clear line to value. SEM is built to close that gap.

Our take: A template is a starting point, not a strategy. The value depends on how well your objectives, scoring criteria, and benefit measures are defined before you configure anything. If those definitions are fuzzy, the dashboards will be too. We recommend aligning executive sponsors on the objective hierarchy and benefit measures first, then mapping them into OnePlan.

AI meets your portfolio: the OnePlan MCP Server (preview)

The OnePlan MCP Server connects AI assistants such as Microsoft Copilot and Claude to OnePlan using the Model Context Protocol, an open standard for linking AI assistants to business systems. In plain language, users can:

  • Portfolio: find and explore plans, create plans, update fields, and move plans to their next stage
  • Resource management: check capacity and availability, compare candidates on availability or cost rate, and adjust allocations (with a preview before anything is saved)
  • Financial management: view budget, forecast, and actuals by cost category, and update values across periods
  • Work plans: view tasks, risks, issues, dependencies, and assignments
  • My Work: see your own assignments and post task status updates

Importantly, everything runs within each user’s existing OnePlan permissions.

Why it matters: Asking “which of my projects are over budget this quarter?” and getting an answer in seconds lowers the barrier for executives and occasional users who rarely log in to a PPM tool.

Our take: This is a preview, and it includes write actions, not just reads. Before piloting, decide which user groups get access, which actions you are comfortable letting an assistant perform, and how you’ll review changes made through it. Permission enforcement is a strong foundation, but governance over AI-driven updates is still your organization’s call. Interested customers can request preview access through their OnePlan Customer Success Manager.

Portfolio and plan details

  • Private plans: Enabled by plan type, these let plan owners limit full access to their plan team. Permissions apply across My Work, Timesheets, Resource Plan, Modeler, Dashboards, and more.
  • Automations that keep hierarchy: Copy Plan and Create Plan now carry over the source plan’s hierarchy, so new plans land where teams expect them.
  • On-demand roadmap printing using your saved views.
  • Richer plan detail pages: dashboard widgets alongside plan data (included in exports), business rules that tailor pages by user, data, or process step, refreshed detail tables, and configurable icons for hyperlink fields.
  • Split fields are now configured within Multi Lookup Field setup and appear in more views, including Portfolio List, Roadmap, and Board.

Watch-out on private plans: Per OnePlan, private plan permissions are enforced only inside OnePlan. They are not enforced in external reports or integrations. If you push OnePlan data into Power BI or other systems, plan to filter private plans by plan type and adjust those datasets before you turn this on. Otherwise, sensitive plans may remain visible downstream.

Reporting: status reports and dashboards

Status reporting gets a meaningful upgrade:

  • Design versioning: Submitted reports keep the design they were created with, even after the template changes. That protects your historical record and makes it safe to evolve report designs.
  • Dedicated pages: One status report can serve executives, sponsors, and delivery teams with different fields per page, each exportable on its own.
  • Dashboard widgets, field sets, and trend fields in status reports, all included in exports.

Dashboards can now pull from a plan’s associated plans, and plan-level dashboards support plan-level widgets, giving a connected view of how related initiatives contribute to shared goals.

Why it matters: Audience-specific pages reduce the number of separate reports PMOs maintain, and versioning addresses a common audit concern about historical reports changing after the fact.

Everyday work: timesheets, financials, and work plans

  • Timesheet views: personal saved views, plus global views admins can set for the organization.
  • Combined Cost Types on demand: for organizations using Combined Cost Types, a Combine Costs option under Import Costs rebuilds combined figures from any financial plan whenever needed.
  • Work item search for quickly narrowing large work plans.

Mobile, language, and accessibility

OnePlan Mobile moves to a new platform with automatic session renewal, threaded conversations, clearer status messages, screen reader labels, and secure on-device session storage. Users will need to select their region and sign in once after updating. OnePlan also adds Portuguese language support, with coverage expanding in future releases.

Security and integrations: action items for IT

These are the changes most likely to require action from your team:

  1. Authentication keys now support expiry dates and granular scopes (OData, backup, or API, with API access defined by entity and create, read, update, or delete permissions). Existing keys are set to never expire and keep all scopes, so nothing breaks. That also means nothing improves until you act. We recommend auditing current keys, reissuing them with least-privilege scopes, and setting a rotation schedule.
  2. Azure DevOps integration moves to OneConnect 2.1 for better performance and reliability with large data volumes. This changes the IP address range used to process Azure DevOps integrations. If you restrict Azure DevOps access by IP, you must update your allow list or the integration may stop syncing. Open a OnePlan support ticket to get the new range. Legacy Azure DevOps Epic and Teams Project integrations are not affected.
  3. Microsoft Project Connector now syncs calendars more efficiently, which should speed up publishing for organizations with many calendars.

Your pre-release checklist

  • Confirm whether you restrict Azure DevOps by IP and request the new range now
  • Inventory authentication keys and plan a scoping and rotation pass
  • Review external reports and integrations before enabling private plans
  • Decide whether to pilot the MCP Server preview, and with which users and guardrails
  • Brief mobile users on the one-time region selection and sign-in
  • Evaluate whether SEM fits your strategic planning process, and define objectives and benefit measures first

How PPM Works can help

As a OnePlan partner with 20+ years in enterprise PPM and 600+ implementations, PPM Works helps organizations get value from releases like this one, not just access to new features. Whether you want to stand up Strategic Execution Management, pilot AI assistants with the right governance, or tighten integration security, our team can help you plan and execute.

Talk to PPM Works about putting the November release to work in your portfolio.

Source: OnePlan November 6, 2026 Release Notes