Tech Ideas & Best Practices

“We’ll Just Use AI to Build Our Intranet.”‍

A sentence we’ve been hearing in almost every second demo.

A few years ago, the objection was: “We’ll build it ourselves.”

Today, it has changed to: “We’ll just ask ChatGPT or Claude to create our SharePoint intranet.”

‍Honestly, we understand why.

AI is incredibly good at generating layouts, writing content, suggesting navigation, and even creating SharePoint page structures. It can produce something that looks impressive in minutes.
But after delivering hundreds of SharePoint projects, we’ve learned one thing: looking like an intranet and functioning like an intranet are two completely different things.

The Hidden Problem with AI-Generated Intranets

Most AI tools start with a prompt: “Create a modern HR intranet.” Within seconds, you receive a homepage, a news section, an employee directory, quick links, a hero banner, and department pages. Everything looks polished.

The problem?

It looks exactly like thousands of other intranets.

Your organization isn’t generic. Your employees aren’t generic. Your processes certainly aren’t generic. An intranet should reflect how your business actually works, not how an AI assumes businesses work.

AI Doesn’t Know Your Organization

AI has never attended your leadership meetings.

It doesn’t know

• how employees search for information,
• which departments rarely collaborate,
• which documents are most frequently requested,
• why employees ignore your current intranet,
• which approval processes create bottlenecks,
• how new hires actually onboard,
• what executives want employees to see first.

Without understanding these realities, AI makes assumptions. Great intranets are built on discovery, while AI builds on probability, and those are very different things.

It Designs Pages, Not Employee Experiences

Many AI-generated intranets look beautiful, until employees start using them.
Then the questions begin:

• Where do I find HR forms?
• Why are there three different document libraries?
• Why is search returning outdated files?
• Why is onboarding scattered across multiple pages?
• Why is nobody using this?

Aesthetics doesn’t measure a successful intranet; adoption does. If employees stop using it after two weeks, the design has already failed.

AI Doesn’t Challenge Bad Decisions

One of the most valuable things consultants do isn’t building; it’s asking uncomfortable questions. Questions like:

• Do employees actually need this page?
• Why are there six approval levels?
• Should this content even exist?
• Who owns this information after launch?

AI rarely pushes back; it simply executes your prompt. Human experts question assumptions before they become expensive mistakes.

Every Company Has Hidden Complexity

During discovery sessions, we often uncover things clients didn’t initially mention, like departments using different naming conventions, duplicate document repositories, outdated policies still being referenced, teams relying on personal OneDrive folders, or manual approval workflows that nobody enjoys. None of these appear in a prompt, yet they determine whether an intranet succeeds or fails.

AI Doesn’t Think About Governance

A homepage is only a tiny part of an intranet. Behind every successful SharePoint deployment are decisions like permission strategy, information architecture, metadata planning, search optimization, content lifecycle, governance policies, site ownership, and long-term maintenance.
These aren’t glamorous, but they’re exactly what keep an intranet useful years after launch. Ignoring them creates technical debt that becomes harder and more expensive to fix over time.

The Biggest Risk: False Confidence

Perhaps the biggest downside isn’t poor design; it’s believing the intranet is “done” because it looks complete. Modern AI produces convincing outputs, and it creates confidence before validation. Many organizations launch an AI-generated intranet only to realize months later that employees aren’t adopting it. By then, redesigning becomes significantly more expensive.

A Story We’ll Never Forget

A few months ago, we met with a prospective client. After our discovery session, they thanked us and said something we’ve been hearing more often:

“We’ll use AI to build this internally.”‍

Fair enough. They had talented people, they had Microsoft 365, and they believed AI would help them create everything they needed.

Several months passed, then they reached out again.

Not because SharePoint had failed. Not because AI had failed. Because the intranet wasn’t working for their employees. They had pages, navigation, and attractive layouts, but they didn’t have adoption.

Employees couldn’t find information, departments had inconsistent structures, content ownership wasn’t clear, search wasn’t delivering the right results, and nobody felt responsible for maintaining it.

The intranet looked finished, but the employee experience wasn’t. This time, instead of asking us to build pages, they asked us to redesign the entire experience. We started where we always do: understanding people before technology.

We interviewed stakeholders, mapped user journeys, simplified navigation, and reorganized content. We created governance, defined ownership, optimized search, and removed unnecessary pages. Only then did we begin redesigning.

The difference wasn’t that humans created prettier pages. The difference was that humans solved the right problems.

We Use AI Too

This isn't an article against AI.

In fact, we use AI every day.

It helps us generate ideas, speed up documentation, create content drafts, brainstorm layouts, and accelerate repetitive work.

AI makes our team faster. It doesn't replace discovery, strategy, or understanding your business.

The Best Intranets Are Built with AI and Human Expertise

Think of AI as an incredibly capable assistant, not as your intranet architect.

Architecture requires experience, and experience comes from solving real business problems across many organizations.

Technology changes, but employee behavior doesn't.

The organizations with the highest adoption rates aren't the ones using the newest AI tools; they're the ones that understand their people.

Before You Ask AI to Build Your Intranet…

Ask yourself a few questions:

• Does it understand how our employees work?

• Can it identify gaps in our business processes?

• Will it challenge our assumptions?

• Can it design governance for the next five years?

• Will it improve employee adoption, not just page design?

If the answer is "no," then AI should be part of the solution, not the entire solution.

Because the goal isn't to launch an intranet; it's to build one your employees actually use.

And that's where experience still matters.

Many users assume that Microsoft OneDrive and Microsoft SharePoint are the same because both allow users to store and share files in Microsoft 365.

But the real difference is actually very simple:

• OneDrive is built for personal work and individual productivity.
• SharePoint is built for team collaboration and organizational content management.

In modern workplaces, organizations use both platforms together because each serves a different purpose. Understanding when to use OneDrive and when to use SharePoint helps employees collaborate more effectively while keeping information organized and secure.

Why does Microsoft 365 Include Both OneDrive and SharePoint?

Since both tools store files and documents, many people naturally ask:

“Why are there two separate tools?”

The answer lies in how the files are being used.

While both platforms manage documents, they are designed for completely different types of work environments.

What is OneDrive?

Microsoft OneDrive is designed for individual use.

It allows users to securely store personal files, drafts, notes, and work-in-progress documents in the cloud. By default, files remain private unless the user decides to share them.

Common OneDrive Use Cases

Users commonly store:

• Draft presentations
• Personal reports
• Temporary work files
• Individual notes
• Files under development
• Personal backups and synchronization files

In most cases, the content is managed and controlled by the individual employee.

What is SharePoint?

Microsoft SharePoint is designed for team collaboration and organizational content management.

Instead of personal storage, SharePoint provides a shared environment where departments and teams can:

• Store documents together
• Collaborate in real time.
• Manage permissions
• Organize information centrally
• Build communication portals and intranet sites.

SharePoint uses team sites and document libraries to help organizations manage shared content efficiently.

OneDrive vs SharePoint: Core Feature Comparison

Security and Governance Comparison

Both platforms are secure and part of the Microsoft 365 ecosystem, but they manage access differently.

• OneDrive focuses on personal ownership and privacy.
• SharePoint focuses on organizational governance and control of collaboration.

Pricing and Licensing Comparison

One important thing many businesses do not realize is that organizations typically do not choose OneDrive instead of SharePoint.

In most Microsoft 365 business subscriptions, both services are included together because they complement each other.

Introduction: A Deadline You Cannot Afford to Ignore

The technology industry runs on lifecycles, and 2026 marks one of the most consequential support-ending milestones Microsoft has ever staged. Long before the calendar turned to summer, Microsoft began winding down support for a cluster of widely deployed products, some of which date back to 2016. For IT administrators, security teams, and business leaders, this is not a distant warning. It is a live event unfolding right now.

This blog covers every major Microsoft product reaching end of support before and around July 14, 2026, what "end of support" actually means for your organization, the risks of inaction, and the migration paths available to you.

Understanding Microsoft's Support Lifecycle

Before diving into the specific products, it helps to understand what Microsoft means by "end of support." Every Microsoft product follows the Microsoft Lifecycle Policy, which typically spans 10 years, divided into two phases:

• Mainstream Support – Includes new features, non-security updates, bug fixes, and technical support.
• Extended Support – Covers only security updates and critical patches. No new features, no design changes, no non-security bug fixes.

When Extended Support ends, Microsoft stops everything: no more security patches, no bug fixes, no technical assistance, and no time-zone updates. Your software will continue to run, but it will be permanently frozen in time as the threat landscape evolves around it.

The Big July 14, 2026, Deadline: Products Hitting End of Support

1.  SQL Server 2016 - End of Support: July 14, 2026

SQL Server 2016 is arguably the most critical product reaching end of life on this date. Launched in 2016, SQL Server 2016 brought major improvements, including Always Encrypted, real-time operational analytics, and Query Store. It became a bedrock database platform for thousands of enterprise applications worldwide.

After a 10-year lifecycle, Microsoft ends extended support for SQL Server 2016 on July 14, 2026. From that date onward:

• No more security patches including for critical vulnerabilities discovered after July 14
• No bug fixes
• No technical support from Microsoft
• No vendor certifications

Why this matters critically: Databases are where sensitive data lives, including customer records, financial transactions, healthcare records, and intellectual property. An unpatched database is a known liability for auditors and cyber insurers. Regulatory frameworks such as PCI-DSS, HIPAA, and GDPR require organizations to run supported, patched software. Continued use of SQL Server 2016 after the deadline creates significant legal exposure.

Migration Options:

• Upgrade on-premises to SQL Server 2019 or SQL Server 2022
• Migrate to the cloud via Azure SQL Database or Azure SQL Managed Instance.
• Purchase Extended Security Updates (ESUs) if available, though this is a temporary bridge, not a solution.

Large-scale database migrations require extensive testing, verification of application compatibility, and potential code modifications, so organizations that haven't started planning should treat this as a five-alarm situation.

2.  SharePoint Server 2016 & SharePoint Server 2019 - End of Support: July 14, 2026

Both SharePoint Server 2016 and SharePoint Server 2019 will reach the end of extended support simultaneously on July 14, 2026. Microsoft will no longer release security updates, cumulative updates, or provide technical support for either version after this date.

• SharePoint Server 2016 entered mainstream support in May 2016 and ended mainstream support in July 2021.
• SharePoint Server 2019, released in October 2018, ended mainstream support in January 2024.

SharePoint is not merely a file repository; it powers intranets, document management workflows, HR portals, legal archives, and business-critical collaboration tools. Leaving it unpatched is a serious risk.

The Security Angle: Threat actors routinely scan the internet for unpatched SharePoint installations. A single unpatched vulnerability could expose corporate documents, HR files, financial data, and legal records. After July 15, 2026, any new vulnerability discovered in SharePoint 2016 or 2019 will remain unpatched forever on those versions.

Critically, unlike Windows Server or SQL Server, Microsoft has NOT announced a paid Extended Security Update (ESU) program for SharePoint 2016 or 2019. There is no fallback option. Organizations must migrate.

Migration Options:

• SharePoint Server Subscription Edition (SE) - Microsoft's evergreen on-premises product, suitable for organizations with data sovereignty or latency constraints. Note: it uses a subscription model, meaning ongoing costs.
• SharePoint Online (Microsoft 365) - The cloud-first path. Offers automatic updates, Microsoft Teams integration, AI-powered features, and elimination of server maintenance overhead. This is Microsoft's recommended path and the catalyst most organizations should embrace.

Compare available SharePoint migration tools here: SharePoint Migration Tools Compared →

3. Project Server 2016 & Project Server 2019 - End of Support: July 14, 2026

Often deployed on top of SharePoint infrastructure, both Project Server 2016 and Project Server 2019 reach the end of support on July 14, 2026. Microsoft will no longer provide security updates, bug fixes, or technical support for these on-premises project management platforms.

Organizations using Project Server for portfolio management, resource planning, and project tracking must act now. The migration path leads to Microsoft Project Online or Microsoft Project as part of Microsoft 365, both of which offer cloud scalability and continuous updates.

Products That Already Crossed the End-of-Support Line: October 14, 2025

While July 14, 2026, is the marquee date, several important Microsoft products have already ended support in the months leading up to it.

4. Exchange Server 2016 & Exchange Server 2019 - End of Support: October 14, 2025

Exchange Server 2016 and Exchange Server 2019 reached the end of support on October 14, 2025 which is already behind us. If your organization is still running either version without a migration plan, you are operating in unsupported, high-risk territory right now.

After October 14, 2025, Microsoft stopped issuing:

• Security fixes for newly discovered vulnerabilities
• Bug fixes affecting server stability
• Time-zone updates
• Technical support

The Microsoft Exchange engineering team communicated this deadline at 12-month, 9-month, 6-month, and 1-month intervals, giving ample warning. The message was clear: migrate or face cascading risk.

Available Paths:

• Exchange Online (Microsoft 365) - The recommended cloud-first option, available as a standalone service or via an Office 365 subscription.
• Exchange Server Subscription Edition (SE) - An evergreen, version-less on-premises product that reached general availability on July 1, 2025. For Exchange 2019 customers, an in-place upgrade to SE is supported. Exchange 2016 customers typically need a side-by-side upgrade.
• Extended Security Updates (ESU) - Microsoft announced a limited one-time, six-month ESU program for Exchange Server 2016/2019 as a short-term lifeline for organizations still completing migrations.

5. Microsoft Office 2016 & Microsoft Office 2019 - End of Support: October 14, 2025

Both Microsoft Office 2016 and Microsoft Office 2019 also reached the end of support on October 14, 2025. This includes widely used applications like:

• Word 2016/2019
• Excel 2016/2019
• PowerPoint 2016/2019
• Outlook 2016 and Outlook 2019
• Access 2016/2019

Organizations still running these Office versions are now using software that will receive no further security updates. The recommended path is migration to Microsoft 365 Apps (formerly Office 365 ProPlus), which receives continuous security and feature updates.

Microsoft 365 Apps on Windows Server 2016: A Special Note

Adding another layer of complexity, support for Microsoft 365 Apps on Windows Server 2016 ended on October 14, 2025. However, Microsoft announced it will continue to provide security updates for Microsoft 365 desktop apps running on Windows Server 2016 for a total of three years, ending October 10, 2028, as a grace period for customers completing migrations. Devices will remain on Version 2602 and receive only security updates until that date.

What About Windows Server 2016?

You may notice Windows Server 2016 is not on the July 14, 2026, list. That's because its extended support end date is January 12, 2027, still critically close, but not part of the July wave. Organizations running Windows Server 2016 should treat the July 2026 deadline as a rehearsal and get migrations fully underway. Windows Server migrations are rarely quick: they require application compatibility checks, hardware assessments, and staged rollouts. January 2027 is closer than it seems.

Available Upgrade Paths:

• Windows Server 2019
• Windows Server 2022
• Windows Server 2025 (the current latest version)
• Azure Virtual Machines or Azure hybrid services for cloud migration

The Real-World Impact of Running Unsupported Software

Let's be direct about what happens when you continue operating on unsupported Microsoft products past their deadlines:

1. Security Exposure

Every vulnerability discovered after the end-of-support date goes permanently unpatched. Attackers actively scan for and exploit known vulnerabilities in end-of-life software. The longer you wait after the deadline, the more exposed your environment becomes.

2. Compliance & Regulatory Failure

Healthcare organizations under HIPAA, financial institutions under PCI-DSS, and businesses operating under GDPR all require the use of supported, actively patched software. Running unsupported software can mean:

• Failed security audits
• Regulatory fines
• Breach liability
• Loss of certifications

3. Insurance Risk

Cyber insurers are increasingly scrutinizing organizations' software currency. Running known end-of-life software can affect your cyber insurance coverage, increase premiums, or invalidate claims in the event of a breach.

4. Operational Degradation

Without cumulative updates, system performance can deteriorate over time. Incremental patches provide stability; once these stop, databases and servers become progressively harder to maintain and troubleshoot without vendor support.

Your Action Plan: What to Do Right Now

If your organization is running any of the affected products, here is a pragmatic roadmap:

Step 1: Inventory Your Environment
‍Run a full audit of every instance of SQL Server 2016, SharePoint 2016/2019, Project Server 2016/2019, Exchange 2016/2019, and Office 2016/2019 in your infrastructure. Include dependencies what applications connect to these servers?

Step 2: Assess Your Risk
‍Prioritize based on data sensitivity and business criticality. A SQL Server holding financial records ranks higher in urgency than a development instance. Classify and triage.‍

Step 3: Choose Your Migration Path
‍Decide between cloud (Microsoft 365, Azure SQL, Exchange Online) and on-premises (newer server versions, Subscription Edition products). Consider your data sovereignty needs, latency requirements, budget, and internal expertise.
Not sure which tool to use for your migration?  
‍See our SharePoint Migration Tools Compared guide to evaluate the top options side by side.

Step 4: Test Before You Migrate
‍Never migrate production workloads without validating compatibility in a staging environment. Application compatibility testing, custom workflow verification, and third-party integration checks are all essential pre-migration steps.

Step 5: Execute in Phases
‍For large organizations, a phased migration is safer than a big-bang cutover. Move non-critical workloads first, validate, then proceed to business-critical systems.

Step 6: Document Everything
‍If leadership decides to accept the risk of temporarily running unsupported software, that decision must be formally documented, with sign-off from appropriate stakeholders and a defined remediation timeline.

Before you start, download the Intranet Migration Best Practices eBook, expert tips from Microsoft MVPs to ensure a smooth, secure SharePoint migration.
‍

‍

An AI-ready intranet is an internal knowledge platform with clean, up-to-date content, accurate permissions, structured metadata, and connected systems. This allows AI search, chat assistants, and RAG-based applications to retrieve reliable answers while respecting access controls and governance policies.

Most enterprise intranets, built over a decade of SharePoint migrations and departmental silos, are not there yet. This guide covers what AI readiness actually means, how to add an AI layer on top of an existing intranet, and a checklist that IT and ops leaders can use to assess their current standing.

Why is this the Need of the Hour?

Consider a common scenario: an employee joins a company and asks, "How many work-from-home days am I allowed per month?" The intranet contains three versions of the policy: one from HR, one from a departmental wiki, and one from a SharePoint site that was never retired after a migration.

An AI assistant retrieves the oldest version because it contains the most keywords in common.

The employee follows the wrong policy; their manager approves it, and HR must later intervene.

It is not an AI issue. The issue was that the organization never decided which document was authoritative.

What "AI-Ready" Actually Means?

An intranet doesn't become AI-ready by installing a chatbot. The chatbot is the visible layer; what makes it trustworthy lies beneath it. In practice, an AI-ready intranet has four properties:

• Content is current and deduplicated, so the AI layer isn't retrieving three contradictory versions of the same policy.
• Permissions are enforced at the data layer, not just the UI layer, so a retrieval system can't surface a document to someone who shouldn't see it.
• Information carries metadata (owner, department, last-reviewed date, sensitivity) that lets an AI system reason about relevance and trust, not just keyword match.
• Systems are connected through APIs or a unified index rather than living in isolated silos that no single search can reach.

None of this requires ripping out the existing intranet. It requires treating the intranet as a knowledge base that a model will consume, and cleaning it up the way you would for any new system of record.

How to Add an AI Layer to Your Intranet?

1. Audit and clean content before anything else. Identify what's authoritative, what's outdated, and what should be archived or deleted. This is unglamorous and is also the single biggest determinant of whether the eventual AI layer is trustworthy.

2. Fix identity and permissions at the data layer. Any retrieval system (commonly known as Retrieval-Augmented Generation, or RAG) needs to inherit existing access controls so it never surfaces a document to someone without permission to view it. This usually means connecting the AI layer to your identity provider and document permissions rather than building a separate access model.

3. Add metadata and structure. Owner, last-reviewed date, department, and confidentiality level allow an AI system to weigh sources rather than treating every document as equally authoritative.

4. Choose the right architecture. For most intranets, RAG over your existing content (rather than fine-tuning a model on internal data) is the right starting point: it's faster to update, easier to audit, and lets you trace any answer back to a source document. Agentic layers, where the AI can take action rather than just answer questions, are a later step once retrieval is reliable.

5. Pilot on a narrow, high-value use case. IT helpdesk FAQs, HR policy questions, or onboarding documentation are common starting points because the content is bounded and the value of getting it right is easy to measure.

6. Govern and monitor continuously. Track what the AI layer is being asked, where it's getting things wrong, and which documents it cites most. This feedback loop is what turns a one-time pilot into a system that improves over time.

7. Scale deliberately. Expand to additional departments and content sources only after the governance and feedback processes from the pilot are working, not before.

The Intranet AI-Readiness Checklist

Content

• Duplicate and outdated documents identified and archived
• Authoritative sources clearly designated.
• Content owners assigned and documented.
• Last-reviewed dates present on key documents

Access and governance

• Permissions audited against the current org structure
• AI retrieval layer inherits existing access controls (not a separate permission model)
• Sensitive categories (legal, HR, financial) are flagged and handled distinctly.
• A named owner for AI governance, not just IT operations

Technical foundation

• Unified or federated index across intranet, wikis, and shared drives
• Metadata schema in place (owner, department, sensitivity, date)
• Retrieval architecture chosen (RAG as the default starting point)
• Source citation built into AI responses so answers are traceable.

Rollout and monitoring

• Pilot scoped to a single, bounded use case.
• Feedback mechanism for flagging wrong or outdated answers
• Usage and accuracy were tracked before the scope was expanded.
• Plan for keeping content fresh as the underlying intranet changes

Rebuilding SharePoint today is like renovating an old house while still living in it. You cannot just tear everything down and start fresh because people are still cooking in the kitchen, working in the rooms, and storing their lives in the cupboards. So instead, you fix the plumbing, improve the lighting, and slowly turn chaos into something not just livable but enjoyable.

That is exactly what is happening with SharePoint in modern workplaces.
At some point in almost every enterprise conversation, someone says, “We should probably replace SharePoint.”
And technically, that sounds appealing. Clean slate. Fresh start. New tools. But in reality, SharePoint is already deeply embedded in how organizations run. It is not just another software that can be replaced easily. It contains decades of documents, approvals, permissions, workflows, and most importantly, user behaviors.

SharePoint is not the problem, user experience is:

SharePoint is powerful. It stores and governs information at scale. The issue is not capability. The issue is user experience.

Employees do not struggle because information does not exist. They struggle because they cannot easily find it, trust it, or know which version is correct.

If someone asks, “Where is the onboarding checklist?” the answer is, “It is somewhere in SharePoint.” It’s like someone asking for directions to a specific place and getting the reply, “It’s somewhere in the city.”

Why replacement rarely works?

Replacing SharePoint sounds simple in theory, but reality is different.

Because organizations are not just replacing a tool. They are replacing:

• Years of content
• Governance and compliance rules
• Embedded workflows
• Deeply ingrained behavior

There is always a moment when a team says, “Our entire process depends on this,” and suddenly the replacement idea becomes less attractive.

How to rebuild SharePoint with an experience layer?

Modern enterprises are not actually trying to throw SharePoint away. They are rebuilding around it.
Instead of users navigating folders and libraries, companies are adding an experience layer that provides:

• Intelligent search
• Contextual answers
• Structured knowledge access
• Task-driven interfaces

This changes everything. Employees stop thinking about where information lives and start focusing on getting work done.

SharePoint becomes the back-end system of record, while the experience layer becomes the front door.
Employees do not want to “use SharePoint.” They want answers:

• What is the latest version?
• What should I do next?
• Who approved this?

One of our clients once summed it up perfectly: “We do not want to understand the folder structure. We just want the file.”

Final thought

Modern workplaces are not replacing SharePoint because the real problem was never SharePoint itself. It was the gap between information and experience.
And the companies that get this right are not tearing the house down. They are renovating it while still living in it, making it quieter, smarter, and finally easier to navigate.

This blog is based on our real-time experience with over 700 clients over the past 10 years.  

Microsoft’s Copilot Cowork is a new AI-powered “co-worker” designed to autonomously plan and execute multi-step tasks across your work apps as a major leap beyond traditional chatbots. Launched in early 2026, Microsoft’s answer to Anthropic’s Claude Cowork (an AI agent introduced just weeks earlier). Copilot Cowork combines Anthropic’s Claude AI technology with Microsoft 365’s ecosystem, creating a digital assistant that works with you inside your day-to-day tools to boost collaboration and creativity. This post explores what Copilot Cowork is, how it compares to Claude Cowork, its key features and use cases, and how it can supercharge productivity for innovation teams.

What is Copilot Cowork?

Copilot Cowork is an AI assistant that you can delegate work to, as if it were a capable team member. You describe the outcome you want, and Cowork generates a step-by-step plan, uses the necessary tools (like Office apps, calendars, email) and data to execute each step, and then presents the outcome.

For example, if you ask it to “prepare next week’s client update presentation,” Copilot Cowork can gather information from your emails and documents, draft slides in PowerPoint, schedule prep meetings on your Outlook calendar, and collate any relevant Excel stats, all while keeping you informed and allowing you to adjust the plan.

This agentic (“autonomous agent”) approach means Copilot Cowork isn’t just answering questions, it’s carrying out tasks on your behalf. It works within the Microsoft 365 cloud environment, drawing on Microsoft’s Work IQ intelligence layer (which aggregates your work data like mails, chats, files, and meetings) to provide rich context.

As a result, Copilot Cowork can do things like prepare a client meeting briefing by cross-referencing your recent email thread with that client, pulling data from a shared spreadsheet, and even blocking time on your calendar for preparation. This depth of integration into your work life is something a standalone AI agent (like a local app) can’t easily replicate.

Notably, Microsoft built Copilot Cowork in close partnership with Anthropic, the AI company behind the Claude model. In fact, the underlying AI brain of Copilot Cowork is Anthropic’s Claude, integrated directly into Microsoft 365 Copilot’s infrastructure. Microsoft opted to collaborate instead of creating a new model from scratch after investing in Anthropic in late 2025, so it could bring Claude’s advanced capabilities into the enterprise setting quickly. Jared Spataro, Microsoft’s AI at Work chief, put it plainly: “What Anthropic has done is demonstrate the value of these agentic capabilities. Microsoft is all about commercialization.” In other words, Anthropic showcased the concept of an AI co-worker, and Microsoft scaled it for business use, leveraging its secure cloud, huge user base, and deep integration in workplace tools.

Key Features and Capabilities

Copilot Cowork introduces a range of powerful features aimed at making knowledge work more efficient and innovative:

• Autonomous Multi-Step Workflows - “Agentic” AI is the core of Cowork. You can delegate complex or repetitive workflows, and it will handle them from start to finish. It breaks your request into sub-tasks, executes them in sequence (or even in parallel when possible), and checks in if it needs guidance^. For instance, if tasked with organizing a project kickoff, Copilot Cowork might create a project plan, draft an agenda in Word, schedule a Teams meeting with invitees, and set up a SharePoint folder for shared files doing in minutes what might take you hours. ‍
• Contextual Intelligence via Work IQ – Because it’s built into Microsoft 365, Copilot Cowork has native access to your work context: your Outlook emails, Teams chats, OneDrive files, calendars, and more. It uses this Work IQ knowledge to make smarter decisions. For example, when drafting a document or email on your behalf, it can pull relevant facts from recent files or conversations. When scheduling or coordinating, it knows your real calendar availability and deadlines. This means the output is highly tailored to your actual work environment and team, which standalone AI tools can’t match. ‍
• Multi-Model Collaboration (Claude + GPT) – Uniquely, Microsoft 365 Copilot (and the Cowork agent) takes advantage of more than one AI model to improve quality. Copilot Cowork can use OpenAI’s GPT for content generation and Anthropic’s Claude to review or refine the results, a feature called “Critique.” In Microsoft’s research agent tests, this two-model approach achieved a 13.8% higher deep-research accuracy score (DRACO benchmark) than a single-model answer. In practice, this means you get more accurate and well-rounded outputs – for example, a detailed analysis report written by GPT might be double-checked by Claude for factual accuracy and completeness before you see it¹. Copilot can even display a Council of multiple model responses side-by-side for comparison, so you get the benefit of diverse AI “opinions” on complex problems. ‍
• Seamless Microsoft 365 Integration – Copilot Cowork works across the apps you use every day. It can create or edit documents in Word, build slides in PowerPoint, analyze data in Excel, extract action items from Teams meeting transcripts, send emails via Outlook, and more, all through the same interface. In a demo, Microsoft showed Cowork automatically compiling a competitive analysis report by pulling information from meeting notes and customer data, outputting a Word doc and a supporting Excel sheet with charts. Because it operates inside the M365 apps, the formatting and file compatibility are taken care of your AI-generated content arrives in the tools you’re already comfortable with. ‍
• Enterprise-Grade Security & Compliance – Designed for corporate environments, Copilot Cowork runs within your organization's secure Microsoft 365 cloud, so it respects all your established permissions, data governance, and auditing rules. Every action the AI takes whether it’s accessing a document or sending an email on your behalf it is logged and auditable by IT. Any files it creates or modifies are stored in your company’s secure cloud, with the usual access controls. This is a critical differentiator from local AI agents: for companies in regulated industries or with strict compliance needs, Copilot Cowork provides the transparency and control required to trust an AI with real work. ‍
• Built-in “Skills” and Tool Integrations – Copilot Cowork comes with specialized capabilities (Microsoft calls them skills) to handle common tasks. For example, it has a calendar management skill to intelligently schedule or rearrange meetings (accounting time zones, availability, etc.), and a daily briefing skill that can summarise your day’s priorities. It can tap into the Microsoft Graph to retrieve contacts or past communications. Over time, Microsoft is likely to add more such skills (and allow custom ones), so the AI can interface with third-party tools or internal systems, further extending what tasks it can automate.

How Copilot Cowork Boosts Productivity and Innovation

For innovation teams and leaders, Copilot Cowork can be a gamechanger. By offloading routine and multi-step chores to the AI, teams can spend more time on creative, high-value work. Here are a few ways Copilot Cowork enhances productivity in collaborative and creative environments:

• Accelerating Project Workflows: Tedious project tasks like gathering status updates, scheduling meetings, or assembling reports can be handed to Copilot Cowork. For example, an innovation lead could ask, “Summarize this quarter’s R&D experiment results and prepare a slide deck with key findings.” Copilot Cowork will fetch data from the related documents and emails, generate a summary report, and draft slides complete with charts in PowerPoint. The team can then focus on refining strategy and brainstorming ideas, rather than crunching numbers and copy-pasting info. ‍
• Enhanced Meeting Preparation: In collaborative work, a lot of time goes into meeting prep and follow-ups. Copilot Cowork shines here by digging through your organisational knowledge to prepare you for meetings. If you have a brainstorm scheduled, you can instruct Cowork: “Gather all recent customer feedback and product improvement ideas from our team chats and create a brief for the meeting.” It will scan your Teams channels and emails for relevant input and present a concise brief. After the meeting, you could ask it to compile action items and even draft follow-up emails. By doing heavy lifting, the AI frees everyone to concentrate on the creative discussion during the meeting, rather than on note-taking or clerical work. ‍
• Continuous Planning and Coordination: Copilot Cowork can serve as an ever-ready project coordinator. For instance, innovation teams often run recurring processes (like monthly innovation reviews or budget planning cycles). Cowork can automate these repeatable workflows for a “monthly innovation portfolio review,” it could automatically pull the latest metrics from Excel, draft an updated report, and send calendar invites for review meetings every month. It ensures nothing falls through the cracks, and that processes run on schedule, with minimal manual effort. ‍
• Cross-functional Collaboration: Because it operates with an awareness of shared files, team calendars, and group chats, Copilot Cowork can help connect dots between different team members’ work. Suppose the design team, engineering team, and marketing team are all working on a new product launch. Copilot Cowork can aggregate insights from each team’s files and chats to generate a combined update or to identify inconsistencies and information gaps in the plan. This not only saves time in chasing information but can also reveal insights that spark new ideas (for example, spotting a recurring customer concern in supporting tickets and bringing it to the product team’s attention). ‍
• Example Early Adopter Success: One early adopter, Capital Group, reported significant benefits from Copilot Cowork. Their teams used it for planning, scheduling, creating deliverables, and preparing executive reviews, all within their secure Microsoft 365 environment. Barton Warner, SVP of Enterprise Tech at Capital Group, highlighted that Cowork isn’t just about generating text, “it’s about taking real action connecting steps, coordinating tasks, and following through across everyday workflows.” Equally important, he noted that because the AI works on their enterprise data within established security boundaries, they can “experiment, learn, and scale with confidence,” focusing on where AI truly adds value. In short, Copilot Cowork let their people move faster on innovation projects by handling the busy work reliably in the background.

Copilot Cowork vs. Anthropic Claude Cowork

Microsoft’s Copilot Cowork emerged very shortly after Anthropic’s Claude Cowork, and at first glance these two “AI coworkers” sound similar – both use Anthropic’s Claude model and both can execute multi-step tasks. However, they are built for different contexts and users. Here’s how they compare:

• Origins and Approach: Anthropic was first to debut the AI co-worker concept with Claude Cowork in January 2026, as a standalone desktop agent. It amazed many by showing an AI could perform lengthy, tool-using tasks on a PC. Microsoft’s response in March 2026 was not to compete directly, but to partner with Anthropic. Microsoft integrated the Claude cowork technology into its own Copilot product, essentially wrapping Claude’s capabilities inside the Microsoft 365 cloud environment. So under the hood, both tools leverage the same AI engine (Claude) for reasoning, but Microsoft adds its multi-model orchestration and enterprise integration on top. ‍
• Integration and Environment: Claude Cowork runs locally on your device. This means it can, in theory, work across any application you have, giving it a lot of flexibility for individual power users. You don’t need Microsoft 365 at all, it’s an independent app. However, running locally also means it lacks built-in access to cloud-based organizational data. It can’t natively tap into a company like SharePoint or your team’s Exchange calendar because it operates outside that cloud ecosystem. Copilot Cowork, by contrast, lives inside Microsoft 365’s cloud. It’s deeply integrated with Office apps and leverages your company data (with permission) emails, SharePoint files, Teams channels, calendars via Work IQ. This makes it extremely powerful for enterprise use, because it operates with full awareness of your organizational context (something a local agent can’t achieve). ‍
• Collaboration and Use Cases: Both tools can handle similar categories of tasks for example, calendar management, drafting documents, doing competitive research, preparing meeting summaries, and coordinating multi-document workflows. The big difference is who they serve. Claude Cowork is tailored more to individuals (developers, researchers, or small teams) who want an AI helper on their personal machine without corporate strings attached. It’s great if you’re a solo operator or a startup techie who needs an AI to automate tasks across various local apps (maybe coding, web research, file operations) and you don’t need it to know about an enterprise network. Copilot Cowork is built for enterprise teams already using Microsoft 365. Its sweet spot is in scenarios where multiple colleagues, shared cloud data, and organizational processes are involved exactly where having that enterprise context “pulls ahead for enterprise users”. For example, coordinating a cross-department project or generating a brief that draws on company-wide information is where Copilot Cowork excels, whereas Claude Cowork in those cases would be limited by only local data. ‍
• Security and Governance: Because Claude Cowork runs locally, it inherently has limited oversight or governance there’s no automatic record of what it accessed on your machine or what it did, which might be acceptable for personal use but is a red flag in big organizations. In fact, any sensitive data it handles isn’t centrally tracked. Copilot Cowork, on the other hand, is cloud-based and auditable by default: all actions it takes in your Microsoft 365 tenant can be logged and reviewed. It adheres to your organization’s identity and access controls (only accessing data you’re allowed to) and keeps administrators in the loop. Microsoft even introduced a tool called Microsoft Agent 365 (available as an add-on) that lets IT monitor and manage AI agent activities across the company, set up policies, and catch any risky behavior. None of that structure exists for a local agent like Claude Cowork. For a CISO or compliance officer, this governance is often non-negotiable in enterprise settings. ‍
• Availability and Licensing: Claude Cowork is available through Anthropic’s platform, typically as part of their Claude AI service subscription (with usage-based pricing). It can be used by anyone who signs up, without needing corporate approval. Copilot Cowork is offered to businesses; it requires a Microsoft 365 E5 subscription or the new E7 “Frontier” Suite (an even higher-tier package launching in 2026 that bundles all the AI goodies). In other words, an individual can’t just download Copilot Cowork an organization needs to enable it for their users. It’s currently in early access (via the Frontier programmer) as of March 2026, with broader rollout expected soon.

Below is a side-by-side comparison of Microsoft Copilot Cowork vs. Anthropic Claude Cowork in terms of features, integrations, and use cases:

A New Era of AI-Assisted Work

In summary, Copilot Cowork represents a new era of AI in the workplace moving from passively assisting with information to actively collaborating on real projects and tasks.

It’s like having a super-skilled assistant who can work at digital speed, attending meetings, reading documents, and producing drafts in parallel, all orchestrated under your guidance.

For innovation leads and forward-thinking teams, this means more time to innovate: the AI takes care of preparation and execution, while humans focus on creativity, strategy, and fine-tuning the results.

Meanwhile, Anthropic’s Claude Cowork shows another side of this evolution: a more open-ended AI agent for individual use, demonstrating what’s possible when an AI can control a computer like a human assistant would. Microsoft’s approach, however, is to bring that power into the everyday tools of business in a governed, scalable way.

By teaming up with Anthropic, Microsoft essentially turned a cutting-edge concept into a product that companies can deploy with confidence.

Conclusion

In a world where innovation and speed are paramount, tools like Copilot Cowork offer a significant edge. By handling the busywork researching, compiling, organizing, cross-checking, this AI frees human teams to concentrate on creative problem-solving and big-picture thinking. At the same time, its integration into the Microsoft 365 suite means it works where you work, securely and contextually, rather than being a disconnected novelty.

For organizations already invested in Microsoft’s ecosystem, Copilot Cowork can amplify productivity across departments. Imagine product managers, engineers, and designers all benefitting from an AI that coordinates their inputs and keeps the project in sync, or an innovation lab where ideas progress faster because the AI continuously gathers insights and takes care of follow-ups.

As AI coworkers become more common, we’re likely to see heightened collaboration between humans and AI. Microsoft Copilot Cowork and Anthropic Claude Cowork are early exemplars of this trend, one optimized for the enterprise, the other for individual power users. Both underline a shift from AI as a tool you consult, to AI as a partner that actively participates in the work.

For innovation leads, that means an exciting opportunity to reimagine workflows: routine tasks can be offloaded, and human talent can be re-focused on innovation itself. In essence, Copilot Cowork lets your team spend less time juggling tasks and more time driving innovation forward.

Quick Answer

To brand your SharePoint intranet, apply your company's primary colors to the site theme using SharePoint's Change the Look settings, upload your logo to the header, and select a consistent font pairing across all pages. The goal is to make the intranet feel like an extension of your corporate website not a generic Microsoft template. Done right, branded intranets see up to 40% higher daily adoption rates than unbranded ones.

Your employees open the intranet and the first thing they see is a grey Microsoft template with the default blue header and a placeholder logo. Within three seconds, they've already decided this isn't worth their time.

This is the branding problem that affects most SharePoint intranets and it's entirely fixable.

Branding your SharePoint intranet isn't about aesthetics for aesthetics' sake. It's about trust, recognition, and adoption. When your intranet looks and feels like your company, your colors, your logo, your voice employees stop seeing it as an IT tool and start seeing it as a company resource worth using every day.

At SharePoint Designs, we've branded over 800+ SharePoint intranets for organizations including Harvard University, Vanderbilt University, and multiple Fortune 500 companies. This guide distils everything we've learned into a step-by-step framework you can apply to your own intranet today.

Why does SharePoint Intranet Branding Matter?

An unbranded intranet sends an unintentional message to employees: this wasn't built for you. It looks like an afterthought. Employees who land on a generic SharePoint site with the default Microsoft theme are significantly less likely to return, less likely to search for content, and less likely to trust the information they find there.

The data backs this up. In our work across 800+ intranet deployments, we consistently find that branded intranets those using company colors, fonts, and logo prominently achieve measurably higher adoption within the first 90 days of launch compared to unbranded equivalents with the same content.

What does good Intranet Branding actually achieve?

• It builds immediate recognition. Employees shouldn't need to read the URL to know they're on the company intranet. The visual identity should communicate that within one second of the page loading.

• ‍It signals that this is a permanent, invested resource. A polished, branded intranet tells employees that leadership cares about this tool. That perception alone increases usage.

• ‍It reduces cognitive friction. When the intranet matches the visual language employees already associate with your brand, they navigate it more instinctively. Familiar colors and typography reduce the mental effort required to use the tool.

• It supports employer branding. For new hires especially, the intranet is often the first internal digital touchpoint after onboarding. A well-branded intranet reinforces the professionalism and culture they were sold during recruitment.

What are the Core Elements of SharePoint Intranet Branding?

There are four core branding elements to get right on a SharePoint intranet:

1. Color palette - Your primary, secondary, and accent colors applied to headers, buttons, section backgrounds, and navigation

2. Typography - Font choices for headings, body text, and UI elements

3. Logo placement - Where your logo sits, at what size, and on which pages

4. Visual language - Photography style, illustration style, icon sets, and graphic elements that feel consistent with your corporate identity

Each of these works together. Getting the colors right but leaving the default SharePoint font makes the intranet feel 70% branded. Getting all four right makes it feel completely native to your company.
You may also like: Typography Trends

Part 1: How to Choose the Right Colors for your SharePoint Intranet

SharePoint Online uses a theming system called Change the Look that lets you apply custom colors to your intranet without any coding. Here's how it works in practice.

Step 1 - Identify your brand color values

Before touching SharePoint, collect your official brand color hex codes from your brand guidelines or marketing team. You'll need:

• Primary color - your main brand color (e.g. #0052CC for a corporate blue) ‍
• Secondary color - a supporting color used for accents or secondary elements ‍
• Neutral colors - your greys, whites, and off-whites for backgrounds and text

If your brand guidelines only specify Pantone or CMYK values, convert them to hex using a color converter tool before proceeding.

Step 2 - Access Change the Look

From your SharePoint home site, click the gear icon (Settings) in the top right → Change the look → Theme. You'll see a palette of Microsoft's pre-built themes. Ignore these you're going to create a custom one.

Step 3 - Apply your primary color

Click Custom at the bottom of the theme panel. You'll see a color picker where you can enter your hex code directly. Enter your primary brand color as the "Theme color."

SharePoint automatically generates a color ramp from your primary color lighter and darker variations used across different UI elements. Review this ramp carefully. Sometimes the auto-generated variations clash or become inaccessible  if so, adjust manually.

Step 4 - Check color accessibility

This is a step most organizations skip and later regret. Every color combination on your intranet needs to meet WCAG 2.1 AA accessibility standards specifically a minimum contrast ratio of 4.5:1 for body text and 3:1 for large text and UI components.

Use the WebAIM Contrast Checker to test your primary color against white and against your neutral backgrounds. If you're a public sector organization or in a regulated industry, you may need to meet the stricter AAA standard.

What colors work best for SharePoint intranets?

The best performing intranet color palettes we've seen across our 300+ projects share a few characteristics:

• Use your primary brand color for the header and navigation only. Applying it everywhere dilutes its impact and makes the intranet feel visually noisy. The header and navigation are high-visibility areas strong brand colour here is immediately z without being overwhelming.

• ‍Use neutral backgrounds (white or light grey) for content areas. Dark or heavily coloured page backgrounds make long-form content harder to read and reduce dwell time. White and off-white backgrounds consistently outperform colored ones for readability metrics.

• Reserve your accent color for calls to action. Buttons, links, and key navigation elements should use your accent color consistently. This creates a clear visual hierarchy that guides employees to take actions submit a form, find a document, read an announcement.

• Avoid pure black (#000000) for body text. Use a very dark grey instead (e.g. #1a1a1a or #111827). Pure black on white creates a harsh contrast that causes eye strain during long reading sessions. Most corporate brand guidelines already specify this.

Part 2: How to Choose and Apply Fonts to your SharePoint Intranet

SharePoint Online supports web-safe fonts natively and also support web fonts through custom CSS injection for organizations with developer access. However, for most intranet projects, working with SharePoint's available font options is both faster and more maintainable.

The available fonts in SharePoint's native theme settings include Segoe UI (Microsoft's default), Arial, Calibri, Georgia, Tahoma, Times New Roman, Trebuchet MS, and Verdana.

If your brand specifies a custom font that isn't in this list (for example, Gilroy, Proxima Nova, or a bespoke typeface), you have two options:

1. Inject a Google Fonts or Adobe Fonts web font via a custom SPFx web part requires developer involvement but gives full control

2. Choose the closest available system font that matches your brand's personality faster and simpler, suitable for most intranet projects

What font pairing works best for SharePoint intranets?

The most reliable and accessible font approach for SharePoint intranets is a two-font system:

• Heading font - bolder, slightly larger, used for H1, H2, H3 page titles and section headings
• ‍Body font - clean, neutral, used for paragraph text, labels, and navigation items

The classic combination that works well across virtually every corporate intranet is Segoe UI for headings (it's Microsoft's own typeface optimized for screen readability) and Segoe UI for body text at a lighter weight. Simple, cohesive, and consistently legible across devices.

If your brand requires more personality, a safe alternative is Georgia for headings (adds warmth and editorial quality) with Arial for body text (neutral and universally accessible).

What font sizes should you use?

Consistent typographic hierarchy makes a SharePoint intranet dramatically easier to scan. Use these as a baseline:

‍

Avoid going below 14px for any text employees need to read regularly. Small text on SharePoint's responsive grid can render even smaller on certain screen resolutions, making it inaccessible on some devices.

Part 3: How to Add and Position your Logo on SharePoint

The logo should appear in two locations at minimum on a well-branded SharePoint intranet:

1. The global navigation header - 0 top left of every page, visible on all sites and sub-sites within your intranet. This is the primary logo placement and the most important.

2. The home page hero section - either within the hero web part or as a standalone image element on the homepage. This reinforces the brand identity on the page employees see most frequently.

How do you add your logo to the SharePoint header?

Step 1 - Prepare your logo file

Your logo needs to be in PNG format with a transparent background. SVG is not supported in all SharePoint contexts. Recommended dimensions: 200px wide × 50px tall at 2x resolution (so upload at 400px × 100px for retina screens). Ensure the logo is legible against your header background color, test both light and dark backgrounds.

Step 2 - Go to Change the Look → Header

Settings gear → Change the Look → Header.
Here you can upload a custom logo image directly.

Step 3 - Upload and position

Click the logo upload area and select your PNG file. SharePoint will position it in the top left of the global header automatically. You can adjust the header layout between Compact, Standard, and Minimal. Standard is the most widely used for branded intranets as it gives the logo adequate breathing space.

Step 4 - Set the site name

Decide whether to show the site name text alongside the logo or suppress it. If your logo is a full wordmark (logo + company name), suppress the text to avoid duplication. If your logo is an icon or symbol only, keep the site name text visible.

What are common logo mistakes on SharePoint intranets?

• Using a logo with a white background instead of transparent. This creates a white box around your logo sitting on a colored header one of the most common and most visible branding errors we see. Always use a PNG with transparent background.

• Uploading a logo that's too small. SharePoint compresses uploaded images. If you upload a small logo, the compression makes it blurry. Always upload at 2x the intended display size.

• Using a dark logo on a dark header. Check contrast carefully. A dark navy logo on a dark teal header background disappears. Either lighten the logo version or choose a header background that provides sufficient contrast.

Part 4: How do you make the whole intranet feel visually consistent?

Applying colors, fonts, and a logo is the foundation but visual consistency across a multi-site intranet requires additional discipline. Here's what the best-branded intranets we've built share:

• Standardized page templates. Create saved page templates in SharePoint for the most common page types news article, department hub, policy document, event listing. Each template has pre-set section layouts, background colors, and web part placements that reflect your brand guidelines. This means whoever creates a new page, the output is always on-brand.

• A defined image style. Decide whether your intranet uses photography (real people, real offices), illustration, or icons and stick to it. Mixed visual styles are one of the most common causes of an intranet looking "off" even when the colors and fonts are correct. A branded photo library shared internally gives content authors the right assets to pull from.

• Consistent icon sets. SharePoint's default icons are functional but generic. Replacing them with a consistent icon set that matches your brand's visual style whether that's outlined, filled, or illustrated significantly elevates the overall feel. Microsoft's Fluent UI icon library is free, comprehensive, and designed to work within the Microsoft 365 environment.

• Section backgrounds used intentionally. SharePoint lets you set background colors on individual page sections. Used well, this creates visual rhythm and hierarchy alternating a white section with a light brand-color section breaks up long pages and draws attention to key content areas. Used poorly (random colours with no logic), it makes pages look chaotic.

You may also like: 10 UX Pitfalls that make your employees hate your Intranet

Part 5: What are the most common branding mistakes on SharePoint intranets?

Across 800+ intranet projects, these are the mistakes we see most frequently:

Applying brand colors everywhere. Covering every section, button, and background in your primary brand color doesn't make the intranet look more branded it makes it look exhausting. Brand colour should be used at strategic points to create impact. White space is your ally.

• Ignoring mobile. Over 30% of intranet visits now happen on mobile devices. SharePoint's responsive design means your intranet will reflow for mobile automatically, but your branding elements won't always translate perfectly. Test your logo size, navigation, and hero sections on a phone before launch.

• Inconsistent department pages. A beautifully branded homepage loses credibility the moment an employee clicks through to a department page that looks completely different. Brand governance who can change what and how needs to be established before launch and enforced afterwards.

• Not updating branding after a rebrand. When a company rebrands, the intranet is frequently the last digital property to be updated. This means employees are working in an intranet that contradicts the new brand identity they're seeing everywhere else. Build a branding update checklist into your intranet governance plan from day one.

• Using the wrong SharePoint theme scope. SharePoint has site-level themes and hub-level themes. If you apply branding only at site level, sub-sites and associated sites won't inherit it. Apply your theme at hub site level so it cascades consistently across the entire intranet.

Your SharePoint Intranet Branding Checklist

Before launching a branded SharePoint intranet, run through this checklist:

• Brand color hex codes collected from official brand guidelines

• Color accessibility tested (minimum 4.5:1 contrast ratio)

• Custom theme applied at hub site level

• Logo uploaded in PNG format with transparent background at 2x resolution

• Logo tested against header color for contrast

• Site name text shown or suppressed (consistent decision)

• Font hierarchy defined for H1, H2, H3, body, and navigation

• Page templates created for each major content type

• Image style guide defined and photo library shared

• Icon set selected and consistently applied

• Section background colors used with a clear logic

• Mobile view tested on iOS and Android

• Department pages and sub-sites checked for brand consistency

• Branding governance policy documented

‍Overview

Fluent UI’s CommandBar is a powerful component for building toolbars with built-in support for responsive layouts and overflow handling. Under normal circumstances, when available horizontal space is insufficient, excess command items should automatically move into the overflow menu (represented by the three-dot icon).

However, in real-world applications, especially those with dynamic data or responsive layouts, developers may encounter a common issue:

CommandBar items extend outside the container instead of moving into the overflow menu.

This article explains why this behavior occurs and presents a reliable solution to ensure proper overflow handling.

The Problem

The issue typically appears when:

• CommandBar items are updated dynamically.
• Items are conditionally added or removed (filters, permissions, feature flags)
• The container is resized after initial render.
• The layout changes due to responsive design.

In these scenarios, the CommandBar may fail to move excess items into the overflow menu, causing buttons to spill outside the container and break the layout.

Root Cause

Internally, Fluent UI’s CommandBar performs width and layout calculations only during its initial render cycle.

These calculations determine:

• Available container width
• Visible command items
• Overflowed items

When the items array changes after the initial render, the component does not automatically re-evaluate its layout. As a result, newly added or resized items are rendered without proper overflow recalculation.

The Solution

To resolve this issue, we need to explicitly force the CommandBar to recalculate its layout.

This can be achieved through two coordinated steps:

• Force a remount of the CommandBar using a dynamic key
• Trigger a resize event to ensure layout recalculation.

This approach ensures Fluent UI re-measures the available space and correctly moves excess items into the overflow menu.

Implementation

1. Use a Dynamic key on the CommandBar

<CommandBar   

key={`commandbar-filter-${commandBarKey}`}   

overflowButtonProps={{ ariaLabel: "More items" }}   

items={items}   

buttonAs={CustomButton}   

className={styles.commandBarContainer}

/>  

Changing the key value forces React to unmount and remount the component, triggering Fluent UI’s internal layout logic.

2. Update the Key When Items Change

useEffect(() => {   

if (items.length > 0) {     

const timer = setTimeout(() => {     

setCommandBarKey(prev => prev + 1);        

// Trigger layout recalculation       

window.dispatchEvent(new Event("resize"));     }, 100);      

return () => clearTimeout(timer);   

}

}, [items.length]);  

Why This Works

• Updating the key forces a full component remount
• Remounting triggers Fluent UI’s width and overflow calculations.
• Dispatching a resize event ensures recalculation in responsive layouts.
• Overflow items are correctly moved to the three-dot menu.
• This approach provides consistent and predictable behavior even when CommandBar items are dynamic.

When to Apply This Fix

• This solution is recommended when:
• CommandBar items are dynamically generated.
• UI changes depend on user interaction or filters.
• The CommandBar is placed inside a responsive or resizable container.
• Overflow behavior is inconsistent or broken.

Conclusion

The Fluent UI CommandBar does not automatically recalculate overflow when its items change after initial render. While this is a known limitation, it can be addressed effectively by forcing a controlled remount using a dynamic key and triggering a resize event.

Until native support for automatic recalculation is introduced, this approach remains the most reliable and production-safe solution for handling dynamic CommandBar layouts.

What is the Best Intranet for Healthcare in 2026?

The best intranet for healthcare in 2026 is Microsoft SharePoint, properly implemented by a specialist partner. Key differentiators include HIPAA security, granular role-based access, seamless EHR integration, and a customized, branded employee experience, all provided without extra vendor licenses for organizations already on Microsoft 365.

Platforms like Simpplr, Staffbase, and Unily target healthcare but can't replace your Microsoft 365 subscription. SharePoint delivers those features with stronger compliance, direct integration with Teams, Outlook, and Power Platform, and workflows customized to your environment.

Healthcare IT leaders: If you use Microsoft 365, you already have the top healthcare intranet platform. You need expert implementation, not another vendor.

Quick Comparison: Intranet Platforms for Healthcare

Why Healthcare Intranets Are Different From Every Other Industry

Healthcare organizations face intranet challenges that no other vertical deals with at the same scale.

The U.S. expects a shortage of over 500,000 registered nurses by 2033. Most clinical staff are rarely at desks and must be reached quickly. Intranets that require desktop logins during long shifts are ignored. Only mobile-first platforms succeed in healthcare.

HIPAA and ePHI compliance is non-negotiable. A data breach in a corporate intranet is a PR problem. A healthcare intranet breach involving protected health information (PHI) triggers mandatory federal breach notification and fines up to $1.9 million per violation category. Your intranet must be architected for compliance from day one, not retrofitted after launch.

Shift-based communication creates dangerous information gaps. A policy update published at 9am reaches the day shift. Night shift nurses starting at 7pm may not see it for 16 hours unless the intranet actively surfaces it on login. Healthcare intranets must handle time-sensitive, shift-aware communication. According to the American Hospital Association, hospitals with more engaged staff deliver measurably safer care and better patient outcomes, linking intranet effectiveness directly to clinical quality.

Multiple departments with radically different needs. Doctors need fast access to clinical protocols and prescription portals. Nurses need shift reports and care plans. HR needs policy management and onboarding workflows. Administrators need real-time operational dashboards. A single homepage layout fails all of them.

Regulatory documentation requires a lifecycle, not just storage. Clinical SOPs, formularies, infection control guidelines, and accreditation documents must be versioned, approved, and retired on a documented schedule. SharePoint handles this natively. A communication-first platform does not.

The Core Problem: Most Healthcare Intranets Are Built Wrong

Across 100+ intranet deployments in hospital networks, multi-site health systems, clinics, and aged care providers, the same failure pattern appears consistently:

The intranet launches as a communication portal. It has a news section, a document library, and quick links. After 6 months, usage drops. Staff returns to email, WhatsApp, and printed handouts. Leadership asks why adoption failed.

The reason is structural, not technical. An intranet not built around the actual daily workflow of each clinical role will fail. The right approach starts with one question: what does each role need to complete their job in the first 10 minutes of their shift?

• A floor nurse clocking in needs today’s patient census, active alerts, shift handover notes, and emergency protocols
• A ward administrator needs to review pending approvals, staff scheduling updates, and HR announcements.
• A department head needs the status of compliance documentation, team performance data, and departmental news.
• A new staff member needs onboarding tasks, a training calendar, and their manager’s contact information.

When those answers drive design, adoption follows because the intranet is useful, not just available.

What a Healthcare SharePoint Intranet Looks Like in Practice

SharePoint Designs has built healthcare intranets across seven distinct design approaches, each tailored to different clinical environments, organizational cultures, and branding requirements. All seven run on the same SharePoint foundation.

Design 1 - Clinic Hub: Acute Care & Multi-Department Hospitals

Built for acute care hospitals and multi-department clinical environments. The homepage centers on role-specific quick access: Emergency Procedures, Patient Safety Guidelines, and Shift Schedules are pinned in the hero section.

Health Updates are filterable by service line: Stroke Center, Behavioral Health, Emergency Services, and Heart Health. A right-side panel separates doctor tools (Patient Records, Prescription Portal) from nurse tools (Shift Reports, Care Plans) and administrative tools (Analytics Dashboard, Staff Management).

A Daily Rounds widget surfaces live operational metrics: Active Patients, Staff on Duty, Emergency Cases, and Bed Occupancy. This is the most operations-dense design, suited to high-acuity hospital environments.

Design 2 - Vision: Large Health Networks (500+ Staff)

Built for multi-location health systems where leadership communication and cultural alignment are priorities. The full-width hero banner carries personalized daily briefing and leadership vision messaging. A service line navigation row lets each department (HR & Payment, Finance, Payroll, Health Care) operate as its own subsite while remaining connected to the central hub.

The Meet the Team and Memorable Moments sections drive connection across distributed sites. Birthdays & Anniversaries and Staff Training, with direct Outlook calendar integration, are consistently among the highest-used features after launch  because they make the platform feel human, not institutional.

Design 3 - Women’s Health & Specialty Clinics

Built for specialty healthcare providers: OB/GYN practices, fertility clinics, maternity hospitals, and women’s health centers. The design language (purple palette, specialty-specific department filters: Obstetrics, Gynecology, Fertility IVF, Maternity Care) signals immediately that this was designed for this organization.

The People Directory includes an org chart filterable by specialty. The calendar surfaces relevant appointments (Prenatal Checkup, Ultrasound Scan) with direct Outlook integration. Service Awards recognize long-tenure staff as a meaningful driver of retention in specialist clinical environments.

Design 4 - Compassionate Care: Community & Family Health

Built for community health centers, family medicine practices, and organizations where patient-centered culture is central to the brand. Quick Links segment by role: Finance & Operations, Mission & Partners, HR & Employees, Communications, Data & Status.

The News section supports filtered views for Company, Covid-19, and Treatments content. Documents are surfaced on the homepage with direct download links; clinical staff never navigate a document library.

The warm hero imagery and Birthdays section reinforce a community feel, which better drives adoption in smaller clinical environments than any feature set.

Design 5 - Research & Pharma: Science-Led Healthcare

Built for pharmaceutical companies, research hospitals, and clinical research organizations. The homepage leads with a CEO Corner video section and lab-focused hero imagery.

Quick Links structure research workflows: Employee Handbook, Tutorials and Guides, Help and Support, Departments, Health and Wellness. A live weather widget supports staff traveling between campuses.

New Employees are highlighted to improve onboarding visibility in organizations with higher researcher turnover. The Quote of the Day section reinforces culture in a format that resonates with research-oriented teams.

Design 6 - Enterprise Hospital Network

The most feature-complete design for large enterprise hospital systems. The personalized hero greeting with vision statement carousel creates immediate personal relevance.

Below it: an Announcements scroller for urgent all-staff communications, Quick Links divided across clinical and operational categories, a My Apps section surfacing role-specific tools (Call Center Web, Front Desk, Payroll, XM Fax, Duo Central), New Joiners, Birthdays & Anniversaries, Testimonials, Company Directory, Calendar, and Events all on a single scrollable homepage.

The Testimonials carousel lets staff share organizational moments, a proven driver of cultural engagement in large, distributed hospital networks.

Design 7 - Mental Health & Behavioral Services

Built for mental health organizations, behavioral health services, and wellbeing-focused healthcare providers. The calm color palette (coral, teal, white) is deliberate, as clinical staff in this sector respond differently to high-intensity blue corporate designs.

Navigation reflects the specific needs of behavioral health: Administration, Locations, Finance, Legal, Clients, Training, Safety, and Library. A full-width mental health awareness banner at the bottom normalizes the organization’s focus on staff and patient wellbeing.

The Calendar and Upcoming Events sections are prominent because scheduling is operationally central to behavioral health service delivery.

‍

SharePoint is moving beyond libraries, folders, and permissions. Microsoft is building an intelligent content platform where AI agents handle documents, letting you focus on meaningful work. Here’s what IT leaders and intranet owners must know for 2025-2026.

The Copilot Era Isn't Coming. It's Already Here.

Let's start with the biggest shift. Microsoft 365 Copilot, now an AI-powered assistant across Word, Excel, PowerPoint, Teams, and SharePoint, has moved from blog post previews to full production. But 2025's story isn't about Copilot itself. It's about what happens when Copilot gets specialized.

Copilot Agents (Agent 365)

Think of these as dedicated AI employees for each SharePoint site. A legal site might have an agent trained on contract templates and regulatory filings. An HR portal could have one that answers benefits questions using your company's actual policy documents. These are not generic chatbots. They are site-specific AI assistants that understand your content.

Agentic Workflows

This is where automation becomes autonomy. An agentic workflow (an automated process managed by AI systems rather than just following preset steps) does more than move a document from folder A to folder B when you click "Approve." It reads the document, finds which approval chain is required, routes it, follows up with stalled approvers, and escalates when deadlines pass. The human stays in the loop but no longer deals with the plumbing.

Key distinction: Traditional Power Automate flows (Microsoft’s service for automating repetitive tasks) follow rigid IF-THEN rules. Agentic workflows use AI reasoning (artificial intelligence logic that can adapt to exceptions) to handle edge cases that would have previously required a human to intervene.

Work IQ and Semantic Search

Work IQ is Microsoft's name for the contextual intelligence layer across your entire M365 tenant. It knows which files you've worked on, which meetings discussed a topic, and which emails are project-related, even if nobody tagged them properly.

The result is semantic search. Instead of searching for "Q3-budget-final-v2-REVISED.xlsx," you search for "the budget spreadsheet Sarah shared after the board meeting." The system understands your intent, matches it to your activity graph, and surfaces the right file. This saves knowledge workers hours each week. It reduces the time spent finding things to 20%.

AI Meeting Summaries

Teams meetings now generate structured summaries. These are not just transcripts, but distilled outputs: decisions made, action items assigned, and questions left open. Summaries are automatically stored as team SharePoint documents, creating a searchable decision log that did not exist before.

SharePoint Premium: Your Documents Learn to Read Themselves

SharePoint Premium (formerly Syntex) is Microsoft's answer to a common problem. Every organization has mountains of unstructured content that no one can find, classify, or govern at scale. The 2025–2026 updates push SharePoint Premium from an "interesting add-on" to strategic infrastructure.

Content Assembly

Imagine you have a SharePoint list with 200 rows of client data. Content Assembly lets you create a Word or PDF template, such as a consulting agreement. You can auto-generate 200 personalized documents in minutes. No mail merge and no manual copy-paste. The templates are modern, using structured content controls rather than legacy fields. The output is clean, branded, and ready to send.

For any organization that generates contracts, proposals, or compliance reports at volume, this capability alone justifies the Premium license.

Taxonomy Tagging

Here's the dirty truth about metadata: everyone agrees it is important. Nobody wants to do it manually. SharePoint Premium solves this with AI-driven auto-tagging. Upload a document, and the system reads it and matches its content to your organization's term store. It automatically applies the right tags.

The accuracy is not perfect on day one, but the model improves as it processes more content. The real value is consistency. Instead of 50 people tagging documents 50 different ways (or not tagging them at all), you get a single, enforced taxonomy across the organization.

Why does this matter for intranets :Taxonomy tagging is the foundation for metadata-driven navigation. Without clean, consistent tags, your smart intranet filters are just empty dropdowns. With good tags, employees find what they need in seconds.

Unstructured Document Processing and OCR

Not every document in your company follows a neat template. Letters, internal memos, invoices, and scanned certificates are messy files that traditional DMS platforms struggle with. SharePoint Premium's AI models read these documents, extract key metadata (like dates, names, amounts, and categories), and index them for search.

OCR is now built into SharePoint libraries. Scanned PDFs and photos of documents become fully searchable text without any third-party tool. For legal, healthcare, or government fields, where paper-to-digital conversion is a constant headache, this is a genuine game-changer.

Smart PDF Tools

This feature is simple but extremely useful. SharePoint and OneDrive now have native PDF operations: merge PDFs, extract pages, add annotations, and apply watermarks. You no longer need to download, open in Adobe, edit, and re-upload. It happens in place, in the browser, with version history kept intact.

Forget Files. The Future Is Living Objects.

The biggest shift in Microsoft 365 is not about a single feature. It's a new way to think about content. Files are static; you create them, save them, and share them, then hope everyone's looking at the right version. Living objects are different.

Loop Components

A Loop component is a piece of content, such as a table, a task list, or a status tracker, that exists independently of any single app. Drop it into a Teams message, and your colleague can edit it there. Paste the same component in an Outlook email; it stays synced. Update it in one place, and it updates everywhere.

This breaks the old model of "files live in folders." Loop components live in the Microsoft Graph. They are objects with relationships, not documents with paths. For organizations still struggling with "which version of the spreadsheet is current," this is the answer.

The file was the atom of digital work for 40 years. Loop components are splitting that atom.

Shared Channels (Teams Connect)

External collaboration has always been painful in Microsoft 365. Guest access is clunky. Tenant switching is even worse. Shared Channels let you create a single Teams channel that spans organizations. Both your team and your client's team work in the same space, with the same files, and under separate tenant governance.

For agencies, consulting firms, and any company with heavy partner or vendor collaboration, this removes significant friction.

Holographic Meetings (Microsoft Mesh)

This feature is further out on the adoption curve. Microsoft Mesh creates 3D virtual meeting spaces where participants appear as avatars. With the right hardware, they can appear as holograms. Today, the practical use case is immersive workshops and brainstorming sessions. Spatial presence adds value in design reviews, architecture planning, or training simulations.

Asynchronous Video and Quick Steps

Two features sound small but change daily habits. Clipchamp integration lets anyone record a quick video update. You can post it to a SharePoint page or Teams channel, replacing a 30-minute meeting with a 2-minute video. Quick Steps in SharePoint libraries add one-click buttons for approve, route, archive, and notify actions. These used to require navigating approval workflows or switching to Power Automate.

AI Made Governance Non-Negotiable

Here's the uncomfortable truth about Copilot: AI is only as good as your data governance. If your SharePoint has oversharing, stale permissions, or sensitive documents in "Everyone" folders, Copilot will surface this content to anyone who asks the right question. The 2025 governance toolkit exists to prevent this.

Data Access Governance (DAG)

DAG gives admins a new tool: a clear dashboard. It shows which sites are overshared, which files have "Everyone" or "Everyone except external users" permissions, and where the highest data risk exists. This is not theoretical. In pilot deployments, organizations often discover that 30-40% of SharePoint sites have broader permissions than intended.

Pre-Copilot audit:If you're planning a Copilot rollout, run a DAG report first. Every overshared site is a potential exposure vector once AI starts indexing and surfacing content. Fix permissions before you flip the switch.

Restricted Access Control (RAC)

RAC is the override button. Set a site-level policy to restrict access to a specific security group, regardless of file or folder permissions. If someone accidentally shares a file with the organization, RAC blocks access for anyone not in the group.

For executive sites, M&A deal rooms, and any workspace with genuinely sensitive content, RAC is the safety net that didn't exist before.

Sensitivity Labels and Document-Level Encryption

Sensitivity labels are persistent metadata that travel with a document when it is downloaded, emailed, copied to a USB drive, or opened on a personal device. The label stays, and its policies (encryption, watermarking, print restrictions) stay with it. This is "data protection that follows the file," not "data protection that depends on the file staying in the right location."

Document-level encryption goes further. For genuinely critical files, board minutes, IP documentation, and pre-announcement financials, encryption ensures that even if the file is exfiltrated, the content is unreadable without the right credentials. Crucially, it also blocks external AI tools from parsing the document's text.

Content Lifecycle Management

The average enterprise SharePoint environment doubles in size every 18-24 months. Most of that growth is content nobody looks at, maintains, or needs, but nobody deletes either. Content Lifecycle Management automates the identification of inactive sites and stale documents, triggers review cycles, and can automatically archive or delete content in accordance with retention policies.

This isn't just about storage costs. Every orphaned document is a governance liability and a distraction for AI-powered search. Cleaning up content sprawl is the single highest-ROI governance activity you can do in 2025.

Building Intranets That People Actually Use

All the AI and governance tooling in the world doesn't matter if employees can't find what they need or won't visit the intranet in the first place. The 2025-2026 architecture and UX trends are about making SharePoint intranets feel less like IT infrastructure and more like a product employees genuinely want to open.

Flat Architecture with Hub Sites

The old model: a single root site with deeply nested subsites, each with its own permissions, navigation, and branding. The new model: independent sites connected through Hub Site associations. Each site manages its own content, but they share navigation, search, and branding through the hub.

This flat architecture is faster to build, easier to govern, and far more flexible. Need to reorganize departments? Detach a site from one hub and attach it to another. No migration required.

Modern Site Theming

SharePoint's new "expressive" templates and adaptive layouts bring modern web design conventions into the intranet: asymmetric hero regions, card-based content, clean typography, and responsive layouts that look good on any device. The days of intranets that look like they were built in 2012 are (finally) ending.

Design tip:The best intranets now look and feel like consumer-grade products. Your intranet is competing for attention with Slack, email, and every other tool on your employees' screens. It needs to earn their click.

Mobile-First Design

Frontline workers, field teams, and hybrid employees don't sit at desktops all day. Designing SharePoint pages for the mobile app first, then adapting them for desktop, ensures that your intranet serves the entire workforce, not just those in the office.

Metadata-Driven Navigation

Instead of clicking through five levels of folders to find a document, users filter by metadata such as department, document type, project, date range, and status. This requires clean taxonomy (see Section 2), but when it's done right, it reduces the average "time to document" from minutes to seconds.

The combination of metadata-driven navigation and semantic search makes the traditional folder structure increasingly irrelevant. Not gone folders still exist for backward compatibility, but no longer the primary way people find things.

What This Means for Your Organization

The trends above aren't a buffet, but they're interconnected layers of the same platform shift. Here's the practical sequence for organizations looking to act on this:

The Three-Step Priority

Step 1:Fix governance first. Run DAG reports, apply RAC policies, and implement sensitivity labels. No AI deployment is safe without this foundation.

Step 2:Build your content intelligence layer. Deploy SharePoint Premium for taxonomy tagging and document processing. Clean, classified content is what makes semantic search and Copilot Agents actually useful.

Step 3:Redesign the experience. Adopt flat architecture, modern theming, and metadata-driven navigation. Layer in Loop components for collaboration and Quick Steps for daily efficiency.

The organizations that will get the most value from this platform in 2025-2026 aren't the ones chasing the shiniest new feature. They're the ones that build the foundation of governance, taxonomy, and architecture, and then let the AI amplify what they've already done well.

The file folder isn't dead yet. But it's definitely on notice.

SharePoint's disorganized content, outdated files, broken links, and missing metadata hinder Copilot’s AI. If your files aren't organized and metadata is inconsistent, Copilot’s answers suffer.

SharePoint Knowledge Agent (renamed “AI in SharePoint” in March 2026) automatically organizes and enriches content, enabling Copilot to deliver accurate answers.

With endless SharePoint sites and files, content chaos is common. To address this, the following sections will explain what the Knowledge Agent does, who uses it, how to enable it, and key tips from our SharePoint Designs testing.

What is a SharePoint Knowledge Agent?

SharePoint Knowledge Agent, built into SharePoint Online (now “AI in SharePoint”), natively organizes your intranet to improve Copilot's answer quality.

Key facts:

• Renamed: As of March 2026, “Knowledge Agent” is now called “AI in SharePoint,” but most documentation and users still refer to it as Knowledge Agent for now.
• Copilot Integration: Requires a Microsoft 365 Copilot license, ensuring your organization gets the full benefit of Copilot’s AI capabilities.
• Knowledge Agent accesses and enriches SharePoint metadata and content natively, providing deep integration within SharePoint. In comparison, Copilot Studio agents are custom-built for specific tasks and currently do not have native access to SharePoint metadata or its content. This distinction affects their capabilities and integration with SharePoint.

At SharePoint Designs, we’ve tested Knowledge Agent since the preview. It makes document libraries much easier to use and manage, especially at scale.

Key Features

SharePoint Knowledge Agent isn’t just another AI add-on. It’s a comprehensive suite of features designed to make SharePoint content Copilot-ready and keep your intranet healthy and usable. Here’s how it works in practice:

• Auto-tagging and Metadata Autofill
  A Knowledge Agent reads documents and creates metadata, such as document type, client, or expiry. You can prompt it for specific details using plain language.Copilot reads file content and metadata (since October 2025). Auto-filled metadata helps Copilot recognize documents and give precise answers.
  For example, an HR team uploads 500 policies. Knowledge Agent auto-tags each with type, review date, and department so Copilot can identify expiring policies instantly.
• AI-generated Views
  Knowledge Agent creates smart library views using metadata, for example, contracts by client or invoices over $500.
  These views are instant, with no manual setup, helping users quickly find and monitor key content.
• Natural Language Rules and Automation
  Describe your workflow in plain English (like “email me for invoices over $500”), and Knowledge Agent automates it. No Power Automate needed for simple tasks.
• Content Health and Site Hygiene
  Knowledge Agent detects broken links, outdated pages, and content gaps. It suggests improvements to keep your intranet fresh and valuable.
• Grounded Q&A on Site Content
  Users can ask Knowledge Agent questions about site content. Enriched metadata improves answer accuracy over standard Copilot queries.

Having reviewed its features, let's turn to who within your organization will benefit most from Knowledge Agent.

Knowledge Agent benefits a wide range of roles across your organization:

• IT Admins: Streamline content governance, automate metadata management, and cut down on manual cleanup.
• HR Teams: Auto-tag policies with review dates and categories; streamline compliance audits.
• Legal Teams: Classify contracts, extract key clauses, and route flagged documents for review.
• Project Teams: Identify outdated documentation, broken links, and missing project artifacts.
• Intranet Managers: Improve findability, keep content fresh, and surface knowledge gaps.

SharePoint Designs configures the Knowledge Agent for every team during your deployment, ensuring that all departments benefit. Learn more at sharepointdesigns.com.

How to Enable Knowledge Agent

This section offers a hands-on walkthrough for enabling the Knowledge Agent in your environment.

Prerequisites

• Microsoft 365 Copilot license: Required for all users accessing Knowledge Agent.
• SharePoint Online Management Shell: Version 16.0.26615.12013 or later.
• Permissions: SharePoint Administrator or Global Administrator role.
• Availability: Not available in GCC, GCC High, DoD, or air-gapped environments.

Step-by-Step: Enable via PowerShell

• Install or update the SharePoint Online Management Shell:
  Install-Module -Name Microsoft.Online.SharePoint.PowerShell
• Connect to your tenant:
  Connect-SPOService https://yourtenant-admin.sharepoint.com
• Enable Knowledge Agent for all sites:
  Set-SPOTenant -KnowledgeAgentScope AllSites
• Or enable for specific sites only:
  Set-SPOTenant -KnowledgeAgentScope IncludeSelectedSites
• Or enable for all sites except specific ones:
  Set-SPOTenant -KnowledgeAgentScope ExcludeSelectedSites
• Verify your configuration:
  Get-SPOTenant | Select-Object KnowledgeAgentScope

Scope Options Explained

• AllSites: Every site gets a Knowledge Agent.
• IncludeSelectedSites: Only specified sites (up to 100).
• ExcludeSelectedSites: All sites except specified ones (up to 100).
• NoSites: Disabled everywhere (default).

EU/UK Tenants: Anthropic Sub-processor Requirement

As of March 2026, AI in SharePoint uses Anthropic models for advanced features. EU and UK tenants must enable Anthropic as a sub-processor in the Microsoft Admin Center; otherwise, users will see errors.

Recommendation
Begin with IncludeSelectedSites. Test 3-5 key libraries for 2-4 weeks, collect feedback, then expand.

Best Practices from Real-World Testing

Based on real-world deployments including projects by SharePoint Designs, here are proven best practices:

• Clean Up Before You Turn It On
  Knowledge Agent works best with tidy libraries. Clean up folders, delete old files, and set naming rules beforehand.
• Start With High-Value Libraries
  Start with libraries where metadata is crucial, such as contracts or policies, rather than broad, shared folders.
• Review Auto-Generated Metadata
  Assign a content owner to review the first metadata batch. Adjust prompts if needed for accuracy.
• Combine With Managed Metadata
  Use SharePoint’s managed metadata with Knowledge Agent to control vocabulary and avoid tag sprawl.
• Measure the Impact
  Track Copilot answer quality before and after Knowledge Agent. Use analytics to see which views succeed.

How this Connects to your Intranet Strategy

Knowledge Agent signals a major shift for SharePoint: from simple file storage to an AI-powered knowledge fabric. Organizations with well-designed intranets and clean information architecture will see the biggest gains. If your SharePoint is messy and underdeveloped, the AI can only do so much, so there’s clear ROI in investing in information architecture now, before general availability. (Teper, 2026)

At SharePoint Designs, we help organizations build SharePoint intranets that are structured, branded, and AI-ready from day one. With the Knowledge Agent entering GA, now is the time to get your content foundation right. SharePoint Designs has delivered intranets for more than 800 clients across 23 countries. We know what works and what doesn’t. Learn more at sharepointdesigns.com.

Conclusion

Knowledge Agent (AI in SharePoint) links content quality to AI quality. Clean up content, enable the preview, and set metadata practices now to get ahead when GA arrives. If you use Microsoft 365 Copilot, SharePoint readiness is essential.

If you’re planning to enable Knowledge Agent and want to make sure your SharePoint environment is ready, talk to the SharePoint Designs team. We’ve been building AI-ready intranets since before Knowledge Agent existed. Contact us at sharepointdesigns.com/contact.

Contact SharePoint Designs

Introduction

Every organization holds vast institutional knowledge policies, processes, project learnings, compliance documents, and expertise that lives in people's heads and inboxes. The challenge has never been creating that knowledge. It has always been making it findable, usable, and governed.

The SharePoint Knowledge Agent solves this problem directly. Built on Microsoft's AI infrastructure and integrated with SharePoint Online and Microsoft 365, it transforms how teams capture, surface, and act on internal knowledge without changing how employees work.

This guide covers:

• What the SharePoint Knowledge Agent is and how it works
• Its key features and real-world use cases
• How it compares to standard SharePoint search
• What organizations in the US, UK, Australia, and beyond need to know before implementing one
• Answers to the most searched questions

What is the SharePoint Knowledge Agent?

The SharePoint Knowledge Agent is an AI-powered knowledge management layer built on top of Microsoft SharePoint Online. It acts as an intelligent assistant that understands your organization's content across sites, document libraries, and Microsoft 365 apps and surfaces it through natural language queries and contextual recommendations.

How it differs from standard SharePoint search:

• Standard search returns a list of keyword-matched documents.
• The Knowledge Agent understands intent, not just words.
• It synthesizes answers from multiple sources and delivers a single, coherent response.
• It recommends relevant content before you even search.

Example: Ask "What is our process for onboarding a new vendor?" and the Knowledge Agent returns the correct policy document, the relevant approver contact, and a workflow summary rather than 47 documents containing the word "vendor."

All data remains inside your Microsoft 365 tenant, under your existing governance, security, and compliance controls. The SharePoint Knowledge Agent aligns with key compliance certifications such as ISO 27001 and supports regulatory requirements, including GDPR. This ensures that data protection and privacy are maintained to standards recognized by IT leaders and auditors. (General Data Protection Regulation - Microsoft GDPR)

Key Features of the SharePoint Knowledge Agent

1. AI-Powered Natural Language Search

• Search across all SharePoint sites, document libraries, and M365 apps using plain English.
• Surfaces documents, policies, FAQs, procedural guides, and best practices in one response
• No need to know which site or library a document lives in
• Especially valuable for large enterprises with content spread across dozens of sites

2. Contextual Knowledge Recommendations

• Proactively surfaces relevant content based on what an employee is currently working on
• A contract reviewer automatically sees approval policies and legal contacts without searching.
• Reduces time spent hunting for information before making decisions
• Increases the likelihood that employees will act on accurate, up-to-date content

3. Automatic Knowledge Article Creation

• Converts unstructured content into structured knowledge automatically
• Processes meeting minutes, project notes, Teams threads, and email chains
• Outputs searchable, governed knowledge articles ready for your intranet
• Closes the gap between where knowledge is created and where it needs to live

4. Deep Microsoft 365 Integration

• Works within Microsoft Teams, Outlook, and Viva Connections, not just SharePoint
• Employees access knowledge inside the tools they already use
• No context switching, no separate knowledge portal to log into
• Unified experience across the entire Microsoft 365 ecosystem

5. Enterprise Security and Compliance

• Fully respects existing SharePoint permission structures.
• Employees only see content they are authorized to access
• Sensitive documents, restricted policies, and confidential files remain protected.
• All data stays within your Microsoft 365 tenant; no third-party data exposure.

5 High-Value Use Cases for the SharePoint Knowledge Agent

1. Employee Onboarding

The problem: New hires waste days searching for training materials, policies, and key contacts, often relying on a manager or buddy to point them in the right direction.

How the Knowledge Agent helps:

• Delivers a role-specific knowledge interface from day one
• Answers plain-language questions with governed, accurate responses.
• Reduces burden on HR and line managers
• Creates a consistent onboarding experience across offices and time zones

Business outcome: Faster time-to-productivity. Less onboarding friction. Lower early attrition.

2. Project Knowledge Management

The problem: Lessons learned, decisions, and project documentation are buried in email threads and the memories of people who may have already left.

How the Knowledge Agent helps:

• Centralizes project knowledge as it is created, not retroactively
• Makes historical project data searchable by future teams
• Surfaces relevant decisions and lessons learned at the start of similar projects
• Reduces repeated mistakes and duplicate effort

Business outcome: Faster project initiation. Better-informed teams. Fewer repeated errors.

3. Customer and Internal Support Teams

The problem: Support agents need the right answer quickly, and finding it across multiple repositories wastes critical time.

How the Knowledge Agent helps:

• Provides instant access to troubleshooting guides, FAQs, and escalation procedures
• Returns a single synthesized answer rather than a list of documents to read through
• Keeps response content consistent across all agents
• Reduces average handling time measurably

Business outcome: Faster resolution. Higher customer satisfaction. More consistent support quality.

4. Policy and Compliance Management

The problem: Employees work from outdated policies. Compliance documents are updated but old versions continue to circulate.

How the Knowledge Agent helps:

• Always surfaces the most current, authorized version of any policy.
• Flags updates and draws related resources to employees' attention.
• Ensures compliance-sensitive teams act on accurate information
• Reduces regulatory risk from outdated documentation

Business outcome: Reduced compliance risk. Consistent policy adherence across departments and geographies.

5. Cross-Departmental Knowledge Sharing

The problem: Different departments solve the same problems independently. Expertise is invisible across team boundaries. Silos cost time and money.

How the Knowledge Agent helps:

• Connects knowledge and expertise across departmental boundaries
• Helps employees find colleagues who have solved similar challenges
• Surfaces reusable solutions from across the organization
• Builds a culture of knowledge sharing over time

Business outcome: Less duplicated effort. Stronger cross-functional collaboration. Faster innovation cycles.

SharePoint Knowledge Agent vs. Standard SharePoint Search

Bottom line: Standard SharePoint search finds documents. The Knowledge Agent finds answers.

What Makes a Successful Implementation?

Deploying a knowledge Agent delivers results only when the underlying environment is ready. Organizations that get the most from AI-powered knowledge management share these characteristics:

• Governed information architecture - The agent surfaces what exists. Unstructured, inconsistently labeled content produces poor output. Clean taxonomy and governance come first.
• Defined content ownership - Every knowledge article needs an owner accountable for keeping it accurate. Without ownership, knowledge bases degrade as policies and processes change.
• An employee adoption strategy - The best tool delivers no value if teams don't use it. Adoption requires visible champions, embedded workflows, and clear communication not just a go-live announcement.
• Iterative refinement - AI systems improve with use and feedback. Treat the Knowledge Agent as a capability that evolves with your organization, not a one-time deployment.