How Nimbus users relate to MS Teams Client roles

Within the MS Teams Client Nimbus will use your existing structures to authenticate any team members as users of Nimbus.

(lightbulb) Please note that we use the terms "service" and "user" in Nimbus to differentiate between MS "teams" channels and its "members" respectively. More info on terms like these can be found in the Nimbus Glossary.

RoleInstallation-related Tasks

TENANT ADMIN

Tenant Admin is required to execute the Nimbus Installation in your company tenant and

The Installation prerequisites on this page and most chapters under Nimbus Installation and Service Provisioning are mainly addressed at Tenant Admins or users with similar roles in your company.

TEAM OWNER

Team Owner is a service administrator in Nimbus and

    • can add the Nimbus application to the Teams Client when Nimbus Installation is complete.
    • can execute Service Provisioning (may require Tenant Administrator assistance where highlighted).
    • can change service Service Settings. Certain settings need to be approved by the Tenant admin.

TEAM MEMBERS

 Team Member is a service user (or agent) in Nimbus and

GUEST MEMBERS

Do not exist in Nimbus.

Script execution and impersonation permissions

Nimbus is deployed and (re)configured using Powershell scripts.

  • You need Tenant permissions to use Powershell for Nimbus deployment. (info) More infos on Provisioning via Microsoft PowerShell
  • On first script run we highly recommend to start the Powershell session as administrator to ensure that necessary dependencies are installed. Our scripts will retrieve dependencies automatically an install them on your running PC if necessary.
  • A re-execution is needed for every service team deployment or service update as the changes need to be pushed to Azure. This process can be automated with Runbook. (info) How to deploy Microsoft Runbook.

External Communication


External access required

TENANT ADMIN You need your tenant to allow external communications with Luware.com. Necessary configuration steps are described in the Microsoft Teams Documentation: Manage external Access.

Some of our customers also use the "Enhanced Presence Privacy Mode" as a global policy, which can be checked via PowerShell:

Get-CsPrivacyConfiguration | Select EnablePrivacyMode
POWERSHELL

(lightbulb) This is a legacy policy used in Lync/SfB which is not available anymore in the Microsoft Teams Admin Center. This is a global setting and always applies to all users of the organization, and unfortunately cannot be deactivated or bypassed for individual users.

(warning) If EnablePrivacyMode is set to True, no one can see the Teams Presence status of the users via Teams Federation - and thus Nimbus functionality is completely disabled. To deactivate this policy, run the following command:

Set-CsPrivacyConfiguration -EnablePrivacyMode $false
POWERSHELL

(question) Why are these steps necessary? Nimbus calls won't get through or distributed as the presence cannot be read.  All Nimbus users will be shown as offline and cannot get call invitations.

PSTN Licensing


Transfer to PSTN limitation

Out of box Nimbus and affiliated addons can only perform PSTN transfers according to Microsoft services licensing & constraints.

Which PSTN license do I need to acquire?

(tick) As a tenant administrator you need to acquire and assign the following licenses to the application instance of the respective Nimbus SOURCE service (team) that will act as PSTN transferor:

Your SetupRequired License
Microsoft Phone System Direct Routing
"Microsoft Teams" (App license, available as part of the Microsoft 365 E1 / E3 / E5 and other packages)
+ "Microsoft Teams Phone Standard" or "Microsoft Teams Phone Standard - Virtual User"
Microsoft Phone System with Calling Plan


"Microsoft Teams Phone Standard" or "Microsoft Teams Phone Standard - Virtual User" 
+ "Microsoft 365 Domestic Calling Plan" or "Microsoft 365 Domestic and International Calling Plan"
+ "
Communication Credits" (if these aren't already included as part of your plan)
How does PSTN licensing affect Service and Call Transfers?

Assuming that Service A has a PSTN license assigned - but further Services don't - the following scenario may unfold:

  • Scenario A - Service A workflow is configured to transfer the caller to Service B. The license of Service A is used, the PSTN transfer occurs. The PSTN license is re-used throughout further transfers to Services C..D...x.
  • Scenario B - Service B is called directly instead. Now the workflow of Service B attempts a redirect to either service A or transfer to C. The PSTN transfer fails due to a missing license on Service B.

Learnings

  • For one first-level-response Service: If you handle first-response calls always via the same Service you need a PSTN license for that particular first-level Service.
  • For multiple first-level-response Services: If you handle first-response calls always via multiple Services you need a PSTN license for all those first-level Services .
  • Nimbus will attempt to use the PSTN license of the first service that responded to a call, regardless of how many further internal service transfers are performed thereafter.
  • If no PSTN license is found on a service that requires it for a transfer, the transfer task will be considered as failed and be treated as such by the system (e.g. workflow exit announcement, reporting "transfer failed" outcome).

(warning) Note that handling and tracking of running cost for PSTN licenses is outside of Luware support scope.
If you require assistance in extending and/or configuring your Nimbus services for PSTN our support will gladly assist you:


(info) Refer to the external reference: Microsoft Teams add-on licenses.

Phone Number configuration

When managing your Phone Numbers for usage of Nimbus services, please note the following:

  • If you're using "Direct Routing" (Numbers managed outside of Teams) you can assign any phone number to a Nimbus service.
  • If you're using calling plans for Microsoft you can only assign a "Service" number type. "User (subscriber)" type numbers will not work.

Further information can be found on in the MSFT documentation: Types of phone numbers used for Calling Plans.