Igor Karon
Coincidentally, I implemented such an AD security group (SG) for a client this week. To test, I added my standard user account to the SG and gave myself an Azure AD P1 license - I am still unclear if the P1 license is only required to change the directory settings including the setting object Id of the SG that can create Teams , Office 365 Groups and Modern Teams sites. Alternatively, do members of the SG need all need to have an Azure AD P1 license? The documentation is a bit vague!
Anyway, the result of the above is than none of the global admins can create a Team :mansad:, they just get that annoying enter code dialog - my standard user account works without any problems. I did further investigation and was able to create a Team with PowerShell as a global admin but bizarrely not the underlying SharePOint site. I get the message telling me to check back later. Has anybody being able limit Teams creation using the above method without impeding the abilities of their Global Admins. If so, it must be down to the one of the less obvious service plans I haven't enabled.