فا
MSLicenseHub
office · reference
📅

Project 2021

Project 2021 Professional — perpetual desktop scheduler: features, Project Server / Project Online integration, support through 2026.

PROJECT 2021
On this page

Editions · channels · activation · audit notes · FAQs

Editions covered
4
Edition matrix with feature differences and the right audience.
In-depth sections
4
Channels, activation, audit, modern management & more.
FAQs answered
6
Common questions buyers and IT admins ask before purchase.
Words of reference
0.4k
Plain-English, no vendor agenda, updated to current Product Terms.
Edition matrix

Pick the right edition

Each edition targets a specific scale and feature set. Match the workload, not the price tag.

Edition 1
Project Standard 2021

Single-user desktop scheduler. No PPM connectivity.

Edition 2
Project Professional 2021

Adds Project Server / Project Online connectivity, team planner, enterprise resource pool.

Edition 3
Project Server 2019

On-prem PPM platform — paired with Project Professional 2021 for enterprise scheduling.

Edition 4
Project Online (Plan 1 / 3 / 5)

Per-user cloud PPM subscriptions. Plan 3 and 5 include the desktop client.

Side-by-side

Edition comparison

Heuristic capability matrix derived from each edition's intended use. For binding commitments, always confirm against the current Product Terms.

CapabilityProject Standard 2021Project Professional 2021Project Server 2019Project Online (Plan 1 / 3 / 5)
Target audienceGeneralProfessionalProfessionalCloud
Domain / Entra join
Virtualisation rights
Advanced security
Centralised management
Volume Licensing path
Deep dive

Project 2021 — what to actually know

Project 2021 is the perpetual desktop version of Microsoft Project that preceded Project 2024. It shipped alongside Office 2021 in October 2021 and remains in mainstream support through 13 October 2026. For organisations standardising on a perpetual scheduler — typically because of policy, network isolation, or because Project Online / Project for the Web does not match the Gantt-centric desktop workflow planners expect — Project 2021 remains a fully supported choice. For everyone else, Project 2024 or the cloud-based Project for the Web are the more current options.

01

Standard vs Professional

Project Standard 2021 is the single-user desktop scheduler — full Gantt charts, resource sheets, baselines, critical path, earned value, reports, and the Office ribbon UX. Project Professional 2021 adds team collaboration features that depend on connecting to Project Server or Project Online: enterprise resource pool, team planner, synchronisation with SharePoint task lists, and the ability to publish projects to a central Project Web App for portfolio reporting. Professional is the right SKU when there is a central PMO or PPM platform behind the scheduler; Standard is the right SKU for individual schedulers, consultants, or teams that share files but do not need centralised portfolio reporting.

02

Licensing channels

Project 2021 reaches users through Retail (single PC per licence), Volume Licensing (per-device or per-user under the chosen agreement), and OEM pre-installation on some workstation hardware. There is no consumer subscription equivalent in the Microsoft 365 family — Project as a subscription is sold under the separate Project Plan 1 / 3 / 5 SKUs, which are per-user cloud subscriptions and are licensed independently of Microsoft 365 E3/E5. Standalone OEM Project keys offered cheaply outside official channels are essentially always leaked volume keys; treat them as the same red flag as standalone OEM Windows keys.

03

Integration with Project Server, Project Online and SharePoint

Project Professional 2021 connects to Project Server 2019 (on-prem) and Project Online (cloud) for enterprise scheduling: published projects appear in Project Web App, the timeline rolls up into portfolio reports, resources draw from a central pool. It also synchronises with SharePoint task lists for lightweight scenarios. For organisations on Project Online, the desktop Project Professional 2021 client is bundled in the Project Plan 3 and Plan 5 subscriptions — buying Professional separately is only necessary when no matching subscription exists.

04

Support timeline and migration

Project 2021 mainstream support runs through 13 October 2026 (no extended support is provided for perpetual Project SKUs at the consumer / Retail tier; the LTSC equivalent under Volume Licensing has the same five-year servicing model). After that date no further security updates ship and the product becomes a compliance issue for anything that touches regulated project data. Project 2024 (perpetual) or Project Plan 3 / Plan 5 (subscription with desktop client) are the migration targets.

By channel

Where to buy this product

Relative fit of each licensing channel for typical buyers of this product. Calibrate against your own scale and renewal strategy.

Channel fit (typical buyer)
Retail / FPP6
Volume Licensing7
CSP / Microsoft 36510
Retail / FPPIndividuals & small teams

Boxed or ESD keys, transferable, registered to a Microsoft account.

Volume LicensingMid-market & enterprise

MAK / KMS activation, centralized VLSC, optional Software Assurance.

CSP / Microsoft 365Subscription, per user

Monthly / annual seats, managed through partner or admin center.

OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Support timeline

Lifecycle phases to plan against

Office is sold two ways: perpetual (one-time, version-locked, no cloud services) and Microsoft 365 (per-user subscription with the desktop apps, OneDrive, Exchange, Teams). Pick by how stable your environment is, not by sticker price alone.

Phase 1
Perpetual release
Every ~3 years

Office 2016 / 2019 / 2021 / 2024 each get 5 years of mainstream support. No new features after release — only security fixes.

Phase 2
Extended support
Beyond year 5

2019 and earlier are out of extended support. 2021 sits in extended-only servicing; 2024 has the longest runway.

Phase 3
Microsoft 365 Apps
Continuous

Monthly or semi-annual enterprise channels, always patched, always at feature parity. The recommended path for any organisation that lives in email and SharePoint.

Procurement checklist

Do this, not that

The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.

DO

Match the channel to the user — Current Channel for power users, Monthly Enterprise for general staff, Semi-Annual Enterprise for change-averse business units.

DON'T

Run perpetual Office 2016 against a modern Exchange Online tenant — connectivity works but several features (modern auth, sensitivity labels) are unsupported.

DO

License the user, not the device — a single M365 seat covers up to 5 PCs/Macs, 5 tablets and 5 phones for the same person.

DON'T

Buy a Retail box of Office for a shared family computer when each person has their own Microsoft account — Microsoft 365 Family is cheaper and adds OneDrive.

DO

Use Group Policy / Cloud Policy to lock down macros, add-ins and sensitive-data egress.

DON'T

Distribute Office through a generic ISO without the Office Customisation Tool — you end up with sideloaded language packs and orphan installs.

Typical deployments

How buyers actually use Project 2021

Three reference deployments — find the closest match and adapt rather than starting from zero.

Scenario 1
Office-bound knowledge worker

Microsoft 365 Business Standard or E3. Desktop apps, OneDrive, SharePoint, Teams. Outlook against Exchange Online. The default office stack for almost everyone in 2026.

Scenario 2
Field / frontline worker

Microsoft 365 F1 or F3 — web and mobile Office only, but full Teams, Stream, Forms and Lists. A fraction of the price of E3 for users who never sit at a desk.

Scenario 3
Compliance-heavy enterprise

M365 E5 for Purview, Defender, Entra ID P2, and the advanced eDiscovery / DLP stack. The price jump is real, but so is the audit surface area it covers.

Cost optimisation

Where the savings actually live

None of these are tricks — they are the same levers Microsoft's own licensing specialists pull on every renewal.

💰
Microsoft 365 Business Premium is the sweet spot

For ≤300 seats, Business Premium bundles Office, Intune, Defender for Business and Entra ID P1 — replacing two or three separate SKUs at a lower total cost.

📊
Perpetual still wins for air-gapped sites

Manufacturing floors, classified networks and lab PCs without internet are the rare cases where a perpetual Office release legitimately beats a cloud subscription.

🎯
Mac and Windows are the same licence

M365 covers both — do not double-buy because of platform.

Counterfeit & risk

Red flags when buying second-hand

These four signals show up in every counterfeit-licence case we have seen. If any of them is present, walk away — no discount makes it worthwhile.

01
Standalone OEM key sold below market

OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is almost certainly leaked, harvested from scrapped hardware, or fully counterfeit.

02
Lifetime key with no invoice or VLSC record

Microsoft entitlement always leaves a paper trail — a Volume Licensing Service Center record, a CSP invoice, a sealed Retail box with a COA, or a Microsoft Store order. No proof = no defence in an audit.

03
Key works once, then 'not genuine' after the next cumulative update

Classic symptom of a MAK key that has exceeded its activation pool, or a KMS key being abused outside its volume programme. Microsoft revokes these centrally; the activation grace period is short.

04
Seller refuses to put the entitlement in your tenant

Legitimate CSPs and LARs transfer the licence into your Microsoft 365 / Azure / VLSC tenant under your domain. If the seller insists on activating 'for you' on their account, you do not own anything.

Acronyms

Licensing terms used on this page

Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.

CSP

Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.

VLSC

Volume Licensing Service Center — the portal where Volume Licensing keys, agreements and downloads live.

MAK

Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.

KMS

Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.

EA

Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.

SA

Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.

Browse the full glossary →
FAQ

Frequently asked questions

Standard or Professional?+
Standard for individual schedulers and ad hoc collaboration. Professional for organisations with Project Server, Project Online, or a central PPM workflow.
Does Project 2021 connect to Project for the Web?+
No. Project for the Web is a separate cloud product with its own data model; the desktop Project 2021 client connects to Project Server / Project Online, not to Project for the Web.
Is Project bundled in Microsoft 365 E3/E5?+
No. Project is licensed separately via Project Plan 1, 3 or 5, or as a perpetual desktop SKU.
When do Project 2021 updates stop?+
13 October 2026 — same date as Office 2021.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel, an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. Anyone offering a 'cheap OEM key' as a standalone download is, by definition, operating outside Microsoft's distribution terms.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail FPP), verify edition alignment (features used must match the licensed edition), and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Small variances usually resolve with a true-up; large gaps escalate to Software Asset Management engagements and back-billing at list price.
Related

Other products in this category