Worth Reading – How to Prevent Microsoft Teams Sprawl
If you’ve ever worked somewhere that allowed anyone to create Teams or even had a conversation with someone where the IT Department allowed it, you likely have your own story of how that looked.
I’ve seen a few and heard more than a few, myself.
It’s not pretty. But what can you do instead? There are some solid ideas in the article below, the first ones should be obvious: limit who can create Teams and have an approval process. Without that, you may as well start a pool to guess how many “test” Teams will be created in the first few months.
My experience tells me that wherever you set the over/under, take the over.
That statement is flippant, I am aware. The end result of all these Teams mailboxes and SharePoint sites is not. It can cause real headaches for InfoGov, Privacy, Security, and Legal teams. It generates a lot of noise that can drown out the signal of useful, relevant information. Even if you manage not to lose vital information, just digging through that much data can cost real money.
Why would you accept that?
