Microsoft will roll out a set of authoring improvements for SharePoint Pages in August 2026, including visual column guides, persistent gridlines, and a command to convert existing sections into Flexible Sections while retaining content placement. The changes, tracked under Roadmap ID 567889, aim to make free-form page design easier for everyday authors without sacrificing the predictable structure that enterprise intranets demand.

What’s Changing in SharePoint Pages

The update bundles three closely related authoring enhancements for Flexible Sections, the free-form canvas that lets page creators move web parts around a grid rather than being locked into rigid columns.

Visual column layout guides

Authors will see familiar column-based guides overlaid on the Flexible Section canvas. These guides resemble the predefined section layouts SharePoint already offers—one, two, or three columns—but don’t enforce permanent boundaries. Instead, they provide a recognizable starting point. An author can begin with a two-column arrangement, then resize or reposition individual web parts beyond those guides, blending template-driven authoring with free-form placement.

Persistent gridlines and layout aids

While editing a Flexible Section, gridlines and alignment aids will remain visible at all times. Previously, these cues could appear inconsistently, leaving authors to judge spacing and alignment by eye. Persistent visual feedback should reduce the trial-and-error of dragging components into place, helping writers, HR specialists, and departmental communicators maintain consistent gutters and avoid misalignments that make pages look sloppy.

One-click section conversion

The most significant change is a conversion command that turns any existing section into a Flexible Section while preserving where web parts sit. Today, if you want to modernize a conventional column-based section, you must create a blank Flexible Section, manually move or recreate every web part, reconfigure their settings, and delete the original. The new tool automates that process, retaining the visual relationships between components so that a two-column layout, for instance, translates its left and right items into corresponding grid positions. This makes Flexible Sections a practical upgrade path for established intranet pages, not just a starting-from-scratch feature.

Why This Matters for Your Team

For most organizations, SharePoint pages are built by people who aren’t professional designers. A human resources coordinator creating an onboarding portal, a project manager assembling a status dashboard, or an executive assistant publishing a monthly newsletter all need tools that balance creative control with guardrails. The current Flexible Section can feel like a blank canvas with no clear starting point. The new column guides give authors a structure they already understand from traditional sections, while the persistent gridlines reduce the guesswork that leads to messy layouts.

For content authors and publishers

The conversion command is a boon for anyone who maintains older pages. Instead of rebuilding a critical news post or departmental landing page from scratch to take advantage of free-form placement, you can convert it in one click and then selectively enhance the design—maybe widening a hero image, overlapping a decorative element, or breaking a single component out of its old column boundary. The ability to preserve content placement means you won’t lose hours of work; the resulting Flexible Section starts with your existing composition intact.

For intranet administrators and governance teams

Easier authoring doesn’t mean giving up control. The visual guides can actually help enforce design consistency because they give editors a shared reference point. Training becomes simpler: you can tell colleagues to align their web parts with the second guide or keep a standard gutter between regions. Conversion also lets organizations incrementally modernize high-visibility pages without a risky, full-intranet overhaul. However, the freedom to overlap and resize components means your design standards should still specify acceptable patterns, spacing, and mobile preview requirements.

For developers building SharePoint Framework web parts

Custom components designed for fixed columns may behave unexpectedly when placed on a flexible grid. The new conversion path adds a testing scenario: a web part that works fine when newly inserted into a Flexible Section might not translate perfectly when its original column context is converted. Developers should validate minimum and maximum widths, responsive behavior, and how their components handle overlap or stacking. With persistent gridlines now visible during editing, it will be easier to see how custom parts snap to the underlying layout system.

For everyday readers and employees

Most end users won’t notice the editing changes directly, but they will see the results. Better authoring tools, paired with good editorial judgment, lead to clearer pages. Flexible Sections allow designers to give more visual weight to a primary message—a large announcement, a key deadline, or a call to action—rather than presenting everything in equal columns that imply everything is equally important. The challenge is to use that flexibility for communication, not decoration, so that pages remain scannable and accessible.

How We Got Here: The Evolution of SharePoint Sections

SharePoint’s modern page experience has always balanced two goals: empowering ordinary employees to create polished content, and ensuring pages remain responsive, accessible, and manageable at enterprise scale. Traditional sections solved that with constraints. Authors pick a preset layout—one, two, or three columns—and drop web parts into those containers. SharePoint handles the dimensions and responsive behavior automatically.

Flexible Sections, introduced in 2023, removed those constraints by giving authors a two-dimensional grid. You can move web parts anywhere, resize them, overlap them, and group items visually. That freedom enables designs no conventional section can handle: asymmetrical campaign banners, dashboard-like statistics, or text laid over an image. But the trade-off is a steeper learning curve. Without column guides or persistent alignment cues, authors often struggle to judge spacing, alignment, and how a complex desktop layout will reflow on a phone or in an email.

The August 2026 update is Microsoft’s answer to that learning curve. It doesn’t expand what Flexible Sections can do; it makes the existing capabilities easier to use by borrowing concepts from the traditional section model. That’s a deliberate design strategy—extend a familiar mental model rather than forcing authors to learn a separate layout language.

What to Do Now to Get Ready

Even though general availability is nearly a year away, early preparation can save headaches later. The feature is planned for the Worldwide Standard Multi-Tenant cloud, with Targeted Release deployment preceding GA. Here’s how to hit the ground running:

  • Identify test pages. Choose a few representative sections that include a mix of web parts—text, images, Quick Links, People, dynamic lists, and any custom components. Pages with complex backgrounds, stacked web parts, or unusual column ratios will be more likely to surface conversion quirks.
  • Run a Targeted Release pilot. If your organization uses Targeted Release, designate a small group of authors to test the new guides and conversion command before broad rollout. Include communications pros, casual editors, accessibility specialists, and developers familiar with your custom web parts.
  • Audit existing web parts for responsive behavior. For custom components, check how they behave at minimum and maximum widths, how they reflow when the browser window narrows, and whether they work sensibly when placed next to native SharePoint web parts. Resize gracefully, or you’ll see clipping and overflow on the free-form grid.
  • Draft lightweight design standards. Determine acceptable patterns for Flexible Sections: which column guides to use for common page types, standard spacing between elements, when overlapping is okay (e.g., decorative banners) and when it isn’t, and a rule that mobile and email previews are mandatory before important news goes live.
  • Set versioning and recovery expectations. Before performing a mass conversion, remind authors that SharePoint’s page version history can restore a prior state if a conversion doesn’t translate well. Treat conversion as a reversible editing operation until you’ve validated critical pages.
  • Monitor Microsoft’s Message Center. The roadmap gives an August 2026 target, but tenant-specific deployment dates and any late-breaking changes will appear in Message Center posts. Updates may also appear in the techcommunity blog or Microsoft Learn documentation.

What’s Next: Beyond August 2026

The unanswered questions for now revolve around conversion fidelity and guide customization. How reliably will the one-click command translate complex sections—particularly those with custom web parts, uneven column widths, or intricate backgrounds? Will authors be able to choose among different guide patterns, adjust their ratios, or hide individual guides? The real-world experience of Targeted Release tenants will determine whether these tools reduce friction or introduce new edge cases.

There’s also a longer strategic thread. Microsoft has been expanding AI-assisted page creation, where Copilot can generate or restructure content. A more explicit grid system and recognizable layout guides could make AI-generated designs easier for humans to understand and tweak. Conversion, too, could fit into future workflows: take an existing conventional section, convert it to a Flexible Section, and then ask AI to propose alternative arrangements. That scenario isn’t part of Roadmap ID 567889, but the new conversion path makes it technically plausible.

For now, the August 2026 update represents a practical step forward. By giving Flexible Sections the visual cues of traditional layouts while preserving the grid’s creative potential, Microsoft is closing the gap between free-form design and predictable enterprise publishing. The result should be pages that are not only more expressive but also easier to build, govern, and maintain.