No, Microsoft Project is not included in any standard Office 365 or Microsoft 365 plan. It is sold as a separate product, either as a one-time desktop purchase or as its own monthly subscription. That split trips up buyers who assume "Microsoft 365" covers every Microsoft app, including the one built for scheduling a real project.
The mix-up costs real time. A manager who expects Project inside an Office 365 admin center login often learns the truth only after a deadline, when Project Professional 2024 turns out to cost $1,129.99 as a one-time purchase.
📋 Which Microsoft 365 plans include zero Project access, and which include a limited edit-only version
💵 What Project costs, broken out by the desktop and subscription paths
🧭 How to tell whether your team needs Project or gets by on free Microsoft Planner
⚠️ The licensing mistakes that leave half a team locked out of a shared schedule
✅ A worked pricing example you can copy for a real team size
Pricing and features reflect the 2026 Microsoft pricing pages. Vendors change these often, so confirm current numbers on Microsoft's own site before you buy anything. A quick check of the live pricing page takes less time than a single support call.
What Microsoft Project Is, and Why It Sits Outside Office 365
Microsoft Project is a dedicated scheduling app, not a document or email tool. It calculates task dependencies, tracks a critical path, and manages workload across a whole team. That is a different job than Word, Excel, or Outlook do, and it explains why Project was built and priced as a specialist tool. Skip Project and try to run the same schedule in a general-purpose app, and the dependencies have to live in someone's head instead of the software.
Microsoft draws a hard line between its everyday apps and its project tools. Office 365 and Microsoft 365 bundle Word, Excel, Outlook, and Teams because nearly every subscriber opens them daily. Project serves a much smaller group of schedulers, so Microsoft prices it apart instead of raising every subscriber's bill for a tool most people never touch. That choice keeps the base Microsoft 365 plans cheap for the millions who never build a formal schedule.
The confusion usually starts with the free tool that IS bundled: Microsoft Planner. Planner ships inside most Microsoft 365 subscriptions and looks similar at a glance, with boards, due dates, and assigned tasks. A reader who has only opened Planner reasonably assumes Project works the same, and that single assumption is why this exact question gets searched so often. Both tools even share icons and a similar color scheme inside the Microsoft 365 app launcher, which makes the mix-up even easier at a glance.
Knowing the difference matters before you promise a client that Microsoft 365 already covers a formal project plan. Skip this step and you end up trying to build a Gantt chart in a tool that was never built for one. You find the gap in a live planning meeting instead of before you signed the contract, and that is a far more costly time to learn it. Many teams only discover this the first time a client demands a real, dated timeline instead of a loose task list, by which point the deadline is already set.
Which Microsoft 365 Plans Come Closest to Including Project
No Microsoft 365 or Office 365 plan, including Business Premium or Enterprise E5, bundles a full Project license. What those plans DO include is limited edit access to a project someone else already created and shared with you. That distinction is easy to miss, because "edit access" sounds like ownership until you try to build something new. Even the top-tier Microsoft 365 E5 plan, with its full security and compliance stack, still stops at that same basic edit line.
Microsoft's own documentation spells out which suites get that access and what it covers. Users with basic edit access can rename a task, reassign it, or shift a start date inside a plan someone else built. They cannot create a new project, and they cannot touch fields the two tools do not share, such as custom dependencies or baseline dates. A reader who tries to click "New Project" from inside one of these plans without a Project license simply will not find the option.
| Microsoft 365 / Office 365 plan | Project access included |
|---|---|
| Microsoft 365 F3, Business Standard, Business Premium | Basic edit on shared plans only |
| Office 365 E1 | Basic edit on shared plans only |
| Microsoft/Office 365 E3 and E5 | Basic edit on shared plans only |
| Any plan plus a Project license | Full create, edit, and schedule access |
The table above covers the everyday productivity tiers, and it leaves out the separate Project line on purpose. Those plans were never built to carry full Project rights, no matter how high a business climbs the Microsoft 365 ladder. Buying a bigger Microsoft 365 plan will not unlock Project on its own, so budget for the license on its own from day one. A common trap is moving a whole company from E3 to E5 hoping Project appears, when the move changes nothing about Project access.
Which Situation Applies to You?
The right path depends on how many people need to build schedules versus only glance at one. Company size and how often plans change both shift the answer. Match your situation below before you spend anything on a new license.
You manage a small team that needs task tracking
If your team needs due dates, assignments, and a simple board, Microsoft Planner already does that job for free. It ships inside most Microsoft 365 plans, so there is nothing extra to buy. You likely do not need Project at all, and paying for it would add cost for features like resource leveling that a basic task board never uses.
Most small teams outgrow Planner only once a client starts asking for a dated, dependency-aware schedule instead of a running list of tasks. Until that day comes, adding a Project license is spending money to solve a problem your team does not have yet. Revisit the question every time a client contract gets noticeably bigger or more formal than the last one.
You are the one project manager building the schedule
A single project manager who owns the Gantt chart and the dependencies needs one Project license. The rest of the team keeps working from Microsoft 365's free edit access to the shared plan. This is the most common real setup, because most contributors only update their own tasks rather than restructure the whole timeline.
One license for the scheduler, paired with free edit access for everyone else, covers this case at the lowest cost. If a second person is ever promoted into a scheduling role, that is the moment to add a second license, not before. Adding the license early, before a second scheduler needs it, is a common cause of overspending for small teams. Wait for the actual promotion, not the plan to promote someone.
Multiple people co-edit the same live schedule
Desktop Project does not support real-time co-editing, even when the file lives in SharePoint or Teams. Two people in the same .mpp file at once is not a supported setup, no matter how the file is stored. If your team truly needs several people on one live plan together, the current Microsoft guidance points to Planner Premium instead of desktop Project.
Planner Premium is the direct successor to Project for the web, built for that shared, real-time case. Teams that force live co-editing onto the desktop app often end up with one person's changes quietly overwriting another's. That silent overwrite is usually the first sign a team has outgrown the desktop app and needs the web-based option instead. Moving one project manager to Planner Premium is often a smaller change than it sounds, since the same task and date fields carry across.
You run a portfolio of projects across a large company
Big companies running many projects at once, sharing staff across departments, need Project Server Subscription Edition. That tier is sold through a partner, not a self-serve checkout. It plugs into SharePoint Server on the company's own systems, so it needs real IT planning before rollout, unlike the desktop app that installs in minutes.
A company at this size usually pairs the rollout with its own PMO, since the reports and resource tools only pay off once someone owns them full time. Skipping that IT planning step is the single biggest reason a Project Server rollout stalls before it ever reaches the teams it was bought for. Budget for a partner-led setup phase up front rather than treating it as an afterthought once licenses are already purchased.
Two Ways to Buy Project on Top of Microsoft 365
Microsoft sells Project through two separate paths, and picking the wrong one is where most wasted budget happens. The first is a one-time desktop purchase. The second is a recurring cloud subscription bundled with Planner's premium tier.
The desktop path, Project Standard 2024 or Project Professional 2024, is a single payment tied to one user and one PC. There is no ongoing monthly fee once you buy it. The subscription path, sold as Planner and Project Plan 1, 3, or 5, bills monthly per user and adds the cloud-connected version of Project alongside Planner's premium features.
A business with steady, long-term project managers often comes out cheaper on the one-time desktop license. A business whose project needs rise and fall month to month gains more from the freedom to add or drop subscription seats. Neither path wins every case, so match it to how stable your project-manager headcount stays over time.
| Buying path | Best fit |
|---|---|
| Desktop (Project Standard/Professional 2024) | One or two long-term project managers, stable headcount |
| Subscription (Planner and Project Plan 1/3/5) | Fluctuating project-manager headcount, cloud-only access needed |
Before you buy either path, check whether your company already runs Project Server Subscription Edition somewhere. Adding a desktop license on top of a big-company system you already own usually adds extra cost. An admin can check what your company already owns in a few minutes, inside the Microsoft 365 Admin Center. It is also worth asking if a former employee's old license still sits unused, since that seat can often cover a new hire for free.
The subscription path has one more edge worth a mention. It includes the web version of Project, so a scheduler on a laptop or a Chromebook is never blocked by the Windows-only desktop tool. That matters more for a remote or contractor-heavy team than for an office where everyone shares the same company PC. A remote-first agency often picks the subscription for this one reason, even when the raw cost slightly favors the desktop license.
Worked Example: Pricing Project for a 12-Person Team
Here is a real calculation using Microsoft's own 2026 pricing, for a company with 12 employees. Only 2 of those 12 people build project schedules day to day. Assume the company already pays for Microsoft 365 Business Premium for all 12 seats, so the only open question is what Project adds on top.
Both project managers get Project Professional 2024 as a one-time desktop purchase at $1,129.99 each. That comes to a one-time cost of $2,259.98 for the whole company. The other 10 employees pay nothing extra, because their existing Microsoft 365 seats already include the basic edit access covered earlier in this article.
Total first-year Project cost: $2,259.98, with $0 in extra cost in year two. That holds true unless the company adds a third project manager or needs a feature only the subscription tier offers. Compare that with the subscription path, listed on Microsoft's current pricing page, which bills every month instead of once. Either path leaves the other 10 employees out of this math entirely, since their free basic edit access already covers what they need.
For a team that keeps the same two project managers for more than about 18 months, the one-time desktop purchase is usually the cheaper choice. A monthly per-seat fee eventually crosses the price of a single upfront license. Run this same math against your own headcount and staff turnover before you commit to either path.
The same math scales down cleanly for a smaller team, too. A five-person consulting firm with one scheduler pays a single $1,129.99 fee and nothing more, while the other four staff work from free Microsoft 365 edit access on any project shared with them. That single number is the entire Project budget line for a team that size, which makes it easy to plan for during annual software renewals.
Where the Free Tools Stop and a Paid License Starts
Three real situations show exactly where Microsoft's free Office 365 tools run out of road. Each one teaches a different lesson about the line between Project and Planner, and together they cover the small, mid-size, and large-company cases. Reading all three before you buy anything helps you spot which pattern your own team is closest to today.
The operations manager who outgrew Planner's boards
Sarah runs operations for a 30-person marketing agency and started every client project on a free Planner board. The boards worked fine until a client asked for a firm date that depended on five tasks in order across three people. Planner has nothing built in to show that one task must wait on another, so the order lived only in Sarah's head.
Microsoft's own To Do app aggregates anything assigned to you across Planner and Outlook, so Sarah could at least see her own tasks in one place. She still could not build a dependency chain in the free toolset, and that gap is exactly what Project closes. Her early guess was that a longer Planner board would slowly turn into a real schedule. In fact, no amount of extra tasks adds real order to the work.
| What Sarah needed | What Planner could do |
|---|---|
| Task dependencies and a calculated critical path | Independent tasks with no sequencing logic |
| One shared schedule multiple people edit live | Boards that do not track schedule-wide slippage |
She bought one Project Professional license for herself and kept the rest of the team on Planner for daily task visibility. She built the client schedule in Project, then mirrored the top-level dates back into a Planner board everyone could already see. The client got the firm delivery date it wanted, and the wider team never had to learn a new tool.
The IT admin who tracks Project like every other Microsoft product
Marcus manages Microsoft 365 licenses for a 200-person shipping company. He keeps a monthly list of every product that loses support, and he tracks Project the same as he tracks Windows, Exchange, and Office. Microsoft retires all of them on overlapping clocks. Project Server 2013 reaches the end of its support around the same time as standalone Office 2013 apps, so an old Project install is the same risk as an old Office install.
IT admins already grumble when Microsoft changes the 365 Admin Center layout without warning. That matters to Marcus because the Admin Center is the exact screen he uses to hand out and take back Project licenses. A moved button costs him real time every quarter, so he now checks for a new layout before each licensing cycle. That habit saves him from a stalled license during a hiring rush.
The 200-person firm that needed portfolio-level visibility
Dana leads the PMO at a factory company running 40 projects at once, all sharing the same pool of engineers. Single Project licenses solved scheduling inside each project, but nobody could see whether one engineer was booked on two projects at the same time. That blind spot cost the company a missed deadline before anyone caught the overlap.
The firm moved to Project Server Subscription Edition, which pools every engineer in one place and shows workload across every live project. One Project license, no matter how well a single person uses it, cannot see past its own file. Only a Server-tier setup gives a PMO that full, company-wide view. Dana's team learned this only after a missed deadline forced the change.
Pros and Cons of Buying Project Separately
Pros
- Only the people who build schedules pay for Project, instead of raising the cost of every Microsoft 365 seat
- The desktop license is a one-time cost with no recurring bill once purchased
- Full Gantt charts, baselines, and resource leveling exist nowhere in the free Microsoft 365 toolset
- A single Project license still lets the rest of the team view and lightly edit shared plans for free
- Enterprise buyers get a dedicated Project Server tier built for true portfolio management
Cons
- Buyers who assume Project ships with Microsoft 365 discover the extra cost only after committing to a deadline
- Desktop Project does not support real-time co-authoring on the same file
- The subscription tier can cost more than a one-time desktop license over several years
- A team with only one Project license creates a single point of failure if that person leaves
- Project for the web is being phased out in favor of Planner Premium, which unsettles teams mid-transition
Do's and Don'ts When Adding Project to Microsoft 365
Do
- Confirm which Microsoft 365 tier your company already holds before assuming any of them include Project
- Buy Project licenses only for the people who build and restructure schedules, not everyone who glances at one
- Check whether your headcount and project length favor the one-time desktop purchase over a monthly subscription
- Test the exact collaboration workflow your team needs, since co-authoring works differently across the desktop and cloud versions
- Revisit your license count whenever a project manager leaves, since an unused seat still bills every month on the subscription tier
Don't
- Don't promise a client a full project schedule before checking whether your Microsoft 365 plan includes Project
- Don't buy a Project subscription for every team member when only one or two people schedule work
- Don't assume Planner and Project behave identically because their interfaces look similar at a glance
- Don't keep paying for a legacy Project 2013 or 2016 license past its end-of-support date without checking the current version
- Don't skip the Project Server conversation if your company already runs 10 or more simultaneous projects sharing resources
Mistakes to Avoid When Assuming Project Is Included
- Quoting a client before checking licensing. A firm that promises a detailed schedule and then discovers it needs a $1,129.99 license mid-project either eats the cost or delays the deliverable.
- Buying a Project license for the whole team. Most teams only need one or two schedulers, and everyone else already gets free edit access through Microsoft 365, so blanket licensing wastes budget every month.
- Assuming Planner and Project are interchangeable. A team that builds a complex, dependency-heavy schedule in Planner eventually hits a wall Planner cannot solve, which forces a late and disruptive migration into Project.
- Ignoring the co-authoring limitation. A team that tries to have three people edit the same desktop Project file at once risks overwriting each other's changes with no built-in conflict resolution.
- Letting old Project versions run past end-of-support. An unsupported Project 2013 or 2016 install stops receiving security patches, a real exposure for any company handling client data in its schedules.
- Choosing the subscription tier for a permanent, stable team. Paying a recurring per-seat fee for years can cost more than the one-time desktop purchase would have, once the subscription runs past roughly 18 months.
- Missing the Project Server conversation at scale. A company running dozens of concurrent projects on individual desktop licenses loses visibility into shared resource conflicts that only a Server-tier deployment can surface.
- Forgetting to reclaim a license when someone leaves. An unused Project subscription seat keeps billing every month until an admin manually removes it in the Microsoft 365 Admin Center.
What to Do Next
- Check your current Microsoft 365 or Office 365 plan against the table above to confirm what Project access it already includes.
- Count how many people on your team need to build and restructure schedules, rather than only view or lightly edit one.
- Decide between the one-time desktop purchase and the monthly subscription based on how stable your project-manager headcount is likely to stay.
- Buy the license through your Microsoft 365 admin, then assign it in the Admin Center to the specific people who need it.
- If your company runs 10 or more concurrent projects sharing resources, start a conversation with a Microsoft partner about Project Server Subscription Edition before your next budget cycle.
Frequently Asked Questions
Does Microsoft 365 Business Premium include Project?
No. Business Premium, like every Microsoft 365 and Office 365 tier, only grants basic edit access to a project someone else built and shared. It does not let you create or own a schedule.
Is Microsoft Planner the same as Microsoft Project?
No. Planner is a free task board included in most Microsoft 365 plans. Project is a paid scheduling tool with dependencies, baselines, and resource tools that Planner does not offer.
How much does Microsoft Project cost in 2026?
Project Standard 2024 costs $679.99 as a one-time purchase. Project Professional 2024 costs $1,129.99. Both are licensed for one user on one device, per Microsoft's current pricing page.
Can I add Project to an existing Microsoft 365 subscription?
Yes. You buy a Project license apart from Microsoft 365, either the desktop app as a one-time purchase or a Planner and Project subscription tier, then assign it to specific users in the Admin Center.
Do all my employees need a Project license to see the schedule?
No. Anyone on a Microsoft 365 or Office 365 plan already gets free basic edit access to a project shared with them. Only the people who build or restructure the schedule need a full license.
What happened to Project for the web?
It is being retired. Microsoft is folding it into Planner, in the Planner Premium tier, so teams that relied on live co-editing there should plan a move to Planner Premium.
Does Microsoft Project work on Mac?
Only with extra steps. Microsoft Project's desktop app is Windows-only, so Mac users typically run it through a Windows virtual machine, or they use the web-based Project tools instead.
What is the difference between Project Standard and Project Professional?
Professional adds resource tools and payroll timesheets. Project Standard covers schedule, task, and cost tracking with Gantt charts. Professional adds full resource tools and the ability to connect to Project Server.
Can two people edit the same Project file at the same time?
No, not in the desktop app. Microsoft Project's desktop app does not support real-time co-editing, even when the file sits in SharePoint or Teams. Two people in one file at once is not a supported setup.
Is there a free version of Microsoft Project?
Not exactly, but Planner comes close for basic task tracking. Microsoft Planner, included in most Microsoft 365 plans, covers free task boards and due dates. It lacks Project's scheduling depth and resource tools.
Do I need Project Server for a small business?
Usually not. Project Server Subscription Edition targets big companies juggling many projects that share the same staff across departments. That is too much for a small business running one or two projects at a time.
How do I check whether my company already owns a Project license?
Look in the Microsoft 365 Admin Center under Billing > Licenses. Any Project Standard, Project Professional, or Planner and Project subscription your company owns will list there, along with how many seats are already assigned.