# Ensure that 'Users can create security groups in Azure portals, API or PowerShell' is set to 'No' .

- Source: https://support.icompaas.com/support/solutions/articles/62000219695-ensure-that-users-can-create-security-groups-in-azure-portals-api-or-powershell-is-set-to-no-
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Azure CIS Benchmark Level 1 & Level 2](https://support.icompaas.com/support/solutions/62000112163) › [1. Identity and Access Management](https://support.icompaas.com/support/solutions/folders/62000167544)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

[](https://docs.microsoft.com/en-us/azure/security/benchmarks/security-controls-v2-governance-strategy#gs-2-define-enterprise-segmentation-strategy "https://docs.microsoft.com/en-us/azure/security/benchmarks/security-controls-v2-governance-strategy#gs-2-define-enterprise-segmentation-strategy")**[](https://docs.microsoft.com/en-us/azure/security/benchmarks/security-controls-v2-governance-strategy#gs-2-define-enterprise-segmentation-strategy "https://docs.microsoft.com/en-us/azure/security/benchmarks/security-controls-v2-governance-strategy#gs-2-define-enterprise-segmentation-strategy")**

Description:

This setting controls whether regular users can create security groups in Microsoft Entra ID. When it is set to No, only administrators can create security groups. This prevents users from creating groups on their own without approval and helps maintain better control over group management in the organization.

  

Rationale:

Stopping users from creating security groups prevents unwanted or unapproved groups. This keeps group management controlled by administrators and reduces security risks.

  

Impact:

This setting improves security by making sure only administrators can create security groups. It prevents regular users from creating groups that may cause confusion or unauthorized access.

  

Default Value:

By default, Microsoft Entra ID allows users to create security groups. The setting must be changed to No if you want to restrict this.

  

Pre-requisites:

-   You must sign in with a Global Administrator or Privileged Role Administrator account.
    

  

Test Plan:

1.  Go to the Azure portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  In the portal, search for Microsoft Entra ID.
    
3.  In the left menu, under Manage, select Groups.
    
4.  Open the General under settings. Go to the Security Groups section.
    
5.  Find the “Users can create security groups in Azure portals, API or PowerShell.”
    
6.  Verify that this setting is set to No.
    

![](https://support.icompaas.com/assets/kb/c8f40eb619d461e2.png)

7.  If it is Yes, follow the implementation steps.
    

  

Implementation steps:

1.  Go to the Azure portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  In the portal, search for Microsoft Entra ID.
    
3.  In the left menu, under Manage, select Groups.
    

                                                 ![](https://support.icompaas.com/assets/kb/bb0af8a3c2ae0ff6.png)

4.  Click General under the Settings section.
    
5.  Go to the Security Groups section.
    
6.  Find the setting where Users can create security groups in Azure portals, API, or PowerShell. Change the toggle to No.
    

![](https://support.icompaas.com/assets/kb/403d976bad6b902b.png)

7.  Click Save at the top of the page to apply the changes.
    

  

Backout Plan:

1.  Go to the Azure portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  In the portal, search for Microsoft Entra ID.
    
3.  In the left menu, under Manage, select Groups.
    
4.  Click General under the Settings section.
    
5.  Go to the Security Groups section.
    
6.  Find the setting where Users can create security groups in Azure portals, API or PowerShell.
    
7.  Change the toggle to Yes.
    
8.  Click Save at the top of the page to apply the changes.  
      
    

Reference:

-   [https://learn.microsoft.com/en-us/entra/identity/users/groups-manage](https://learn.microsoft.com/en-us/entra/identity/users/groups-manage)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
