Create and configure resource accounts for rooms and shared Teams devices
This article provides steps to create resource accounts for shared spaces and devices, and it includes steps to configure resource accounts for Microsoft Teams Rooms on Windows, Teams Rooms on Android, Teams Rooms on Surface Hub, and hot-desking on Teams displays.
Microsoft 365 resource accounts are mailbox and Teams accounts that are dedicated to specific resources, such as a room or projector. These resource accounts can automatically respond to meeting invites using rules you define when they're created. For example, if you have a common resource such as a conference room, you can set up a resource account for that conference room that will automatically accept or decline meeting invites depending on its calendar availability.
Every resource account is unique to a single Microsoft Teams Rooms installation or Teams display hot-desking implementation.
If using Microsoft Teams panels, the Teams Rooms resource account signs in to both Teams Rooms and associated Teams panels.
Microsoft 365 resource accounts aren't the same as Teams resource accounts. Teams resource accounts can be used with call queues and auto attendants to accept phone calls from external phone numbers. Microsoft 365 resource accounts are tied to an Exchange Online mailbox and enable booking of shared resources, such as rooms, projectors, and so on.
If you want to know more about Teams resource accounts, see Manage resources accounts in Microsoft Teams.
Skype for Business
If you need to enable your resource account to work with Skype for Business, see Deploy Microsoft Teams Rooms with Skype for Business Server
Before you begin
Depending on your environment, you need one or more roles to create resource accounts.
|Azure Active Directory
||Global Administrator or User Administrator
||Active Directory Enterprise Admins, Domain Admins, or have delegated rights to create users. Azure Active Directory Connect Sync rights.
||Global Administrator or Exchange Administrator
||Exchange Organization Management or Recipient Management
If you're creating resource accounts for Teams Rooms, the UPN must match the SMTP address of the resource account. See Microsoft Teams Rooms requirements before you deploy Teams Rooms.
What license do you need?
Before you create a Microsoft 365 resource account, check to see what kind of license it needs:
Teams meetings If you want to associate the resource account with a shared device, such as a Microsoft Teams Room or Teams display with hot-desking, and use it to join a Teams meeting so attendees can use it to present video and audio through it, you need a Meeting Room License. For more information about licensing for meeting rooms, see Teams Meeting Room Licensing.
PSTN calls If you want the resource to make or receive calls to or from an external phone number (called a Public Switched Telephone Network or PSTN call), you need a Microsoft 365 Phone System or Microsoft 365 Business Voice license. You only need to complete Step 1 in the following overview. Then, see Microsoft Teams add-on licenses for more information.
If you're only using a resource account to book a resource—that is, invite the resource to your meeting and have it automatically accept or decline the invitation—you don't need to assign a license to the resource account and you only need to complete Step 1 in the following overview.
Step 2 - Then, configure your account for Teams Meetings.
Step 3 - If the resource account is going to be associated with a shared device, such as Teams displays with hot-desking, turn off password expiration.
Step 4 - Lastly, assign a meeting room license so the account can access Microsoft Teams.
After you create and configure your resource accounts, see Next steps to review additional setup tasks, including distribution groups, network capability, and calling.
Create a resource account
When naming your resource accounts, we recommend using a standard naming convention to the beginning of the e-mail address. This will help with creating dynamic groups to ease management in Azure Active Directory. For example, you could use "mtr-" for all resource accounts that will be associated with Microsoft Teams Rooms.
We recommend that you create all resource accounts using Exchange Online and Azure Active Directory.
Create a resource account using a method from one of the following tabs:
- In Microsoft 365 admin center
- With Exchange Online
- With Exchange Server
- Modify an existing Exchange room mailbox
Sign in to the Microsoft 365 admin center.
Provide the admin credentials for your Microsoft 365 tenant.
Go to Resources in the left panel, and then select Rooms & equipment. If these options aren't available in the left panel, you may need to select Show all first.
Select Add a resource mailbox to create a new room account. Enter a display name and email address for the account, select Add, and then select Close.
By default, resource accounts are configured with the following settings:
- Allow repeat meetings
- Automatically decline meetings outside of the following limits
- Booking window (days): 180
- Maximum duration (hours): 24
- Auto accept meeting requests
If you want to change them, select Set scheduling options before you select Close. If you want to change them later, go to Resources > Rooms & equipment, select the resource account. Then under Booking options, select Edit.
Go to Users > Active users, and select the room you created to open the properties panel.
Next, assign a password to the resource account. In the panel, select Reset password.
Requiring users to change the password on a shared device will cause sign in problems. Uncheck Require this user to change their password when they first sign in, and select Reset.
In the Licenses and Apps section, set Select location to the country or region where the device will be installed. Then select the license you want to assign, such as Meeting Room, and select Save changes. The license may vary depending on your organization.
To change the settings of the resource mailbox, see Configure mailbox properties or use the Exchange admin center.
You may also need to apply bandwidth policies or meeting policies to this account. See Next steps for more information.
If you're only using this resource account to book space and automatically accept or decline invitations, you've completed the set up. If you're using this resource account for PSTN calling, see Microsoft Teams add-on licenses to determine what license it needs.
Continue to the next section only if the resource account is for a Teams Rooms on Windows, Teams Rooms on Android, Teams Rooms on Surface Hub, or a Teams display with hot-desking.
Configure mailbox properties
In Exchange PowerShell, either online or on-premises, configure the following settings on the room mailbox to improve the meeting experience:
AutoAcceptMeeting organizers receive the room reservation decision directly without human intervention.
$falseThe meeting organizer isn't added to the subject of the meeting request.
$falseKeep any text in the message body of incoming meeting requests. This is required to process external Teams and third-party meetings to provide One Touch Join experience.
$falseKeep the subject of incoming meeting requests.
$trueSpecifies whether to process meeting requests that originate outside the Exchange organization. Required for external Teams meetings and third-party meetings.
$falseEnsures the private flag that was sent by the meeting organizer in the original meeting request remains as specified.
$trueThe text specified by the AdditionalResponse parameter is added to meeting requests.
AdditionalResponse: "This is a Microsoft Teams Meeting room!" The additional text to add to the meeting acceptance response.
This example configures these settings on a room mailbox named ConferenceRoom01:
Set-CalendarProcessing -Identity "ConferenceRoom01" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false -DeleteComments $false -DeleteSubject $false -ProcessExternalMeetingMessages $true -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This is a Microsoft Teams Meeting room!"
For detailed syntax and parameter information, see Set-CalendarProcessing.
Turn off password expiration
If the resource account password expires, the device won't sign in after the expiration date. The password will then need to be changed for the resource account and then updated on each device. To avoid this, you can turn off password expiration.
Setting Password never expires is a requirement for shared Microsoft Teams devices. If your domain rules prohibit passwords that don't expire, you'll need to create an exception for each Teams device resource account.
Follow the steps in one of the following tabs to turn off password expiration:
First, Connect to Active Directory PowerShell:
Then, see Set a password to never expire.
This example sets the password for the account ConferenceRoom01@contoso.com to never expire.
Set-AzureADUser -ObjectID ConferenceRoom01@contoso.com -PasswordPolicies DisablePasswordExpiration
Assign a meeting room license
The resource account needs a Microsoft 365 or Office 365 license to sign into Microsoft Teams.
Microsoft Teams Rooms Standard and Microsoft Teams Rooms Premium are the two available SKUs for shared meeting room devices, including Teams Rooms. A meeting room license is required for Teams displays with hot-desking. For more information, see Teams meeting room licensing.
To assign licenses using the Microsoft 365 admin center, see Assign licenses to users. To assign licenses using Azure AD, see one of the following tabs:
Connect to Azure AD
For details about Active Directory, see Azure Active Directory PowerShell for Graph.
Assign a usage location to your resource account using the
Set-AzureADUsercmdlet. This determines what license SKUs are available.
In this example, the user is located in the United States (US):
Set-AzureADUser -ObjectID ConferenceRoom01@contoso.com -UsageLocation 'US'
Get-AzureADSubscribedSkuto retrieve a list of available SKUs for your Microsoft 365 or Office 365 organization.
Get-AzureADSubscribedSku | Select -Property Sku*,ConsumedUnits -ExpandProperty PrepaidUnits
To assign the license, use the
Set-AzureADUsercmdlet, and convert the license SKU ID (see step 2) into a PowerShell license type object. Then, assign that object to the resource account. In the following example, the license SKU ID is 6070a4c8-34c6-4937-8dfb-39bbc6397a60, and it's assigned to the account firstname.lastname@example.org:
#Create an object for a single license type $License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense $License.SkuId = "6070a4c8-34c6-4937-8dfb-39bbc6397a60" #Create an object for a multiple license type $Licenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses #Add the single license object to the multiple license object $Licenses.AddLicenses = $License #Assign the license to the resource account Set-AzureADUserLicense -ObjectId ConferenceRoom01@contoso.com -AssignedLicenses $Licenses
To validate the account creation and license assignment, sign in to any Teams Client using the account you created.
You may need to apply custom network, bandwidth, or meeting policies to this account. For more information on network and bandwidth policies, see Meeting policy settings for audio & video. For Teams Rooms, we recommend you set the meeting policy bandwidth to 10 Mbps.
For collaboration purposes, turn on PowerPoint Live, Whiteboard, and shared notes. It is recommended that you enable the meeting policy setting "Meet now in private meetings". You may want to create a meeting policy to adjust participants and guest settings for Teams Rooms. For example, review the lobby settings such as which attendees to automatically admit to meetings. For more information on Teams meeting policies, see Manage meeting policies in Microsoft Teams.
There are no unique requirements to enable calling with resource accounts. You enable the resource account for calling in the same way you enable a regular user.
We recommend turning off voice mail for shared devices by assigning a calling policy to the device resource accounts. See Calling and call-forwarding in Teams for more information.
Configure distribution groups for Teams Calendar
To organize your meeting room locations, you can add your device resource accounts to Exchange distribution groups. For example, if you have offices in three different geographic locations, you can create three distribution groups and add the appropriate resource accounts to each location. For more information, see Create a rooms list.
Configure places for Outlook Calendar
In order for meeting room locations to appear in the Outlook Room Finder, you need to use the Set-Place Exchange PowerShell cmdlet. Not only does Set-Place populate the Room Finder in Outlook, it also allows you to add additional metadata such as the capacity of the room or the floor of building the room is in. For more information, see Set-Place.
Indsend og få vist feedback om