We want to set up a team for all our 250+ employees, and need advice about what to expect if we create an org-wide team.
I've read that certain types of users won't be added (Accounts that are blocked from sign-in; Guests; Resource or service accounts; Room or equipment accounts; Accounts backed by a shared mailbox). But I don't know how clean our AD is. There's no way of testing/checking who would actually be added, so we're cautious about going ahead!
Our other concern is that Teams would instantly send an automated notification to all our employees, but we have no way of knowing what it will say. From experience, there are at least 3 types of notifications, depending on how/where a Team is set up, and the wording can't be customised. Can anybody share an example of the automated notification for an org-wide team? Or, is it possible to suppress the automated notification, maybe via Powershell?
As an alternative, we had considered a team based on a dynamic rule-based group. We could control it by basing the criteria on a field in our AD which is only used for current employees. However, we have E3 licences, which don't support the creation/use of dynamic groups.
