Overview
Restricts group creation to administrators with permissions only.
Rationale
Self-service group management enables users to create and manage security groups or Office 365 groups in Microsoft Entra ID. Unless a business requires this day-to-day delegation for some users, self-service group management should be disabled. Users can access the Access Panel to reset their passwords, view their information, etc. By default, users can also access the Group feature, which shows groups, members, and related resources (SharePoint URL, Group email address, Yammer URL, and Teams URL). By setting this feature to 'Yes', users will no longer have access to the web interface but still have access to the data using the API. This is useful to prevent non-technical users from enumerating group-related information, but technical users will still be able to access this information using APIs.
Impact
Setting it to Yes could create administrative overhead by customers seeking certain group memberships that will have to be manually managed by administrators with appropriate permissions.
Default Value
By default, Restrict user ability to access groups features in My Groups is set to No.
Manual Audit
There is no customer-facing API available to check this setting. Please refer to the Remediation tab.
After you ensure the setting is correctly set, exempt the corresponding asset.
If you need this checked automatically (it would make sense if you have multiple Entra ID tenants with multiple administrators who might change settings) and are willing to provide additional permissions, reach out to your Cyscale contact person.
Remediation guidance
From Azure Portal
- Open Groups | General
- Set
Restrict user ability to access groups features in My GroupstoYes.
Multiple Remediation Paths
SERVICE-WIDE (RECOMMENDED when many resources are affected): Apply organization/tenant-level guardrails and baseline policies for the entire platform.
ASSET-LEVEL: Fix only the affected resources identified by this control.
PREVENTIVE: Add preventive policy checks to CI/CD and periodic posture scans.
References for Service-Wide Patterns
- Platform policy/governance and preventive control patterns should be applied tenant-wide where supported.
Query logic
These are the stored checks tied to this control.
All Entra tenants
Connectors
Covered asset types
Expected check: eq []
{
connectors(where: {cloudProvider: "entra"}) {
...AssetFragment
}
}