SharePoint Showcase: Refreshed SharePoint mobile app
SharePoint Showcase: Refreshed SharePoint mobile app Your sites, files, news, and people, together in the redesigned SharePoint mobile app. Work does not always happen while you are sitting at your desk. You may need to review a presentation before a meeting, find a document someone shared, or catch up on an important team update while moving between tasks. The redesigned SharePoint mobile app now gives you a mobile starting point for finding relevant content, seeing what is new, and returning to the work that matters to you, similar to the SharePoint Discover experience on web. The app brings your sites, files, news, and people together in a connected experience designed for how you work on a phone. Alongside the refreshed design, we’ve updated sign-in, improved content loading and made navigation more dependable. These changes help make everyday tasks feel smoother, whether you’re checking a document before a meeting or catching up on the go.Publish rich and interactive content with HTML pages in SharePoint
HTML pages in SharePoint let you create rich, interactive content with Copilot or upload existing HTML, then edit, publish, and share it alongside modern pages. Copilot-created pages use your site’s branding, while familiar SharePoint permissions and security controls help manage access. Availability is rolling out gradually through the Frontier program.
Inconsistent behaviour populating Word template from Microsoft List via Power Automate
I'm using a Premium Power Automate and using a series of flows to manage an approval process and populate a Word template from a Microsoft List using content controls at each stage of approval. Approval occurs at several stages in a workflow and, in most cases, works correctly. However, I have two issues occurring at specific points in the process, despite the flows, mappings, list columns and content controls being configured identically to other stages that work correctly. Issue 1 - Field not populating Word template Data entered into the Microsoft List is present and saved correctly. One specific field (Q1) fails to populate its corresponding content control in the Word template, leaving it blank. Other fields populate correctly. The same field and content control setup works correctly at other stages of the process. Issue 2 - Field reverting to previous value A different field (Q2) behaves unexpectedly when an amendment is made in the Microsoft List. The user updates the field and saves the item successfully. The updated value is visible in the list. When the flow triggers, this specific field reverts back to its previous value and the Word template is populated with the old information. All other fields retain their updated values. This only occurs at one or two stages of the process. Elsewhere, the same setup works as expected. Troubleshooting already completed Confirmed the data exists in the Microsoft List. Checked list column settings and data types. Checked Word template content controls. Deleted and recreated the affected actions. Copied actions from working flows and also rebuilt them from scratch. Reviewed dynamic content mappings. Exhausted all troubleshooting steps suggested by Copilot. Has anyone experienced fields intermittently failing to populate Word content controls, or list column values reverting to a previous value when a flow runs? Any guidance on what else I should investigate would be appreciated.SharePoint Publish: The next steps for Viva Amplify and centralized corporate communications
By: Sarah Mathurin and Kripal Kavi Corporate communicators need more than a place to publish updates. They need a connected workspace to create compelling content, plan campaigns, reach employees across channels, and measure impact. That is the foundation of the new Publish experience in SharePoint. With Publish, communicators don’t have to remember another destination, they get a unified place to create, distribute, and measure communications without leaving the platform where their organizational news already lives. Publish serves as the primary hub for communicators and content creators in SharePoint, bringing pages, news, Amplify content, campaigns, templates, analytics, and publishing workflows into a single modern interface, all powered by AI. Our goal is to help communicators deliver the right message to the right audience at the right time. Site campaigns are one way we’re bringing that vision into the everyday SharePoint publishing workflow. Learn more about Publish Getting started with Publish in SharePoint | Microsoft Support What's new: Site Campaigns Today we’re introducing Site campaigns in SharePoint, a new capability that brings campaign management closer to where SharePoint news is created and published. Site campaigns are built directly into your SharePoint site. You can create a site campaign from the Publish experience in SharePoint or inside an existing or new SharePoint site by navigating to the ‘site settings’ menu. Note: For more information on campaigns in SharePoint, click here: Manage campaigns in SharePoint | Microsoft Support Once a site campaign is created, corporate communicators can: Centralize news content: Create and group related SharePoint news posts into a campaign on your SharePoint site. Distribute across channels: Publish to SharePoint, Outlook, Viva Engage, and Teams in one workflow. Track campaign performance: View aggregated analytics across all channels in one place, providing the same visibility you’d expect from the Amplify app. Build on SharePoint's foundation: Because site campaigns are native to SharePoint, communicators and organizations automatically benefit from SharePoint’s existing governance, permissions, co-authoring, and content management capabilities. Site campaigns are available for all SharePoint and Amplify users. Campaigns: Viva Amplify app vs. Amplify in SharePoint To help your organization navigate this evolution, here is how the capabilities compare across both experiences. Both app campaigns and site campaigns are surfaced in SharePoint Publish for easy access. Amplify publications appear alongside news posts labeled as coming from an Amplify campaign and both campaign types appear together in the campaigns section. Feature Viva Amplify App Campaigns Site Campaigns in SharePoint Structure & Hosting Built on dedicated campaign sites. Groups cross-channel publications together for centralized analytics tracking. Lives within a SharePoint site, grouping related news posts for cross-channel publishing and aggregated analytics Publishing Enables publishing across SharePoint, Viva Engage (up to 5 communities), Teams and Outlook. Enables publishing across SharePoint, Viva Engage (cross-post only), Outlook, Teams* *With Viva license Customization per channel Supports channel-specific content customization, allowing users to tailor content separately for Viva Engage, SharePoint, Outlook, or Teams. Does not support channel-specific content customization across SharePoint, Viva Engage, Teams, and Outlook. Approvals Amplify app approvals work with Teams Approvals and let you publish automatically, on a schedule, or manually after approval Site-level approvals can be applied across SharePoint news posts hosted in a site campaign, with Power Automate supporting customizable workflows. Scheduling Schedule any publication created on a campaign site to go live at a future date and time, without additional site setup Schedule pages and news post to publish at a future date and time, once enabled at the site level. Membership & Permissions Campaign-level roles include Owners, Editors, and Approvers; there is no read-only role. Managed broadly at the site level. Site owners/members inherit full site campaign access, while site visitors or readers can view published news. Strategic Planning Includes a Campaign Brief for defining goals, objectives, and key messages that remain visible while drafting. No standalone Campaign Brief; site campaigns focus on multi-channel distribution and analytics. Creation control IT administrators can manage global creation permissions to control who can create campaigns in the organization. Campaign creation follows SharePoint site permissions; site members and owners can create site campaigns. Analytics Supports cross-channel campaign analytics for Outlook, Teams, SharePoint and Engage. Supports cross-channel campaign analytics for Outlook, Teams, SharePoint and Engage. Note: Amplify app campaigns and SharePoint site campaigns are not interchangeable. SharePoint news posts can only be associated with SharePoint site campaigns; Amplify app publications can only be associated with Amplify app campaigns. Editing per channel is not available in Amplify from SharePoint & site campaigns. What's coming soon: Cross-post to Viva Engage SharePoint helps communicators create rich, engaging stories, announcements or news posts for their organizations. Viva Engage helps those stories travel through the communities and conversations where people connect every day. With cross-posting from SharePoint to Viva Engage, authors can bring these experiences together: one post, one conversation. The new experience lets you distribute a SharePoint news post to a Viva Engage storyline or community. Readers can open the complete news post in full fidelity from Engage, while comments, replies, and reactions made in SharePoint or across Engage surfaces (mobile, web, Outlook, Teams) remain synchronized as one conversation. Learn more here: Cross-post SharePoint News to Viva Engage | Microsoft Support Distributing to Engage: Viva Amplify app vs. Amplify in SharePoint Feature Viva Amplify App Amplify in SharePoint Destinations Share to multiple (5) Engage destinations. Each Engage post has its own separate conversation. Share to only one Engage destination. The SharePoint news post and the Engage post share one conversation. Editing Authors can edit the post directly in Engage. Authors edit the SharePoint news post, and changes sync to Engage automatically. Posts can't be edited in Engage. Media attachments Shown at the end of the Engage thread. Not shown at the end of the Engage thread. Readers can select 'view news post' to see all content, including media. Analytics Thread created is classified as 'Article' type Thread created is classified as 'SharePoint News' type What does it mean for Viva Amplify customers? The Viva Amplify app will continue to be available, allowing organizations to maintain their existing workflows without interruption. There are no changes to our licensing model. At the same time, we’re bringing Amplify capabilities directly into SharePoint Publish, making it easier for creators to access distribution and analytics within their existing SharePoint workflows. We’ve already integrated Amplify distribution and analytics features into native SharePoint experiences, and over time, we’ll continue bringing more Amplify capabilities into this unified experience. This update is not a replacement for the Viva Amplify app. Rather, it gives customers more choice in how they access Amplify capabilities while establishing SharePoint as the direction for future corporate communications investments. We encourage customers to become familiar with and use Amplify in SharePoint whenever possible. Together with AI-powered experiences such as Copilot in SharePoint, this evolution gives corporate communicators a more integrated way to create and manage campaigns, streamline workflows, distribute content, and understand performance across Microsoft 365. Appendix Learn more Introducing SharePoint News and Viva Engage cross-posting SharePoint Showcase Copilot in SharePoin
Unlocking Microsoft 365 Adoption in Engineering, Manufacturing, and Regulated Industries
Executive Feedback to Microsoft Leadership: Expanding the Value of Microsoft 365 Beyond Cloud-First Workflows Executive Summary Microsoft has successfully built the industry's leading cloud collaboration ecosystem around Microsoft 365, OneDrive, and SharePoint. The strategy has delivered substantial value for information workers, distributed teams, and organizations pursuing cloud-first operating models. However, there is a significant and often overlooked customer segment that remains underserved: engineering, manufacturing, healthcare, medical device, industrial, laboratory, defense, and other regulated organizations whose primary workflows are intentionally built around file-based repositories, network shares, PDM/PLM systems, and controlled document environments. The challenge is not opposition to cloud technology. The challenge is that many of these organizations prioritize data integrity, traceability, predictability, and workflow continuity above all else. As a result, they often perceive modern Microsoft productivity capabilities such as AutoSave, coauthoring, and version history as being unnecessarily coupled to OneDrive and SharePoint. This creates an important business opportunity. Microsoft could unlock substantial additional Microsoft 365 adoption and customer goodwill by extending modern document protection and collaboration capabilities to local, network-hosted, and hybrid file environments without requiring a complete migration to OneDrive or SharePoint. This is not a request to replace cloud services. It is a request to recognize that cloud-first and file-based workflows can coexist. The Opportunity Is Larger Than It Appears Many of Microsoft's largest enterprise customers operate in environments where files are not simply documents. They are: Design history files Manufacturing records Engineering drawings Validation reports Device master records Controlled procedures Laboratory data Regulatory submissions Quality records For these organizations, file location, revision control, ownership, auditability, and retention are operational requirements rather than convenience features. Microsoft itself acknowledges that Office AutoSave currently requires files to be stored in OneDrive or SharePoint. Files opened from traditional file-system locations do not receive the same experience. As a result, many organizations feel they must choose between: Maintaining proven operational workflows. Accessing Microsoft's most advanced productivity features. That is a business decision many organizations simply refuse to make. The Real Barrier Is Not Technology. It Is Trust. Discussions around cloud adoption are often framed as a resistance-to-change problem. Research consistently suggests otherwise. Studies examining enterprise cloud adoption repeatedly identify security concerns, data privacy concerns, and control over organizational information as major barriers to adoption. One study found security concerns dramatically increased the likelihood that organizations would reject cloud adoption. Similarly, KPMG's cloud transformation research notes that concerns about data loss, audit findings, compliance issues, and operational risk can slow or limit cloud initiatives. The lesson is important: Organizations rarely reject technology because it is new. They reject technology because they do not trust it with critical business information. Once users experience: unexpected file overwrites, synchronization ambiguity, permission confusion, data residency uncertainty, conflicting document versions, trust declines rapidly. Trust, not functionality, is often the limiting factor. Engineering Users Experience the World Differently Microsoft's cloud ecosystem was largely designed around information-worker collaboration. Engineering organizations frequently operate under different assumptions: Information Worker Priority Engineering Priority Seamless sharing Data integrity Anywhere access Traceability Real-time collaboration Configuration control Ease of use Auditability Cloud accessibility Revision certainty Neither approach is wrong. The challenge is that Microsoft increasingly optimizes for one while under-serving the other. An Example: AutoSave AutoSave is one of the most valuable additions Microsoft has made to Office. The value proposition is obvious: Reduced data loss Improved productivity Lower cognitive burden Better user confidence Microsoft's own documentation describes AutoSave as continuously saving changes while users work, but only when documents reside in OneDrive or SharePoint. From Microsoft's perspective, this design is understandable. From the customer perspective, the message often becomes: "Modern document protection is available, but only if you adopt Microsoft's preferred storage architecture." Many customers view this not as a technical limitation, but as product segmentation. Microsoft Could Learn from Version Control Systems Modern software development solved multi-user document conflicts decades ago. Git was specifically designed around realities such as: multiple devices, multiple contributors, offline work, concurrent editing, conflicting changes. Critically, Git assumes conflicts are inevitable. Rather than hiding them, Git exposes conflicts and provides mechanisms to resolve them. Many engineers trust Git precisely because its behavior is transparent. By comparison, file synchronization systems often attempt to abstract away complexity. When synchronization fails, users can no longer determine: which version is authoritative, which edits are newer, what happened, who changed what. The engineering mindset is frequently: Show me the conflict. rather than Hide the conflict and make a decision on my behalf. The Untapped Hybrid Customer Much discussion around Microsoft 365 assumes organizations are either: Cloud-first, or Legacy. In reality, many enterprises are neither. Many operate as hybrid organizations and intentionally will continue to do so. Research from industry and security organizations continues to show persistent adoption of hybrid and multi-cloud architectures driven by governance, security, compliance, and operational requirements. These customers are not rejecting Microsoft. They are already paying customers. They often purchase: Microsoft 365 Windows Azure Teams Active Directory SQL Server Yet many would immediately purchase additional capabilities if Microsoft offered: Local AutoSave Office AutoSave functionality for: NTFS local storage SMB file shares NAS systems PDM-managed documents Local Version History Built-in document time travel without cloud dependence. Hybrid Collaboration Coauthoring capabilities that operate through enterprise file infrastructure. Enterprise Conflict Resolution Visualization and reconciliation of competing document changes. Network-Aware Document Protection The same confidence users experience in OneDrive without requiring migration to OneDrive. The Revenue Opportunity This is not merely a product-improvement request. It is a business opportunity. A significant portion of engineering and regulated industries remain hesitant to migrate entirely into cloud-centric document ecosystems because the perceived operational risks exceed the perceived benefits. Rather than forcing an all-or-nothing decision, Microsoft could monetize a middle path: Microsoft 365 Hybrid Collaboration A premium offering delivering: AutoSave Version History Recovery Conflict Resolution Audit Visibility for enterprise-controlled file infrastructure. Organizations that decline OneDrive adoption today may still eagerly purchase these capabilities. In effect, Microsoft could create incremental revenue from customers who are already committed to the Microsoft ecosystem but currently feel underserved by a cloud-only feature strategy. Recommendation Microsoft should stop treating file-server and network-share users as transitional users waiting to migrate. Many are not transitioning. Many have intentionally chosen architectures optimized for regulatory compliance, engineering rigor, operational control, and data governance. The future should not require choosing between: modern productivity features, and trusted enterprise workflows. The organizations building medical devices, industrial equipment, aerospace systems, manufacturing infrastructure, energy systems, and critical technologies represent some of Microsoft's most technically sophisticated and commercially valuable customers. They deserve first-class support for the workflows they intentionally operate. The opportunity is not to move every customer to the cloud. The opportunity is to bring Microsoft's best innovations to every customer, regardless of where their files live.
Disable incessant nagware popups
I don't know about everyone else, but I am sick and tired of the nagware pop ups in Word, Excel, PowerPoint, Outlook, etc. Every single product harasses me with pop ups trying to tell me "hey, did you know this feature was here?", "you can do this if you click that", "let me hold your hand through using products you've used for decades even though you don't want daddy Microslop to do that". This is a prime example. I keep getting the same ones again and again and again and everything I've read indicates they should only appear once. But they don't. They keep coming back like a psychotic stalker ex who wants alimony even though you were never married. How do I get this nagware to stop?!Copilot, Microsoft 365 & Power Platform Community call
💡 Copilot, Microsoft 365 & Power Platform weekly community call focuses on different use cases and features within the Microsoft 365 and Power Platform - across Microsoft 365 Copilot, Copilot Studio, SharePoint, Power Apps and more. Demos in this call are presented by the community members. 👏 Looking to catch up on the latest news and updates, including cool community demos, this call is for you! 📅 On 29th of October we'll have following agenda: Latest on SharePoint Framework (SPFx) Latest on Copilot prompt of the week PnPjs CLI for Microsoft 365 Dev Proxy Reusable Controls for SPFx SPFx Toolkit VS Code extension PnP Search Solution Demos this time Ranjith D – Build Power Automate Flows and Power Apps from Copilot Studio - Just by Asking Marc André Schröder-Zhou – Designing Adaptive Cards with AI support in SharePoint David Warner - Using Copilot Notebooks - Instant Agentic Experiences & More 📅 Download recurrent invite from https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/m365-powerplat-dev-call-invite 📞 & 📺 Join the Microsoft Teams meeting live at https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/m365-powerplat-dev-call-join 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/request/demo 👋 See you in the call! 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/samples Microsoft 365 & Power Platform community details - https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/home 🧡 Sharing is caring!Copilot, Microsoft 365 & Power Platform product updates call
Copilot, Microsoft 365 & Power Platform product updates call concentrates on the different use cases and features within the Microsoft 365 and in Power Platform. Call includes topics like Microsoft 365 Copilot, Copilot Studio, Microsoft Teams, Power Platform, Microsoft Graph, Microsoft Viva, Microsoft Search, Microsoft Lists, SharePoint, Power Automate, Power Apps and more. 👏 Weekly Tuesday call is for all community members to see Microsoft PMs, engineering and Cloud Advocates showcasing the art of possible with Copilot, Microsoft 365 and Power Platform. 📅 On the 27th of October we'll have following agenda: News and updates from Microsoft Together mode group photo Joe Komban - Copilot in SharePoint: Using Custom Plugins for Enterprise AI Rabia Williams - Introduction on Copilot prompt sample gallery Paolo Pialorsi - Understanding Copilot Cowork extensibility 📞 & 📺 Join the Microsoft Teams meeting live at https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/ms-speakers-call-join 🗓️ Download recurrent invite for this weekly call from https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/ms-speakers-call-invite 👋 See you in the call! 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/samples Microsoft 365 & Power Platform community details - https://un5mzpanxv5t0qg.subtlesoundimmersion.net/community/home 🧡 Sharing is caring!Introducing a team knowledge base, curated by Copilot and agents
Collaboration is changing as teams of humans and agents now work together to get more done. That’s why we’ve evolved Copilot to empower these human-agent teams: just last month, we announced copilot in Teams, Autopilot as your digital teammate, and new tools in Copilot for managing a team’s content workflows. Today, we are taking the next step in human-agent team collaboration, designed to help address the problem of fragmented and outdated information and enable agent teammates to have the required team context they need to perform tasks and answer questions. In Frontier Preview, Copilot and agents in the newly announced Copilot app, Teams, and SharePoint will be able to create, contribute to, curate, and reference a team’s knowledge base in SharePoint. If the player doesn’t load, open the video in a new window: Open video Knowledge bases can support a range of team needs by bringing together the context people and agents need to do their best work. Here are some examples of how we are working with frontier teams to leverage a knowledge base: Legal: Collecting isolated knowledge from emails, files, and personal notes to help agents reference relevant context when creating agreements and contracts. Engineering: Combining technical specifications, user feedback, market research, and product history to give coding agents project context and support the onboarding of new engineers. Sales: Organizing account knowledge and history so sales agents can recommend relevant next steps or quickly provide account snapshots. Team members can explicitly contribute content— whether email, messages, meetings or content that is already on the SharePoint sites they work with. Copilot will organize all this information into an up-to-date knowledge base for the team, readable to people and grounding any agents that are working with the team. Turning raw content into synthesized knowledge At its core, the knowledge base is a specialized library of interlinked agent-friendly markdown files, created by Copilot using Work IQ’s native knowledge compilation engine. This content processing platform can help transform a team’s content into agent-ready knowledge to improve agent performance and results. In our early internal testing, we see that an agent’s responses were up to 4x faster and 30% more token-efficient with the knowledge base when retrieving content to answer questions and performing team tasks 1 . Figure 1: The knowledge base pipeline We believe this is the first step in transforming how human-agent teams work together by leveraging Work IQ’s knowledge compilation engine. As the science advances, the engine improves. By combining advances in content processing with the latest corpus enrichment innovations from our Applied Science research teams, we are continually improving how enterprise content is transformed into usable knowledge. The evidence is promising so far. For example, in a recent paper, we evaluated agents on the task of answering complex questions that require connecting information across multiple documents. We observed significant improvements in both cost efficiency and quality when compared with traditional agents that worked with the original documents or other enrichment methods. Figure 2: Retrieval quality and cost improvement when using the knowledge base corpus map. Note: Results are from a synthetic test environment and published in a public research paper. With millions of sites created by customers every day, SharePoint plays a critical role as the home for the content and knowledge of a team, whether as a vibrant site of pages, files, and lists or the backing content store for a Teams Channel or Modern Group. When enhanced with a knowledge base, the SharePoint site evolves from a content source to the context layer for a team that people, Copilot, and agents can use and reference together. What’s available now This is rolling out now to our Frontier preview tenants. You can start by adding a knowledge base to any SharePoint site— including those backing Teams Channels and Microsoft 365 Groups. You can further use Copilot in SharePoint and the newly announced Autopilot in the Copilot app to create, curate and use your knowledge base. And with the power of Autopilot, you can also use the knowledge base directly from within Teams, from email (by emailing your autopilot). If the player doesn’t load, open the video in a new window: Open video Note: While the knowledge base and its tools are available in Frontier public, the integration with Autopilot requires access to Autopilot, which is rolling out on a separate cadence. Knowledge base is currently available only to users enabled for usage-based billing. Administrators can manage access and spending through the Microsoft 365 admin center. Learn more about managing AI experiences enabled by usage-based billing and how to create the right policies for your organization. Because knowledge base capabilities are currently in preview, billing terms may change before general availability. What’s coming soon Next on our roadmap: Knowledge bases in more places you work, including tools in Cowork and Copilot in Teams, and custom agents created in Microsoft Copilot Studio. Deeper integration with M365 groups – to allow for easier bootstrapping knowledge bases from existing sources (channels, email). Automated, ongoing curation with the help of Microsoft Copilot Studio’s agent flows to help keep your knowledge bases up to date as your organization’s content changes. Greater content scaling, building on our corpus map approach to support larger volumes of content with higher quality at a lower cost. Integration with CLIs and coding agents via Work IQ to allow a broader range of agents to contribute to and work with a knowledge base. If the player doesn’t load, open the video in a new window: Open video More content AI innovation across the Copilot ecosystem Our content AI strategy is focused on helping organizations turn their content into knowledge that people and agents can use in the flow of work. We’re continuing to bring that strategy to life across the Microsoft 365 and Copilot ecosystem with knowledge bases in SharePoint. And we’re not done yet! Here are a few more recent updates in the content AI space: SharePoint tools in Work IQ are coming soon. Last month, we announced that SharePoint tools were coming to the new Copilot app through Work IQ. Copilot in SharePoint is now generally available, bringing Copilot directly into the place where your organization’s content lives. It helps you understand, create, organize, and act on content with AI. Learn more in last month’s blog. New capabilities to govern the content that powers AI. Copilot and agents perform best on well-governed content. The SharePoint Admin Agent is the centerpiece of our new capabilities for getting there. Admins can use natural language to get tenant-level analysis and guided remediation across permissions, content lifecycle, storage, and settings. They can also monitor cross-geo content moves (preview). Catalog management turns a sprawling tenant into structured, manageable content clusters, so admins can scale actions like site attestations, access reviews, and Restricted Content Discovery, and build rollout plans that better match how their organization works. A detailed file level EEEU permissions report enables targeted cleanup, insights on agent access show which agents are reaching SharePoint and OneDrive content, and Governance Hub helps site owners follow through on assigned actions. Today’s preview is just a first step, and we look forward to building this with you. Learn more about how you can be among the first to put the knowledge base to work for your teams and help shape what comes next by sharing feedback. You can either share in-product feedback using Copilot in SharePoint, Autopilot, or sign up here for an opportunity to go deeper with us on this journey. References: 1. Results are based on Microsoft internal testing, October 2026.
