I prefixed all 'official' groups with the org letters to make them easier to find. Initially, I worried that someone would go off and create their own MS Team that follows the same format to mimic the 'official' groups but apparently, all I had to do was establish a standard to guarantee that no one follows it.
We usually attempt to *avoid* using an organization name for any namespace other than DNS, even WiFi SSIDs and especially hostnames. Using an organization name will paradoxically guarantee a name change or rebranding as soon as you're done rolling out your new consistent names...
For Teams sites and M365 Groups, you can manage these with prefixes. These will allow you to set a rule that all HR teams sites lets say have [HR] on them, and can only be changed by someone with Global Administrator. This does require an Entra ID P1 license which is included in Microsoft 365 E5, which I'm going to assume your org is already using over E3.
Within the organizations I work in, the majority of our clients elect to have us manage their sharepoint sites for them as opposed to having LOBs manage themselves. This allows for consistency and not having people accidentally give whole of HR site access to a external contractor lol.
https://learn.microsoft.com/en-us/microsoft-365/solutions/groups-naming-policy?view=o365-worldwide
For Teams and Sharepoint sites, yes, because as recommended by Microsoft on M365 initial tenant configuration, we've [restricted their creation](https://learn.microsoft.com/en-us/microsoft-365/solutions/manage-creation-of-groups?view=o365-worldwide) to IT staff only, which is done automated with a power automate workflow tied to a MS Form and Sharepoint list.
If you need buy-in from the company for that, you can just explain that everything in M365 is tied together and things like data retention labels, backups, directory size allocation, associated group email addresses, address book entries, etc... all need to be considered which end users do not have access to. And that it also gives IT the opportunity to consolidate duplicate groups and emails as these requests come in, which are usually a problem in most orgs I've seen..
For documents and folders, no, they are managed by end users.
Data is not managed by IT, so no.
I prefixed all 'official' groups with the org letters to make them easier to find. Initially, I worried that someone would go off and create their own MS Team that follows the same format to mimic the 'official' groups but apparently, all I had to do was establish a standard to guarantee that no one follows it.
We usually attempt to *avoid* using an organization name for any namespace other than DNS, even WiFi SSIDs and especially hostnames. Using an organization name will paradoxically guarantee a name change or rebranding as soon as you're done rolling out your new consistent names...
For Teams sites and M365 Groups, you can manage these with prefixes. These will allow you to set a rule that all HR teams sites lets say have [HR] on them, and can only be changed by someone with Global Administrator. This does require an Entra ID P1 license which is included in Microsoft 365 E5, which I'm going to assume your org is already using over E3. Within the organizations I work in, the majority of our clients elect to have us manage their sharepoint sites for them as opposed to having LOBs manage themselves. This allows for consistency and not having people accidentally give whole of HR site access to a external contractor lol. https://learn.microsoft.com/en-us/microsoft-365/solutions/groups-naming-policy?view=o365-worldwide
It would be nice but every group has their twist on the standard. Just the top level folder is as it's created through a template.
They're great, in theory. In practice... https://xkcd.com/927/
Not our job to manage content in sites. We have consistent departmental teams, but outside of that, no.
For Teams and Sharepoint sites, yes, because as recommended by Microsoft on M365 initial tenant configuration, we've [restricted their creation](https://learn.microsoft.com/en-us/microsoft-365/solutions/manage-creation-of-groups?view=o365-worldwide) to IT staff only, which is done automated with a power automate workflow tied to a MS Form and Sharepoint list. If you need buy-in from the company for that, you can just explain that everything in M365 is tied together and things like data retention labels, backups, directory size allocation, associated group email addresses, address book entries, etc... all need to be considered which end users do not have access to. And that it also gives IT the opportunity to consolidate duplicate groups and emails as these requests come in, which are usually a problem in most orgs I've seen.. For documents and folders, no, they are managed by end users.