Users who are creating Microsoft Loop Teams components
AI summary
Monitor users creating Microsoft Loop components in their OneDrive to understand usage patterns and prevent data sprawl. You can use this policy to provide guidance on appropriate use and implement governance that supports collaboration while protecting data. The rule identifies users with files having 'fluid' or 'loop' extensions.
What it detects
A list of users that are creating Microsoft Loop components in their OneDriveOneDriveOneDrive is the personal file storage of each Microsoft 365 user. The OneDrive connector of Rencore Governance, part of the Digital Workplace module, inventories every OneDrive with its files, folders and file sharing.Read more.
Why it matters
Microsoft Loop component creation in OneDrive requires oversight to ensure secure collaboration practices and prevent data sprawl across personal storage locations. Monitor Loop component creation through Rencore Governance to understand usage patterns, provide guidance on appropriate use cases and security best practices, and implement governance policies that balance collaborative innovation with data protection requirements.
The rule
Every User that has any Files where File Extension equals 'fluid' or File Extension equals 'loop'
FilesIn Rencore Governance
Details
| Applies to | User |
|---|---|
| Connector | Microsoft 365 |
| Severity | Medium |
| Category | Operation |
| Recommended | No |
| Recommended automation | None |
| License type | Standard |
Related policies
Other policies that check User objects:
- Copilot adoption opportunity - E3/E5 users (Medium)
- Copilot license assigned to disabled account (High)
- Inactive Copilot users - 30 days (Medium)
- Excessive draft agent creation pattern (Medium)
- External users (Information)
- External users with pending acceptance (Low)
- Users with Power Platform Premium license (Information)
- Users with E3 license not using Outlook in last 12 month (Low)
- Users with passwords not changed in last 6 months (Medium)
- Disabled user accounts (Medium)
- Admin accounts with an Office 365 E3 license assigned (Medium)
- Administrators without MFA (High)
- External users invited 3 month ago with pending acceptance (Low)
- Disabled user accounts with assigned licenses (High)
- Global administrators without MFA (High)
- Guest users with a Dynamics license assigned (Medium)
- Inactive external users (Medium)
- Inactive internal users (Medium)
- Over-licensed user accounts (High)
Frequently asked questions
What does the users who are creating Microsoft Loop Teams components policy detect?
What does the users who are creating Microsoft Loop Teams components policy detect?A list of users that are creating Microsoft Loop components in their OneDrive.
Which objects does the users who are creating Microsoft Loop Teams components policy check?
Which objects does the users who are creating Microsoft Loop Teams components policy check?The Users who are creating Microsoft Loop Teams components policy checks User objects from the Microsoft 365 inventory and reports each one that matches its rule as a violation.
How severe is a violation of the users who are creating Microsoft Loop Teams components policy?
How severe is a violation of the users who are creating Microsoft Loop Teams components policy?Violations of the Users who are creating Microsoft Loop Teams components policy have Medium severity. The policy is in the Operation category.
Which module includes the users who are creating Microsoft Loop Teams components policy?
Which module includes the users who are creating Microsoft Loop Teams components policy?The Users who are creating Microsoft Loop Teams components policy comes with the Microsoft 365 connector in the Digital Workplace module of Rencore Governance, which every Plan includes.
Was this page helpful?
Thanks for the feedback.
Thanks. What was wrong?