<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Wasif Ali on Medium]]></title>
        <description><![CDATA[Stories by Wasif Ali on Medium]]></description>
        <link>https://medium.com/@george_21432?source=rss-09d94389103e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fEDVsFE4TKwjdvzNWPA_xA.jpeg</url>
            <title>Stories by Wasif Ali on Medium</title>
            <link>https://medium.com/@george_21432?source=rss-09d94389103e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:58:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@george_21432/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What Breaks When Classic SharePoint Goes Modern, and Where SPFx Fits In]]></title>
            <link>https://medium.com/@george_21432/what-breaks-when-classic-sharepoint-goes-modern-and-where-spfx-fits-in-aa8d3f41cd15?source=rss-09d94389103e------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa8d3f41cd15</guid>
            <category><![CDATA[classic-sharepoint]]></category>
            <category><![CDATA[sharepoint-online]]></category>
            <category><![CDATA[spfx]]></category>
            <dc:creator><![CDATA[Wasif Ali]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 14:50:09 GMT</pubDate>
            <atom:updated>2026-11-19T14:50:09.434Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Classic customizations rarely fail loudly when a site goes modern, so here is what breaks, where SPFx fits, and how I decide what to rebuild, replace or retire.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f18hyxjNU8oEdQ_FRwdX6A.png" /></figure><h3>What carries over from classic to modern SharePoint, and what does not?</h3><p>Most classic customizations have a supported modern replacement, and many of them need no code at all.</p><p>In early 2025 my team moved a regional engineering firm’s intranet, used by about 600 people, from classic publishing sites to modern communication sites. The content moved cleanly and the new pages looked far better. On the first Monday, the help desk queue filled up. The staff directory search on the home page had vanished. So had the [project status colours] in the main project list, and the news rollup that used to match the company’s branding now looked like every other SharePoint site.</p><p>None of those features were in the migration scope. A contractor had built them years earlier with a script editor web part, a JSLink file and a custom master page, and nobody at the firm remembered they were customizations. To the people using them, they were simply “SharePoint.”</p><p>That project changed how I start every SharePoint modernization. Before anything moves, I now find every customization, decide what each one is worth, and plan where SPFx fits. This article walks through that process.</p><h3><strong>Why Classic Customizations Do Not Carry Over</strong></h3><p>Classic SharePoint let you change almost anything by adding your own code to the page. Modern SharePoint takes a different approach: Microsoft controls the page, and customizations plug in through defined, supported extension points. That shift is what makes modern pages faster, mobile-friendly and safe to update, and it is also why the old techniques stop working.</p><h3>Four classic techniques cause most of the trouble I see.</h3><p><strong>Script Editor and Content Editor Web Parts.</strong></p><p>These let anyone paste HTML and JavaScript straight onto a page, which made them the quickest way to add a widget, a tweak or a form. Microsoft is direct about it: the script editor web part is one of the <a href="https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-customizations">classic web parts that has no out-of-the-box modern equivalent</a>. Anything built in one has to be rebuilt as an SPFx web part or replaced.</p><p><strong>Custom master pages and alternate CSS.</strong> Classic branding usually lived in a custom master page that controlled the whole site’s look. The modern interface <a href="https://learn.microsoft.com/en-nz/sharepoint/dev/transform/modernize-branding">simply ignores custom master pages and alternate CSS</a>. Modern branding comes from a tenant-controlled SharePoint theme, plus site headers, footers and navigation.</p><p><strong>JSLink.</strong> JSLink changed how a list column or view displayed, such as turning a status value into a coloured badge. It does not work in modern lists. Microsoft’s guidance is to use <a href="https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-customizations">column formatting when the change is purely visual</a>, and an SPFx field customizer when more behaviour is needed.</p><p><strong>User custom actions that embed script.</strong> These added buttons to the list ribbon or injected script into every page, for example a site-wide banner. Microsoft notes that this pattern <a href="https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-customizations">does not work in the modern list and library experience</a>, and the replacements are SPFx command sets and application customizers.</p><p>One behaviour catches teams out. When SharePoint detects an incompatible customization on a list, it quietly falls back to the classic list interface. The list keeps working, so nobody reports a problem, and the site never fully becomes modern.</p><h3><strong>What Microsoft Has Already Retired</strong></h3><p>Over the past year, Microsoft set hard dates for the oldest parts of classic SharePoint. <a href="https://support.microsoft.com/en-US/SharePoint/platform/sharepoint-2013-workflow-retirement">SharePoint 2013 workflows were retired on April 2, 2026</a>, with Power Automate as the recommended replacement, and <a href="https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/retirement-announcement-for-add-ins">SharePoint Add-ins stopped working for all tenants on the same day</a>, with SPFx named as the primary replacement. <a href="https://techcommunity.microsoft.com/blog/spblog/support-update-for-infopath-forms-services-in-microsoft-365/3858190">InfoPath Forms Services retires from July 14, 2026</a>: designers can no longer create or publish InfoPath forms, and forms that were not migrated stop accepting new responses.</p><p>Classic sites themselves are a different story. They still open in SharePoint Online. The September 15, 2025 change <a href="https://mc.merill.net/message/MC1117115">turned custom scripting off by default on classic publishing sites</a> and blocked new classic publishing site collections by default, but scripts already on a page keep running. My rule is simple: a read-only archive site with no customizations can stay classic for a while, and a site that depends on custom script or classic publishing features goes into an early modernization wave, because one setting change could break it.</p><p>To see what a tenant holds, I start with the <a href="https://pnp.github.io/pnpassessment/">Microsoft 365 Assessment tool</a>. Its modules cover classic pages, with the web parts on each page and optional page-view data, plus InfoPath forms, add-ins with their Azure ACS principals, and alerts. It does not report on JSLink files, custom master pages or user custom actions, so my team checks those separately with PnP PowerShell, site by site. For the retired 2013 workflows, the useful question now is which processes people still miss, and the site owners usually know.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MKKvQlFQOZhgqh2D-FLO5w.png" /></figure><p>Three deadlines in under a year moved modernization from the backlog into the plan.</p><h3><strong>What SPFx Is, Explained Without the Jargon</strong></h3><p>The SharePoint Framework, usually shortened to SPFx, is Microsoft’s supported way to add your own features to modern SharePoint. Microsoft calls it <a href="https://learn.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview">the recommended customization and extensibility model for SharePoint</a>.</p><p>The simplest way to think about it: classic customization meant pasting your own code onto the page and hoping the page did not change underneath it. SPFx gives developers official sockets to plug into. Microsoft can keep improving the page, and the plug-ins keep working.</p><p>SPFx builds four main kinds of things:</p><ul><li><strong>Custom web parts</strong>, the building blocks you add to a page, such as a staff directory, a project dashboard or a feed from another system.</li><li><strong>Extensions</strong>, which change things around the page: a banner or footer on every page (application customizer), a new button on a list (command set), or a custom display for a column (field customizer).</li><li><strong>Adaptive Card Extensions</strong>, the cards on the Viva Connections dashboard.</li><li><strong>Copilot UX components</strong>, <a href="https://devblogs.microsoft.com/microsoft365dev/copilot-ux-components-are-generally-available-bring-interactive-experiences-into-copilot/">generally available with SPFx 1.24 since October 28, 2026</a>, which show custom interface elements inside Copilot. These need a Copilot add-on license, and mobile support is not available yet.</li></ul><p>For a non-developer, three characteristics matter most. An SPFx solution <a href="https://learn.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview">runs in the context of the current user</a>, and any API access it needs beyond that has to be approved by an admin. The same web part can work on SharePoint pages and in Microsoft Teams. And it is installed through an app catalog, where IT can see and approve it.</p><p>That last point is the one I stress with clients. In the engineering firm’s tenant, the script editor web parts were scattered across dozens of pages with no record of who wrote them. With SPFx, every customization is a named package that someone approved.</p><p>The hardest of the SPFx builds on that project was the staff directory search. It reads people data through Microsoft Graph, so it would not load until an admin approved the API permission, and getting that approval through the firm’s security team took a week. The build itself took about 3 weeks, and a Node.js version that did not match the SPFx toolchain] cost us 2 days at the start. The HR systems team owns it now and ships updates through the app catalog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_1A7cvDj-6TUIM_28u-Ng.png" /></figure><p>Every SPFx solution goes through an app catalog, where IT can see and` approve it.</p><h3><strong>Rebuild, Replace or Retire</strong></h3><p>Every classic customization lands in one of three buckets. I sort them with three questions, asked in this order.</p><p><strong>Does anyone still use it?</strong></p><p>If nobody can name a person who relies on it, it goes in the retire bucket. Page view data from the assessment tool helps here, and so does asking. Retiring is the cheapest option, and in my experience it applies to far more customizations than clients expect.</p><p><strong>Does Microsoft now do it out of the box?</strong></p><p>A surprising share of old customizations recreated features modern SharePoint now has built in. A JSLink badge becomes column formatting. A script-based news rollup becomes the News web part. A custom branding master page becomes a SharePoint theme with a site header. A 2013 approval workflow becomes a Power Automate flow. These go in the replace bucket, and they need configuration, with no development at all.</p><p><strong>Is it valuable and specific to the business?</strong></p><p>Only what is left after the first two questions is worth rebuilding as an SPFx solution: a directory search tied to the HR system, a dashboard pulling from a line-of-business app, a form with real business logic. Before writing anything, I check whether an open-source web part from the <a href="https://pnp.github.io/sp-dev-fx-webparts">PnP SPFx samples gallery</a> already does the job.</p><p>On the engineering firm’s project, that sorting changed the size of the work entirely. Of the 40 customizations we found, [20] were retired, [14] were replaced with built-in features, and only [6] needed SPFx development.</p><p>This is where I disagree with a lot of modernization advice. Many guides treat the script editor web part as something to recreate in SPFx, and there are generic “modern script editor” web parts that bring the paste-your-own-code model back to modern pages. I avoid them on client tenants. They recreate exactly the unmanaged, undocumented code that made the classic site hard to move in the first place. If something is worth keeping, it is worth building properly as a named web part that someone owns.</p><p>One more call I make often: for a form, I reach for Power Apps before SPFx. Most classic forms collect data into a list and route it for approval, and Power Apps with Power Automate does that with far less code to maintain. I choose SPFx for a form only when it has to sit inside a page as part of a larger experience, or needs an interface Power Apps cannot produce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8iKCCU2deTH1dVND43H_hw.png" /></figure><p>Asked in order, the first two questions clear most of the list before any development starts.</p><h3><strong>Modernize in Waves</strong></h3><p>The biggest risk in a modernization project is trying to do it all in one release. I learned that on an [earlier] project, where we committed to rebuilding [every] customization in SPFx before switching a single site to modern. The development backlog grew to [5 months], and the business saw nothing change in that time. When [the operations director] asked in a steering meeting what they had been paying for, I did not have a good answer, and support for the project faded before the first site went live. Since then, I release modern sites in waves and build each SPFx piece only when a wave needs it.</p><p>I now run modernization in four phases.</p><ol><li><strong>Inventory</strong></li></ol><p>Run the Microsoft 365 Assessment tool for classic pages, InfoPath and add-ins, then scan separately for JSLink, master pages and custom actions. Add usage data and a named business owner for each item.</p><p><strong>2. Retire and Replace</strong></p><p>Remove what nobody uses and swap the rest for built-in features. This phase usually clears most of the list, costs little, and shows visible progress within weeks.</p><p><strong>3. Modernize Sites in Waves</strong></p><p>Move sites to modern pages a department at a time, starting with those that have the fewest remaining customizations. Each wave goes live on its own, so people see improvements early and feedback shapes the next wave.</p><p><strong>4. Build the SPFx Pieces that Matter</strong></p><p>Develop the remaining SharePoint custom web parts and extensions in order of business value, and release each one when the sites that need it are ready. A [staff directory] web part might ship in the first wave, and a dashboard for a department in the third.</p><p>This order keeps the expensive work small and focused. It also means the SPFx development is shaped by real use of the modern sites, which tends to change the requirements in useful ways.</p><p>The classic pages themselves convert with Microsoft’s page transformation tooling. My team runs <a href="https://learn.microsoft.com/en-gb/sharepoint/dev/transform/modernize-userinterface-site-pages-powershell">ConvertTo-PnPPage in PnP PowerShell</a> on wiki, web part and publishing pages, using the assessment tool’s mapping score to decide which pages to try first. The tooling has a clear limit: Microsoft notes that the score <a href="https://learn.microsoft.com/en-us/sharepoint/dev/transform/assessment-tool-classic-pages">does not guarantee a transformed page will keep all its visual or business behavior</a>. Every converted page gets a human check, and pages built around a heavily customized layout are usually faster to rebuild by hand.</p><h3><strong>Key Takeaways</strong></h3><ul><li>Classic customizations stop working on modern pages because modern SharePoint only accepts supported extensions. Microsoft has set hard dates for 2013 workflows, add-ins and InfoPath, and turned custom scripting off by default on classic publishing sites.</li><li>Sort every customization into retire, replace or rebuild before anyone writes code; most never need SPFx.</li><li>Modernize in waves, and build SPFx solutions only for what is valuable and specific to the business.</li></ul><h3><strong>Where to Start</strong></h3><p>This week, run the <a href="https://pnp.github.io/pnpassessment/">Microsoft 365 Assessment tool</a> against your tenant and look at two numbers: how many classic pages are still in use, and how many contain web parts with no modern equivalent. Those two figures tell you how big your SharePoint modernization really is, and which sites to put in the first wave.</p><p>If you have moved a classic intranet to modern, I would like to hear which customization surprised you most when it disappeared. Mine was a staff directory search nobody remembered adding. Share yours in the comments.</p><p>I’m Wasif Ali, a Microsoft 365 and SharePoint Solutions Expert and CTO at Code Creators. I write about SharePoint and Microsoft 365. My team’s SharePoint development work is at <a href="https://codecreators.ca/sharepoint-development/">Code Creators</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa8d3f41cd15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why SharePoint Governance Fails After Launch and the Four Basics That Hold Up]]></title>
            <link>https://medium.com/@george_21432/why-sharepoint-governance-fails-after-launch-and-the-four-basics-that-hold-up-69eef63255ba?source=rss-09d94389103e------2</link>
            <guid isPermaLink="false">https://medium.com/p/69eef63255ba</guid>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[sharepoint-online]]></category>
            <category><![CDATA[sharepoint-governance]]></category>
            <dc:creator><![CDATA[Wasif Ali]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 21:25:53 GMT</pubDate>
            <atom:updated>2026-11-09T21:27:00.606Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>SharePoint governance rarely fails at launch. It fails in the quiet months afterwards, when the project team moves on and the rules stay on paper. Here is the framework I use to keep sites under control while people keep working.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z3pNOuKalCc4xLBPEImb_g.jpeg" /></figure><p>The intranet launch went well. A small team had designed about 30 sites with clear owners, a navigation everyone agreed on, and a governance document signed off by the steering committee. When I reviewed the same tenant 18 months later, it held roughly 2,400 sites. Around 600 had a single owner or none, a few dozen were named some version of “Test,” and nobody I asked could find the governance document. Four months later, we put the basics in this article in place, the number of sites with fewer than two owners was down to about 40, and the tenant had archived roughly 700 sites nobody needed.</p><p>Nobody did anything wrong. Every Teams team created a site. Every project created a team. People left, and their sites stayed. That is how SharePoint governance usually fails: slowly, after launch, through ordinary use.</p><p>This article covers how that sprawl builds up, why governance documents so often end up unread, how to find the balance between control and usability, and the four basics I put in place on every tenant. It ends with the signs that your own environment needs attention now.</p><h3><strong>How Site Creation Turns Into Sprawl</strong></h3><p>SharePoint makes creating a site easy by design. <a href="https://learn.microsoft.com/sharepoint/manage-site-creation">By default, users can create communication sites and Microsoft 365 group-connected team sites</a>, and every Microsoft 365 group comes with its own team site. Create a team in Teams, a plan in Planner or a group in Outlook, and a SharePoint site appears behind it, whether or not anyone intended to use it.</p><p>Many organizations try to close this off with the site creation setting in the SharePoint admin center. Microsoft is clear that this only covers part of the picture: <a href="https://learn.microsoft.com/sharepoint/manage-site-creation">turning off site creation does not stop people creating Microsoft 365 groups or Teams</a>, and each of those still brings a site with it. Group creation is controlled separately.</p><p>The result follows a familiar pattern. A project team creates a site, uses it intensely for six months, then disbands. The site stays. Its owner changes roles or leaves the organization, and now nobody is responsible for it. Multiply that by every project, every pilot and every “quick test” over three years, and you have sprawl.</p><p>Sprawl causes three practical problems. People cannot find the right site, so they create another one, and duplicates multiply. Ownerless sites keep whatever access they had when their owners left, with nobody to review it. And search, and now Copilot, surface content from all of them, including the stale drafts and outdated policies nobody meant to keep.</p><h3><strong>Why Governance Documents Get Written and Then Ignored</strong></h3><p>Most organizations I work with already have a SharePoint governance plan. It is usually 30 to 40 pages long, written by the launch project team, approved by a steering committee, and saved in a library few people have opened since. It fails for four reasons I see again and again.</p><ul><li><strong>It was written for launch day.</strong> Reorganizations, new teams and Copilot change the landscape within a year, and nobody updates the plan to match.</li><li><strong>Nobody owns it after the project ends.</strong> The rules have no one to enforce them, answer questions about them, or change them when they stop making sense.</li><li><strong>The rules live on paper only.</strong> “Every site must have two owners” does nothing on its own. A policy that notifies people when a site drops below two owners does the work every day.</li><li><strong>It is written for administrators.</strong> Site owners and everyday users create the sites and share the files, and they never read it.</li></ul><p>My view is simple. A SharePoint governance plan worth keeping fits on two pages, names an owner for each rule, and points to the setting or policy that enforces it. Anything that cannot be enforced or reviewed belongs in training material for site owners.</p><h3><strong>The Balance Between Control and Usability</strong></h3><p>Governance fails in two directions, and I have seen organizations swing from one to the other.</p><ul><li><strong>Too little control.</strong> Anyone can create anything, nobody reviews it, and within a couple of years the tenant has more sites than anyone can name, with search full of duplicates.</li><li><strong>Too much control.</strong> IT locks down creation after a sprawl scare, requests wait 2 weeks, and projects move to personal OneDrive folders or tools outside Microsoft 365, where IT cannot see them at all.</li></ul><p>The goal is a middle path: people get what they need quickly, inside guardrails they barely notice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q8TVjsxZMDGDSEIvPEXRKQ.jpeg" /></figure><p>This is where my advice differs from a lot of standard guidance. I rarely recommend restricting Microsoft 365 group creation to IT alone. I would rather let people create a team in a few minutes, with a naming rule, two owners and a sensitivity label, than make them wait for approval. Speed keeps work inside the tenant, and the lifecycle and review basics below catch what self-service gets wrong. I restrict creation only where the content demands it, such as sites for HR, legal or regulated projects.</p><p>The second opinion follows from the first. In a small tenant, of under 150 people, I would drop formal provisioning before any of the other basics. Ownership, lifecycle and reviews prevent sprawl from lasting. Provisioning only slows it down, and a small organization can usually see its whole site list on one screen.</p><h3><strong>Four Governance Basics That Hold Up After Launch</strong></h3><p>Strip SharePoint governance best practices down to what survives a busy organization, and four basics remain. Each one is a habit backed by a setting, so it keeps working after the project team has gone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PaTFsMyN32A5JmIsdR34xQ.jpeg" /></figure><h4><strong>Site Ownership</strong></h4><p>Every site has at least two named owners, and both know they are responsible for it. Two owners mean one can be on leave or change roles without the site becoming orphaned. When someone leaves, their sites are reassigned as part of offboarding, in the same checklist that recovers their laptop.</p><p>Microsoft’s <a href="https://learn.microsoft.com/en-us/sharepoint/create-sharepoint-site-ownership-policy">site ownership policy</a> automates the check: you set a minimum number of owners, and it notifies the people you choose when a site falls below it. It is part of SharePoint Advanced Management, which comes with Microsoft 365 Copilot licenses or as a separate add-on.</p><p><strong>Provisioning</strong></p><p>Provisioning is how a new site comes into existence, and I keep it fast. Two settings do most of the work wherever people create a site.</p><p>The <a href="https://learn.microsoft.com/entra/identity/users/groups-naming-policy">Microsoft 365 group naming policy</a> in Microsoft Entra ID adds a prefix or suffix to every new group name and blocks words you choose, across Teams, Outlook, SharePoint and Planner. A rule such as “PRJ-” in front of project teams keeps the site list readable and makes duplicates easy to spot. It needs Microsoft Entra ID P1 licenses.</p><p><a href="https://learn.microsoft.com/purview/sensitivity-labels-teams-groups-sites">Sensitivity labels for teams, groups and sites</a> let people choose a label when they create a team or site. The label sets privacy, guest access and external sharing for the whole container, so a site created as “Confidential” starts with the right settings before anyone shares a file.</p><p>Teams creation stays self-service. For sites created outside Teams, such as communication sites, I turn off direct creation and use a short request form, usually Microsoft Forms with a Power Automate flow, that captures the purpose, two owners and an expected end date. Communication sites are fewer and longer-lived, so a short wait there costs little.</p><p><strong>Lifecycle</strong></p><p>Every site should have a defined end, and two Microsoft tools cover different parts of the tenant.</p><p>The <a href="https://learn.microsoft.com/en-us/entra/identity/users/groups-lifecycle">Microsoft 365 group expiration policy</a> asks owners to renew groups after a set period. Groups in active use renew automatically, and owners of the rest are emailed 30 days, 15 days and 1 day before expiry. An expired group can be restored for 30 days after deletion. It needs Microsoft Entra ID P1 or P2 licenses, and a tenant can have only one expiration policy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Db9_EHlSI9hNDeXWtFpq1Q.jpeg" /></figure><p>The group expiration policy only applies to Microsoft 365 groups, so communication sites and other sites without a group are outside it. The <a href="https://learn.microsoft.com/sharepoint/inactive-site-policy">inactive site policy</a> reaches those. It finds sites with no recent activity and asks owners to confirm they are still needed. If nobody responds, it can set the site to read-only and then archive it with Microsoft 365 Archive. Microsoft’s own wording is worth noting: <a href="https://learn.microsoft.com/en-us/sharepoint/site-lifecycle-management">these policies don’t delete sites directly</a>. They notify, and act only as far as you configure them.</p><p>I learned to introduce lifecycle gently. On an [early] project for a [mid-sized accounting firm], I switched on a [180-day] group expiration policy across the whole tenant with little warning to owners. Within [2 months], [14] groups expired, including the internal audit team’s, whose site only came alive at year-end. Their lead’s first message to me was [“Where did our working papers go?”]. We restored every group inside the 30-day window and nothing was lost, but it cost trust. Since then, I run the SharePoint lifecycle policies in simulation mode first. The group expiration policy has no simulation mode, so I apply it to a <a href="https://learn.microsoft.com/en-us/entra/identity/users/groups-lifecycle">selected set of groups</a> first (Microsoft allows up to 500) and tell owners what is coming before it covers everyone.</p><p><strong>Regular Reviews</strong></p><p>Once a quarter, someone looks at the whole picture: the new sites created, sites below two owners, inactive sites, and external sharing. Periodically, owners confirm their sites are still needed and their members are still right; I recommend a 12-month cycle. Microsoft’s <a href="https://learn.microsoft.com/en-us/SharePoint/request-site-attestations">site attestation policy</a> handles that confirmation by asking owners for an explicit review, which catches the sites activity data cannot judge.</p><p>The tools have a shared weak spot. Every one of them works by emailing owners, so a site with no active owner is exactly where the notifications go unanswered. I always set a fallback recipient, usually the business area’s lead, for sites where nobody responds.</p><h3><strong>Signs Your SharePoint Needs Governance Attention Now</strong></h3><p>You do not need a full audit to know whether SharePoint governance has slipped. If several of these sound familiar, it is time to act:</p><ul><li>Nobody can say, without checking, roughly how many sites the tenant holds.</li><li>A noticeable share of sites have one owner or none.</li><li>The site list includes names like “Test,” “New Team” or three versions of the same project.</li><li>People ask which of several sites holds the current version of a document.</li><li>The governance document predates your last reorganization.</li><li>Search or Copilot returns outdated policies and drafts from sites nobody uses.</li></ul><p>One or two of these are normal in any busy tenant. Four or more usually means governance stopped at launch and needs to start again, beginning with ownership.</p><h3><strong>Key Takeaways</strong></h3><ul><li>SharePoint governance usually fails after launch, through ordinary use, so it needs owners and settings that outlast the project team.</li><li>Aim for fast self-service inside guardrails, and save tight control for sensitive content.</li><li>Ownership, provisioning, lifecycle and regular reviews hold up because each one is backed by a setting or policy.</li></ul><h3><strong>Questions I Get Asked</strong></h3><p><strong>Who should own SharePoint governance?</strong></p><p>A named person in the business, supported by IT. IT owns the settings and policies, but the decisions about what a site is for, who belongs in it and when it can close sit with the business. In organizations where governance holds up, I usually see a small group of site owners from each department meeting once a quarter, with one person accountable for the result.</p><p><strong>Do we need a third-party governance tool?</strong></p><p>For most organizations, Microsoft’s own tools cover the basics: site creation settings, the group expiration policy, and the SharePoint Advanced Management lifecycle policies. I recommend a third-party tool when provisioning needs approval workflows and templates beyond what Microsoft offers, or when a large tenant needs reporting across many sites at once. The trade-off is cost and one more system to maintain, so I start with the native tools and add only what is missing.</p><h3><strong>Where to Start</strong></h3><p>This week, open the SharePoint admin center, expand <strong>Policies</strong>, select <strong>Site lifecycle management</strong>, and create a <a href="https://learn.microsoft.com/en-us/sharepoint/create-sharepoint-site-ownership-policy">site ownership policy</a> in simulation mode with a minimum of two owners. It runs once and produces a report without ongoing enforcement. Every site on that report is a decision waiting to be made, and assigning owners is the fastest way to bring SharePoint governance back under control.</p><p><strong>If you have rebuilt governance after a sprawl problem, I would like to hear what worked for you. Share it in the comments.</strong></p><p>I’m Wasif Ali, a Microsoft 365 and SharePoint Solutions Expert and CTO at <a href="https://www.codecreatorsinc.com/">Code Creators Inc</a>. I write about SharePoint and Microsoft 365. You can check out my team’s managed SharePoint work at Code Creators.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69eef63255ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SharePoint Copilot Readiness: What I Fix Before Anyone Gets a License]]></title>
            <link>https://medium.com/@george_21432/sharepoint-copilot-readiness-what-i-fix-before-anyone-gets-a-license-7c36db38ec51?source=rss-09d94389103e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c36db38ec51</guid>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[copilot-readiness]]></category>
            <dc:creator><![CDATA[Wasif Ali]]></dc:creator>
            <pubDate>Sat, 31 Oct 2026 21:56:20 GMT</pubDate>
            <atom:updated>2026-10-31T21:56:20.487Z</atom:updated>
            <content:encoded><![CDATA[<p>Copilot follows SharePoint permissions exactly, which is why it exposes oversharing that was already there. Here is what I fix before the first licenses go out, what continues during the pilot, and why the work keeps going after rollout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q0pK6iO2QyBFAbflqV8UYw.jpeg" /></figure><p>A pilot user types a simple question into Copilot: what were last year’s bonus figures? Copilot answers, and cites a spreadsheet on an HR site the user had never visited. Nobody broke in. The HR site holding it had been open to “Everyone except external users” for three years, and Copilot simply found the file.</p><p>Some version of that moment comes up in most Copilot pilots I support. It is the heart of SharePoint Copilot readiness. <a href="https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-privacy">Copilot only surfaces organizational data that a user can already view</a>, using the same access controls as the rest of Microsoft 365. What changes is effort. Before Copilot, finding an overshared file meant knowing where to look. With Copilot, it takes one question in plain language.</p><p>So the useful question before a rollout is what your users can already open. Below I cover how to tell an environment needs work, what I fix before the first licenses and what can continue during the pilot, the Microsoft tools that help, and how to keep things clean once Copilot is live.</p><h3><strong>What Changes When Copilot Arrives</strong></h3><p>Copilot works on behalf of the signed-in user. When it grounds an answer in your content, the <a href="https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-privacy">Semantic Index honors that user’s access boundary</a> and draws only on content the person is authorized to see. Files encrypted with sensitivity labels follow the usage rights the label grants. That design is sound. The risk sits in the gap between what people can open and what they should open.</p><p><strong>Before Copilot</strong></p><p>Oversharing was real and quiet. A folder shared with the whole company sat three clicks deep on a site most people never visited. Search could surface it, but few people searched for salaries or board minutes, and fewer scrolled past the first page of results. Obscurity did a lot of unofficial security work.</p><p><strong>With Copilot</strong></p><p>Copilot reads across every site a user can reach, summarizes what it finds and cites the source. A question about restructuring plans, a client’s fees or a colleague’s review draws on whatever that user can open, wherever it lives. The permissions are identical. The distance between a user and an overshared file shrinks to a single prompt.</p><p>That is why I describe Copilot to clients as the most thorough permission audit they will ever run, and also the most public one.</p><h3><strong>Five Signs Your Environment Needs Work First</strong></h3><p>None of these are exotic. I find most of them in nearly every tenant that has used SharePoint and Teams for a few years.</p><ul><li><strong>Sites Nobody Owns.</strong> Teams created for projects that ended, and sites whose owners have left. Nobody reviews membership or sharing on them, so access only ever grows, and there is nobody to ask when something looks wrong.</li><li><strong>Access Granted to Everyone.</strong> “Everyone except external users” added to a team site to stop a run of access requests, or a Microsoft 365 group created as Public, which puts that same claim in the site’s members. Both quietly turn a team space into a company-wide one, and Copilot treats it that way.</li><li><strong>Sharing Links That Outlived Their Purpose.</strong> Links created for one meeting or one reviewer years ago, many with no expiration date. Each one is a small permanent exception, and a busy library can hold thousands of them.</li><li><strong>Content With No Clear Current Version.</strong> Three copies of the travel policy on three sites, a pricing sheet from 2021 next to this year’s, folders full of “final_v4” drafts. Copilot answers only as well as the content it draws on, so stale content produces confident, outdated answers.</li><li><strong>Sensitive Files With No Label.</strong> HR, finance and legal content that relies entirely on site permissions for protection. Without sensitivity labels, a single permission mistake exposes it completely.</li></ul><h3><strong>What I Fix Before the First Licenses Go Out</strong></h3><p>On a recent readiness review for a professional services firm of about 400 people, the tenant held roughly 1,200 sites. The site permissions baseline report showed around 90 of them granting access to “Everyone except external users,” about 300 had no active owner, and one finance library alone carried several thousand sharing links. None of it was malicious, and most of it was years old. We spent 3 weeks on the must-fix items before the first 50 licenses went out. By the end of the pilot, about two-thirds of the site owners we contacted had completed their site access reviews; we had archived roughly 250 inactive sites, and the pilot group had raised no cases of content they should not have seen.</p><p>That project followed the rule I now apply everywhere. Three things must be finished before the first license: the broadest exposure is fixed, the most sensitive sites are protected, and every site the pilot group can reach has been reviewed. Everything else, from the long tail of old sharing links to content cleanup in quieter departments, continues during the pilot.</p><p>The work runs in three passes.</p><ul><li><strong>Permissions.</strong> I fix the broadest exposure first, sorted by how sensitive the content is: a public site holding the canteen menu can wait, and a public site holding salary reviews cannot. Sensitive libraries also get a sensitivity label. I agree the label set with the compliance team in Microsoft Purview, and a SharePoint site admin can then set a <a href="https://learn.microsoft.com/en-us/purview/sensitivity-labels-sharepoint-default-label">default label on each HR, finance and legal library</a> so new and edited files pick it up automatically. It does not label files already sitting in the library, so existing content needs an auto-labeling policy or a manual pass.</li><li><strong>Ownership.</strong> Every active site gets at least two named owners, and sites with no owner and no recent activity are archived.</li><li><strong>Content Quality.</strong> Each department names the authoritative location for its key documents and archives the older copies. Clients are most tempted to skip this step, and users notice it first, because it decides whether Copilot’s answers are current.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xq-3OYB4AK5tYap_06a-Qg.jpeg" /></figure><h3><strong>Microsoft’s Tools, and the One I Use First</strong></h3><p>Microsoft has put most of the readiness tooling into SharePoint Advanced Management. Licensing used to be a barrier, but <a href="https://learn.microsoft.com/sharepoint/sharepoint-advanced-management-features-copilot-license">if you assign at least one Copilot license, SharePoint admins get the SharePoint Advanced Management features that support a Copilot deployment</a>.</p><p>The image below shows which feature fits which problem. The ones I lean on most are the data access governance reports, site access review, and the site ownership and inactive sites policies. You will find the reports in the SharePoint admin center under <strong>Reports &gt; Data access governance</strong>.</p><p>The tool I open first is the <a href="https://learn.microsoft.com/en-my/sharePoint/data-access-governance-site-permissions-report">site permissions baseline report</a>. It counts permissions across every site at a point in time, including permissions granted to “Everyone except external users,” and turns a vague worry about oversharing into a ranked list a steering committee can act on.</p><p>The reports have limits worth knowing. The <a href="https://learn.microsoft.com/en-us/sharepoint/data-access-governance-everyone-except-external-user-report">“Everyone except external users” activity report</a> lists the top 100 sites where content was shared with the whole organization in the past 28 days, so exposure created years ago never appears in it. <a href="https://learn.microsoft.com/sharepoint/site-access-review">Site access reviews</a> have their own weak spot: a review stays pending until the owner completes it, and owners of neglected sites are the least likely to respond. I always plan a second round of follow-up, and a fallback owner for sites where nobody answers.</p><p>Restricted SharePoint Search is on its way out. <a href="https://learn.microsoft.com/sharepoint/restricted-sharepoint-search">New enablement has been blocked since July 31, 2026</a>, and Microsoft’s message center post MC1395311 sets <a href="https://mc.merill.net/message/MC1395311">full retirement for January 31, 2027</a>. Microsoft names Restricted Content Discovery as its replacement, which keeps a site out of Copilot and organization-wide search while leaving its permissions unchanged.</p><p>My view on Restricted Content Discovery runs against how it is often promoted. It is the right emergency brake for a handful of genuinely sensitive sites that people still need to reach. Applied widely, it postpones the permission fix and makes useful content harder to find, so I use it sparingly and always with a date to revisit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RkXtGILs6Xxq8R688SLoRQ.jpeg" /></figure><h3><strong>A Readiness Checklist That Keeps Running</strong></h3><p>The checklist I hand clients has three parts: what must be done before the first licenses go out, what continues during the pilot, and what to repeat every quarter afterwards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAlWhX3uUIQcVPlOtG1jeA.jpeg" /></figure><p>The quarterly part matters as much as the rest. A tenant keeps changing after cleanup: new teams appear every week, projects end without anyone closing their sites, and people keep sharing files the quickest way they know. Agents built on SharePoint content inherit the same exposure, because <a href="https://learn.microsoft.com/sharepoint/manage-access-agents-in-sharepoint">their responses depend on each user’s permissions to the agent’s data sources</a>. A one-time cleanup starts drifting the moment it finishes, so I assign the quarterly review to named people and put it in the calendar before the rollout begins.</p><p>I learned the right order the hard way. On an early Copilot pilot, I gave licenses to 20 people in the sales team before reviewing the sites they could reach. Within the first week, one of them asked Copilot to summarize upcoming changes to the commission plan, and it answered from a draft on a finance site that had been open to the whole company for years. Nothing left the organization, but the draft was months from final, and it took a difficult week of conversations to settle the questions it raised. Since then, I review every pilot group’s sites first, and the licenses follow.</p><p>One more piece of advice goes against the usual caution. I do not wait for a perfect tenant before a pilot. Once the broadest exposure is fixed and the most sensitive sites are protected, I start a pilot with a small group whose work sits on sites we have already reviewed. Their questions show which content matters, and that shapes the rest of the cleanup better than any report.</p><h3><strong>Key Takeaways</strong></h3><ul><li>Copilot uses the access people already have, so Copilot readiness is largely permission work.</li><li>Fix the broadest exposure first, then pilot on reviewed sites while the wider cleanup continues.</li><li>Readiness lasts only with owners and a review cadence, because the tenant keeps changing.</li></ul><h3><strong>The Question I Get Asked The Most</strong></h3><p><strong>How long does a readiness review take?</strong></p><p>My rule of thumb for a mid-sized tenant is about 3 weeks for the assessment, and the must-fix items before the first licenses go out. The pilot then runs while the rest of the cleanup continues. Larger or older tenants take longer, mainly because of the number of site owners who need to be found and asked.</p><h3><strong>Where to Start</strong></h3><p>This week, open the SharePoint admin center, go to <strong>Reports &gt; Data access governance</strong>, and run the site permissions baseline report. Look for the sites flagged with “Everyone except external users” permissions. The sites at the top of that list are usually where your SharePoint Copilot exposure starts, and they are often the fastest fixes you will make.</p><p>If you have already rolled out Copilot, I would like to hear what it surfaced that surprised you. Share it in the comments.</p><p><strong><em>I’m Wasif Ali, a Microsoft 365 and SharePoint Solutions Expert and CTO at Code Creators. I write about SharePoint and Microsoft 365. My team’s Copilot readiness work is at </em></strong><a href="https://codecreators.ca/copilot-readiness-assessment/"><strong><em>Code Creators</em></strong></a><strong><em>.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c36db38ec51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why SharePoint Online Migrations Go Wrong After Cutover, and What I Decide First]]></title>
            <link>https://medium.com/@george_21432/why-sharepoint-online-migrations-go-wrong-after-cutover-and-what-i-decide-first-b3b5fb68897b?source=rss-09d94389103e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3b5fb68897b</guid>
            <category><![CDATA[sharepoint-migration]]></category>
            <dc:creator><![CDATA[Wasif Ali]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 23:12:48 GMT</pubDate>
            <atom:updated>2026-10-27T23:12:48.427Z</atom:updated>
            <content:encoded><![CDATA[<p>The hardest problems in a SharePoint Online migration show up in places the migration tool never touches. Here are the lessons from my projects, and the decisions I now make before a single file moves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zjacv4CCKr0Pf94S6eV4KQ.jpeg" /></figure><p>The Monday after a cutover is usually quiet until about ten o’clock. Then the messages start. A finance manager cannot find the folder she has opened every day for six years. A project lead can suddenly see a contracts library he was never meant to reach. Someone in operations asks, politely, when “the S: drive” is coming back. The migration report says every item transferred successfully, and it is right.</p><p>That gap between a clean report and a working organization is what this article is about. My team and I have run SharePoint Online migrations from file shares, from SharePoint on-premises, and between tenants after mergers. The tools have improved enormously. What still goes wrong is almost always about structure, people and decisions nobody made in time.</p><p>The timing makes this worth writing now. <a href="https://learn.microsoft.com/en-us/lifecycle/products/sharepoint-server-2019">SharePoint Server 2016 and 2019 reached end of support on July 14, 2026</a>, so many organizations are planning a SharePoint on-premises to online migration under some pressure. Microsoft’s documentation covers the mechanics well. These are the lessons I now build into every project.</p><h3><strong>Lesson 1: Permission Mapping Takes Far Longer than Anyone Plans For</strong></h3><p>Every project plan I have seen gives permissions a line or two. In practice they take more time than the data transfer itself. A few years ago I migrated an accounting firm of about 120 people from a single file server to SharePoint Online. Roughly 1.5 terabytes moved over one weekend. The permissions took 3 weeks.</p><p>File shares are the clearest example. A typical departmental share has grown for a decade: nested Active Directory groups, folders granted to individuals who left years ago, and the occasional Deny entry someone added to keep one person out of one folder. SharePoint works on a different model, so all of that has to be translated.</p><p>Microsoft is upfront about how the SharePoint Migration Tool handles this. <a href="https://learn.microsoft.com/sharepointmigration/understanding-permissions-when-migrating">It translates three file share permission types</a>: Read becomes Read, Write becomes Contribute, and Full Control stays Full Control. Special permissions such as Deny are not carried across, and any user without a matching account in Microsoft Entra ID falls back to the default permissions of the destination. Each of those rules is reasonable. Applied to ten years of folder-level exceptions, they produce a permission set nobody designed.</p><p>SharePoint on-premises sources bring the opposite problem. <a href="https://learn.microsoft.com/sharepointmigration/understanding-permissions-when-migrating">Unique permissions migrate item by item for users the tool can map</a>, while inherited permissions do not migrate at all. Years of broken inheritance and one-off shares can arrive in the new tenant largely as they were, now with Copilot able to surface anything a user can open.</p><p>A SharePoint tenant to tenant migration adds another layer, because every identity changes. Users, groups and guests all need a mapping from the old tenant to the new one, and two groups with the same name rarely have the same members.</p><p>What I do now is treat permissions as a design exercise before any mapping starts. I define the target model first: one audience per site, access through groups, and inheritance broken only at library level. Then I map old groups onto that model, run a pilot migration for one department, and have real users confirm they can reach what they need before anything else moves.</p><p>The surprise that catches most teams is how much of the old permission set belongs to people who no longer exist. On that accounting firm’s server, a large share of the named entries belonged to people who had already left, and every one of them needed a decision. The tool cannot map them, so they quietly disappear, and nobody can say whether anything important depended on them.</p><p>So before the first planning meeting, I run a simple report: every folder with an individual permission entry, the account, its access level, whether the account is still active, and when it last signed in. It changes the conversation from “copy the permissions” to “decide the permissions.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JPvc6-uZrezTRzhi9gGgQA.jpeg" /></figure><h4><strong>Lesson 2: Every File Share Carries Context the Tools Cannot See</strong></h4><p>Cutover feels like the finish line. The project team celebrates, the old system goes read-only, and the steering committee closes the item. In my projects, the first problems appear in week 1 and the last ones surface around week 12, long after the project team has moved on. They tend to arrive in waves:</p><ul><li><strong>Week 1: missing files and broken links.</strong> Shortcuts, linked workbooks and bookmarked paths stop working, and people ask where their folders went.</li><li><strong>By week 3: old habits.</strong> People who cannot find a file save a copy to their desktop or OneDrive, and others sync entire libraries to their laptops because it feels like the old drive.</li><li><strong>By week 6: governance gaps.</strong> Sites lose their project-era owners, users start sharing file by file, and search and Copilot begin surfacing content people did not know they could see.</li><li><strong>Around week 12: the old system.</strong> The read-only file share is still where some teams look first, and without a switch-off date it becomes the source of truth again.</li></ul><p>My rule of thumb is an 8-week hypercare period after every migration, with named people answering questions and a weekly review of sharing activity and new sites. That covers the first three waves. The fourth is handled by a firm switch-off date that everyone hears about in advance, and by site owners who are named and briefed before cutover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7uc_OlpteBchj4Ojexe4IQ.jpeg" /></figure><h3><strong>Lesson 3: The Real Work Starts After Cutover</strong></h3><p>Cutover feels like the finish line. The project team celebrates, the old system goes read-only, and the steering committee closes the item. In my projects, the first problems appear in week 1 and the last ones surface around week 12, long after the project team has moved on. They tend to arrive in waves:</p><ul><li><strong>Week 1: Missing Files and Broken Links.</strong> Shortcuts, linked workbooks and bookmarked paths stop working, and people ask where their folders went.</li><li><strong>By week 3: old habits.</strong> People who cannot find a file save a copy to their desktop or OneDrive, and others sync entire libraries to their laptops because it feels like the old drive.</li><li><strong>By week 6: governance gaps.</strong> Sites lose their project-era owners, users start sharing file by file, and search and Copilot begin surfacing content people did not know they could see.</li><li><strong>Around week 12: the old system.</strong> The read-only file share is still where some teams look first, and without a switch-off date it becomes the source of truth again.</li></ul><p>My rule of thumb is an 8-week hypercare period after every migration, with named people answering questions and a weekly review of sharing activity and new sites. That covers the first three waves. The fourth is handled by a firm switch-off date that everyone hears about in advance, and by site owners who are named and briefed before cutover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZMZYx2kR6t-3-FdWKCRyVw.jpeg" /></figure><p><strong>A Migration that Worked on Paper</strong></p><p>The scenario below is a composite. It combines patterns I have seen across several projects, and no single client went through all of it. Every problem in it, though, is one I have watched happen.</p><p>A professional services firm of about 300 people moved four terabytes from a single file server to SharePoint Online over one weekend. The pre-migration scan was clean, the transfer finished on schedule, and the error log held a handful of path-length issues that were fixed by Sunday night. By every technical measure, it was a success.</p><p>In week 1, the finance team’s monthly reporting broke. Their workbooks linked to each other through network paths that no longer existed, and rebuilding the links took three days at month-end.</p><p>In week 2, a junior employee opened a folder of HR investigation notes. On the file server, a Deny entry had kept general staff out of that one subfolder. The entry did not migrate, so the folder inherited the library’s permissions and everyone in the department could read it.</p><p>By week 6, several partners had stopped using SharePoint for client work. The old structure sorted folders by client code, and the new libraries organized the same content by practice area. People could not find anything, so they went back to the read-only share and emailed attachments to each other.</p><p>The fixes were straightforward once the problems were visible: relinking the workbooks, a permission review on every library holding sensitive content, and a reworked structure designed with the partners. What made them costly was timing. Each one was discovered by users in production, weeks after the project team had handed over.</p><p>Every one of these problems traced back to a decision that was never made: who would find and fix the hidden dependencies, how sensitive content would be protected, and how people actually navigated.</p><h3><strong>The Tools I Reach For, and Where they Stop</strong></h3><p>None of those problems would have been solved by a different tool, but the choice of tool still matters.</p><p>For file shares, I start with Microsoft’s own options. The SharePoint Migration Tool is free and works well for a handful of shares run from one machine. Once a project has dozens of shares, I switch to <a href="https://learn.microsoft.com/sharepointmigration/mm-get-started">Migration Manager</a> in the SharePoint admin center, which spreads the work across agents installed on several servers and gives one view of progress and reports. Both stop at the same point: they move content and translate permissions by rule, and the redesign is left to you.</p><p>For SharePoint on-premises sources and any SharePoint tenant to tenant migration, I usually recommend a third-party tool such as ShareGate or AvePoint. The license adds cost, and in return you get deeper pre-migration reporting and far more control over how permissions are remapped. My view is simple: if the source carries more than a few years of custom permissions, the paid tool pays for itself in the permission work alone.</p><h3><strong>What I Decide Before a Single File Moves</strong></h3><p>A typical SharePoint migration checklist starts with inventory, tools and scheduling. Those matter, and Microsoft documents them well. Mine now starts with seven decisions, because each one prevents a problem I have watched surface after cutover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHmfDQLg14J190iYUV6tDw.jpeg" /></figure><p>Three of them do most of the work: the target permission model, the hidden dependencies, and a firm end date for the old system. Settle those early and the rest of the plan becomes much easier to agree.</p><p>One piece of advice surprises clients more than any other. I often tell them not to migrate their largest share as it is. When most of a share has not been opened in years, I move the active content, leave the rest read-only in an archive with a clear way to request files, and design the new structure around what people actually use. Everyone starts out wanting everything moved. Very few people ask for the archive once the new environment works.</p><p>If I had to reduce all of this to one rule, it would be this: decide what the new environment should look like first, then move content into it. Otherwise a SharePoint Online migration simply moves the old mess to a new address.</p><h3><strong>Key Takeaways</strong></h3><ul><li>Most migration trouble comes from permissions, structure and habits, and each needs design work before any content moves.</li><li>Problems arrive in waves from week 1 to around week 12, so plan support well beyond cutover.</li><li>Measure success by whether people can work in the new environment, which a clean transfer report cannot show.</li></ul><h3><strong>The Question I Get Asked Most</strong></h3><p><strong>How long does a SharePoint Online migration take?</strong></p><p>The data transfer is usually the shortest phase. A prepared file server can move over a weekend. Discovery, permission design and structure work typically take several times longer, and hypercare adds another 8 weeks. When people ask me for a timeline, I estimate the decisions first and the copying last.</p><h3><strong>Where to Start</strong></h3><p>If a migration is on your roadmap, start by booking an hour with the three heaviest users of your largest file share and asking them to walk you through a normal week. What you learn will shape your plan more than any scan.</p><p>If you have run a migration that looked perfect on paper and still went sideways, I would like to hear what surprised you. Share it in the comments.</p><p><em>I’m Wasif Ali, a Microsoft 365 and SharePoint Solutions Expert and CTO at Code Creators. I write about SharePoint and Microsoft 365. See how my team approaches </em><a href="https://www.codecreators.ca/sharepoint-migration/"><em>SharePoint migration </em></a><em>on Code Creators.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3b5fb68897b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SharePoint Permissions: What Goes Wrong and How I Fix It]]></title>
            <link>https://medium.com/@george_21432/sharepoint-permissions-what-goes-wrong-and-how-i-fix-it-42aaf83f4625?source=rss-09d94389103e------2</link>
            <guid isPermaLink="false">https://medium.com/p/42aaf83f4625</guid>
            <category><![CDATA[microsoft-copilot]]></category>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[sharepoint-online]]></category>
            <category><![CDATA[sharepoint-permission]]></category>
            <category><![CDATA[sharepoint-development]]></category>
            <dc:creator><![CDATA[Wasif Ali]]></dc:creator>
            <pubDate>Mon, 12 Oct 2026 23:27:45 GMT</pubDate>
            <atom:updated>2026-10-12T23:27:45.488Z</atom:updated>
            <content:encoded><![CDATA[<p>Copilot can surface anything a user is able to open, which turns years of quiet permission sprawl into a live exposure risk. Here is how I audit it safely and the group-based model I recommend.</p><p>A typical department site I am asked to look at was built for about 40 people. By the time I see it, it often carries well over 1,000 unique permission scopes, and the owner cannot tell me who can open the payroll folder.</p><p>Nobody made a bad decision. SharePoint permissions go wrong through accumulation: hundreds of reasonable exceptions pile up, and nobody reviews the total.</p><p>For years that was mainly an administration headache. Microsoft 365 Copilot raises the stakes, because it can draw on any content a user is able to open. A team site that quietly grants access to “Everyone except external users” is a site whose contents can appear in anyone’s Copilot answers.</p><p>Below I cover how the sprawl forms, the two concepts behind it, how I audit a site without locking anyone out, and the model I recommend.</p><h3><strong>Why a Small Site Ends Up with Hundreds of Unique Permissions?</strong></h3><p>A new site has one set of permissions. Owners, Members and Visitors sit at the top, and everything beneath inherits from them. Every exception after that creates a separate scope that has to be managed on its own.</p><p>Four everyday actions produce almost all of them: sharing a folder directly with an auditor or contractor, restricting a sensitive folder to a few named people, sending a “Specific people” link to a single file, and adding a new joiner by name to the folders their predecessor had.</p><p>The file link does the most damage, because people do it constantly and never see the result. Each link on an individual file gives that file its own scope. As a rough illustration, a team sharing two files a week would create about 300 unique scopes over three years, before counting folders.</p><p>The site keeps working throughout, so nobody steps in. The cost arrives later: former contractors who still have access, new hires who need a string of access requests before they can work, and owners who avoid changing anything for fear of locking someone out.</p><p>When I started doing these audits, I assumed the deliberately locked folders would make up most of the unique permissions. In practice they are usually a small share. Most of the count comes from individual files that someone shared once, often years ago, and nobody looked at again.</p><h3><strong>SharePoint Permission Levels and Inheritance</strong></h3><p>Every permission answers three questions: who (a person or group), what (a permission level), and where (a site, library, folder or item).</p><p>SharePoint permission levels are named bundles of rights, and four of them cover nearly everything I see. Full Control lets Owners manage everything, including permissions. Edit, the Members default, covers adding, changing and deleting files as well as creating and removing lists and libraries. Contribute allows the same file work inside existing lists and libraries, which suits sites where the structure should stay fixed. Read, the Visitors default, allows viewing and downloading.</p><p>I advise against custom permission levels. I have yet to see one that a well-named group with a standard level could not replace, and each custom level is one more thing the next administrator has to decode.</p><p>You will also meet Limited Access in every audit. SharePoint assigns it automatically when someone has access to a single item and needs to pass through the site to reach it. A long list of Limited Access entries points to item-level sharing, and it usually clears once that sharing is cleaned up.</p><p>Inheritance is the “where.” Permissions flow downward by default: site to library, library to folder, folder to file. Change the Members group once and the change applies everywhere.</p><p>The “Stop inheriting permissions” command copies the parent’s permissions at that moment and detaches the item. This is the part most site owners miss. Membership changes inside a group the item still references carry through. A new group or person granted access on the site never reaches the item, and anyone granted access directly on it keeps that access until someone removes them by hand.</p><p>A fully inherited site has one place to manage. A site with 200 broken-inheritance points has 201.</p><h3><strong>The Three Causes I Find In Almost Every Audit</strong></h3><p><strong>Broken inheritance deep in the folder tree</strong></p><p>Breaking inheritance is a legitimate feature, and the level where you use it decides whether it stays manageable. A unique scope on a library is visible and easy to govern. One on a subfolder four levels down goes unnoticed until it causes a problem. Most of it is unintentional, because sharing a file or folder with specific people breaks inheritance on that item behind the scenes, and the Share dialog gives no hint of it.</p><p>Scale is a factor too. <a href="https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits">Microsoft supports</a> up to 50,000 unique permission scopes per list or library and recommends staying under 5,000. Libraries near those numbers become slow to load and slow to administer.</p><p><strong>Permissions Assigned To Individuals</strong></p><p>A named assignment stays tied to one person. When that person changes role, their group memberships update in one place and their individual assignments stay where they were, while their replacement spends months requesting access piece by piece. Named assignments also hide intent. “Finance Managers: Edit” tells me why access exists. A person’s name with Edit beside it only tells me someone once thought they needed it, and I have to go and ask.</p><p><strong>“Everyone Except External Users”</strong></p><p>This built-in claim covers every internal account in the tenant, which makes it right for a company intranet or a policy library. It becomes a problem when an owner adds it to a team site to settle a run of access requests, or when a Microsoft 365 group is created as Public, which places it in the site’s Members group with edit rights. Nothing looks broken afterwards, so it persists, and the site’s content flows into everyone’s search results and Copilot answers. If your organization is preparing for Copilot, this is the first setting I would check.</p><h3><strong>How I Audit A Site Without Locking Anyone Out</strong></h3><p>The concern I hear most is that a cleanup will lock out someone important. My process is built to prevent that: read everything first, change things second, and add the new route to access before removing the old one.</p><p><strong>Step 1: Take An Inventory</strong></p><p>I start under Settings &gt; Site permissions &gt; Advanced permissions settings. Where unique permissions exist, a yellow banner offers a “Show these items” link that lists the affected lists and libraries.</p><p>For external sharing, the “Shared with external users” report under Site usage exports the details to a CSV. It covers external shares only, so it will not show internal links. For a complete view of one or more sites I use a PnP PowerShell script that returns every list, library, folder and file with unique permissions, along with who holds access.</p><p>For a tenant-wide view of oversharing, the data access governance reports in the SharePoint admin center, part of SharePoint Advanced Management, are the better fit. Whatever the tool, I keep the export as the baseline and the rollback record.</p><p><strong>Step 2: Sort Every Unique Scope</strong></p><p>I use three categories. Intentional and current scopes, such as a payroll folder limited to two roles, stay, and their individuals move into a group. Intentional and stale scopes, such as a folder shared with an auditor whose engagement has ended, come out once the site owner confirms. Accidental scopes, such as single files with leftover sharing links, return to inheritance.</p><p>The accidental category is usually the largest, and for site members restoring inheritance changes nothing, because they already have access through the site. The exception is anyone who reached an item only through a direct share or a link, often an external guest. They lose access when inheritance returns.</p><p><strong>Step 3: Confirm Who Relies On Each Scope</strong></p><p>This applies to all three categories. For accidental items, I first look for direct or external shares in the item’s Manage access panel or in the export. For the rest, Check Permissions shows what a named person can reach and where it comes from, and the Microsoft Purview audit log shows whether they have opened the content recently. I treat a year without use as a strong case for removal. The site owner answers what no report can, such as whether the auditor returns every January.</p><p><strong>Step 4: Build The New Route First</strong></p><p>For each scope I keep, I create or select a group, add the right people, and grant the group access. The individual entries come out afterwards, so people briefly hold access two ways and at no point hold none.</p><p><strong>Step 5: Change In Small Batches</strong></p><p>I work one library at a time, announce each change in advance, and leave a few working days between batches, so any missed dependency surfaces while the change is recent and easy to trace. One caution: “Delete unique permissions” removes everything specific to the item, sharing links included, so confirm its category before using it.</p><h3><strong>SharePoint Permissions Best Practices I Follow</strong></h3><p>Everything I recommend rests on one principle: permissions belong to groups, and people belong to groups. Access changes by editing membership, and the permissions themselves stay still.</p><ul><li><strong>Three groups per site.</strong> Owners, Members and Visitors cover most sites. On group-connected sites, manage Owners and Members through the Microsoft 365 group so Teams, Planner and SharePoint stay aligned.</li><li><strong>Every assignment goes to a group.</strong> When none fits, create one whose name states its purpose, such as “Finance — Payroll Editors.”</li><li><strong>Standard permission levels only.</strong> Full Control, Edit, Contribute and Read cover nearly every case.</li><li><strong>At least two owners per site.</strong> A single owner on leave stalls every access request.</li><li><strong>Different permissions mean a different library.</strong> If a folder needs different permissions from the rest of its library, give it its own library, or its own site when the audience is clearly different. A separate HR Confidential site is far easier to govern than a locked folder inside a general HR site.</li><li><strong>Broader group access over one more unique scope.</strong> I would rather give someone slightly broader read access through an existing group than create a new unique scope for them, unless the content is genuinely sensitive.</li><li><strong>Sharing links for one-off access only.</strong> They suit short-lived access, as long as they expire and standing access runs through groups.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OzFdPX89EbI3-u0D53R4jA.jpeg" /></figure><h3><strong>Keeping It Clean Afterwards</strong></h3><p>Three light routines keep a cleanup from unravelling. Twice a year, each site owner confirms group membership and reviews any unique scopes; Microsoft Entra access reviews and SharePoint site access reviews can automate the reminder and the sign-off. In the SharePoint admin center, set the default sharing link to “Specific people” or “People with existing access,” with an expiration on guest access. And a one-page owner guide that says which group to use for which request prevents most new sprawl, because owners want to do the right thing and simply need it spelled out.</p><h3><strong>Key Takeaways</strong></h3><ul><li>SharePoint permissions sprawl through small exceptions, and Copilot now surfaces whatever that sprawl exposes.</li><li>A safe audit reads first, sorts every unique scope, and adds the group route before removing the old one.</li><li>Groups over individuals, inheritance broken only at library level or higher, and a twice-yearly review keep it maintainable.</li></ul><h3><strong>Questions I Get Asked</strong></h3><p><strong>What are the different types of permissions in SharePoint?</strong></p><p>SharePoint grants access through permission levels, which are named bundles of rights. The standard ones are Full Control (manage everything, including permissions and settings), Edit (add, change and delete content, plus create and remove lists and libraries), Contribute (add, change and delete content within existing lists and libraries) and Read (view and download). SharePoint also assigns Limited Access automatically when someone has been given a single item and needs to pass through the site to reach it. Any of these can be granted at the site, library or list, folder, or individual item level. By default, each site’s Owners, Members and Visitors groups get Full Control, Edit and Read.</p><p><strong>What does “stop inheriting permissions” mean?</strong></p><p>By default, every library, folder and file takes its permissions from the level above it. “Stop inheriting permissions” breaks that link for one item: SharePoint copies the parent’s current permissions onto it, and from then on the item is managed on its own. Membership changes inside groups it still references carry through, but anything new granted at the site level never reaches it. To undo it, use “Delete unique permissions,” which returns the item to its parent’s permissions and removes anything granted directly on it, including sharing links.</p><p><strong>Is SharePoint going away in 2026?</strong></p><p>No. SharePoint Online is part of Microsoft 365 and continues to be developed. What ended on July 14, 2026 was <a href="https://learn.microsoft.com/en-us/lifecycle/products/sharepoint-server-2019">support for the on-premises SharePoint Server 2016 and 2019</a>. Those servers still run, but they no longer receive security updates. Organizations still on them can move to SharePoint Online or to SharePoint Server Subscription Edition. I treat a migration as the right moment to rebuild permissions on a group-based model, because copying old permissions across simply moves the sprawl with them.</p><h3><strong>Where to Start</strong></h3><p>Pick one site this week. Open the advanced permissions page, click “Show these items,” and note the count. That number is your baseline, and the five steps above will bring it down one library at a time. The standard I aim for is a site where the owner can answer “who can see this?” in under a minute.</p><p>If you have untangled a site like this, tell me what you found in the comments.</p><p>I’m Wasif Ali — a Microsoft 365 &amp; SharePoint Solutions Expert and CTO at Code Creators. I write to share about my expertise and experience in SharePoint and Microsoft 365 governance. If you want to learn more about my and my team’s work, then check out our <a href="https://www.codecreatorsinc.com/sharepoint-consulting/">SharePoint consulting</a> services.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42aaf83f4625" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>