Standalone SharePoint Online Plans Are Going Away: What Organizations Should Review Before 2029

Microsoft has announced the retirement of standalone SharePoint Online and OneDrive for Business Plan 1 and Plan 2 SKUs. For some organizations, this may look like a licensing update that can wait until later.

That would be a mistake.

SharePoint Online is often more than document storage. It can support intranets, department portals, document management, approval processes, Microsoft Teams file storage, Power Apps, Power Automate flows, retention policies, external sharing, and business-critical collaboration.

If your organization still uses standalone SharePoint Online plans, the retirement timeline should trigger a practical review of licensing, storage, governance, permissions, integrations, and long-term Microsoft 365 architecture.

This is not just a procurement exercise. It is an opportunity to clean up how SharePoint and OneDrive are being used before the deadline forces a rushed decision.

TL;DR

Microsoft is retiring standalone SharePoint Online Plan 1, SharePoint Online Plan 2, OneDrive for Business Plan 1, and OneDrive for Business Plan 2.

Key dates from Microsoft’s Partner Center announcement:

End of sale: June 2026. No new tenants or customers after May 31, 2026. Renewals are limited to existing customers.
End of life: January 2027. No renewals. Existing contracts continue until expiration.
End of service: December 2029. Standalone plans are fully retired. Customers must transition to Microsoft 365 suites, capacity packs, or pay-as-you-go storage options.

Organizations should review:

Which users and tenants still depend on standalone SharePoint or OneDrive plans
Whether SharePoint is being used as simple file storage or as a business platform
Storage consumption and future growth
Licensing alternatives such as Microsoft 365 Business, E1, E3, or E5 plans
External sharing, permissions, guest access, and ownership
Power Apps, Power Automate, Teams, and third-party integrations
Migration, archival, and cleanup plans before 2029

The safest approach is to start the assessment early, not when renewals become a blocker.

What is changing?
Why this matters beyond licensing
Who is most likely affected?
The timeline organizations should pay attention to
What to review before choosing a replacement plan
SharePoint governance items to clean up during the transition
Power Platform and automation risks to check
A practical readiness checklist
What I would avoid
Final thoughts

What is changing?

Microsoft is retiring the standalone versions of SharePoint Online and OneDrive for Business Plan 1 and Plan 2.

The affected standalone SKUs are:

SharePoint Online Plan 1
SharePoint Online Plan 2
OneDrive for Business Plan 1
OneDrive for Business Plan 2

Microsoft’s stated direction is that Microsoft 365 suites remain the primary way customers access SharePoint and OneDrive capabilities. Microsoft also mentioned future storage alternatives such as capacity packs and pay-as-you-go storage options.

For many organizations, this means SharePoint and OneDrive can no longer be treated as isolated cloud storage products. The future direction is more integrated with the broader Microsoft 365 platform.

That has practical consequences.

A move from standalone SharePoint Online to a Microsoft 365 suite may affect:

Licensing cost and assignment strategy
User access to Teams, Exchange, Office apps, and other services
Identity and security features
Compliance and retention capabilities
Storage planning
Power Platform usage
Support model and admin ownership

The technical migration may be small in some cases. The operational impact can be much larger.

Why this matters beyond licensing

It is easy to look at this announcement and think: “We just need to swap licenses before 2029.”

In reality, SharePoint environments are rarely that simple.

A tenant may have started with a small standalone SharePoint Online plan because the business only needed document libraries. Over time, that same environment may have grown into something much more important:

A company intranet
Department document repositories
HR onboarding libraries
Finance approval folders
Project collaboration sites
Teams-connected SharePoint sites
Power Apps using SharePoint lists as data sources
Power Automate flows routing approvals and notifications
External sharing portals for vendors or clients

When SharePoint becomes part of daily operations, licensing changes become business continuity planning.

The bigger question is not only “Which license replaces the current one?”

The better question is:

What business processes, content, permissions, automations, and users depend on this SharePoint environment today?

That answer should drive the transition plan.

Who is most likely affected?

This change is especially relevant for organizations that intentionally avoided full Microsoft 365 suites and only licensed standalone SharePoint or OneDrive.

Common scenarios include:

Small organizations using SharePoint as affordable document storage

Some organizations purchased standalone SharePoint Online because they wanted cloud document libraries without the full Microsoft 365 bundle.

This may have worked well for basic document management, but it can become a problem if the organization now depends on SharePoint for more than storage.

Organizations using OneDrive for large personal or departmental storage

Some tenants may have used standalone OneDrive for Business plans for large storage scenarios. Those environments should review storage usage early because replacement licensing and future storage options may not map exactly to the same assumptions.

Businesses with mixed licensing

Some users may have Microsoft 365 Business or Enterprise licenses while others still have standalone SharePoint or OneDrive plans.

Mixed licensing can make it harder to understand:

Who has access to what
Which services users are entitled to use
Which users depend on standalone plans
Whether guest or external access is configured safely
Which automations run under which accounts

Tenants managed by partners or inherited from older setups

Some organizations may not even realize they are using standalone plans because licensing decisions were made years ago by a previous admin, reseller, consultant, or IT provider.

That is why the first step should be discovery, not assumptions.

The timeline organizations should pay attention to

Microsoft’s published Partner Center timeline gives organizations a multi-year window, but there are important milestones before 2029.

Milestone	Date	What it means
Retirement announcement	January 2026	Microsoft communicated the retirement of standalone SharePoint Online and OneDrive for Business Plan 1 and Plan 2.
End of sale	June 2026	No new tenants or customers after May 31, 2026. Existing customers may still renew during this phase.
End of life	January 2027	No renewals. Existing contracts continue until expiration.
End of service	December 2029	Standalone plans are fully retired. Customers must transition to Microsoft 365 suites, capacity packs, or pay-as-you-go storage options.

The risk is not only the final 2029 date.

The earlier risk is that procurement, renewal, and licensing decisions become constrained before the technical team has completed an environment review.

A good transition plan should start before renewal pressure begins.

What to review before choosing a replacement plan

Before moving users to a Microsoft 365 suite or another storage option, organizations should review how SharePoint and OneDrive are actually being used.

1. Current license assignments

Start with a clear inventory:

Which users have SharePoint Online Plan 1 or Plan 2?
Which users have OneDrive for Business Plan 1 or Plan 2?
Which users already have Microsoft 365 Business, E1, E3, or E5 licenses?
Are there disabled users still holding licenses?
Are service accounts or automation accounts licensed correctly?

This is important because license changes can affect access to content, OneDrive storage, Teams-connected sites, and app connections.

2. SharePoint site inventory

Review all active SharePoint sites:

Communication sites
Team sites
Teams-connected sites
Hub sites
Classic sites
External collaboration sites
Archived or inactive sites

For each site, identify:

Business owner
Technical owner
Last activity date
Storage usage
External sharing status
Sensitivity or compliance requirements
Connected Teams, Planner, Power Apps, or Power Automate flows

This can quickly reveal whether the environment is clean or whether years of unmanaged growth need to be addressed.

3. Storage usage and growth

Do not only check current storage. Check growth trends.

Review:

Total SharePoint storage used
Total OneDrive storage used
Largest sites
Largest document libraries
Version history growth
Recycle bin usage
Retention policy impact
Records or compliance requirements
Large media, backup, export, or archive libraries

One common mistake is using SharePoint as a cheap dumping ground for files that should be archived, classified, or stored somewhere else.

The retirement of standalone plans is a good time to ask whether the content still belongs in SharePoint.

4. User roles and service needs

Not every user needs the same Microsoft 365 plan.

For example:

Some users may only need browser-based collaboration.
Some users may need desktop Office apps.
Some users may need advanced security, compliance, or information protection.
Some users may need Power Platform capabilities.
Some users may only need access to a limited set of content.

The replacement plan should reflect how people work, not just the cheapest license that appears to include SharePoint.

5. Compliance and retention requirements

If your organization uses SharePoint for regulated or sensitive content, licensing decisions should involve compliance stakeholders.

Review whether you depend on:

Retention labels
Retention policies
eDiscovery
Audit logs
Sensitivity labels
Data loss prevention
Legal hold
Information barriers
Advanced identity and access controls

Some capabilities depend on specific Microsoft 365 plans or add-ons. Treat this as part of the planning process, not an afterthought.

SharePoint governance items to clean up during the transition

Licensing changes are a good reason to improve SharePoint governance.

Here are the areas I would prioritize.

Site ownership

Every active SharePoint site should have a real business owner.

Not just an IT admin.

A business owner should be able to answer:

What is this site used for?
Who should have access?
Is the content still active?
Does anything need to be archived?
Are external users still required?

If nobody can answer these questions, the site should be reviewed before being carried forward into the next licensing model.

Permissions

Permissions are one of the biggest SharePoint risks during any transition.

Review:

Sites with broken inheritance
Document libraries with unique permissions
Folders with custom permissions
Sharing links with broad access
External users
Guest accounts
Microsoft 365 Groups ownership
Overuse of site collection administrators

A license transition should not blindly preserve a messy permission model.

External sharing can be valuable, but it needs control.

Before 2029, review:

Which sites allow external sharing
Which domains are allowed or blocked
Whether anonymous links are enabled
Whether guest access is still needed
Whether old vendors or contractors still have access
Whether sensitive content is exposed through sharing links

For organizations with compliance requirements, this review should happen early.

Information architecture

Look for signs that SharePoint has become difficult to maintain:

Too many sites with unclear purpose
Deep folder structures copied from file shares
Duplicate libraries
Inconsistent metadata
Poor naming conventions
Inactive hub sites
Confusing navigation

Moving to a new licensing model will not fix poor information architecture. It may simply preserve the problem.

Support model

Ask who supports SharePoint today.

Is it:

Internal IT?
A Microsoft 365 admin?
A department power user?
A managed service provider?
Nobody clearly assigned?

If SharePoint supports business-critical work, it needs a support model that includes ownership, documentation, monitoring, and escalation.

Power Platform and automation risks to check

Many organizations use SharePoint lists as the data source for Power Apps and Power Automate.

That makes this licensing change more important.

Before making licensing changes, review:

Power Apps connected to SharePoint lists
Power Automate flows triggered by SharePoint events
Approval flows using SharePoint libraries
Scheduled flows using service accounts
Apps embedded in SharePoint pages
Forms customized with Power Apps
Connections owned by individual users
Flows owned by users who left the company

A common issue is that a business-critical automation runs under one person’s account.

That may work until:

The user leaves
The license changes
The password changes
The account is disabled
The connection expires
The flow owner loses access

This is why the transition should include an automation review, not only a license review.

Practical example

Imagine HR has a SharePoint list called Employee Onboarding.

A Power App is used by managers to submit new hire requests. A Power Automate flow creates folder structures, sends approvals, posts notifications in Teams, and updates the onboarding status.

From a licensing perspective, this may look like a simple SharePoint site.

From a business perspective, it is an onboarding system.

If license or ownership changes break that process, the impact is not “SharePoint had a problem.”

The impact is delayed onboarding.

That is why business process mapping matters.

A practical readiness checklist

Here is a practical checklist organizations can use before 2029.

Licensing discovery

Identify all users assigned standalone SharePoint Online Plan 1 or Plan 2.
Identify all users assigned standalone OneDrive for Business Plan 1 or Plan 2.
Review renewal dates and contract terms.
Compare Microsoft 365 Business, Enterprise, and storage alternatives.
Identify users who may need different license tiers.
Confirm whether service accounts are licensed and governed properly.

SharePoint inventory

Export a list of active SharePoint sites.
Identify site owners and business owners.
Review storage usage by site.
Identify inactive or abandoned sites.
Review hub site structure and navigation.
Identify Teams-connected sites.
Identify classic sites that may need modernization.

Review external sharing settings.
Identify sites with anonymous or broad sharing links.
Review guests and external users.
Check sites with broken permission inheritance.
Review Microsoft 365 Group owners and members.
Remove stale users and old vendors.

Content cleanup

Identify large libraries and storage-heavy sites.
Review version history settings.
Archive old content where appropriate.
Remove duplicate or obsolete files.
Confirm retention requirements before deleting content.
Document content that must be migrated or preserved.

Power Platform and integrations

Identify Power Apps connected to SharePoint.
Identify Power Automate flows triggered by SharePoint or OneDrive.
Review flow owners and connection owners.
Replace user-owned critical flows with governed ownership where appropriate.
Review third-party integrations.
Test critical business processes after license changes.

Communication and change management

Notify business owners early.
Explain what is changing and what is not changing.
Provide a timeline for license transition.
Identify high-risk departments.
Schedule testing before production changes.
Document support contacts and escalation paths.

What I would avoid

Waiting until 2029

The final retirement date may feel far away, but licensing, procurement, governance, and technical cleanup can take longer than expected.

Waiting increases the chance of rushed decisions.

Treating SharePoint as just storage

SharePoint may look like file storage on the surface, but it often supports permissions, metadata, automation, Teams collaboration, intranet pages, and business workflows.

Review the environment as a platform, not just a file repository.

Migrating everything without cleanup

A transition is a chance to remove stale content, clean permissions, and archive old sites.

Do not carry forward every problem just because it is technically easier.

Ignoring Power Automate and Power Apps

If SharePoint lists are used by Power Apps or Power Automate, a license or ownership change can create unexpected issues.

Review apps and flows before changing production licensing.

Choosing a license only by price

Cost matters, but so do security, compliance, supportability, and user experience.

The cheapest option may not be the right option if the organization depends on Microsoft 365 for daily operations.

Technical recommendations

For SharePoint admins and Microsoft 365 consultants, I would approach this transition in phases.

Phase 1: Discover

Inventory licenses, users, sites, storage, external sharing, and integrations.

Tools and areas to review:

Microsoft 365 admin center licensing reports
SharePoint admin center active sites
Microsoft Entra ID users and groups
Microsoft Purview compliance settings
Power Platform admin center
PowerShell reports using Microsoft Graph or PnP PowerShell

Phase 2: Classify

Group sites and users into categories:

Keep active
Clean up
Archive
Modernize
Migrate
Retire

This helps avoid treating every site the same way.

Phase 3: Plan licensing

Map user groups to the most appropriate Microsoft 365 licensing model.

Consider:

Frontline users
Office workers
Power users
Admins
External collaboration scenarios
Compliance-heavy departments
Storage-heavy users

Phase 4: Remediate governance gaps

Clean up the issues that could create risk later:

Missing owners
Old guests
Over-permissioned libraries
Abandoned Teams-connected sites
Critical flows owned by individuals
Unclear retention requirements

Phase 5: Test and transition

Before making broad changes:

Pilot with a small group
Test access to key SharePoint sites
Test OneDrive sync
Test Teams file access
Test Power Apps and Power Automate flows
Validate retention and compliance behavior
Confirm user experience changes

Final thoughts

The retirement of standalone SharePoint Online plans is not something organizations should panic about, but it should not be ignored.

For many businesses, SharePoint has quietly become part of the operational backbone. It stores documents, supports Teams collaboration, powers intranet pages, feeds Power Apps, triggers Power Automate flows, and holds content that departments rely on every day.

That means the right response is not simply “replace the license.”

The right response is:

Understand where standalone plans are used
Review what SharePoint and OneDrive support today
Clean up stale content and risky permissions
Validate Power Platform dependencies
Choose a licensing path that supports the business long term
Communicate early with users and stakeholders

The organizations that start early will have time to make thoughtful decisions.

The organizations that wait may end up treating a platform transition like an emergency renewal problem.

If you are planning a SharePoint Online or Microsoft 365 licensing review, this is a good time to also review your SharePoint governance, permissions, site ownership, Power Platform dependencies, and long-term collaboration strategy.

If you are reviewing SharePoint, Microsoft 365, Power Apps, or Power Automate solutions and want to see practical examples of my work, feel free to explore my portfolio, GitHub projects, and technical blogs.