Share via

Teams Tidbit - Controlling Teams provisioning

  • Article

Hello All,

Going thru all my sticky notes I saw this was a topic of interest to you so I thought I would do some quick digging and provide you a high level look.

If you are interested in further information let me know and we can work out the details for a 1 or 2 hour discussion.

Installation of Teams:

Microsoft has provided MSI files (32-bit or 64-bit)to help you in your deployment of the Teams application thru tools like GPO or SCCM.  Things to consider:

  1. It’s recommended that you install to the default location, otherwise updating the application will be complicated.
  2. When installing the MSI we recommend except all defaults
  3. Application will update itself thru O365 service
  4. Target machine recommendations
    1. .NET Framework 4.5 or later
    2. Windows 7 or later
    3. 3GB of free disk pace for each profile

Control thru Portal:

By now you should be seeing the new Teams & Skype admin center (You may or may not) so I will talk only about that portal.  For more information about managing teams without the new portal, please see here.

During the migration any settings like Email integration, Cloud storage, Calls and Meetings, and messaging will be migrated to the new admin portal for you.

Here are the policies that you can apply to Teams:

  1. Microsoft Teams messaging policy: Create policy for user-level management of the Microsoft Teams client experience for Messaging scenarios.
  2. Microsoft Teams upgrade policy: Configure the interoperability and upgrade experience between Skype for Business and Microsoft Teams. See, https://docs.microsoft.com/en-us/microsoftteams/migration-interop-guidance-for-teams-with-skype.
  3. Microsoft Teams guest messaging settings: Control the messaging capabilities for guest accounts in Microsoft Teams.
  4. Federation settings: Manage the federation between tenants for Microsoft Teams and Skype for Business.
  5. User management: Assign policies and configure user accounts.
  6. Audio conferencing: Configure dial-in numbers and settings for Skype for Business and Microsoft Teams.

Control thru PowerShell:

First of all, as of 6/1/2018 the O365 Teams PowerShell module is in Beta and is not fully supported for production use.

Follow instructions on this page to download/install the module.  NOTE: At the bottom of this page it will list any updates that are released for the module

Add-TeamUser - Adds an owner or member to the team, and to the unified group which backs the team.

Connect-MicrosoftTeams - Connects an authenticated account to use for Microsoft Teams cmdlet requests

Disconnect-MicrosoftTeams - Disconnects an authenticated account to use for Microsoft Teams cmdlet requests

Get-Team - Gets all the teams that the user belongs to

Get-TeamChannel - Get all the channels for a team.

Get-TeamFunSettings - Gets a team's fun settings.

Get-TeamGuestSettings - Gets Team guest settings.

Get-TeamHelp - Gets a list of commands for Microsoft Teams.

Get-TeamMemberSettings - Gets team member settings.

Get-TeamMessagingSettings - Gets team messaging settings.

Get-TeamUser - Returns users of a team.

New-Team - This cmdlet lets you provision a new Team for use in Microsoft Teams and will create an O365 Unified Group to back the team.

New-TeamChannel - Add a new channel to a team.

Remove-Team - Deletes a team.

Remove-TeamChannel - Delete a channel. This will not delete content in associated tabs.

Remove-TeamUser - Remove an owner or member from a team, and to the unified group which backs the team.

Set-Team - Updates a team.

Set-TeamChannel - Update Team channels settings.

Set-TeamFunSettings - Update Giphy, Stickers and Memes settings.

Set-TeamGuestSettings - Updates team guest settings.

Set-TeamMemberSettings - Updates team member settings.

Set-TeamMessagingSettings - Updates team messaging settings.

Set-TeamPicture - Update the team picture.

Pax