How to make a loop component bigger, expanded - I want the full table to show but some columns are hidden and I have to scroll to get to them

Tomic, Mijat 0 Reputation points
2026-01-14T21:35:42.18+00:00

When you have a table embedded directly on a Loop page, Microsoft Loop provides an "expand" arrow functionality that allows you to view all columns of that table, even if some columns extend beyond the visible area. This expansion feature helps you navigate wide tables without losing context or having to scroll horizontally.

However, when you move that same table into a Loop component, this expand arrow functionality is no longer available. The Loop component has a more constrained viewing experience, and users lose the ability to easily expand and view all columns in the same way they could on the full Loop page.

This limitation means that:

  • On Loop pages: Tables are more interactive with built-in expansion controls for better column visibility
  • In Loop components: Tables have reduced functionality, making it harder to work with wide tables that have many columns

Moved from: Microsoft 365 Insider | Loop | Windows

Microsoft 365 and Office | Loop | Other
Microsoft 365 and Office | Loop | Other

A collaborative workspace app in Microsoft 365 designed to help teams co-create, stay organized, and work together in real time across apps and devices.

0 comments No comments

1 answer

Sort by: Oldest
  1. Kai-H 26,760 Reputation points Microsoft External Staff Moderator
    2026-01-15T09:47:01.5033333+00:00

    Hi, Tomic, Mijat

    Welcome to Microsoft Q&A forum.

    Thanks for your question. Currently, a table on a full Loop page can use the page’s wider canvas and “expand” controls, but the same table shared as a Loop component is rendered inside a fixed-width frame (Teams, Outlook, etc.), so the “expand to show all columns” experience is not available there.

    Here are some alternatives you can try:

    1) Open the component in the full Loop page view (best option)

    When you need to see everything at once, open the component in Loop instead of working inside the embedded frame. In most hosts you can use the component header menu (or copy the component link) to Open in Loop / Open in browser, then view and work with the table on the full page canvas.

    2) Keep the “key columns” visible by hiding or reordering columns

    If the component must stay embedded, a practical approach is to:

    • Move the most important columns to the left
    • Hide rarely used columns so the table fits without constant horizontal scrolling

    3) Zoom out to fit more columns on screen

    Not elegant, but it works quickly. In the host app or browser, reduce zoom (for example with Ctrl + mouse wheel) so more columns fit in the component frame.

    4) Split the table into two smaller tables (or a “summary” + “details” table)

    If you consistently have many columns, splitting usually makes the embedded experience much nicer:

    • Table A: the columns people reference all the time
    • Table B: the extra columns (linked from Table A with a row name or ID)

    5) Use row “detail view” for extra info instead of more columns

    If your extra columns are really “details per row,” consider moving them into the row detail pane, and keep the main table narrower for embedded viewing.

    6) Send feedback

    If the goal is “full-width / expand” inside components, it’s worth submitting feedback from Loop (Help > Give feedback). This is one of those areas where enough feedback tends to drive improvements.

    Hope this helps. Feel free to get back if you need further assistance.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment."    

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.