Managing Teams App Permission Policies

%3CLINGO-SUB%20id%3D%22lingo-sub-1382400%22%20slang%3D%22en-US%22%3EManaging%20Teams%20App%20Permission%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1382400%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20an%20enterprise%20in%20the%20midst%20of%20rolling%20out%20Teams%20to%20approximately%207K%20users.%20An%20area%20of%20concern%20we%20have%20is%20around%20managing%20the%20App%20Permission%20Policies.%20We%20have%20developed%20a%20process%20to%20approve%20additional%20apps%20that%20our%20business%20units%20might%20find%20useful.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20initial%20thought%20was%20to%20manage%20the%20app%20access%20via%20AD%20groups%2C%20but%20that%20appears%20to%20require%20some%20kind%20of%20automated%20PowerShell%20script%20to%20get%20the%20correct%20app%20permission%20policy%20applied%20to%20the%20users%20of%20the%20group.%20Then%20we%20have%20the%20challenge%20of%20a%201%3A1%20ratio%20of%20a%20user%20to%20app%20permission%20policy%20rather%20than%20building%20a%20base%20policy%20for%20the%20enterprise%2C%20and%20if%20you%20are%20in%20%3CEM%3Ex%3C%2FEM%3E%20group%2C%20you%20also%20get%20this%20additional%20app.%20This%20approach%20comes%20across%20to%20me%20as%20a%20maintenance%20nightmare.%20We%20have%20also%20recently%20run%20into%20a%20token%20bloat%20issue%20with%20users%20having%20many%20AD%20groups%20that%20this%20approach%20may%20exacerbate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20looking%20for%20ideas%20or%20suggestions%20of%20how%20others%20might%20be%20handling%20multiple%20app%20permission%20policies.%20Are%20you%20limiting%20the%20number%20of%20policies%20you%20create%3F%20Are%20you%20using%20the%20global%20policy%20and%20taking%20the%20stance%20that%20all%20approved%20apps%20are%20available%20enterprise-wide%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1382400%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAppPermissionPolicy%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Senior Member

Hi Everyone,

 

We are an enterprise in the midst of rolling out Teams to approximately 7K users. An area of concern we have is around managing the App Permission Policies. We have developed a process to approve additional apps that our business units might find useful.

 

Our initial thought was to manage the app access via AD groups, but that appears to require some kind of automated PowerShell script to get the correct app permission policy applied to the users of the group. Then we have the challenge of a 1:1 ratio of a user to app permission policy rather than building a base policy for the enterprise, and if you are in x group, you also get this additional app. This approach comes across to me as a maintenance nightmare. We have also recently run into a token bloat issue with users having many AD groups that this approach may exacerbate.

 

We are looking for ideas or suggestions of how others might be handling multiple app permission policies. Are you limiting the number of policies you create? Are you using the global policy and taking the stance that all approved apps are available enterprise-wide?

0 Replies