Modern Workplace

    Microsoft Loop: lists and pages, in sync and governed.

    With Loop your team keeps agendas, tasks and decisions together in chat, in email and in workspaces. Every edit appears at once wherever the content is shared.

    For teams that keep agendas, tasks and decisions together across chat, email and meetings, and whose IT wants to roll out Loop with rules.

    • Microsoft Loop
    • Copilot Pages
    • Microsoft Teams
    • Outlook
    • SharePoint Embedded
    • Microsoft Purview
    • Planner
    Laptop, phone and tablet on a lakeside café table show the same checklist, joined by dashed loops
    01

    Thursday, trade fair planning

    Thursday, trade fair planning is under way. A Loop task list sits in the marketing team's chat; everyone adds their part, and assigned tasks show up for the owners in Planner and To Do. The team lead pastes the same list into his email to the board; anything ticked off there is done in the chat too. The stand concept and budget decision sit in the channel's workspace.

    02

    From the list to retention

    Loop content appears in many places at once: in chat, in channels, in email, in the Loop app and from Copilot. We set Loop up with one team on its real work, agree storage and policies with your IT and hand over so that your team maintains templates and workspaces on its own. Which sharing the tenant allows in principle is set by Microsoft 365 governance; here we apply it to Loop.

    • Components in chat and emailAgendas, task lists, tables and votes straight in Teams and Outlook, edited by each person where they happen to be working; assigned tasks show up in Planner and To Do.Result: everyone edits the same list, wherever it has been pasted.
    • Workspaces and templatesA workspace in the channel whose members are set by the Microsoft 365 group, or a separate workspace in the Loop app for work across departments, with owners you appoint. Page templates for the weekly report, decision log or project profile are ready for every member.Result: whoever joins the work finds status and decisions in the same structure.
    • Copilot PagesAn answer from Copilot Chat becomes a page that your team keeps writing and shares as a component in chat or email.Result: a draft from Copilot becomes a shared document with history that stays after the chat.
    • Storage and policiesCloud Policy for workspaces, Copilot Pages and components in Outlook, the tenant setting for Loop in Teams, workspace containers in the admin center and guest sharing through the sensitivity label of workspaces created in the app.Result: your IT knows where each kind of Loop content lives and who may create new content.
    • Retention, labels and eDiscoveryRetention policies that also cover workspace containers, sensitivity labels for pages and components, eDiscovery search that reaches personal containers; periods and classes come from your compliance rules.Result: Loop content follows the same rules as the rest of your files.
    • Loop next to Planner and OneNoteA short rule per team on what goes into a Loop page, what becomes a task in Planner, a note in OneNote or a document in the library.Result: your team reaches for the right tool, and content lands where others look for it.
    03

    What your IT decides first

    A team with a running piece of work that tries Loop day to day, and one person who signs off the first page templates. From your IT, the decisions on who may create workspaces, whether guests take part and which sensitivity labels apply. Retention periods we take over from your existing rules for files.

    04

    What is in place after the rollout

    Cloud Policy and tenant settings for Loop, documented and active. A workspace for the pilot team with page templates, tested from the first task list to an eDiscovery search. Retention and labels for Loop content, agreed with your compliance team. A page for staff on when Loop, Planner or OneNote fits. Our support and operations team keeps track of new Loop features and policies from Microsoft for you.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: 9 October 2026

    • As of 14 May 2026

      Copilot Pages and My workspace share one container.

      Copilot Pages, Copilot Notebooks and My workspace in Loop live in the same personal SharePoint Embedded container, which appears in admin tools as the application «Loop». It is created as soon as either of the two Cloud Policies allows it; to prevent it, switch off both for the same person. Each shared workspace gets a container of its own.

      Source: Microsoft Learn: Overview of Loop storage
    • As of 6 July 2026

      Purview covers Loop, with two gaps for workspaces.

      eDiscovery, retention policies, sensitivity labels and DLP are supported for Loop. Information barriers apply to content in OneDrive and SharePoint and so far to no SharePoint Embedded container; deleted workspaces have no end-user recycle bin. Microsoft expects to let you pick the personal container directly as a custodian data source in eDiscovery in October 2026.

      Source: Microsoft Learn: Governance, lifecycle and compliance for Loop
    • As of 18 August 2026

      Loop components are leaving OneNote for the web.

      Since 1 September 2025 Loop components can no longer be inserted in Word for the web, and support in OneNote for the web ends from mid-September 2026. Existing components are kept: they turn into links to the Loop page and stay editable there. The OneNote desktop app for Windows keeps supporting Loop components.

      Source: Microsoft Learn: Requirements for Loop components and workspaces

    Before your team starts writing in Loop.

    Is Loop included in our Microsoft 365 subscription?

    According to Microsoft, Loop components need a OneDrive or SharePoint licence. Since February 2026 anyone with access to the Loop app who meets the storage requirements can create workspaces and manage members. Copilot Pages need an active OneDrive site, Copilot features in the Loop app a Copilot licence. We check your plans in the admin center before the start.

    Where does Loop content live?

    Where it is created. Components from chats, emails and OneNote sit in the OneDrive of the person who created them, components from a channel in the channel's files. Each shared workspace has its own SharePoint Embedded container, and My workspace shares a personal container with Copilot Pages. All of it counts towards your tenant's storage quota.

    Can we decide who creates workspaces?

    Yes. The Cloud Policy for Loop workspaces applies to everyone or to one group, Copilot Pages have a setting of their own, and components in Teams are switched by a setting for the whole tenant. Existing content stays accessible; access to it is governed by Conditional Access policies.

    Can partners work with us in Loop?

    Yes, if your organisation allows external sharing. Single pages, components and Copilot Pages can be shared with guests, whole workspaces with people who already have a guest account in your tenant. Whether a workspace from the Loop app admits external people is set by its sensitivity label, in a channel by the Microsoft 365 group. Whether your tenant shares externally at all is set in Microsoft 365 governance.

    What happens to Loop content when someone leaves the company?

    Components in OneDrive follow your OneDrive rule. The personal container with My workspace and Copilot Pages follows the same deletion process, with one manual step: access and notification for the successor are done by hand, and the container can be reassigned permanently to a new person. Shared workspaces remain; if all owners have left, IT appoints new ones.

    When do we use Loop, and when Planner or OneNote?

    Planner tracks tasks with dates and owners across a whole piece of work, OneNote collects notebooks with images and handwriting, Loop holds what several people edit at the same time. Assigned tasks from a Loop list show up in Planner and To Do, which keeps both tools connected. We record the rule per team on a single page.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.