Loop-sharing a workspace-shared within firm-yet still no access

Dear @Dermot O'Mahony,

First of all, please confirm that subscription of members having this issue has support for with Loop workplaces. Also, check the impacted users have needed subscription to use Microsoft Loop. Loop access via Microsoft 365 subscriptions - Microsoft Support

Microsoft Loop has a distinct “workspace link” flow: users click the link and become Pending Members, and then the workspace owner must Accept them:

• Go to the workspace member roster and look for a Pending Members section.
• If you see your MD / leaders listed there, select Accept (or Accept all). Join Loop workspaces with a link

In addition, please ask each impacted leader to:

Open the invite using an InPrivate/Incognito window, then sign in only with their work account (to avoid the browser auto-using a personal Microsoft account). (Best-practice suggestion; not from a Microsoft doc.)

• Alternatively, have them go directly to the Loop web entry point and check whether the workspace appears under their shared workspaces. It is noted users can access Loop content via Microsoft Loop.

If the issue persists, kindly contact your IT Admin to check if Loop is ready to use. Manage Loop in your organization | Microsoft Learn

I hope this fulfil your request, if it does not, please share more detailed information which I could help you efficiently.

As a moderator, I do not have the tools to investigate your specific account directly because this is a user-to-user support forum. Our role is limited to providing technical support on reported issues, requests, or ideas. However, I will try my best to clarify as clearly as possible.

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.

The most likely causes are licensing or admin policy preventing the invitees from using Loop workspaces, even though they receive the email.

Use these checks in order:

1. Confirm each leader has a supported Microsoft 365 plan for Loop workspaces
   Each invitee needs one of these plans on their work account to be able to create/manage workspaces and fully participate in them:
   • Microsoft 365 Business Standard or Business Premium
   • Microsoft 365 E3 or E5
   • Microsoft 365 A3 or A5
   • Microsoft 365 E3/E5/A3/A5 Extra Features (with a corresponding Office/Microsoft 365 plan)
   • Microsoft 365 Copilot
   Users with only an Office 365 E3/E5/A3/A5 plan do not get full Loop workspace capabilities. In that case, assign a qualifying Microsoft 365 plan or the Extra Features license.
2. Verify Loop workspace creation is not disabled by policy
   Ask the Microsoft 365 admin to check the Loop workspace configuration:
   • If workspace creation is disabled, users can still open existing Loop components, but:
     • They cannot create new workspaces.
     • Depending on configuration, they may not see or be able to join workspaces in the Loop app.
   When all Loop creations are disabled:
   • Users cannot create new Loop files or new SharePoint Embedded containers.
   • Existing workspaces and files remain accessible only if they already have permissions.
   If the admin has disabled workspace creation after initial enablement, existing workspaces remain visible to users who already had access, but new users may not be able to join or create workspaces. The admin should re‑enable workspace creation for the affected users or groups.
3. Confirm the invitees can open Loop at all
   Have one of the affected leaders:
   • Browse to the Loop app (loop.cloud.microsoft) while signed in with the same work account that received the invite.
   • If they cannot open the app or see any Loop content, this indicates either licensing or conditional access blocking Loop.
4. Check for tenant‑wide Loop disablement
   If the admin has disabled Loop components and/or Loop app experiences via cloud policy:
   • The create/insert entry points in Teams/Outlook are hidden.
   • .loop files only open as links in the browser.
   • Users can still edit existing .loop files if they have permission, but interactive components are limited.
   The admin should review those policies and ensure Loop is enabled for the leadership group.

Once licensing and policies are corrected, resend the workspace invitation and have the recipients open it in a browser while signed in with their work account.

References:

• Loop access via Microsoft 365 subscriptions
• Loop experience examples based on admin settings
• Overview of Loop components in the Microsoft 365 ecosystem