Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Some Microsoft Planner experiences create or rely on Microsoft Loop content. If you disable Loop for your organization, these experiences won't work as expected. Planner features that aren't listed in this article don't depend on Loop.
Loop access for Planner Agent
For Planner Agent experiences, Planner checks for Loop access as part of a user's Microsoft 365 Copilot license. Loop must also be enabled for the tenant.
Loop is managed through several admin settings. For the full list of settings and how to configure them, see Manage Loop in your organization.
Affected Planner user experiences
Tasks assigned to Planner Agent
Planner Agent creates task output as a Loop page in the plan's SharePoint folder. The output appears as a Loop component in the task details.
When you disable Loop for your organization, the option to assign tasks to Planner Agent remains visible to your users. However, assigning a task to the agent results in a generic execution error. Planner adds an Error label to the task card and moves the task to Needs Input.
Planner Agent status reports
Planner Agent status reports open in Loop and are stored in the plan's SharePoint folder.
When Loop is disabled, the Reports tab remains visible to your users, but reports fail to open or generate.
Tasks from Loop task lists
Loop task lists in Teams chat, Outlook, and the Loop app sync tasks to Planner and To Do.
When Loop is disabled, users cannot create Loop task lists, so no tasks sync into Planner from them. Tasks users create directly in Planner are not affected.
Tasks from Teams collaborative meeting notes
Teams collaborative meeting notes are built on Loop.
When Loop is disabled, tasks from these meeting notes do not sync into Planner.
Other policies that can block Loop content
Conditional Access policies and Outlook on the web mailbox policies can block Loop content for some people, even when Loop is enabled for your organization. If these policies block your Loop access, users will experience the same effects described above.