Article
With Project Online retiring September 30, 2026, Carolinas PMOs are looking for a replacement that lives where their teams already work. Here is what running project and portfolio management inside Microsoft Teams actually looks like, and why the Copilot integration matters.
Every Project Online replacement conversation we have with a Carolinas PMO eventually lands on the same practical question: where do people actually work? For most mid-market organizations on the Microsoft stack, the honest answer is Teams. Status meetings happen in Teams calls. Approvals happen in Teams chat. If the project plan lives somewhere else, in a separate browser tab, a separate login, a separate mental model, adoption suffers no matter how good the tool is underneath.
That is the specific problem a Teams-native PM app solves, and it is worth understanding on its own terms rather than as a footnote to the Project Online migration.
A project management tool that lives inside Teams as a proper app, not an embedded browser frame or a link that opens a new tab, changes how the tool gets used day to day. Dashboard, project, and governance views become personal tabs a user opens the same way they open any other Teams tab. A specific project board can be pinned to a channel, so a standup happens next to the live Gantt or Kanban board instead of next to a screenshot that was accurate three days ago.
For PMOs across the Carolinas managing distributed teams, that matters more than it sounds. A Charlotte-based program manager and a Greenville field team looking at the same pinned board in the same channel are looking at the same data, updated in real time, without anyone exporting a status deck first.
The part of this shift that is genuinely new is the Microsoft 365 Copilot integration. Onplana ships an agent for Copilot that answers plain-language questions grounded in live Onplana data, not a static export. A project manager can ask what is assigned to them right now, what is overdue, or for a status summary of their most active project, and get an answer sourced directly from the current state of the plan, with a citation and a link back to the record.
This is a meaningfully different interaction model than clicking through a portfolio dashboard looking for the same information. It also respects the same permissions the user already has. The agent can only see and change what that person’s role and plan allow, so asking Copilot for a portfolio summary does not become a way around access controls.
For PMOs that have been trying to get Copilot adoption past the “it drafts my emails” stage, a grounded agent tied to actual project data is one of the more concrete uses we have seen land with non-technical staff.
Any tool asking for a foothold inside Teams gets, and should get, scrutiny from IT before it gets scrutiny from end users. The relevant details for Carolinas IT admins evaluating this:
Sign-in is single sign-on only, through Microsoft Entra ID, including organizations running SAML or OIDC through enterprise SSO. The Teams app requests no standing access to mailboxes, files, or directory data beyond what authentication requires.
Onplana has completed Microsoft Publisher Attestation, and data is hosted on Microsoft Azure and encrypted in transit. That combination gives a security review a known baseline to work from rather than an unknown vendor’s self-reported claims.
Rollout is phased through the Teams admin center. An admin allows the app once, then uses permission and setup policies to pilot with a single team before widening access and pinning it more broadly. That is the same rollout pattern most Carolinas IT teams already use for other Teams apps, which keeps this from becoming a special case in the governance process.
Project Online retires September 30, 2026, with no in-place upgrade path, which is the forcing function behind most of these evaluations right now. A Teams-native PM tool that imports existing .MPP files, XML exports, and Project Online schedules, and preserves dependencies and milestones in the process, removes one of the bigger objections we hear from PMOs: that migrating means rebuilding every active plan by hand.
Landing the result directly inside the Teams environment the organization already runs on also sidesteps a second common objection, that a new PM platform means training an organization on a new interface it has to remember to check. If the destination is a tab inside an app people already have open all day, the adoption curve looks very different than it does for a standalone portal.
This is not a fit for every organization. A PMO running heavy custom reporting workflows or deeply specific enterprise governance built up over a decade of Project Online use should still go through a full requirements mapping before picking a destination platform, and for some of those organizations a dedicated enterprise PPM tool remains the right call.
For the mid-market Carolinas PMOs we work with most often, organizations in the 50 to 500 employee range that need real portfolio and resource visibility without the overhead of an enterprise PPM deployment, a Teams-native option that also carries a grounded Copilot agent solves the adoption problem and the reporting problem at the same time. Onplana for Microsoft Teams is worth a look specifically for that reason, and it is free on every plan with automatic Microsoft sign-in, so a pilot with one team costs an afternoon, not a procurement cycle.
Devsoft Solutions helps Carolinas organizations plan and execute Project Online migrations, including platform selection, data export, and Teams rollout governance. If your PMO is working through the September 2026 deadline, get in touch.
— Continue reading
Moving from Slack to Microsoft Teams is more than a chat platform switch. For North and South Carolina businesses already on Microsoft 365, the migration unlocks Teams Copilot and meeting AI that Slack cannot match at the same price point. Here is what to preserve, what to accept losing, and how to run the cutover without disrupting your team.
Network drives are the single biggest barrier between Carolina businesses and AI tools like Microsoft 365 Copilot. Here is what the migration involves, what breaks along the way, and what you gain on the other side.
Microsoft Copilot is reshaping the productivity platform calculus for Carolinas businesses. If your organization runs on Google Workspace and AI adoption is on the agenda, here is what the migration to Microsoft 365 actually involves and whether the AI payoff justifies the disruption.
— Related services
On-prem to Azure, Google Workspace to Microsoft 365, file shares to SharePoint. Planned migrations with no surprises at cutover.
Microsoft Copilot rollout, custom copilots with Copilot Studio, and Azure OpenAI integrations for the parts of your business where AI actually pays back.
Tailored Microsoft 365 plans, deployment, and ongoing support — designed for businesses that need reliable productivity infrastructure without the in-house overhead.
