![]() ![]() This will differ dependant on the topology you are using: With the resource account assigned it’s license it is time to assign a number to the resource account. However, I have also done one after the other without issue! It is recommended to leave at least 24 hours between license assignment and number assignment. In some cases, issues have been reported with assigning numbers just after licensing has been applied. However, you can now use a free license “Phone System - Virtual User” instead.Īssign Telephone Number to Resource Account Originally ‘E’ plan licenses + Phone System + Calling Plan was required for this. Once the account has been created and appears in the Office 365 Admin Portal (as a disabled user), it is ready to be licensed. The resource account Display Name will be shown to the Teams client when receiving calls, so bear this in mind when naming it. The -ApplicationId needs to be configured depending on if the resource account is for a CQ or AA:Īuto Attendant: ce933385-9390-45d1-9512-c8d228074e07Ĭall Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07 To create a on-premises resource account for SfB hybrid deployments (not CCE), run the following (SfB Server PowerShell): New-CsHybridApplicationEndpoint -DisplayName "Resource Account" -SipAddress sip: -ApplicationId "11cd3e2e-fccb-42ad-ad00-878b93575e07" -OU "ou=Users,dc=lee-ford,dc=co,dc=uk" To create an online resource account, run the following (SfB Online PowerShell): New-CsOnlineApplicationInstance -UserPrincipalName -ApplicationId "ce933385-9390-45d1-9512-c8d228074e07" -DisplayName "Resource Account" I’ll quickly cover the steps needed to create, license and configure a resource account: Create Resource Account For online scenarios, the resource account is created in Office 365. If you are in an SfB hybrid (not CCE), you will need to create on-premises resource account called an “HybridApplicationEndpoint”. How you create a resource account depends on the topology you have. Resource accounts are essentially entry points in to a voice application. These are not to be confused with Resource Mailboxes in Exchange. There are two parts to make a CQ or AA work - the voice application (CQ/AA) itself and resource accounts that get assigned to them. *Currently only supports Teams clients - 3PIP or SfB clients are not supported.Īs you can see there are some fundamental differences between the two. There are some key differences between the two versions that I will highlight:Ĭalling Plans, Direct Routing, CCE, SfB Hybrid (2019) You could previously create and administer the “SfB” CQ and AA in the (legacy) Skype for Business Admin Centre, but these have now been migrated as “Teams” CQ and AA in to the Teams Admin Centre. This article will give an explanation of the Teams Call Queues (CQ) and Auto Attendants (AA) - what they are and how to set them up. Last Updated: 2nd October 2019 Introduction ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |