Table of Contents
Creating and managing resource accounts in Microsoft Teams is a fundamental step for administrators who need to manage features like auto attendants and call queues, which are used for handling incoming calls to an organization. Resource accounts are objects in Microsoft Teams that give these services a phone system identity.
To create a resource account, you need to have the necessary administrative privileges in the Microsoft Teams admin center or through PowerShell. Follow these steps to create a resource account in the Teams admin center:
Alternatively, you can use PowerShell to create a resource account by using the New-CsOnlineApplicationInstance
cmdlet, which would look like this:
New-CsOnlineApplicationInstance -UserPrincipalName [email protected] -DisplayName “Resource Account” -ApplicationId 11cd3e2e-fccb-42ad-ad00-878b93575e07
For example, creating an auto attendant could be as simple as:
New-CsAutoAttendant -Identity “Auto Attendant for Main Line” -ApplicationId (Get-CsOnlineApplicationInstance -Identity [email protected]).ApplicationId
Remember to assign a license to the resource account if you want to assign a phone number directly.
After creation, resource accounts can be managed in the Teams admin center or via PowerShell. You can assign or configure a phone number, link it to an auto attendant or call queue, and modify the resource account settings.
Here is how you can manage a resource account through the Teams admin center:
PowerShell can also be used to manage resource accounts. Here’s an example of how to set up a phone number for a resource account:
Set-CsOnlineVoiceApplicationInstance -Identity [email protected] -TelephoneNumber +1234567890
Resource accounts are directly linked to auto attendants and call queues. Here are some considerations for management:
Feature | Management through Teams admin center | Management through PowerShell |
---|---|---|
Auto Attendants | Can be configured under “Voice” > “Auto attendants” | Use Set-CsAutoAttendant cmdlet |
Call Queues | Can be configured under “Voice” > “Call queues” | Use Set-CsCallQueue cmdlet |
Resource Accounts | Can be created and managed under “Org-wide settings” > “Resource accounts” | Use New-CsOnlineApplicationInstance and related cmdlets |
Assigning Phone Numbers | – | Use Set-CsOnlineVoiceApplicationInstance cmdlet |
Consider the scenario where a company wants to set up an auto attendant for their customer service hotline using a resource account. The following steps would be taken:
In summary, resource accounts in Microsoft Teams are central to the functionality of auto attendants and call queues. Administrators can create and manage these accounts effectively using both the Microsoft Teams admin center and PowerShell commands. Proper management of these accounts ensures that incoming calls to an organization are handled efficiently and according to business needs.
Answer: A) True
Explanation: A resource account is used to associate Microsoft Teams Rooms with the Teams service, enabling a Teams meeting space to be scheduled and managed.
Answer: C) Resource accounts for rooms and equipment
Explanation: Resource accounts in Microsoft Teams are used for rooms and equipment to integrate these physical resources with Teams scheduling and management.
Answer: A) True
Explanation: A Microsoft 365 phone system license can be assigned to a resource account if you want it to be used for direct routing or to have a phone number associated with an audio conferencing bridge.
Answer: B) Microsoft 365 Phone System Virtual User
Explanation: The Microsoft 365 Phone System Virtual User license is provided for resource accounts that are used by auto attendants or call queues without additional costs.
Answer: B) False
Explanation: Resource accounts are not meant for individual use, hence do not require licenses to schedule meetings. However, they might need licenses for other functionalities like making calls.
Answer: B) Create a user account
Explanation: A resource account is essentially a special type of user account, so you need a user account to represent the Teams Room or other resource in Office 365 before you can transform it into a resource account.
Answer: B) False
Explanation: Resource accounts are not created in the Microsoft Teams admin center. They are created in the Microsoft 365 admin center or using PowerShell, after which you can manage them in the Teams admin center.
Answer: C) Assign a Calling Plan or configure Direct Routing
Explanation: To assign a phone number to a resource account, you must either assign a Calling Plan license to the resource or configure Direct Routing for it.
Answer: B) False
Explanation: Typically, a single resource account is used for one conference room. While it can have different capabilities assigned, creating multiple accounts for the same physical space is neither necessary nor recommended.
Answer: C) To provide a voice menu system for call routing
Explanation: In the context of Microsoft Teams’ auto attendant service, a resource account is used to provide a voice menu system for callers to be able to navigate and be routed to the appropriate department or person.
A resource account is a type of account in Microsoft Teams that represents a non-human entity, such as a conference room, equipment, or a team.
Resource accounts can be created in the Microsoft Teams admin center or through PowerShell.
Resource accounts can be assigned a display name, email address, location, and capacity, among other settings.
Resource accounts can only be managed by administrators.
Resource delegates are users who can manage resource accounts on behalf of the resource owner.
Resource delegates can be added in the Microsoft Teams admin center or through PowerShell.
Resource accounts are used to represent non-human entities, while user accounts are used to represent individuals.
Yes, a resource account can be used to join a meeting in Microsoft Teams, either through the web or the desktop app.
The calendar of a resource account can be viewed in the Teams web app or in the Outlook desktop app.
Yes, resource accounts can be used for calling and messaging in Microsoft Teams, depending on the settings configured for the account.
The auto-accept setting determines whether meeting requests for the resource account are automatically accepted or require approval from a delegate.
Resource accounts can be deleted in the Microsoft Teams admin center or through PowerShell.
Yes, resource accounts can be used for file sharing in Microsoft Teams, depending on the settings configured for the account.
The booking options setting allows administrators to control how far in advance meetings can be booked for the resource account.
No, a resource account cannot be converted into a user account in Microsoft Teams.
If this material is helpful, please leave a comment and support us to continue.