Upcoming changes to classic experiences in SharePoint Online
For the latest details, timelines, FAQs, and implementation guidance, read the full Microsoft Learn article. In 2016, we introduced modern SharePoint and the SharePoint Framework to our online service – a cloud-born user experience & developer extensibility framework. Ten years later, we continue to invest in this stable platform to provide reliable, well-governed, AI-ready, mobile-friendly, and secure-by-default foundations for customers’ publishing and content management needs. Also in 2016, we renamed our previous publishing and UX extensibility system to “classic”. These features were designed to ease our customers’ transition from on premises environment to the cloud service. Now, ten years later, these classic features are used by fewer than 5% of our monthly active tenant base, and the classic SharePoint page content is not participating in the latest ways content should be secured, managed, and shared. Classic pages are also not fully represented in the content formats that power Microsoft 365 Copilot, which can reduce the coverage and accuracy of Copilot responses that draw on classic content. As such, over the next two years, we will take steps to retire classic SharePoint pages and custom scripting add/update capability in SharePoint Online from Microsoft 365 – below you will find details on timelines, assessment tooling, and migration guidance. Overview We are introducing a set of changes to classic experiences in SharePoint Online across two phases. No classic page content or data will be deleted by Microsoft in these phases. Existing pages will remain accessible in a read-only form. Phase 1 – Beginning March 1, 2027 The following changes will take effect: For all tenants Creation of new classic publishing sites and activation of the classic publishing feature will be disabled for site collection and sub sites. The AllowClassicPublishingSiteCreation tenant setting will be enforced as False and cannot be changed. For new tenants created on or after March 1, 2027 Users cannot create new classic pages — including wiki pages, web part pages, blog pages, publishing pages, and custom ASPX pages. The ability to add or update custom scripts will be disabled by default, and the site setting DenyAddAndCustomizePages will be enforced as True and cannot be changed. Note that this setting applies only to classic pages — modern SharePoint pages are not affected, and custom solutions built on the SharePoint Framework (SPFx) will continue to work under your organization's existing governance. Phase 2 - Beginning October 1, 2028 The following changes will extend to all tenants: Classic user-created pages — including wiki pages, web part pages, blog pages, publishing pages, and custom ASPX pages — will become read-only. Users will no longer be able to create or edit these classic pages. The ability to add or update custom scripts will be disabled and the DenyAddAndCustomizePages site setting will be enforced as True and cannot be changed. What you should do now For SharePoint administrators: No data or content will be deleted by Microsoft as part of this change, and all existing data governance features will continue to be honored and continue to function. Discover and assess your classic SharePoint environment Identify usage of classic sites and pages across your tenant. Use the “SharePoint Classic Activities” Purview Audit log category - included in Audit (Standard) and available to all organizations, and events (ClassicPageCreated, ClassicPageEdited, and ClassicPageViewed) to identify active classic page usage, and leverage the Microsoft 365 Assessment Tool to understand the overall classic scope and modernization feasibility. Prioritize based on business importance and usage If your assessment finds no classic content, none of these changes apply to your organization — no action needed. Otherwise, focus first on high-value or frequently updated classic sites and pages, and identify where modernization will have the greatest impact. Classifying content by business criticality can help guide a phased migration plan. Transform to modern SharePoint experiences before enforcement deadlines SharePoint administrators should use modernization tools such as SharePoint PnP Modernization and SharePoint Page Modernization Agent to convert classic pages into modern SharePoint experiences where applicable. Microsoft will continue enhancing the tooling to accelerate page modernization with best-effort fidelity reservation, but it may not fully automate complex scenarios; modernization is a project that typically requires planning, resourcing, and highly customized pages often need redesign or manual rebuilding. Adopt a phased migration strategy Combine centralized IT-led planning and prioritization with distributed execution by site owners over time. Most organizations find success by modernizing page content in waves rather than attempting a single large-scale migration. For detailed guidance, tools, and step-by-step recommendations, refer to the Microsoft Learn article. For site owners and content authors: Site owners should work with their SharePoint administrators to identify classic sites and pages that are still actively used and determine which content should be modernized, retired, or replaced. Documentation, assessment tools, and migration guidance linked below can help organizations understand available modernization options and prepare for the transition. How do I get help? Refer to the following documentation, tools, and Microsoft partner resources to support your migration from classic SharePoint experiences: Modernize your classic SharePoint sites | Microsoft Learn Transform classic pages to modern pages | Microsoft Learn Microsoft 365 Assessment Tool Microsoft Solution Providers Learn more For complete details, timelines, FAQs, and ongoing updates, see the Microsoft Learn announcement. A Message Center post in the Microsoft 365 admin center has been sent to all tenants. (MC1464926 & MC1464924)SharePoint Flexible Sections just got more predictable and easier to use
A new set of usability updates makes Flexible Sections more predictable and easier to author: column layout guides for cleaner reflow, a persistent grid toggle for at-a-glance structure, and one-click, non-destructive conversion from standard sections. Watch the demo and share your feedback in the comments; it's what keeps shaping what we build nex
How much of your Microsoft 365 environment can you actually see at once?
Not how many users you have. Not how many sites, teams, apps or flows you have. How much of it can you actually see connected together? I've been working across Microsoft 365 environments for a while, and I kept running into the same thing. There is no shortage of information. If anything, there is probably too much of it. Users, groups, permissions, SharePoint, Teams, Power Apps, Power Automate, Power BI, Dataverse, OneDrive, Exchange, Intune, licensing, configuration... It's all there. But when you're actually trying to understand how everything fits together, it can be a different story. You open one blade. Find something. Open another. Cross-check it. Go back. Open something else. Before long, you're jumping between different parts of the tenant trying to build the bigger picture in your head. And if you're working with larger environments, that gets difficult pretty quickly. The information isn't necessarily missing. The relationships between the information are what can be difficult to see. That got me thinking about a slightly different question: Instead of "where do I find this information?" "Show me what's connected to this." That's where VisibleState started. Start anywhere. Follow the connections. Imagine starting with a single user. Instead of seeing that user simply as a record with a list of properties, imagine being able to explore the relationships around them: User → Groups → SharePoint → Teams → Power Apps → Power Automate → Power BI → Dataverse → OneDrive → Exchange → Intune Then the questions become different: What does this user have access to? Is that access direct or coming through a group? What resources are connected to them? What depends on something they're associated with? Which licenses are involved? Are there relationships that look unusual? If something changes, what else might be affected? Those questions aren't necessarily about finding another piece of information. They're about putting information that already exists into context. A report can tell you that something exists. A connected view helps you understand what it is connected to. Illustrative example below — not a real customer environment. I'm not suggesting Microsoft 365 doesn't already give us this information Quite the opposite. Microsoft 365 already gives administrators an incredible amount of information and tooling. The thing I've been thinking about is what happens when you want to look across those boundaries. Sometimes I don't want another export. I don't want another list. I don't necessarily want another dashboard. I want to start with something I'm looking at and ask: "What's connected to this?" And then keep following the trail. That's the idea I'm exploring with VisibleState. The interesting part is what happens when you change the viewpoint The same relationships can be useful for completely different reasons. For example: Administrators may want to understand access, permissions and dependencies. Security and governance teams may want to find unusual relationships or exceptions. Compliance teams may need to understand who can access something and why. People managing multiple environments may want a consistent way to understand what's there without rebuilding the picture manually every time. Leadership may not need to see the graph at all. They may simply want to know what's important, what's exposed and what could be affected. It's still the same underlying environment. You're just looking at it from a different angle. And that's where I think things get interesting. Where I'm at with it VisibleState started as something I was building to make my own work easier. I was spending a lot of time investigating environments, tracing access and putting information together for reports. The individual tasks weren't necessarily difficult. It was the jumping between different places and reconstructing the bigger picture that took the time. So I started building something that would let me approach the environment through the relationships instead. It's grown quite a bit from where it started, and I'm continuing to build it. I'm not posting this as a product launch, and I'm not looking for people to sign up. I'm genuinely interested in whether the problem I'm seeing is familiar to other people working with Microsoft 365. So I'm curious... If you could start with any object in your Microsoft 365 environment and immediately see what it's connected to, where would you start? Would it be: Users and access Groups and permissions SharePoint and Teams Power Apps, Power Automate, Power BI and Dataverse Licensing and resources Governance and unusual relationships Something completely different Maybe you've already got a good way of doing this. Maybe you still find yourself jumping between different services and piecing things together manually. Or maybe I'm looking at the problem from the wrong direction. What's the one relationship in your Microsoft 365 environment that you wish you could see instantly?Copilot Extensibility community call - September 2026
🚀 The Copilot Extensibility Monthly Community Call is a recurring virtual gathering designed to keep the global developer and maker community consistently connected, informed, and engaged with the latest advancements in Microsoft 365 Copilot, Copilot Cowork, Microsoft Scout, GitHub Copilot, Microsoft IQ, etc. and their extensibility ecosystem. 👏 Monthly Wednesday call is for all community members to see Microsoft PMs, engineering and Cloud Advocates showcasing the art of possible with the Microsoft AI technologies. 📅 On the 9th of September we'll have following agenda: News and updates from Microsoft Community group photo Anthony Shaw - Personal Microsoft IQ Dashboards with the IQ APIs Sébastien Levert - Introducing the Work IQ Dev Tools Kevin Ly - Understanding Copilot credits in Copilot Cowork and Work IQ 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/CopilotExtensibility-call-invite 🗓️ Download recurrent invite for this weekly call from https://aka.ms/community/CopilotExtensibility-call-invite 👋 See you in the call! 💡 Building something cool with Microsoft AI technologies (Copilot, Cowork, Copilot Studio, Microsoft IQ, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Labs and training material about Microsoft 365 Copilot Extensibility - https://aka.ms/copilotdevcamp Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!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 3rd of September 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 Ian Tweedie – Sometimes a Little Code Saves a Hundred-Step Flow Katrina Frolinka – Custom Copilot Agent for Document Generation in SharePoint Elio Struyf - Supporting WebMCP within an SPFx extension 📅 Download recurrent invite from https://aka.ms/community/m365-powerplat-dev-call-invite 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/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://aka.ms/community/request/demo 👋 See you in the call! 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/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 Microsoft 365 and Power Platform. 📅 On the 1st of September we'll have following agenda: News and updates from Microsoft Together mode group photo Rémi Dyon - Introduction of GitHub Harness in Copilot Studio Scott Durow – Learn the new GitHub Copilot Harness in Copilot Studio with Agent Academy Vesa Juvonen – Surfacing your business apps in Copilot canvas – AI Project Portfolio Scenario 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/ms-speakers-call-join 🗓️ Download recurrent invite for this weekly call from https://aka.ms/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://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!AutoSave disabled when opening SharePoint-synced files from Finder after macOS Tahoe 26.6 update
Files stored in SharePoint Online and synchronized locally through OneDrive are opened as local documents when launched from Finder. Office applications display "Saved to my Mac" and AutoSave is turned off by default. However, opening the exact same files through Word/Excel > Open > Sites, or via SharePoint "Open in Desktop App", correctly identifies them as cloud documents. In that scenario, AutoSave is enabled and collaboration/version history features work as expected. Troubleshooting already performed: OneDrive reset and re-linked SharePoint library re-synced Signed out and back into both Office and OneDrive Removed Microsoft credentials from macOS Keychain and re-authenticated Recreated local OneDrive sync relationships Verified OneDrive File Provider extensions are enabled Verified Office applications and OneDrive are fully up to date Tested with newly created files and existing files Tested "Always Keep on This Device" with no change in behavior The issue appears to be specific to the Finder-to-Office launch path after upgrading to macOS Tahoe 26.6. Before upgrading to macOS Tahoe 26.6, opening the same SharePoint-synchronized files directly from Finder correctly preserved cloud document identity and AutoSave was enabled as expected. I discussed this issue in detail with Apple Support, but they quickly dismissed it, saying that the problem is not on Apple's side and that I should contact Microsoft instead.Backout Plan for EWS to MS Graph API upgrade for SharePoint|sapiens
Microsoft has announced the retirement of Exchange Web Services (EWS) in Exchange Online, effective October 1, 2026. After this date, EWS-based integrations will no longer be supported. To ensure uninterrupted email functionality, all affected SharePoint|sapiens solutions must be upgraded to use the Microsoft Graph API. My question is this - if we upgrade to Graph and our SharePoint|sapiens solution goes sideways somehow, is backout / rollback to EWS an option? I realize we could only roll back until 10/1 since that's the EWS retirement date, but our leadership may request that we make our solution functional temporarily (if the upgrade causes a problem) by rolling back.SharePoint Showcase: 5 Ways Organizations Improve Business Processes with Copilot in SharePoint
AI becomes most impactful when it helps with the work teams already do every day. The challenge is rarely a lack of information. It is turning trusted information into a clear, repeatable process without starting from scratch each time. That is where Copilot in SharePoint can help. It works with the content and structure already in SharePoint, including sites, pages, lists, libraries, and files. Teams can ask questions, compare and summarize content, organize information, create outputs, and turn repeatable multi-step processes into reusable skills. The examples below are based on real customer scenarios from organizations exploring Copilot in SharePoint. To protect customer confidentiality, organization names and identifying details have been generalized. What matters is the pattern: start with trusted SharePoint content, define the work that needs to happen, keep people in control, and make the process easier to repeat.The Case of the Massive Loop Container
Why would a seemingly simple Loop workspace develop into a monster SharePoint Embedded container? That’s the question to answer when a Loop container grew to fill nearly 88 GB of SharePoint Embedded storage. The workspace had been through many hundreds of edits, but that’s an unlikely reason to spread and occupy so much storage. Loop and SharePoint Embedded are black boxes when it comes to administration, so we must wait for Microsoft to explain. https://office365itpros.com/2026/08/27/loop-workspace-big-container/
