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.
For a Microsoft 365 Family (consumer) subscription, Loop access is limited compared to work/school (Microsoft Entra) accounts, and workspace creation can be affected by backend requirements and service limits.
The specific error text matches a known Loop issue:
“We couldn't save the Loop workspace and pages you've created.”
For personal Microsoft accounts (used with Microsoft 365 Family), the documented resolution is:
- Sign in to Outlook on the web once
- Go to outlook.com and sign in with the same Microsoft account used in Loop.
- This one-time sign-in allows Loop to set up everything it needs from Outlook/Exchange for that account.
- Return to Loop and try creating a workspace again
- After Outlook has initialized the needed backend, retry “Create new” → Workspace in Loop.
If using a work or school account instead of a pure personal account, the required conditions are:
- The account must have an Exchange Online mailbox (not a shared mailbox) and must have been signed into at least once.
- The account must have at least read access to the organization’s SharePoint Online root site.
If those conditions are not met, Loop cannot save workspaces and pages and will show the error being seen.
Note that:
- Loop components and basic Loop app access are broadly available, but full workspace capabilities and behavior differ between consumer and work/school plans.
- For work accounts, admins can also disable workspace creation via Cloud Policy (for example, disabling “Create Loop workspaces in Loop”), which would prevent new workspaces from being created even if the app is visible.
If signing into Outlook on the web once (for a personal account) does not resolve the issue, or if using a work/school account that may be missing an Exchange Online mailbox or SharePoint root access, contact the Microsoft 365 administrator or support to verify mailbox provisioning, SharePoint permissions, and any Loop-related admin policies.
References: