SharePoint's 2026 Redesign: Prepare Before Help Desk Tickets Spike

Microsoft is rolling out the biggest SharePoint interface overhaul since the Modern Experience launched in 2017. The redesign, which started appearing in tenants during May 2026, changes the navigation structure, introduces Copilot-powered page creation, and adds new AI-driven web parts. Every employee who uses SharePoint daily will need to adjust to a new layout, and your IT team should plan for a temporary increase in support requests.

The changes roll out automatically through Microsoft’s standard update channel. You don’t choose when it hits your tenant. If you haven’t prepared your team, the first sign will be a Monday morning full of “SharePoint looks different” tickets. Here’s what’s changing, what to do about it, and how to communicate it to your employees before the update lands.

What’s Changing in the New SharePoint Experience

The redesign affects three areas that every SharePoint user touches daily.

Navigation and layout. The global navigation bar moves to a new position, site navigation gets a restructured menu, and the overall page layout uses updated spacing and typography. If your team has memorized where the “Documents” link sits or how to find the company intranet from the home page, those muscle-memory paths are about to break. The functionality is all still there, but it’s in different places.

Page creation. SharePoint now offers Copilot-powered page creation for tenants with Copilot licenses. Instead of starting from a blank page or a template, users describe what they want (“create a project status page with a timeline and task list”) and Copilot generates a draft. This is a genuine productivity improvement for teams that create SharePoint pages regularly, but it also means the “New Page” workflow looks completely different from what your team is used to.

New web parts. The update adds an AI Charts web part that generates data visualizations from natural language prompts, and a Citations Analytics feature that shows how often your SharePoint documents are referenced in Copilot responses across your organization. Citations Analytics is particularly useful for identifying outdated content that Copilot is still surfacing to employees, or finding gaps where employees are asking questions but no documentation exists.

What Requires a Copilot License and What’s Free

This distinction matters for budgeting. Not every feature in the redesign requires additional spending.

Free for all Microsoft 365 users (no Copilot license needed):

• The new navigation structure and updated UI
• Redesigned page editing experience (manual page creation still works without Copilot)
• Updated web part gallery and layout options
• Improved mobile experience

Requires a Copilot license ($30 per user per month at current pricing):

• AI-powered page creation (describe a page and Copilot builds it)
• AI Charts web part (natural language to data visualization)
• Citations Analytics (tracking which documents Copilot references)

If your organization already has Copilot licenses, your users get the full experience automatically. If you don’t, your team still gets the UI and navigation changes. The core SharePoint experience is changing for everyone regardless of license tier. The AI features are an optional layer on top.

For businesses evaluating whether Copilot is worth the per-user cost, the page creation and Citations Analytics features add concrete value for teams that build and maintain SharePoint content regularly. If your SharePoint is mostly a document repository where employees store and retrieve files, the free tier covers what you need.

Plan for the Help Desk Impact

Interface changes generate support tickets. This is predictable, temporary, and manageable if you prepare for it.

Based on patterns from previous Microsoft UI updates (the Outlook New Experience rollout is the most recent comparable example), expect help desk ticket volume to increase by 20% to 40% during the first two weeks after the redesign hits your tenant. The most common tickets will be:

• “Where did [feature] go?” (navigation changes)
• “The page I was editing looks different” (page creation workflow changes)
• “I can’t find my documents/sites” (reorganized site navigation)
• “What is this Copilot thing on my page?” (new AI features appearing for licensed users)

Most of these are five-minute conversations, not complex technical issues. The volume is the challenge, not the difficulty. A 200-person company using SharePoint daily might see 30 to 50 additional tickets in week one, dropping to near-normal levels by week three.

Two things reduce this significantly.

First, send a communication to your employees before the change arrives. A simple email explaining what’s different and where to find the three or four most-used features in the new layout prevents the majority of “where did it go” tickets. A template for this is included below.

Second, prepare a one-page quick reference guide showing the old navigation versus the new navigation with screenshots. Pin it to your company’s Teams channel or intranet. Employees will reference it themselves instead of submitting a ticket. This is standard change management work that pays for itself in reduced ticket volume.

Admin Preparation Checklist

IT administrators should complete these steps before the redesign reaches your tenant. Some require testing, so don’t wait until the week of rollout.

1. Review custom site templates and branding. If your organization uses custom SharePoint site templates, hub site configurations, or branded navigation elements, test them against the new experience. The redesign changes how navigation renders, which can break custom headers or menu structures. Microsoft provides a preview mode in the SharePoint admin center to test your sites before the change goes live.

2. Check third-party integrations. Any third-party web parts, apps, or workflows that interact with SharePoint’s UI layer need testing. Most modern SPFx (SharePoint Framework) web parts will work fine, but older add-ins or custom solutions built on legacy APIs may need updates.

3. Test internal workflows. If your team uses Power Automate flows triggered by SharePoint events, or if you have custom forms built with Power Apps embedded in SharePoint pages, verify they still function correctly in the new layout. The underlying APIs haven’t changed, but visual rendering and user interaction points may shift.

4. Audit your site structure. The redesign makes site navigation more prominent and structured. This is a good time to clean up orphaned sites, archive inactive team sites, and verify that your hub site hierarchy makes sense. A messy site structure becomes more visible in the new navigation model.

5. Update your Microsoft 365 security settings. The redesign introduces new sharing and permission prompts. Review your external sharing policies and guest access settings to make sure the new UI doesn’t expose sharing options you’ve intentionally restricted.

6. Prepare help desk staff. Brief your IT help desk team on the specific changes so they can handle tickets efficiently. A 15-minute walkthrough of the new interface for your support team saves hours of per-ticket research during week one.

Communication Template for Your Employees

Send this (or your own version) to all SharePoint users one week before the change reaches your tenant. Check your Microsoft 365 Message Center for your specific rollout date.

Subject: SharePoint Is Getting a New Look Next Week

Starting [date], SharePoint will have an updated interface. The same documents, sites, and content you use every day will still be there, but the menus and navigation will look different.

What to expect:

• The navigation menu has moved. Your sites and documents are in the same place, but the path to reach them looks slightly different.
• Creating new pages works differently. If you build SharePoint pages regularly, you’ll notice a new creation flow.
• Everything you’ve saved is still there. No files, pages, or sites have been removed.

If you get stuck: Check the quick reference guide pinned in [Teams channel / intranet location], or submit a help desk ticket and we’ll walk you through it.

This is a visual update, not a data change. Nothing has been moved or deleted.

Keep the message short and focused on what employees actually care about: where their stuff is and what to do if they can’t find it. Skip the feature announcements.

What to Do This Week

The rollout window is May through June 2026, and tenants are receiving the update on a rolling basis. Your specific timeline depends on your release channel configuration, but you may have as little as two weeks before the change appears.

Here’s the priority order:

1. Check your Message Center for your tenant’s rollout date. If you don’t see one yet, you likely have a few weeks, but don’t count on that.
2. Test the preview in your SharePoint admin center if available. Walk through your most-used sites and note what looks different.
3. Run through the admin checklist above. Custom templates and third-party integrations are the most likely to break.
4. Draft and schedule your employee communication. Send it one week before your rollout date.
5. Brief your help desk. Even 15 minutes of preparation cuts week-one ticket resolution time significantly.

If your internal IT team is already at capacity, a managed IT provider can handle the testing, communication, and help desk surge so the transition doesn’t pull your team away from existing projects.

The SharePoint redesign is not optional, and it’s not something you can delay at the tenant level. The only variable is whether your team is prepared when it arrives or scrambling after the fact. Fifteen minutes of admin review and one proactive email to your employees make the difference between a smooth week and a chaotic one.