Teams Doesn’t Need Two PowerShell Modules (But Why Two Exist)

%3CLINGO-SUB%20id%3D%22lingo-sub-1036097%22%20slang%3D%22en-US%22%3ETeams%20Doesn%E2%80%99t%20Need%20Two%20PowerShell%20Modules%20(But%20Why%20Two%20Exist)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1036097%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20work%20with%20Teams%20through%20PowerShell%2C%20you'll%20know%20that%20you%20sometimes%20need%20to%20open%20the%20Skype%20for%20Business%20Online%20module.%20It's%20a%20royal%20pain%20in%20the%20rear%20end%20to%20deal%20with%20two%20inconsistent%20modules.%20It%20would%20be%20much%20neater%20if%20everything%20was%20gathered%20into%20one%20coherent%20module.%20However%2C%20that's%20not%20going%20to%20happen%20much%20before%20Skype%20for%20Business%20Online%20retires%20in%202021.%20In%20the%20interim%2C%20here%20are%20seven%20sets%20of%20policy%20cmdlets%20that%20you'll%20probably%20need%20to%20use%20to%20assign%20policies%20to%20multiple%20users%20at%20one%20time.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.petri.com%2Fteams-doesnt-need-two-powershell-modules%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.petri.com%2Fteams-doesnt-need-two-powershell-modules%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1036097%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1047678%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Doesn%E2%80%99t%20Need%20Two%20PowerShell%20Modules%20(But%20Why%20Two%20Exist)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1047678%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3BThe%20links%20is%20giving%20me%20a%20404.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1047940%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Doesn%E2%80%99t%20Need%20Two%20PowerShell%20Modules%20(But%20Why%20Two%20Exist)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1047940%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13305%22%20target%3D%22_blank%22%3E%40digiweten%3C%2FA%3E%26nbsp%3Bback%20online.%20for%20some%20reason%20the%20post%20was%20rescheduled%20for%20tomorrow%20despite%20being%20posted%20last%20week...%20The%20complexities%20of%20online%20publishing...%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
MVP

 

If you work with Teams through PowerShell, you'll know that you sometimes need to open the Skype for Business Online module. It's a royal pain in the rear end to deal with two inconsistent modules. It would be much neater if everything was gathered into one coherent module. However, that's not going to happen much before Skype for Business Online retires in 2021. In the interim, here are seven sets of policy cmdlets that you'll probably need to use to assign policies to multiple users at one time.

 

https://www.petri.com/teams-doesnt-need-two-powershell-modules

2 Replies
Highlighted

@Tony Redmond The links is giving me a 404.

 

Highlighted

@digiweten back online. for some reason the post was rescheduled for tomorrow despite being posted last week... The complexities of online publishing...