SOLVED

Block internal but allow external

%3CLINGO-SUB%20id%3D%22lingo-sub-1521191%22%20slang%3D%22en-US%22%3EBlock%20internal%20but%20allow%20external%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1521191%22%20slang%3D%22en-US%22%3E%3CP%3EA%20strange%20request%2C%20but%20since%20we%20use%20a%20different%20chat%20platform%20for%20internal%20communication%20we%20currently%20disallow%20MS%20Teams%20within%20our%20organization.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20many%20of%20the%20other%20people%20and%20firms%20we%20collaborate%20with%20outside%20of%20our%20organization%20are%20using%20MS%20Teams.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3EIs%20there%20a%20way%20in%20O365%20admin%20to%20disable%20MS%20Teams%20for%20any%20internal%20communication%20(direct%20messages%2C%20creating%20teams%2C%20etc.)%3C%2FSTRONG%3E%20but%20still%20allow%20users%20to%3A%3C%2FP%3E%3CUL%3E%3CLI%3ECreate%20MS%20Teams%20meetings%20and%20send%20invites%3C%2FLI%3E%3CLI%3EDirect%20message%20external%20users%20at%20different%20domains%3C%2FLI%3E%3CLI%3EJoin%20external%20domains%20as%20guests%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1521191%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGuest%20Access%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1521976%22%20slang%3D%22en-US%22%3ERe%3A%20Block%20internal%20but%20allow%20external%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1521976%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F351376%22%20target%3D%22_blank%22%3E%40th3_w-rz%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAFAIK%2C%20this%20can't%20be%20done%20using%20the%20parameters%20and%20functionalities%20you%20need.%20%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20could%20lock%20down%20Team%20creation%20(%3CA%20href%3D%22https%3A%2F%2Fmicrosoft365pro.co.uk%2F2019%2F07%2F10%2Fteams-real-simple-with-pictures-controlling-who-can-create-teams%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoft365pro.co.uk%2F2019%2F07%2F10%2Fteams-real-simple-with-pictures-controlling-who-can-create-teams%2F%3C%2FA%3E)%20and%20then%20use%20information%20barriers%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Finformation-barriers-in-teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Finformation-barriers-in-teams%3C%2FA%3E)%20to%20isolate%20users%20meaning%20internal%20users%20can't%20communicate%20with%20one%20another%2C%20however%20the%20caveat%20here%20is%20that%20it%20would%20impact%20meetings%20too%20which%20is%20a%20requirement.%20I%20did%20think%20about%20turning%20off%20private%20chat%20but%20the%20caveat%20here%20would%20be%20that%20this%20would%20also%20impact%20the%20ability%20to%20message%20external%20federated%20users%20as%20well%20as%20internal%20users%20-%20again%20a%20requirement%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20advice%20here%20is%20as%20follows%3CBR%20%2F%3E%3CBR%20%2F%3E1.)%20The%20preferred%20option%3A%20go%20with%20Teams.%20If%20orgs%20you%20work%20with%20are%20using%20Teams%20and%20it%20is%20their%20preferred%20method%20of%20communication%20then%20there%20is%20a%20strategic%20case%20to%20move%20to%20Teams%20in%20order%20to%20do%20business%20and%20make%20the%20partner%2Fcustomer%20experience%20as%20slick%20as%20possible%3CBR%20%2F%3E%3CBR%20%2F%3E2.)%20Set%20an%20internal%20org%20policy%20to%20use%20both%20for%20a%20period%20and%20see%20which%20one%20wins%20out%20over%20a%20period%20of%20time%3CBR%20%2F%3E%3CBR%20%2F%3E3.)%20Run%20a%20test%20pilot%20with%20Teams%20for%20a%20part%20of%20your%20organisation%20using%20Teams%20only%20and%20measure%20the%20productivity%20gains%20from%20that%20(in%20terms%20of%20internal%20satisfaction)%20and%20feed%20that%20back%20into%20the%20business%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20may%20find%20that%20several%20users%20are%20already%20guests%20in%20Teams%20anyway.%20Orgs%20will%20likely%20invite%20your%20users%20on%20personal%20domains%20if%20they%20know%20that%20you%20aren't%20using%20Teams%20already.%20There%20is%20a%20case%20for%20using%20Teams%20so%20that%20users%20aren't%20pushed%20to%20using%20shadow%20IT%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20answers%20your%20question%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E
Occasional Visitor

A strange request, but since we use a different chat platform for internal communication we currently disallow MS Teams within our organization.

 

However, many of the other people and firms we collaborate with outside of our organization are using MS Teams.

Is there a way in O365 admin to disable MS Teams for any internal communication (direct messages, creating teams, etc.) but still allow users to:

  • Create MS Teams meetings and send invites
  • Direct message external users at different domains
  • Join external domains as guests
1 Reply
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution
Hi @th3_w-rz

AFAIK, this can't be done using the parameters and functionalities you need.

You could lock down Team creation (https://microsoft365pro.co.uk/2019/07/10/teams-real-simple-with-pictures-controlling-who-can-create-...) and then use information barriers (https://docs.microsoft.com/en-us/microsoftteams/information-barriers-in-teams) to isolate users meaning internal users can't communicate with one another, however the caveat here is that it would impact meetings too which is a requirement. I did think about turning off private chat but the caveat here would be that this would also impact the ability to message external federated users as well as internal users - again a requirement

My advice here is as follows

1.) The preferred option: go with Teams. If orgs you work with are using Teams and it is their preferred method of communication then there is a strategic case to move to Teams in order to do business and make the partner/customer experience as slick as possible

2.) Set an internal org policy to use both for a period and see which one wins out over a period of time

3.) Run a test pilot with Teams for a part of your organisation using Teams only and measure the productivity gains from that (in terms of internal satisfaction) and feed that back into the business

You may find that several users are already guests in Teams anyway. Orgs will likely invite your users on personal domains if they know that you aren't using Teams already. There is a case for using Teams so that users aren't pushed to using shadow IT

Hope that answers your question

Best, Chris