Deploy Microsoft Teams Rooms with Exchange on premises
Read this topic for information on how to deploy Microsoft Teams Rooms in a hybrid environment with Exchange on premises and Microsoft Teams or Skype for Business Online.
If your organization has a mix of services, with some hosted on premises and some hosted online, then your configuration will depend on where each service is hosted. This topic covers hybrid deployments for Microsoft Teams Rooms with Exchange hosted on premises. Because there are so many different variations in this type of deployment, it's not possible to provide detailed instructions for all of them. The following process will work for many configurations. If the process isn't right for your setup, we recommend that you use Windows PowerShell to achieve the same end result as documented here, and for other deployment options.
Microsoft provides SkypeRoomProvisioningScript.ps1, a script that will help create new user accounts, or validate existing resource accounts you have in order to help you turn them into compatible Microsoft Teams Rooms user accounts. If you prefer, you can follow the steps below to configure accounts your Microsoft Teams Rooms device will use.
Before you deploy Microsoft Teams Rooms with Exchange on premises, be sure you have met the requirements. For more information, see Microsoft Teams Rooms requirements.
If you are deploying Microsoft Teams Rooms with Exchange on premises, you will be using Active Directory administrative tools to add an email address for your on-premises domain account. This account will be synced to Microsoft 365 or Office 365. You will need to:
Create an account and synchronize the account with Active Directory.
Enable the remote mailbox and set properties.
Assign an Microsoft 365 or Office 365 license.
Enable the device account with Skype for Business Server. To enable the device account your environment will need to meet the following prerequisites:
You'll need to have Skype for Business Online (Plan 2) or higher in your Microsoft 365 or Office 365 plan. The plan needs to support conferencing capability.
If you need Enterprise Voice (PSTN telephony) using telephony service providers for Microsoft Teams Rooms you need Skype for Business Online (Plan 3).
Your tenant users must have Exchange mailboxes.
Your Microsoft Teams Rooms account does require a Skype for Business Online (Plan 2) or Skype for Business Online (Plan 3) license, but it does not require an Exchange Online license.
Assign a Skype for Business Server license to your Microsoft Teams Rooms account.
Create an account and synchronize with Active Directory
In the Active Directory Users and Computers tool, right-click on the folder or Organizational Unit that your Microsoft Teams Rooms accounts will be created in, click New, and then click User.
Type the display name from the previous cmdlet into the Full name box, and the alias into the User logon name box. Click Next.
Type the password for this account. You'll need to retype it for verification. Make sure the Password never expires checkbox is the only option selected.
Selecting Password never expires is a requirement for Skype for Business Server on Microsoft Teams Rooms. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Microsoft Teams Rooms device account.
After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Microsoft 365 admin center and verify that the account created in the previous steps has merged to online.
Enable the remote mailbox and set properties
In Exchange PowerShell, create a mailbox for the account (mailbox-enable the account) by running the following command:
Enable-Mailbox PROJECTRIGEL01@contoso.com -Room
For detailed syntax and parameter information, see Enable-Mailbox.
In Exchange PowerShell, configure the following settings on the room mailbox to improve the meeting experience:
AutomateProcessing: AutoAccept (Meeting organizers receive the room reservation decision directly without human intervention: free = accept; busy = decline.)
AddOrganizerToSubject: $false (The meeting organizer is not added to the subject of the meeting request.)
DeleteComments: $false (Keep any text in the message body of incoming meeting requests.)
DeleteSubject: $false (Keep the subject of incoming meeting requests.)
RemovePrivateProperty: $false (Ensures the private flag that was sent by the meeting organizer in the original meeting request remains as specified.)
AddAdditionalResponse: $true (The text specified by the AdditionalResponse parameter is added to meeting requests.)
AdditionalResponse: "This is a Skype Meeting room!" (The additional text to add to the meeting request.)
This example configures these settings on the room mailbox named Project-Rigel-01.
Set-CalendarProcessing -Identity "Project-Rigel-01" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false -DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This is a Skype Meeting room!"
For detailed syntax and parameter information, see Set-CalendarProcessing.
Assign a Microsoft 365 or Office 365 license
Connect to Azure Active Directory. For details about Active Directory, see Azure ActiveDirectory (MSOnline) 1.0.
Azure Active Directory PowerShell 2.0 is not supported.
The device account needs to have a valid Microsoft 365 or Office 365 license, or Exchange and Microsoft Teams will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account. You can use
Get-MsolAccountSkuto retrieve a list of available SKUs.
- Next, you can add a license using the
Set-MsolUserLicensecmdlet. In this case, $strLicense is the SKU code that you see (for example, contoso:STANDARDPACK).
Set-MsolUser -UserPrincipalName 'PROJECTRIGEL01@contoso.com' -UsageLocation 'US' Get-MsolAccountSku Set-MsolUserLicense -UserPrincipalName 'PROJECTRIGEL01@contoso.com' -AddLicenses $strLicense
For detailed instructions, see Assign licenses to user accounts with Office 365 PowerShell.
Enable the device account
Skype for Business Online PowerShell is used to manage services for both Microsoft Teams and Skype for Business Online.
- Create a remote Windows PowerShell session from a PC as follows:
Skype for Business Online Connector is currently part of the latest Teams PowerShell module.
If you're using the latest Teams PowerShell public release, you don't need to install the Skype for Business Online Connector.
Import-Module -Name MicrosoftTeams $cssess=New-CsOnlineSession -Credential $cred Import-PSSession $cssess -AllowClobber
Obtain SIP address of the account:
$rm = Get-Csonlineuser -identity <insert SIP address> | select -expandproperty sipaddress
To enable your Microsoft Teams Rooms account, run this command:
Enable-CsMeetingRoom -Identity $rm -RegistrarPool'sippoolbl20a04.infra.lync.com' -SipAddressType EmailAddress
If you aren't sure what value to use for the RegistrarPool parameter in your environment, you can get the value from an existing user using this command:
Get-CsOnlineUser -Identity 'email@example.com'| fl *registrarpool*
Assign a license to your Microsoft Teams Rooms account
- Log in as a tenant administrator, open the Microsoft 365 admin center, and click on the Admin app.
- Click on Users and Groups and then click Add users, reset passwords, and more.
- Click the Microsoft Teams Rooms account, and then click the pen icon to edit the account information.
- Click Licenses.
- In Assign licenses, select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Microsoft Teams Rooms.
- Click Save.
For validation, you should be able to use any client to log in to this account.