SharePoint Copilot Component rendering displays excessive whitespace and unexpected scrolling in inline and expanded views

[ejazhussain]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• Microsoft 365 Copilot
• SharePoint Copilot Components
• Latest SPFx Copilot Component framework - 1.24.0-beta.2

Describe the bug / error

Issue

We have noticed a change in how SharePoint Copilot Components are rendered within Microsoft 365 Copilot.

The same component was rendering correctly previously, but is now displaying excessive empty space and unexpected scrolling in both inline and expanded views.

Expected Behaviour

• Component height should fit the rendered content appropriately.
• Inline view should not contain large unused areas.
• Expanded view should make effective use of the available space.
• Scrollbars should only appear when the content exceeds the available viewport.

Actual Behaviour

• Large areas of empty whitespace are displayed beneath the rendered content.
• Vertical scrollbars appear even when only a small amount of content is shown.
• The behaviour is visible in both inline and expanded component experiences.

Steps to reproduce

Steps to Reproduce

1. Deploy a SharePoint Copilot Component.
2. Open Microsoft 365 Copilot.
3. Render the component in the inline experience.
4. Expand the component.
5. Observe the amount of whitespace and scrolling behaviour.

Additional Notes

• This behaviour was not observed previously and appears to be a recent change.
• We have not identified whether the issue originates from the component itself or from the Copilot hosting/rendering experience.
• One possibility is that a fixed height or minimum height is now being applied by the host container, but this has not been confirmed.

Screenshots

Screenshots attached showing the behaviour in both inline and expanded views.

Inline view

Expanded view

Expected behavior

[Ashlesha-MSFT]

Hello Ejaz Hussain (@ejazhussain)
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.