Microsoft SharePoint

Name: Microsoft SharePoint
Brand: Microsoft

Microsoft SharePoint is a collaboration and content platform that creates team sites and intranets, stores and manages documents, and publishes pages and news to share information across an organization.

Est 1975|Valuation $2888.5B|Raised $72.9B|214 Ref Customers

LinkedIn 29.0M|Website|Web traffic 1233.4M|FTEs 232,851|HQ Redmond, Washington, US

MarketsInternal Communications & Intranet Productivity & Collaboration Suite

Platform CoversPolicy Management Knowledge Management

Published Oct 24, 2026

01Common complaints

Company sizes or stages where this product is overkill or insufficient
- Very small teams (under ~25 users) without IT support may find SharePoint’s governance and configuration overhead disproportionate.
Industries or use cases where competitors may be preferable
- Communications-led intranet programs that require a turnkey, polished intranet experience quickly may be better served by dedicated intranet vendors (e.g., Simpplr, LumApps, Staffbase), depending on requirements and budget.
Technical requirements that this product may not meet
- If an organization requires a radically custom web application and full control without platform constraints, SharePoint Online’s modern model and tenant guardrails can be limiting.
Budget constraints that make alternatives more appropriate
- If an organization is not already licensing Microsoft 365, a simpler content tool may be cheaper and faster to deploy.
- If the primary need is external collaboration and storage, solutions like Box or Google Workspace may offer simpler experiences, though total cost should be validated with governance requirements in mind.
Specific workflows or integrations where the product falls short
- Complex contract lifecycle management implemented on SharePoint can become brittle; studies and practitioner interviews document challenges when SharePoint is used as a bespoke CLM system.
Red flags in the buying process
- Assuming inclusion in a licensing bundle implies low implementation effort
- No defined governance model for site creation, external sharing, and retention
- No plan for permissions and information architecture (a frequent root cause of user dissatisfaction)
Current limitations acknowledged by the vendor
- Microsoft Learn documentation indicates legacy page models and certain legacy features are not available in the modern experiences in SharePoint Online.
Features on the roadmap (not yet available) - note estimated dates if available
- Microsoft Tech Community posts describe a visual refresh rolling out to general availability; schedules can vary by tenant and update channel.
Scale limitations (at what volume/size does it break down?)
- Scale depends on architecture and governance; performance and perceived latency are influenced by multiple factors (per Microsoft Learn guidance).
Security or compliance gaps
- The platform can support strong controls, but real-world risk often comes from misconfiguration:
  - Overly broad sharing
  - Permission inheritance complexity
  - Third-party app permissions in the Microsoft 365 ecosystem (research highlights risks associated with fine-grained OAuth permissions and third-party integrations across Microsoft 365 data, including files).
Technical debt or architectural limitations mentioned in reviews
- Community threads frequently cite:
  - Developer experience pain
  - Confusing legacy vs modern feature split
  - Inconsistent behavior across UI surfaces (SharePoint vs Teams vs OneDrive)
API limitations or integration constraints
- Microsoft Graph is commonly used for Microsoft 365/SharePoint Online access patterns; building robust integrations often requires specialist knowledge and careful permission modeling.

- Company sizes or stages where this product is overkill or insufficient - Very small teams (under ~25 users) without IT support may find SharePoint’s governance and configuration overhead disproportionate. - Industries or use cases where competitors may be preferable - Communications-led intranet programs that require a turnkey, polished intranet experience quickly may be better served by dedicated intranet vendors (e.g., Simpplr, LumApps, Staffbase), depending on requirements and budget. - Technical requirements that this product may not meet - If an organization requires a radically custom web application and full control without platform constraints, SharePoint Online’s modern model and tenant guardrails can be limiting. - Budget constraints that make alternatives more appropriate - If an organization is not already licensing Microsoft 365, a simpler content tool may be cheaper and faster to deploy. - If the primary need is external collaboration and storage, solutions like Box or Google Workspace may offer simpler experiences, though total cost should be validated with governance requirements in mind. - Specific workflows or integrations where the product falls short - Complex contract lifecycle management implemented on SharePoint can become brittle; studies and practitioner interviews document challenges when SharePoint is used as a bespoke CLM system. - Red flags in the buying process - Assuming inclusion in a licensing bundle implies low implementation effort - No defined governance model for site creation, external sharing, and retention - No plan for permissions and information architecture (a frequent root cause of user dissatisfaction) - Current limitations acknowledged by the vendor - Microsoft Learn documentation indicates legacy page models and certain legacy features are not available in the modern experiences in SharePoint Online. - Features on the roadmap (not yet available) - note estimated dates if available - Microsoft Tech Community posts describe a visual refresh rolling out to general availability; schedules can vary by tenant and update channel. - Scale limitations (at what volume/size does it break down?) - Scale depends on architecture and governance; performance and perceived latency are influenced by multiple factors (per Microsoft Learn guidance). - Security or compliance gaps - The platform can support strong controls, but real-world risk often comes from misconfiguration: - Overly broad sharing - Permission inheritance complexity - Third-party app permissions in the Microsoft 365 ecosystem (research highlights risks associated with fine-grained OAuth permissions and third-party integrations across Microsoft 365 data, including files). - Technical debt or architectural limitations mentioned in reviews - Community threads frequently cite: - Developer experience pain - Confusing legacy vs modern feature split - Inconsistent behavior across UI surfaces (SharePoint vs Teams vs OneDrive) - API limitations or integration constraints - Microsoft Graph is commonly used for Microsoft 365/SharePoint Online access patterns; building robust integrations often requires specialist knowledge and careful permission modeling.

Deal disqualifiers: indicators of poor fit

Organizations that need a fully managed "done for you" intranet with minimal administration
Organizations lacking resources to manage permissions, site sprawl, and lifecycle governance
Organizations that primarily need lightweight wiki authoring and rapid cross-linking rather than document-library centric workflows

Why some customers left for competitors (churn reasons)

Commonly cited churn drivers in community discourse and competitor marketing:
- Preference for simpler UX (Google Drive/Dropbox-like workflows)
- Desire for a communications-focused intranet product with faster time-to-value and less governance overhead (Simpplr/LumApps/Staffbase)
- Frustration with SharePoint customization/development complexity

02Why they buy

Competitive advantages validated by customer feedback (not just vendor claims)
- Frequently cited selection reasons include additional perceived value when bundled with Microsoft 365 and deep integration with Microsoft collaboration tools.
Unique features and capabilities competitors lack
- SPFx extensibility that spans SharePoint, Teams, and Viva Connections (single development model across multiple Microsoft surfaces)
Differentiation from competitors based on reviews
- SharePoint is commonly described as feature-rich but complex, whereas competitors often emphasize usability and faster time-to-value.
Value propositions with evidence from case studies
- Vendor-published materials describe governance patterns at scale; these illustrate potential outcomes but are vendor-reported and should be validated independently.
Areas where competitors have advantages (balanced)
- Confluence: more natural wiki-like knowledge workflows in many teams
- Box: simpler external sharing and cross-platform file collaboration in certain scenarios
- Simpplr/LumApps: faster rollout for communications-focused intranets with less configuration required

- Competitive advantages validated by customer feedback (not just vendor claims) - Frequently cited selection reasons include additional perceived value when bundled with Microsoft 365 and deep integration with Microsoft collaboration tools. - Unique features and capabilities competitors lack - SPFx extensibility that spans SharePoint, Teams, and Viva Connections (single development model across multiple Microsoft surfaces) - Differentiation from competitors based on reviews - SharePoint is commonly described as feature-rich but complex, whereas competitors often emphasize usability and faster time-to-value. - Value propositions with evidence from case studies - Vendor-published materials describe governance patterns at scale; these illustrate potential outcomes but are vendor-reported and should be validated independently. - Areas where competitors have advantages (balanced) - Confluence: more natural wiki-like knowledge workflows in many teams - Box: simpler external sharing and cross-platform file collaboration in certain scenarios - Simpplr/LumApps: faster rollout for communications-focused intranets with less configuration required

Why customers chose this product over alternatives

Frequently cited reasons across review ecosystems:
- Already paying for Microsoft 365
- Native integration with Teams/Office desktop apps
- Centralized repository owned by the organization (vs tied to individual user accounts)

03Field reports

Review-platform availability and scale

G2 lists a very large number of SharePoint reviews (example snapshots show several thousand reviews).
TrustRadius lists a large review volume as well (example snapshots show a few thousand reviews and ratings).
Gartner Peer Insights has a SharePoint product page, but full quote extraction can be limited by access controls; this report includes only small excerpts available via publicly accessible pages.

Positive themes (what customers say they like)

Integration with Microsoft 365
- Review aggregators and commentary consistently frame SharePoint as a common choice when an organization already uses Microsoft 365.
Versioning and collaboration
- TrustRadius review summaries emphasize version history and collaboration benefits; reviewers often cite improved workflows versus emailing attachments.
Intranet publishing and information findability (when implemented well)
- SharePoint’s modern pages/news and hub structures are often used for intranets, with Graph-powered content experiences described in Microsoft support documentation.

- Integration with Microsoft 365 - Review aggregators and commentary consistently frame SharePoint as a common choice when an organization already uses Microsoft 365. - Versioning and collaboration - TrustRadius review summaries emphasize version history and collaboration benefits; reviewers often cite improved workflows versus emailing attachments. - Intranet publishing and information findability (when implemented well) - SharePoint’s modern pages/news and hub structures are often used for intranets, with Graph-powered content experiences described in Microsoft support documentation.

Negative themes (what customers complain about)

Complexity / usability / governance burden
- Multiple third-party summaries and community threads emphasize the product can feel complex, with a steep learning curve and significant governance needs.
Support frustration
- Reddit threads report long-running support tickets and users sometimes getting better answers from the community than from official support.
Outages and search/indexing sensitivity
- Some reviewers report outages affecting indexing, per excerpts on vendor review pages.
Storage and overage cost pain
- Reddit community threads explicitly complain about SharePoint storage overages and describe overage pricing as high.

- Complexity / usability / governance burden - Multiple third-party summaries and community threads emphasize the product can feel complex, with a steep learning curve and significant governance needs. - Support frustration - Reddit threads report long-running support tickets and users sometimes getting better answers from the community than from official support. - Outages and search/indexing sensitivity - Some reviewers report outages affecting indexing, per excerpts on vendor review pages. - Storage and overage cost pain - Reddit community threads explicitly complain about SharePoint storage overages and describe overage pricing as high.

Direct quotes from review/community sources (positive and negative)

Gartner Peer Insights (excerpt visible on accessible page)
- “We have noticed that there are often Service Outages reported by Microsoft where SharePoint outages almost always affect indexing.” (Reviewer quote shown on Gartner Peer Insights page.)
Reddit (examples)
- Storage: “Overage pricing for Sharepoint is insane.” (r/sharepoint)
- Support: “I have a ticket open with Microsoft for months now…” (r/sharepoint)
- General sentiment thread: “Anyone else here hate SharePoint?” (r/sharepoint)

- Gartner Peer Insights (excerpt visible on accessible page) - “We have noticed that there are often Service Outages reported by Microsoft where SharePoint outages almost always affect indexing.” (Reviewer quote shown on Gartner Peer Insights page.) - Reddit (examples) - Storage: “Overage pricing for Sharepoint is insane.” (r/sharepoint) - Support: “I have a ticket open with Microsoft for months now…” (r/sharepoint) - General sentiment thread: “Anyone else here hate SharePoint?” (r/sharepoint)

Specific outcomes customers achieved (with metrics when available)

Review platforms often contain qualitative outcomes (reduced errors, better collaboration). TrustRadius all-reviews pages include user-reported claims like reducing errors due to improved data management, but those claims are not independently verified.

Case Studies

Microsoft "customer zero" style case study (vendor-published)
- Microsoft published an “Inside Track” post describing lessons learned from deploying SharePoint at Microsoft over decades (framed as a customer deployment).
- Critical evaluation:
  - This is informative for governance patterns and scale considerations.
  - It is vendor-authored and not independent validation of outcomes.
Migration tooling narrative (independent coverage)
- VentureBeat covered Microsoft’s acquisition of Mover, explicitly connecting it to Microsoft 365 migration solutions including the SharePoint Migration Tool.
- Critical evaluation:
  - Confirms Microsoft investment in reducing migration barriers.
  - Does not prove migrations are easy in all environments; practitioner feedback still commonly flags migration complexity.

- Microsoft "customer zero" style case study (vendor-published) - Microsoft published an “Inside Track” post describing lessons learned from deploying SharePoint at Microsoft over decades (framed as a customer deployment). - Critical evaluation: - This is informative for governance patterns and scale considerations. - It is vendor-authored and not independent validation of outcomes. - Migration tooling narrative (independent coverage) - VentureBeat covered Microsoft’s acquisition of Mover, explicitly connecting it to Microsoft 365 migration solutions including the SharePoint Migration Tool. - Critical evaluation: - Confirms Microsoft investment in reducing migration barriers. - Does not prove migrations are easy in all environments; practitioner feedback still commonly flags migration complexity.

04Best fit

Company sizes

Typical fit
- Mid-market to large and enterprise organizations with significant employee counts and enterprise-scale revenue.
- Organizations with IT/admin capacity for governance, security, and information architecture.
Also viable
- Smaller organizations when requirements are modest (team sites and document libraries) and Microsoft 365 is already in use.

Industries and verticals where adoption is strongest (with customer examples)

Common across:
- Professional services
- Manufacturing
- Financial services
- Healthcare (with appropriate compliance configuration)
- Public sector (often in specialized clouds / configurations)

Roles and personas: decision makers AND end users

Decision makers
- CIO/IT Director, Head of Digital Workplace, Security & Compliance leads
Implementers
- Microsoft 365 admins, SharePoint admins, intranet managers, Power Platform teams
End users
- Knowledge workers, internal communications teams, HR, project teams

Pain points and challenges the product addresses

Centralizing documents and reducing attachment-related workflow issues
Publishing internal news/policies and creating an intranet landing experience
Providing structured team collaboration spaces and search-based discovery (when maintained)

Qualification criteria: indicators of a good fit

Organizations that already standardize on Microsoft 365 (Teams/Office/Entra)
Organizations able to invest in governance and information architecture
Organizations that require extensibility (SPFx/Power Platform) and enterprise controls

05The pitch

What the product does (core value proposition in objective terms)

Microsoft SharePoint is a collaboration and content platform used to create team sites/intranets, store and manage documents, publish pages/news, and share information across an organization.
In practice, SharePoint typically shows up in two primary deployment modes:
- SharePoint Online (cloud service as part of Microsoft 365)
- SharePoint Server (on‑premises)
Microsoft’s official marketing pages could not be accessed due to automated-user-agent blocking, so this report relies on other first‑party Microsoft materials (support and learning documentation) as primary evidence for “what it is/how it works,” and third‑party sources for validation and criticism.

- Microsoft SharePoint is a collaboration and content platform used to create team sites/intranets, store and manage documents, publish pages/news, and share information across an organization. - In practice, SharePoint typically shows up in two primary deployment modes: - SharePoint Online (cloud service as part of Microsoft 365) - SharePoint Server (on‑premises) - Microsoft’s official marketing pages could not be accessed due to automated-user-agent blocking, so this report relies on other first‑party Microsoft materials (support and learning documentation) as primary evidence for “what it is/how it works,” and third‑party sources for validation and criticism.

Target market and market positioning

Most commonly positioned as:
- Employee intranet / internal communications hub
- Document management and team collaboration layer tightly integrated with Microsoft 365 (Teams, OneDrive, Outlook, Viva)
- A configurable platform for building internal sites, workflows (via Power Automate), and extensions (via SharePoint Framework / SPFx)

Get a comprehensive analysis of Microsoft SharePoint including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Microsoft SharePoint

01Common complaints

Deal disqualifiers: indicators of poor fit

Why some customers left for competitors (churn reasons)

02Why they buy

Why customers chose this product over alternatives

03Field reports

Review-platform availability and scale

Positive themes (what customers say they like)

Negative themes (what customers complain about)

Direct quotes from review/community sources (positive and negative)

Specific outcomes customers achieved (with metrics when available)

Case Studies

04Best fit

Company sizes

Industries and verticals where adoption is strongest (with customer examples)

Roles and personas: decision makers AND end users

Pain points and challenges the product addresses

Qualification criteria: indicators of a good fit

05The pitch

What the product does (core value proposition in objective terms)

Target market and market positioning

How it compares

01Common complaints

Deal disqualifiers: indicators of poor fit

Why some customers left for competitors (churn reasons)

02Why they buy

Why customers chose this product over alternatives

03Field reports

Review-platform availability and scale

Positive themes (what customers say they like)

Negative themes (what customers complain about)

Direct quotes from review/community sources (positive and negative)

Specific outcomes customers achieved (with metrics when available)

Case Studies

04Best fit

Company sizes

Industries and verticals where adoption is strongest (with customer examples)

Roles and personas: decision makers AND end users

Pain points and challenges the product addresses

Qualification criteria: indicators of a good fit

05The pitch

What the product does (core value proposition in objective terms)

Target market and market positioning

How it compares