Forum Discussion

2 Replies

  • Six years is fair to be annoyed about. Three options that work today.

    Nested groups is the real fix. Build a security group with everyone you need, then add that group to the team instead of adding people one at a time. Membership propagates, and anyone you add to the group later gets inherited automatically without touching the team again.

    PowerShell if you'd rather script it. Connect-MicrosoftTeams, then loop Add-TeamUser against a CSV of UPNs. Handles hundreds in about a minute, and you don't need admin rights as long as you're a team owner.

    The Teams admin center under Manage teams is slightly faster than the client, but it's still one entry at a time. Not really a bulk fix.

    It's on the feedback backlog with plenty of votes, but after six years I'd treat nested groups as the permanent answer rather than waiting for a native import.

  • ZoltanG's avatar
    ZoltanG
    Copper Contributor

    Have you considered Entra Catalogs+Access Packages? It will definitely solve the adding to multiple teams part. 

    It requires some organization, but will make things very easy in the long term.