Microsoft SharePoint Online

SharePoint Online connects to Power Automate for building approval and notification workflows, and to Power Apps for custom forms and lightweight apps built on top of SharePoint lists and libraries, both included in most Microsoft 365 plans without separate licensing for basic use.

Practical Details

Power Automate has per-license throttling limits (API call limits per 24-hour period) that can affect high-volume automated workflows, which is a real constraint worth testing against before rolling out an approval flow expected to run thousands of times a day across a large organization.

Actionable Considerations

1. Power Automate and Power Apps are included with most Microsoft 365 plans for basic SharePoint automation
2. Test high-volume workflows against Power Automate's per-license API throttling limits before production rollout
3. Start from Microsoft's prebuilt approval flow templates rather than building complex flows entirely from scratch

SharePoint Syntex uses AI to automatically classify documents and extract metadata from content (like pulling key fields out of invoices or contracts), reducing manual tagging work, while Microsoft 365 Copilot (a separate license) can summarize documents and answer questions grounded in SharePoint content a user has permission to access.

Practical Details

Syntex requires its own licensing and model training/configuration per content type before it can auto-classify documents accurately, so it's not an instant-on feature -- setting up a Syntex model for a specific document type (like expense reports) takes deliberate configuration and testing against sample documents first.

Actionable Considerations

1. SharePoint Syntex auto-classifies documents and extracts metadata, but requires per-content-type model setup first
2. Microsoft 365 Copilot in SharePoint requires separate licensing and respects existing user permissions on content
3. Test Syntex models against representative sample documents before relying on them for accurate auto-classification

SharePoint's permission model inherits down from site to library to folder to item by default, and most team sites are backed by a Microsoft 365 Group, where group membership (owners, members) actually drives site access rather than permissions being managed purely inside SharePoint itself.

Practical Details

Breaking inheritance to set unique permissions on a specific library or item is possible but creates ongoing maintenance burden -- Microsoft's documented best practice is to use SharePoint groups or the underlying Microsoft 365 Group to manage access changes rather than editing permissions item by item.

Actionable Considerations

1. Team sites backed by a Microsoft 365 Group are managed through group membership, not separate SharePoint-only permissions
2. Use groups for ongoing access changes rather than breaking inheritance at the item level repeatedly
3. Review permissions specifically during team reorganizations, since group membership can drift from actual team structure

SharePoint Online has two distinct site types worth choosing deliberately: team sites (backed by a Microsoft 365 Group, which also provisions a shared mailbox, calendar, and optional Teams connection) for collaborative work, and communication sites (no group, broadcast-style) for organization-wide announcements or a curated intranet landing page.

Practical Details

Choosing the wrong site type early creates rework later -- a team site created for what should have been a broadcast communication page ends up with unnecessary group overhead, while a communication site used for active team collaboration lacks the group-based tools (shared calendar, easy membership management) a team site provides.

Actionable Considerations

1. Choose team sites for active collaboration and communication sites for broadcast or intranet-style content
2. Team sites provision a Microsoft 365 Group with shared mailbox and calendar; communication sites don't
3. Define site structure and naming conventions upfront, since site type is a decision that's disruptive to change later

SharePoint Online handles large-scale deployments well, but individual document libraries have practical limits worth planning around -- Microsoft recommends keeping libraries under roughly 100GB and 300,000 items for best performance, even though the hard technical ceiling is higher (5 million items per list/library). The modern flat-metadata approach (tagging and views instead of deep nested folders) performs noticeably better at scale than replicating an old file-server folder structure.

Practical Details

Hub sites let you group related sites (like all sites for one department) under shared navigation and branding without merging them into one massive library, which is the recommended pattern for organizing growth rather than piling everything into a single site collection.

Actionable Considerations

1. Use hub sites to group related sites rather than growing one site collection indefinitely
2. Avoid deep nested folder structures; use metadata and views instead for better performance at scale
3. Monitor library item counts and split libraries before approaching the 300,000-item practical guidance threshold

Modern SharePoint sites support theming (colors, logo, header layout) and customizable page layouts built from web parts, but deep custom branding through custom CSS or master pages -- common in the older "classic" SharePoint experience -- is intentionally limited in the modern experience to keep sites compatible with mobile apps and future platform updates.

Practical Details

This is a genuine trade-off worth knowing upfront: modern SharePoint prioritizes consistency and forward compatibility over the deep visual customization classic SharePoint allowed, so organizations expecting a fully custom-branded intranet may need SharePoint Framework (SPFx) development rather than out-of-box theming alone.

Actionable Considerations

1. Modern SharePoint theming covers colors, logo, and layout, not deep custom CSS or master-page changes
2. Custom SharePoint Framework (SPFx) development is the path for branding beyond built-in theming options
3. Document any custom theme or SPFx changes, since they need to be maintained through platform updates

SharePoint's built-in site usage reports (accessible to site owners) show page views, unique visitors, and file activity per site, while the Microsoft 365 admin center's broader adoption reporting shows organization-wide usage trends across SharePoint, Teams, and other Microsoft 365 apps together.

Practical Details

Because SharePoint sites often decay into unused "ghost sites" without active sponsorship, tracking usage data specifically to identify sites with declining activity (rather than assuming every created site stays useful) is what actually drives meaningful governance decisions like archiving or consolidation.

Actionable Considerations

1. Site owners can access built-in usage reports showing page views and file activity per site
2. The Microsoft 365 admin center shows organization-wide adoption trends across SharePoint and related apps
3. Track declining-activity sites specifically to identify candidates for archiving rather than letting them accumulate indefinitely

SharePoint Online's security is tied into the broader Microsoft 365 and Entra ID (formerly Azure AD) security stack -- Conditional Access policies, sensitivity labels via Microsoft Purview, and data loss prevention (DLP) policies all apply to SharePoint content, not just permissions configured within SharePoint itself.

Practical Details

Permissions can be scoped down to individual items, but Microsoft's own guidance actively discourages heavy use of item-level "unique permissions" (breaking inheritance from the library or site), since it makes access auditing significantly harder and easy to lose track of over time.

Key Considerations

• Conditional Access, sensitivity labels, and DLP policies extend security beyond SharePoint's own permission settings
• Avoid overusing item-level unique permissions, since Microsoft's own guidance flags this as an audit and maintenance risk
• Review external sharing settings (Anyone links, specific people, org-only) at both tenant and site level regularly

Microsoft Learn provides free, official SharePoint documentation and training modules, and Viva Learning can surface curated training content directly within Microsoft 365 for organizations that want a centralized learning hub rather than sending users to external documentation.

Practical Details

Microsoft retired its standalone "SharePoint Learning Pathways" tool, so organizations relying on that specific product for in-app guided training should plan a transition to Viva Learning or a third-party training resource rather than expecting Learning Pathways to remain available.

Actionable Considerations

1. Microsoft Learn offers free, official documentation and structured training modules for SharePoint
2. Viva Learning centralizes training content delivery within Microsoft 365 for organizations wanting an in-app hub
3. Plan around Learning Pathways' retirement if your organization was relying on that specific legacy tool