SOLVED
Home

Show a list of all teams and owners

%3CLINGO-SUB%20id%3D%22lingo-sub-30526%22%20slang%3D%22en-US%22%3EShow%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-30526%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20a%20way%20via%20web%20console%2Fpowershell%20to%20see%20a%20list%20of%20all%20teams%20and%20owners%20under%20our%20account%3F%20%26nbsp%3BIf%20not%20is%20there%20a%20way%20to%20limit%20who%20can%20make%20a%20team%20channel%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-30526%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%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-263130%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-263130%22%20slang%3D%22en-US%22%3E%3CP%3Eis%20this%20still%20all%20there%20is%3F%20There%20needs%20to%20be%20a%20better%20solution%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165183%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165183%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20this%20post%20is%20old%20so%20PowerShell%20for%20Teams%20was%20probably%20not%20around%20at%20the%20time%20but%20it%20is%20now...%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fskypehybridguy%2F2017%2F11%2F07%2Fmicrosoft-teams-powershell-support%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fskypehybridguy%2F2017%2F11%2F07%2Fmicrosoft-teams-powershell-support%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-153559%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-153559%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20should%20help%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FMicrosoft-Teams-Enabled-O365-Groups-Report-PowerShell-CSV-Output%2Ftd-p%2F151875%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FMicrosoft-Teams-Enabled-O365-Groups-Report-PowerShell-CSV-Output%2Ftd-p%2F151875%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-123020%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123020%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20the%20posting%20this%20script%20in%20year%202016%2C%20i%20think%20yammer%20groups%20are%20not%20exist.%20You%20can%20use%20the%20below%20script.%3C%2FP%3E%3CPRE%3EGet-UnifiedGroup%20%7CWhere-Object%20%7B%24_.ProvisioningOption%20-eq%20'ExchangeProvisioningFlags%3A481'%7D%7Cselect%20DisplayName%2CAlias%2CProvisioningOption%2CGroupSKU%2CSharePointSiteUrl%2CSharePointDocumentsUrl%2CAccessType%3C%2FPRE%3E%3CP%3EThe%20above%20script%20is%20posted%20from%20the%20below%20thread.%5BRefer%20post%20by%20Santhosh%20Balakrishnan%5D%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Groups%2FPowershell-attribute-to-distinguish-where-a-group-was%2Fm-p%2F53351%23M2614%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Groups%2FPowershell-attribute-to-distinguish-where-a-group-was%2Fm-p%2F53351%23M2614%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-122964%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-122964%22%20slang%3D%22en-US%22%3EFYI%20-%20this%20also%20returns%20groups%20that%20were%20created%20in%20Yammer.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-55958%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-55958%22%20slang%3D%22en-US%22%3EGood%20stuff..%20Thanks%20for%20sharing%20as%20this%20would%20suffice%20for%20now%20until%20more%20admin%20tools%20are%20available.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-36425%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-36425%22%20slang%3D%22en-US%22%3EThanks.%20Ideally%20there%20would%20be%20Team%20commands.%20Until%20then%2C%20this%20works%20for%20me.%20(For%20those%20not%20in%20the%20know%2C%20like%20me%2C%20this%20is%20an%20Exchange%20PowerShell%20command.)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-30731%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-30731%22%20slang%3D%22en-US%22%3E%3CP%3EA%20simple%20workaround%20as%20of%20now%20to%20find%20the%20newly%20created%20teams%20is%20by%20using%20Get-UnifiedGroup.%20By%20default%20when%20a%20new%20team%20is%20created%20its%20Office%20365%20Group%20will%20also%20be%20created.%20The%20difference%20is%20between%20the%20regular%20Office%20365%20Groups%20and%20Teams%20Groups%20is%20Welcome%20message.%20It%20is%20disabled%20in%20groups%20that%20are%20created%20from%20Teams.%20This%20logic%20will%20not%20work%20when%20a%20new%20Team%20is%20created%20using%20existing%20groups.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EGet-UnifiedGroup%20%7CWhere-Object%20%7B%24_.WelcomeMessageEnabled%20-like%20%22False%22%7D%7Cselect%20Alias%2CManagedByDetails%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-30551%22%20slang%3D%22en-US%22%3ERe%3A%20Show%20a%20list%20of%20all%20teams%20and%20owners%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-30551%22%20slang%3D%22en-US%22%3EMy%20two%20cents%20here%3A%3CBR%20%2F%3E(1)%20The%20only%20way%20to%20get%20such%20information%20is%20via%20API%2C%20but%20I%20have%20not%20dug%20into%20Teams%20API%3CBR%20%2F%3E(2)%20You%20can%20limit%20Teams%20creation%20in%20the%20same%20way%20you%20can%20do%20it%20for%20Groups%20and%20Planner%3A%20by%20Azure%20AD%20Policy%3C%2FLINGO-BODY%3E
Vivek Desai
Occasional Contributor

Is there a way via web console/powershell to see a list of all teams and owners under our account?  If not is there a way to limit who can make a team channel?

9 Replies
My two cents here:
(1) The only way to get such information is via API, but I have not dug into Teams API
(2) You can limit Teams creation in the same way you can do it for Groups and Planner: by Azure AD Policy
Solution

A simple workaround as of now to find the newly created teams is by using Get-UnifiedGroup. By default when a new team is created its Office 365 Group will also be created. The difference is between the regular Office 365 Groups and Teams Groups is Welcome message. It is disabled in groups that are created from Teams. This logic will not work when a new Team is created using existing groups.

 

Get-UnifiedGroup |Where-Object {$_.WelcomeMessageEnabled -like "False"}|select Alias,ManagedByDetails
Thanks. Ideally there would be Team commands. Until then, this works for me. (For those not in the know, like me, this is an Exchange PowerShell command.)
Good stuff.. Thanks for sharing as this would suffice for now until more admin tools are available.
FYI - this also returns groups that were created in Yammer.

At the posting this script in year 2016, i think yammer groups are not exist. You can use the below script.

Get-UnifiedGroup |Where-Object {$_.ProvisioningOption -eq 'ExchangeProvisioningFlags:481'}|select DisplayName,Alias,ProvisioningOption,GroupSKU,SharePointSiteUrl,SharePointDocumentsUrl,AccessType

The above script is posted from the below thread.[Refer post by Santhosh Balakrishnan]

https://techcommunity.microsoft.com/t5/Office-365-Groups/Powershell-attribute-to-distinguish-where-a...

I know this post is old so PowerShell for Teams was probably not around at the time but it is now... https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/

 

is this still all there is? There needs to be a better solution

Related Conversations