Forum Discussion

BrigitteS's avatar
BrigitteS
Occasional Reader
May 14, 2026

Collapsible section icon alignment no longer respected – recent SharePoint change?

Hi all,

I’m looking to validate whether others are seeing a recent change to collapsible sections on modern SharePoint pages.

Across multiple communication sites in our environment, the expand/collapse icon is no longer rendering inline with the section heading, despite the settings being configured correctly (e.g. alignment set to “Right”).

Instead, the icon is now:

  • appearing below the heading
  • defaulting to the left-hand side
  • ignoring the alignment setting in the section properties

This change appears to have happened “overnight” and is consistent across all sites we’ve checked, not just a single page or site.

Impact

We rely heavily on collapsible sections for:

  • knowledge guides
  • FAQ-style content
  • onboarding materials

The current behaviour is:

  • increasing vertical spacing unnecessarily
  • reducing scan-ability of pages
  • creating inconsistency between existing and newly rendered content

It’s also causing confusion for content authors, as the settings no longer reflect what is displayed.

Questions

  • Is anyone else seeing the same behaviour across their tenant?
  • Has this been confirmed as a design change vs a bug?
  • Has anyone found a workaround or mitigation approach?

I have already raised this and upvoted it on the Microsoft Feedback Portal and would encourage everyone to do the same if they are experiencing this issue. I'd rather not have to change the design across multiple SharePoint site - an enormous amount of work.

Thanks!

1 Reply

  • virendrak's avatar
    virendrak
    Steel Contributor

    Microsoft is rolling out UI changes across Teams and SharePoint, and during these rollouts you may see weird, inconsistent, or half‑baked UI behavior. It seems like a UI glitch related to Microsoft’s ongoing SharePoint design rollout, and we expect it will be corrected once the update fully propagates.

    I noticed this exact issue last year during the Document Library UI rollout, and it resolved itself automatically after a few days.