Impact of roadmap change on Teams polices

%3CLINGO-SUB%20id%3D%22lingo-sub-1812067%22%20slang%3D%22en-US%22%3EImpact%20of%20roadmap%20change%20on%20Teams%20polices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1812067%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20are%20continuing%20to%20deploy%20a%20large%20number%20of%20changes%20to%20Microsoft%20Teams.%20Some%20of%20these%20feature%20ship%20with%20a%20default%20as%20'switch%20on'%20whilst%20other%20changes%20are%20'switched%20off'%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20trying%20to%20confirm%20the%20behaviour%20of%20changes%20that%20relate%20to%20the%20Teams%20polices%20both%20to%20the%20org%20wide%20(default)%20and%20to%20custom%20policies.%3C%2FP%3E%3CP%3EFor%20example%20if%20a%20new%20feature%20in%20a%20Teams%20meeting%20policy%20is%20shipped%20with%20a%20setting%20on.%20Will%20that%20configuration%20appear%20in%20both%20the%20global%20org%20wide%20and%20also%20the%20custom%20policies.%3C%2FP%3E%3CP%3EI%20have%20a%20client%20that%20want%20to%20freeze%20the%20policies%20once%20agreed%20and%20them%20only%20change%20the%20configuration%20after%20internal%20approval.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20understand%20the%20global%20org%20wide%20policies%20being%20evergreen%20as%20they%20are%20the%20default%20but%20am%20concerned%20that%20the%20custom%20policies%20may%20be%20evergreen%20too%20and%20and%20if%20a%26nbsp%3B%20feature%20is%20shipped%20switched%20on%20by%20default%20it%20will%20automatically%20appear%20in%20a%20custom%20Teams%20polices%20rather%20honouring%20existing%20settings.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIts%20not%20always%20easy%20for%20an%20organisation%20to%20keep%20on%20top%20of%20the%20Microsoft%20road%20map%20and%20it%20is%20also%20difficult%20for%20the%20Microsoft%20365%20Admins%20to%20know%20when%20the%20new%20functionality%20will%20actually%20land%20in%20their%20tenant%20so%20they%20can%20check%20their%20custom%20policies%20and%20switch%20feature%20off.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20there%20any%20standard%20rules%20on%20the%20behaviour%20on%20custom%20policies%20or%20are%20the%20rules%20set%20on%20each%20roadmap%20item%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1812067%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%20Policies%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1812376%22%20slang%3D%22en-US%22%3ERe%3A%20Impact%20of%20roadmap%20change%20on%20Teams%20polices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1812376%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380093%22%20target%3D%22_blank%22%3E%40Nikki1%3C%2FA%3E%26nbsp%3BHi%2C%20a%20good%20question%20and%20I%20can't%20say%20for%20sure%20but%20it%20should%20be%20the%20Global%20policy%20that%20we%20need%20to%20act%20on.%20Would%20be%20a%20hassle%20if%20Microsoft%20updated%20settings%20in%20all%20custom%20policies%20as%20well%2C%20wouldn't%20it%3F%20With%20the%20exception%20of%20major%20updates%20obviously%2C%20such%20as%20moving%20from%20Stream%20to%20OneDrive%2FSharePoint%20where%20you%20don't%20even%20have%20the%20option%20to%20stay%20with%20Stream.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20this%20is%20just%20me%20thinking%20out%20loud%20so%20I'll%20wait%20for%20someone%20else%20to%20reply%20as%20well.%20Cheers!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Microsoft are continuing to deploy a large number of changes to Microsoft Teams. Some of these feature ship with a default as 'switch on' whilst other changes are 'switched off'

 

I am trying to confirm the behaviour of changes that relate to the Teams polices both to the org wide (default) and to custom policies.

For example if a new feature in a Teams meeting policy is shipped with a setting on. Will that configuration appear in both the global org wide and also the custom policies.

I have a client that want to freeze the policies once agreed and them only change the configuration after internal approval.

 

I can understand the global org wide policies being evergreen as they are the default but am concerned that the custom policies may be evergreen too and and if a  feature is shipped switched on by default it will automatically appear in a custom Teams polices rather honouring existing settings.

 

Its not always easy for an organisation to keep on top of the Microsoft road map and it is also difficult for the Microsoft 365 Admins to know when the new functionality will actually land in their tenant so they can check their custom policies and switch feature off.

 

Are there any standard rules on the behaviour on custom policies or are the rules set on each roadmap item?

 

 

1 Reply
Highlighted

@Nikki1 Hi, a good question and I can't say for sure but it should be the Global policy that we need to act on. Would be a hassle if Microsoft updated settings in all custom policies as well, wouldn't it? With the exception of major updates obviously, such as moving from Stream to OneDrive/SharePoint where you don't even have the option to stay with Stream.

 

But this is just me thinking out loud so I'll wait for someone else to reply as well. Cheers!