The latest version of Teams supports the ability to create org-wide teams, but only if your tenant has fewer than 1,000 accounts. It’s a neat idea, if you can use it, but if you have more than 1,000 accounts, there are other ways to foster company-wide communications.
Slack is the most obvious competitor for Microsoft Teams. The question is how many users does each platform have? Here is our best guess.
A quirky side of the New-Team cmdlet is that it creates some interesting values for the properties of the underlying Office 365 group that you might like to control better. As it turns out, the Alias parameter is what you need to set.
Security groups are often used to protect access to resources, but they can’t be used to control membership for Office 365 Groups or Teams. If you want to use AAD security groups to control membership for Groups and Teams, you need to come up with a way to synchronize. PowerShell is available to do the job, and as it turns out, it’s not too difficult.
Some will tell you that you can figure out what resources an Office 365 Group is connected to by checking the ProvisioningOption property with the Get-UnifiedGroup cmdlet. Well, you can’t. If you want to do something like check for team-enabled groups, you’ll need a different approach.