Home
%3CLINGO-SUB%20id%3D%22lingo-sub-482604%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482604%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20really%20great%20news!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482527%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482527%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482449%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482449%22%20slang%3D%22en-US%22%3E%3CP%3EVery%20helpful%20and%20great%20thanks.%20I%20have%20tried%20both%200.9.6%20and%201.0.0%20and%20got%20one%20question.%3C%2FP%3E%3CP%3EWhen%20adding%20owner%20using%20Add-TeamUser%20like%3A%26nbsp%3B%20%3CEM%3EAdd-TeamUser%26nbsp%3B%20-GroupId%20%3CGROUPID%3E%20-User%20%3CUSEREMAIL%3E%20-Role%20Owner%20%3C%2FUSEREMAIL%3E%3C%2FGROUPID%3E%3C%2FEM%3Ethen%20check%20its%20status%20in%20Office365%20group%2C%20I%20found%20the%20identified%20user%20is%20just%20shown%20as%20O365%20group%20owner%20and%20have%20no%20member%20permission.%20So%20each%20time%20I%20have%20to%20run%20command%20twice%2C%20one%20for%20-role%20owner%20and%20one%20for%20-role%20member%20to%20ensure%20this%20user%20can%20use%20every%20function%20in%20Teams.%3C%2FP%3E%3CP%3EDo%20you%20intentionally%20design%20the%20command%20like%20this%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMeanwhile%2C%20the%20owner%20identified%20in%20New-Team%20like%3A%26nbsp%3B%20%3CEM%3ENew-Team%20-DisplayName%20%3CTEAMNAME%3E%20-Owner%20%3CUSEREMAIL%3E%20-Visibility%20Private%20%3C%2FUSEREMAIL%3E%3C%2FTEAMNAME%3E%3C%2FEM%3Ecan%20be%20found%20as%20both%20owner%20and%20member%20in%20office365%20group.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482372%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482372%22%20slang%3D%22en-US%22%3E%3CP%3EBe%20sure%20to%20check%20out%20the%20DSC%20resources%20as%20well!%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoft%2FOffice365DSC%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FMicrosoft%2FOffice365DSC%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482361%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482361%22%20slang%3D%22en-US%22%3E%3CP%3Eawesome%20-%20thanks!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482285%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482285%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EJust%20installed%20GA%20version%20of%20the%20MicrosoftTeams%20%23PowerShell%20module.%20Connect-MicrosoftTeams%20command%20worked%20as%20expected.%20The%20next%20one%2C%20Get-Team%2C%20failed%20with%20the%20error%20message%20%22%3CFONT%20color%3D%22%23ff0000%22%3EUnsupported%20token.%20Unable%20to%20initialize%20the%20authorization%20context.%3C%2FFONT%3E%22%20%3A(%3C%2Fimg%3E%20Using%20-Verbose%20or%20-Debug%20doesn't%20provide%20any%20additional%20information%20useful%20for%20a%20troubleshooting.%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482157%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482157%22%20slang%3D%22en-US%22%3E%3CP%3Eplease%20make%20sure%20that%20this%20gets%20posted%20to%20the%20O365%20Admin%20Center%20Message%20page%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482131%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482131%22%20slang%3D%22en-US%22%3EExcellent%20news%20!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482101%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482101%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20news!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-484153%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-484153%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11122%22%20target%3D%22_blank%22%3E%40Aleksandar%20Nikolic%3C%2FA%3E%26nbsp%3BI%20experienced%20the%20same%2C%20restarting%20the%20PowerShell%20helped%20me%20fix%20the%20issue.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F110564i3835F2318AECCCB7%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Teams1.0%20Module.png%22%20title%3D%22Teams1.0%20Module.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EGet-Team%20with%201.0%20module%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-493540%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-493540%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wish%20Get-Team%20returned%20the%20URL%20for%20the%20team.%26nbsp%3B%20That%20would%20make%20our%20lives%20a%20lot%20easier.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-499301%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-499301%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%20with%20you%20Alex%2C%20instead%20of%20providing%20the%20Group%20ID%2C%20if%20it%20returns%20the%20Team%20Site%20URL%20or%20both%20would%20be%20really%20helpful.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480934%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480934%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20excited%20to%20announce%20the%20general%20availability%20of%20the%20Microsoft%20Teams%20PowerShell%20module.%20This%20PowerShell%20module%2C%20first%20released%20in%20Beta%20last%20year%2C%20allows%20you%20to%20manage%20the%20lifecycle%20of%20teams%20within%20your%20organization.%20As%20a%20Global%20Administrator%20or%20Teams%20Service%20Administrator%2C%20you%20can%20identify%20and%20manage%20teams%20on%20behalf%20of%20your%20users%2C%20and%20make%20bulk%20updates%20to%20teams%20faster%20%E2%80%93%20including%20changing%20memberships%20or%20managing%20team%20settings.%20This%20new%20version%20of%20our%20module%20leverages%20only%201.0%20Graph%20APIs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGoing%20forward%2C%20we%20will%20be%20maintaining%20both%20a%20Preview%20and%20Generally%20Available%20versions%20of%20the%20Microsoft%20Teams%20PowerShell%20module.%20This%20will%20allow%20us%20to%20deliver%20new%2C%20preview%20functionality%20to%20our%20customers%20faster%20for%20testing%2C%20while%20ensuring%20that%20our%20Generally%20Available%20module%20continues%20to%20leverage%20only%201.0%20APIs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20following%20cmdlets%20are%20supported%20in%20our%20generally%20available%20module%3A%3C%2FP%3E%0A%3CTABLE%20width%3D%22636%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CSTRONG%3ECmdlet%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3E%3CSTRONG%3EDescription%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FConnect-MicrosoftTeams%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConnect-MicrosoftTeams%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EConnects%20an%20authenticated%20account%20to%20use%20for%20Microsoft%20Teams%20environment%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FDisconnect-MicrosoftTeams%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDisconnect-MicrosoftTeams%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EDisconnects%20from%20the%20Microsoft%20Teams%20environment%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FGet-Team%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGet-Team%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3ERetrieves%20teams%20with%20particular%20properties%20or%20information%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FGet-TeamChannel%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGet-TeamChannel%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EGets%20all%20the%20channels%20for%20a%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FGet-TeamHelp%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGet-TeamHelp%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EProvides%20a%20list%20of%20commands%20for%20Microsoft%20Teams%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FGet-TeamUser%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGet-TeamUser%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EReturns%20the%20users%20of%20a%20specific%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FNew-Team%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ENew-Team%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EProvisions%20a%20new%20Team%2C%20or%20converts%20a%20group%20to%20a%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FNew-TeamChannel%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ENew-TeamChannel%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EAdds%20a%20new%20channel%20to%20a%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FAdd-TeamUser%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAdd-TeamUser%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EAdds%20an%20owner%20or%20member%20to%20the%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FRemove-Team%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ERemove-Team%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EDeletes%20a%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FRemove-TeamChannel%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ERemove-TeamChannel%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EDeletes%20a%20channel%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FRemove-TeamUser%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ERemove-TeamUser%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3ERemoves%20an%20owner%20or%20member%20from%20a%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FSet-Team%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESet-Team%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EUpdates%20properties%20of%20a%20team%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22155%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fteams%2FSet-TeamChannel%3Fview%3Dteams-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESet-TeamChannel%3C%2FA%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22481%22%3E%3CP%3EUpdates%20Team%20channel%20information%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAdditional%20Functionality%20in%20New%20Release%3C%2FSTRONG%3E%20%3CBR%20%2F%3EIn%20addition%20to%20leveraging%20solely%201.0%20APIs%2C%20we%20have%20made%20a%20few%20improvements%20to%20cmdlets%20in%20the%20Generally%20Available%20module%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3EConnect-MicrosoftTeams%3C%2FU%3E%3A%20You%20can%20now%20specify%20a%20Teams%20Government%20Environment%20(-TeamsEnvironmentName)%20that%20your%20organization%20is%20homed%20in.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3EGet-Team%3C%2FU%3E%3A%20We%20expanded%20the%20filter%20and%20selection%20criteria%20to%20include%20properties%20such%20as%20the%20Visibility%20or%20Archived%20state%20of%20the%20teams%20so%20that%20you%20can%20more%20easily%20identify%20teams%20that%20may%20require%20your%20attention%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3ESimplified%20Experience%3C%2FSTRONG%3E%3CBR%20%2F%3ETo%20improve%20the%20discoverability%20of%20certain%20team%20settings%2C%20we%20consolidated%20the%20functionality%20of%20the%20following%20cmdlets%20into%20the%20Get-Team%20and%20Set-Team%20cmdlets%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20Get-TeamFunSettings%3CBR%20%2F%3E-%20Get-TeamGuestSettings%3CBR%20%2F%3E-%20Get-TeamMemberSettings%3CBR%20%2F%3E-%20Get-TeamMessagingSettings%3CBR%20%2F%3E-%20Set-TeamFunSettings%3CBR%20%2F%3E-%20Set-TeamGuestSettings%3CBR%20%2F%3E-%20Set-TeamMemberSettings%3CBR%20%2F%3E-%20Set-TeamMessagingSettings%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3ENote%3C%2FU%3E%3A%20These%20beta%20cmdlets%20will%20not%20be%20available%20in%20future%20module%20releases%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EWant%20to%20learn%20more%20about%20PowerShell%3F%3C%2FSTRONG%3E%3CBR%20%2F%3EBecause%20Teams%20is%20built%20on%20top%20of%20different%20services%2C%20PowerShell%20controls%20for%20Teams%20are%20split%20across%20several%20modules.%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fteams-powershell-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20PowerShell%20for%20Teams%3C%2FA%3E%20(also%20includes%20links%20to%20the%20technical%20docs%20for%20individual%20cmdlets).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ELet%20us%20know%20what%20you%20think!%3C%2FSTRONG%3E%3CBR%20%2F%3EIf%20you%20have%20suggestions%20on%20how%20to%20make%20Teams%20better%2C%20please%20submit%20your%20idea%20via%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EUser%20Voice%3C%2FA%3E%20or%20vote%20for%20existing%20ideas%20to%20help%20us%20prioritize%20the%20requests.%20We%20read%20every%20piece%20of%20feedback%20that%20we%20receive%20to%20make%20sure%20that%20Microsoft%20Teams%20meets%20your%20needs.%20%3CBR%20%2F%3E%E2%80%94%20%3CEM%3EChristopher%20Bryan%2C%20Microsoft%20Teams%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-480934%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20PowerShell%20module%20allows%20you%20to%20manage%20the%20lifecycle%20of%20teams%20within%20your%20organization.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F109897i3A5A710F7B7C286A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22teaser.jpg%22%20title%3D%22teaser.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-480934%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-514330%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-514330%22%20slang%3D%22en-US%22%3E%3CP%3EExcellent%20news%2C%20just%20one%20thing%20which%20would%20be%20a%20really%20nice%20to%20have%20would%20be%20to%20change%20the%20group%20a%20Team%20is%20attached%20to%2C%20is%20this%20something%20on%20the%20Roadmap%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-525823%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-525823%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20can%20i%20get%20the%20GuestSettings%20now%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576276%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576276%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20finding%20it%20impossible%20to%20report%20on%20which%20Teams%20have%20guests%20in%20the%20new%20module%20and%20the%20table%20in%20the%20Admin%20Center%20isn't%20sortable%20or%20filterable.%20I%20need%20to%20keep%20an%20eye%20on%20guest%20access%20but%20I'm%20also%20not%20trained%20in%20PowerShell%20and%20one%20of%20those%20saps%20who%20has%20to%20google%20everything%20and%20snag%20others'%20scripts.%20I%20found%20one%20but%20it%20times%20out%20before%20it%20finishes%20so%20I'm%20not%20even%20sure%20if%20it%20works%20or%20not.%20I%20don't%20even%20really%20need%20to%20know%20who%20the%20guests%20are%2C%20I%20just%20need%20to%20say%20to%20Team%20owners%20%22Hey%2C%20you%20have%20external%20guests%20in%20your%20Team.%20Please%20make%20sure%20these%20are%20valid%20guests%20and%20remove%20access%20as%20needed.%22%20etc.%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576440%22%20slang%3D%22en-US%22%3ERE%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576440%22%20slang%3D%22en-US%22%3EGo%20into%20the%20Teams%20Admin%20Center.%20Click%20on%20Teams.%20The%20landing%20page%20lists%20all%20teams%20and%20the%20number%20of%20guest%20users%20in%20each%20team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576441%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576441%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343389%22%20target%3D%22_blank%22%3E%40Aashe4%3C%2FA%3Eone%20easy%20way%20to%20do%20that%20is%20with%20the%20Access%20Review%20feature%20in%20Azure%20AD%2C%20it%20is%20specifically%20designed%20for%20that%20purpose.%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fgovernance%2Faccess-reviews-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fgovernance%2Faccess-reviews-overview%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754990%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754990%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20somebody%20tell%20me%20what%20the%20alternative%20is%20for%20the%20'%3CFONT%3ESet-TeamPicture%3C%2FFONT%3E'%20cmdlet%2C%20becuase%20it%20seems%20to%20be%20gone...%3C%2FP%3E%3CP%3EHow%20can%20I%20set%20a%20logo%20for%20a%20team%20now%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-767551%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-767551%22%20slang%3D%22en-US%22%3E%3CP%3EI%20appreciate%20that%20we%20now%20have%20this%20module.%20However...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3Ewhy%20is%20this%20hosted%20on%20PowerShellGallery%3F%20Microsoft%20specifically%20says%20that%20scripts%20in%20the%20PSG%20are%20not%20supported%20and%20no%20warranty%20is%20given.%20And%20I%20really%20don't%20like%20when%20necessary%20tools%20are%20published%20at%20a%20place%2C%20where%20there%20is%20no%20support%20nor%20warranty.%3C%2FLI%3E%3CLI%3EI%20dislike%20that%20the%20Powershell%20modules%20for%20managing%20Office%20365%20are%20all%20over%20the%20place.%20Why%20is%20there%20not%20a%20single%20'hub'%20where%20I%20can%20get%20all%20the%20modules%20from%2C%20that%20I%20need%20to%20manage%20Office%20365%3F%20Can%20you%20please%20communicate%20better%20with%20your%20colleagues%2C%20instead%20of%20everyone%20doing%20his%20own%20thing%3F%20This%20pisses%20me%20off!%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-842400%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-842400%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20the%20powershell%20modulets%20from%20SharePoint%2C%20Groups%20and%20Teams%20a%20lot%20as%20the%20backbone%20in%20our%20provisioning%20tool%20an%20the%20GA%20of%20Teams%20powershell%20was%20a%20major%20event%20for%20us.%20However%20in%20order%20to%20complete%20the%20governance%20module%20we%20have%20to%20archive%20Teams%2C%20and%20am%20very%20surprised%20that%20this%20can%20be%20done%20in%20the%20GUI%20and%20not%20in%20powershell.%20Any%20eta%20for%20this%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-842728%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-842728%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F98819%22%20target%3D%22_blank%22%3E%40Kasper%20Bo%20Larsen%3C%2FA%3E%26nbsp%3BYes%2C%20only%20way%20to%20achieve%20it%2C%20via%20Graph%20API%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fteam-archive%3Fview%3Dgraph-rest-1.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fteam-archive%3Fview%3Dgraph-rest-1.0%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-855888%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-855888%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20biggest%20issue%20I%20have%20is%20the%20lack%20of%20support%20for%20the%20pre-canned%20templates%20available%20to%20the%20GUI.%20Being%20an%20educational%20institution%2C%20we%20regularly%20provision%20Teams%20(about%20200%20per%20semester%20with%20up%20to%20150%20members%20in%20each)%20based%20on%20the%20class%20template%20so%20manual%20provisioning%20is%20not%20exactly%20an%20option.%3C%2FP%3E%3CP%3EThe%20template%20option%20was%20available%20in%20the%20last%20beta%20(0.9.6)%20which%20I%20have%20had%20to%20roll%20back%20to.%20Still%20getting%20my%20head%20around%20the%20Graph%20API%20but%20there%20doesn't%20appear%20to%20be%20an%20option%20in%20the%20create%20team%20call%20for%20templates%20unless%20we%20create%20a%20blank%20team%20based%20on%20the%20pre-canned%20template%20and%20then%20clone%20that%20but%20that%20seems%20to%20be%20re-inventing%20the%20wheel%20given%20that%20what%20I%20need%20already%20exists%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-863223%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-863223%22%20slang%3D%22en-US%22%3E%3CP%3EI%20downloaded%20the%20latest%20version%20and%20attempted%20to%20connect%20but%20go%20this%20error%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConnect-MicrosoftTeams%20%3A%20Could%20not%20load%20file%20or%20assembly%20'System.Net.Http%2C%20Version%3D4.2.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db03f5f7f11d50a3a'%20or%20one%20of%20its%20dependencies.%20The%20system%20cannot%3CBR%20%2F%3Efind%20the%20file%20specified.%3CBR%20%2F%3EAt%20line%3A1%20char%3A1%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20am%20I%20doing%20wrong%3F%20Any%20advice%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-887232%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-887232%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F211041%22%20target%3D%22_blank%22%3E%40Maha%20Elkoshairi%3C%2FA%3E%26nbsp%3BSame%20issue%20here%20-%20Solution%20for%20me%20was%20to%20install%20Visual%20Studio.%3C%2FP%3E%3CP%3EAll%20my%20Googling%20kept%20turning%20up%20mentions%20of%20Package%20Managers%2C%20NuGet%2C%20etc%2C%20and%20Visual%20Studio.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20an%20expert%20in%20there%20area%20but%20this%20is%20how%20I%20got%20it%20working%3A%3C%2FP%3E%3CP%3EInstalled%20VS%2C%20checked%20off%20anything%20related%20to%20.NET%3C%2FP%3E%3CP%3ERan%20PowerShell%20for%20Developer%3C%2FP%3E%3CP%3EDid%20a%20Find-Module%20and%20select%20yes%20to%20install%20the%20NuGet%20package.%3C%2FP%3E%3CP%3EThen%20in%20PowerShell%20as%20admin%2C%20ran%20Connect-MicrosoftTeams%20and%20I%20was%20in.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-890297%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20PowerShell%20Module%20General%20Availability%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-890297%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F418320%22%20target%3D%22_blank%22%3E%40Perri29%3C%2FA%3E%26nbsp%3BThis%20worked%20for%20me%20too.%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E

We are excited to announce the general availability of the Microsoft Teams PowerShell module. This PowerShell module, first released in Beta last year, allows you to manage the lifecycle of teams within your organization. As a Global Administrator or Teams Service Administrator, you can identify and manage teams on behalf of your users, and make bulk updates to teams faster – including changing memberships or managing team settings. This new version of our module leverages only 1.0 Graph APIs.

 

Going forward, we will be maintaining both a Preview and Generally Available versions of the Microsoft Teams PowerShell module. This will allow us to deliver new, preview functionality to our customers faster for testing, while ensuring that our Generally Available module continues to leverage only 1.0 APIs.

 

The following cmdlets are supported in our generally available module:

Cmdlet

Description

Connect-MicrosoftTeams

Connects an authenticated account to use for Microsoft Teams environment

Disconnect-MicrosoftTeams

Disconnects from the Microsoft Teams environment

Get-Team

Retrieves teams with particular properties or information

Get-TeamChannel

Gets all the channels for a team

Get-TeamHelp

Provides a list of commands for Microsoft Teams

Get-TeamUser

Returns the users of a specific team

New-Team

Provisions a new Team, or converts a group to a team

New-TeamChannel

Adds a new channel to a team

Add-TeamUser

Adds an owner or member to the team

Remove-Team

Deletes a team

Remove-TeamChannel

Deletes a channel

Remove-TeamUser

Removes an owner or member from a team

Set-Team

Updates properties of a team

Set-TeamChannel

Updates Team channel information

 

Additional Functionality in New Release
In addition to leveraging solely 1.0 APIs, we have made a few improvements to cmdlets in the Generally Available module:

 

Connect-MicrosoftTeams: You can now specify a Teams Government Environment (-TeamsEnvironmentName) that your organization is homed in.

 

Get-Team: We expanded the filter and selection criteria to include properties such as the Visibility or Archived state of the teams so that you can more easily identify teams that may require your attention

Simplified Experience
To improve the discoverability of certain team settings, we consolidated the functionality of the following cmdlets into the Get-Team and Set-Team cmdlets:

 

- Get-TeamFunSettings
- Get-TeamGuestSettings
- Get-TeamMemberSettings
- Get-TeamMessagingSettings
- Set-TeamFunSettings
- Set-TeamGuestSettings
- Set-TeamMemberSettings
- Set-TeamMessagingSettings

 

Note: These beta cmdlets will not be available in future module releases

 

Want to learn more about PowerShell?
Because Teams is built on top of different services, PowerShell controls for Teams are split across several modules. Learn more about PowerShell for Teams (also includes links to the technical docs for individual cmdlets).

 

Let us know what you think!
If you have suggestions on how to make Teams better, please submit your idea via User Voice or vote for existing ideas to help us prioritize the requests. We read every piece of feedback that we receive to make sure that Microsoft Teams meets your needs.
Christopher Bryan, Microsoft Teams

25 Comments

Great news!

New Contributor
Excellent news !
Respected Contributor

please make sure that this gets posted to the O365 Admin Center Message page

Just installed GA version of the MicrosoftTeams #PowerShell module. Connect-MicrosoftTeams command worked as expected. The next one, Get-Team, failed with the error message "Unsupported token. Unable to initialize the authorization context." :( Using -Verbose or -Debug doesn't provide any additional information useful for a troubleshooting.

New Contributor

awesome - thanks! 

Be sure to check out the DSC resources as well!  

https://github.com/Microsoft/Office365DSC

 

New Contributor

Very helpful and great thanks. I have tried both 0.9.6 and 1.0.0 and got one question.

When adding owner using Add-TeamUser like:  Add-TeamUser  -GroupId <GroupID> -User <UserEmail> -Role Owner then check its status in Office365 group, I found the identified user is just shown as O365 group owner and have no member permission. So each time I have to run command twice, one for -role owner and one for -role member to ensure this user can use every function in Teams.

Do you intentionally design the command like this? 

 

Meanwhile, the owner identified in New-Team like:  New-Team -DisplayName <TeamName> -Owner <UserEmail> -Visibility Private can be found as both owner and member in office365 group.

 

 

 

Senior Member

Great Thanks

This is really great news!

Senior Member

@Aleksandar Nikolic I experienced the same, restarting the PowerShell helped me fix the issue.

Teams1.0 Module.pngGet-Team with 1.0 module

Occasional Contributor

I wish Get-Team returned the URL for the team.  That would make our lives a lot easier.

Occasional Visitor

I agree with you Alex, instead of providing the Group ID, if it returns the Team Site URL or both would be really helpful.

Occasional Contributor

Excellent news, just one thing which would be a really nice to have would be to change the group a Team is attached to, is this something on the Roadmap?

Occasional Contributor

How can i get the GuestSettings now?

Occasional Visitor

I'm finding it impossible to report on which Teams have guests in the new module and the table in the Admin Center isn't sortable or filterable. I need to keep an eye on guest access but I'm also not trained in PowerShell and one of those saps who has to google everything and snag others' scripts. I found one but it times out before it finishes so I'm not even sure if it works or not. I don't even really need to know who the guests are, I just need to say to Team owners "Hey, you have external guests in your Team. Please make sure these are valid guests and remove access as needed." etc., etc.

Occasional Contributor
Go into the Teams Admin Center. Click on Teams. The landing page lists all teams and the number of guest users in each team.
Respected Contributor

@Aashe4one easy way to do that is with the Access Review feature in Azure AD, it is specifically designed for that purpose. see https://docs.microsoft.com/en-us/azure/active-directory/governance/access-reviews-overview

Occasional Contributor

Could somebody tell me what the alternative is for the 'Set-TeamPicture' cmdlet, becuase it seems to be gone...

How can I set a logo for a team now?

Senior Member

I appreciate that we now have this module. However...

 

  • why is this hosted on PowerShellGallery? Microsoft specifically says that scripts in the PSG are not supported and no warranty is given. And I really don't like when necessary tools are published at a place, where there is no support nor warranty.
  • I dislike that the Powershell modules for managing Office 365 are all over the place. Why is there not a single 'hub' where I can get all the modules from, that I need to manage Office 365? Can you please communicate better with your colleagues, instead of everyone doing his own thing? This pisses me off!
Frequent Visitor

We use the powershell modulets from SharePoint, Groups and Teams a lot as the backbone in our provisioning tool an the GA of Teams powershell was a major event for us. However in order to complete the governance module we have to archive Teams, and am very surprised that this can be done in the GUI and not in powershell. Any eta for this? 

Senior Member
Occasional Visitor

The biggest issue I have is the lack of support for the pre-canned templates available to the GUI. Being an educational institution, we regularly provision Teams (about 200 per semester with up to 150 members in each) based on the class template so manual provisioning is not exactly an option.

The template option was available in the last beta (0.9.6) which I have had to roll back to. Still getting my head around the Graph API but there doesn't appear to be an option in the create team call for templates unless we create a blank team based on the pre-canned template and then clone that but that seems to be re-inventing the wheel given that what I need already exists

Regular Visitor

I downloaded the latest version and attempted to connect but go this error: 

 

Connect-MicrosoftTeams : Could not load file or assembly 'System.Net.Http, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot
find the file specified.
At line:1 char:1

 

What am I doing wrong? Any advice would be appreciated.

Occasional Visitor

@Maha Elkoshairi Same issue here - Solution for me was to install Visual Studio.

All my Googling kept turning up mentions of Package Managers, NuGet, etc, and Visual Studio.

 

Not an expert in there area but this is how I got it working:

Installed VS, checked off anything related to .NET

Ran PowerShell for Developer

Did a Find-Module and select yes to install the NuGet package.

Then in PowerShell as admin, ran Connect-MicrosoftTeams and I was in.

 

 

 

 

Frequent Visitor

@Perri29 This worked for me too. Thanks