Manage who is allowed to create groups in Office 365

Currently, the use of Microsoft Teams for teaching around the world is continuously increasing. However, in the process of using teachers will also encounter a lot of annoying pedagogical situations, such as students setting up secret chat groups on it to do their own work ... But teachers should not be too worry Microsoft provides us with tools so that teachers may want to make this easier to control.

In this tutorial, we will set up allowing who is allowed to create groups on Microsoft Teams

To do this, teachers first need to have an Office 365 system administrator account of their school or unit

Step 1: Create a security group for users who need to create an Office 365 Group

 Important!

When using a  security group  to restrict who can create groups, you should also consider that this will not allow members outside the security group to create groups on the Office 365 sharepoint.

Perform

  • In the Microsoft 365 Admin Center , Select Groups > Groups.

Manage who is allowed to create groups in Office 365

  • Click Add a GroupManage who is allowed to create groups in Office 365
  • Select the Security group type -> Next

Manage who is allowed to create groups in Office 365

  • Name the group and click Next

Manage who is allowed to create groups in Office 365

  • Click Create a group to complete the security group setup, add people or other security groups that teachers want to be able to create groups in their school or unit.

Step 2: Run the above PowerShell command

Teachers need to make sure that Powershell is installed on the computer

Manage who is allowed to create groups in Office 365

Copy the script below into Windows PowerShell ISE .

Replace  SecurityGroupName >  with the name of the security group you created. For example:

$GroupName = "Group Creators"

Save the file as GroupCreators.ps1

In the PowerShell window , use the CD command to return to the folder where the teacher saved the GroupCreators.ps1 file (enter “CD”). Assuming that file is saved in the adminschool folder, drive D, the teacher will type the command as shown

Manage who is allowed to create groups in Office 365

Run the script by typing:

.\GroupCreators.ps1

Manage who is allowed to create groups in Office 365

Then you log in with your administrator account at the Powershell command prompt

$GroupName = "" $AllowGroupCreation = "False" Connect-AzureAD $settingsObjectID = (Get-AzureADDirectorySetting | Where-object -Property Displayname -Value "Group.Unified" -EQ).id if(!$settingsObjectID) { $template = Get-AzureADDirectorySettingTemplate | Where-object {$_.displayname -eq "group.unified"} $settingsCopy = $template.CreateDirectorySetting() New-AzureADDirectorySetting -DirectorySetting $settingsCopy $settingsObjectID = (Get-AzureADDirectorySetting | Where-object -Property Displayname -Value "Group.Unified" -EQ).id } $settingsCopy = Get-AzureADDirectorySetting -Id $settingsObjectID $settingsCopy["EnableGroupCreation"] = $AllowGroupCreation if($GroupName) { $settingsCopy["GroupCreationAllowedGroupId"] = (Get-AzureADGroup -SearchString $GroupName).objectid } else { $settingsCopy["GroupCreationAllowedGroupId"] = $GroupName } Set-AzureADDirectorySetting -Id $settingsObjectID -DirectorySetting $settingsCopy (Get-AzureADDirectorySetting -Id $settingsObjectID).Values

The last line of the script will show the updated settings:

Manage who is allowed to create groups in Office 365

If you later want to change which security group is used, you can run the above script again with the name of the new security group.

If you want to turn off the group creation limit and allow all users to create groups (including students, set $GroupName to “” and $AllowgroupCreation to “True” and run the above script again.

Step 3: Double check if it's already working?

  1. Sign in to Office 365 with a user account that isn't allowed in groups to create groups. 
  2. Select Teams
  3. In Teams, try to create a new group
  4. Teachers will receive a notification to disable the group creation function.

If there are any problems in the process of running the command on Powershell, please create a Ticket and send it to Microsoft's technical support for detailed support (because this is a newly updated feature, there is no many people have experience in this) or select Support in the Microsoft 365 Admin Center

Good luck teachers!

Leave a Comment

Enable FIPS Mode on SLES 15 and Verify the Boot State

Enable FIPS Mode on SLES 15 and Verify the Boot State

Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.

Set Up a LUKS-Encrypted Data Volume on SLES

Set Up a LUKS-Encrypted Data Volume on SLES

Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.

Build a Custom AppArmor Profile on SUSE Linux

Build a Custom AppArmor Profile on SUSE Linux

Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.

Build a Local SUSE Update Server with RMT on SLES 15

Build a Local SUSE Update Server with RMT on SLES 15

Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.

Join SLES 15 to Active Directory with SSSD in YaST

Join SLES 15 to Active Directory with SSSD in YaST

Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.

Enable SLES Live Patching and Verify a Kernel Fix

Enable SLES Live Patching and Verify a Kernel Fix

Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.

Apply the SLES 15 STIG Safely with OpenSCAP

Apply the SLES 15 STIG Safely with OpenSCAP

Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.

Restore Cockpit Access to SUSE Linux Enterprise Server

Restore Cockpit Access to SUSE Linux Enterprise Server

Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.