You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Using PnP, there doesn't to be an efficient way to find out which teams a particular user belongs to if there are thousands of teams within a tenant.
Describe the solution you'd like
Create the equivalent of the Teams PowerShell module's Get-Team -User <upn> command.
Describe alternatives you've considered
The obvious approach restricting myself to just using PnP is to use Get-PnPTeamsTeam to first get all the Teams with the tenant, and then pipe that into Get-PnPTeamsUser to get all the members of each team, and then checking to see if the is in that list of members.
If I don't restrict myself to using just the PnP modules, the Microsoft Teams module offers the Get-Team cmdlet which takes a -User parameter for just getting the teams for which the user belongs to. The Azure AD modules also offer cmdlets to search for which AD groups a user belongs to.
Is there currently a way of solving your problem with existing cmdlets? Optionally through the use of other PowerShell Modules (for instance by using the Microsoft Graph cmdlets or the Microsoft SPO Management Shell)
The obvious approach restricting myself to just using PnP is to use Get-PnPTeamsTeam to first get all the Teams with the tenant, and then pipe that into Get-PnPTeamsUser to get all the members of each team, and then checking to see if the is in that list of members.
If I don't restrict myself to using just the PnP modules, the Microsoft Teams module offers the Get-Team cmdlet which takes a -User parameter for just getting the teams for which the user belongs to. The Azure AD modules also offer cmdlets to search for which AD groups a user belongs to.
Additional context
Our tenant has over 20000 Teams.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Using PnP, there doesn't to be an efficient way to find out which teams a particular user belongs to if there are thousands of teams within a tenant.
Describe the solution you'd like
Create the equivalent of the Teams PowerShell module's
Get-Team -User <upn>
command.Describe alternatives you've considered
The obvious approach restricting myself to just using PnP is to use
Get-PnPTeamsTeam
to first get all the Teams with the tenant, and then pipe that intoGet-PnPTeamsUser
to get all the members of each team, and then checking to see if the is in that list of members.If I don't restrict myself to using just the PnP modules, the Microsoft Teams module offers the
Get-Team
cmdlet which takes a-User
parameter for just getting the teams for which the user belongs to. The Azure AD modules also offer cmdlets to search for which AD groups a user belongs to.Is there currently a way of solving your problem with existing cmdlets? Optionally through the use of other PowerShell Modules (for instance by using the Microsoft Graph cmdlets or the Microsoft SPO Management Shell)
The obvious approach restricting myself to just using PnP is to use
Get-PnPTeamsTeam
to first get all the Teams with the tenant, and then pipe that intoGet-PnPTeamsUser
to get all the members of each team, and then checking to see if the is in that list of members.If I don't restrict myself to using just the PnP modules, the Microsoft Teams module offers the
Get-Team
cmdlet which takes a-User
parameter for just getting the teams for which the user belongs to. The Azure AD modules also offer cmdlets to search for which AD groups a user belongs to.Additional context
Our tenant has over 20000 Teams.
The text was updated successfully, but these errors were encountered: