Cannot Remove Direct Access Permissions in Microsoft Loop: Fix & Solutions
Question details
The user is unable to remove direct access permissions for users who were added directly to a shared component page in Microsoft Loop.

- Product
- Microsoft Loop
- Device & OS
- not provided
- Scenario
- Attempting to manage user access and remove specific individuals from a shared component page.
- Observed behavior
- Direct-access permissions are unavailable or greyed out in Loop. Additionally, accessing SharePoint Advanced Settings to manage the file yields a File Not Found error.
Verify if the issue persists across different sessions by opening Microsoft Loop in a private or incognito browser window, and document the specific pages and user emails affected.
Report and Escalate the Known Microsoft Bug
Since this is a recognized backend issue affecting Microsoft Loop and SharePoint permissions, escalating it to Microsoft Support is the primary resolution path.
This behavior is an identified bug currently under investigation by the Microsoft SharePoint and Loop departments. Because the error stems from the Microsoft backend (producing File Not Found errors in SharePoint Advanced Settings), standard user-level permission changes are blocked.
Open a Private or Incognito browser window and log into Microsoft Loop. Attempt to remove the user's direct access to rule out local browser caching issues.
Take screenshots of the greyed-out permissions menu in the Microsoft Loop interface and the 'File Not Found' error displayed when accessing SharePoint Advanced Settings.
Navigate to the Microsoft 365 Admin Center. Go to the Support section and create a new service request, providing the screenshots, the backend error details, and the list of affected users to assist the investigation.

Manage Access via the SharePoint Backend (Alternative Check)
Attempt to bypass the Microsoft Loop interface by modifying the file permissions directly within the connected SharePoint site.
Looking for a Seamless and Bug-Free Collaboration Experience? Try WPS Office
If Microsoft Loop and SharePoint permission bugs are complicating your team's workflow, consider switching to WPS Office. It provides a robust, lightweight, and highly compatible workspace for document creation and sharing without the complex permission glitches.

Frequently Asked Questions
Why are direct access permissions greyed out in Microsoft Loop?
This is a known backend service issue affecting Microsoft Loop and SharePoint. When users are added directly to a shared component page, the system currently fails to load the appropriate removal options, leaving the permissions greyed out.
What does the 'File Not Found' error mean in SharePoint Advanced Settings?
This error is a symptom of the same permissions bug. When you attempt to manage access for the Loop component through the SharePoint backend, the server incorrectly fails to locate the component's underlying file, preventing you from modifying permissions.
Can I force remove a user from a Loop workspace if direct access is bugged?
If direct access removal is greyed out for a specific component, you cannot remove them from that component individually. As a temporary workaround, you can remove the user from the broader Microsoft 365 Group or SharePoint site, but this will revoke their access to the entire workspace.




