Information Barriers: Microsoft Teams

Information barriers preclude someone from communicating someone else (additional O365 services are going to implement it eventually, Teams just happens to be on the leading edge). Now there are lines of business where this is an awesome feature — law firm representing both sides of a case, for instance, don’t want people on side A chatting with people from side B. A company with a large front-line workforce may want to preclude the unwashed masses from communicating with Corporate.
If it were free and low effort to set up and maintain, I could come up with use cases for it here. Say, isolating the C11 people so someone unauthorized to talk to C11 people aren’t accidentally disclosing information. En mass blocking people from using federated communication is an interesting option — basically disallow it for everyone & have a specific request to be thrown into the “talks to people outside the company” group.
There’s some initial setup effort in building out the policies and applying them, and there would be effort in getting some mechanism for people to be moved into and out of policies. So it probably passes the ‘low effort’ test. Cost, not so much. It looks like, while anyone with an E3 SKU can use it during this preview, barrier’d accounts need an E5 or an add-on compliance/regulatory license once this goes GA.
Based on cost, I’m thinking we don’t want go dig into it. It’s an additional 8$/month for the compliance add-on license. Something like 15$/month to go from an E3 to an E5. And I don’t particularly care 8$ a user if people in our call center are inviting their friends from the MS call center to lunch over the chat federation.
Anyone else see a use case where it’d be worth the additional money for the technologically enforced barrier?

Leave a Reply

Your email address will not be published. Required fields are marked *