(tick) Ensure you know about the Required Permissions for Nimbus. Consent will be requested from the corresponding users during service team provisioning and first login.

(warning) About Hybrid-Deployment:  Deployments in hybrid namespaces may be possible, but are much more complex while offering no functional benefit. Luware only tests and supports service deployments in online-only namespaces.

External access required

TENANT ADMIN You need your tenant to allow external communications with 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

(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

(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.

Before you start

 Nimbus can be added to any existing Team within MS Teams. If not marked otherwise, steps below can be performed either by a TENANT ADMIN or TEAM OWNER.

(lightbulb) Provisioning a service according to steps below will automatically apply the Advanced Routing license to your service, starting with a minimum set of Nimbus Features. Contact your service partner or Luware support if you need any other Service types with their according license applied.

(lightbulb) There is no need to create an Azure user or resource account before adding Nimbus.

First time Nimbus installation 

Existing Nimbus installation 

TENANT ADMIN Make sure you are the person to provision the first new Nimbus service on your tenant.

(info) During the first installation you will be prompted to select a region for all your (future) tenant data. 

(warning) After this decision the selection is fixed for your whole tenant and cannot be changed easily, as all your future Nimbus service teams and their call data are automatically stored under that tenant.

(lightbulb) We recommend to pick the region mainly for billing (currency) and data-law reasons. Performance should not be affected by your choice.

TEAM OWNER With Nimbus already present on your tenant and at least one service team existing.

(info) All future service provisioning can be done without having to pick a region again.

(warning) Please note that once a service has been provisioned via the steps below it is tied to a team in Microsoft Teams. It can not be easily converted to a Contact Center service. Please follow our Use Case - Setting up a Contact Center or - if you already know how to create services - learn how to manually grant individual users Service Permissions.

Add Nimbus to a Team 

  1. There are two methods to add Nimbus to a Team:
    1. Go to the store and search for Nimbus. Locate the Nimbus app and click "Add "
    2. Alternatively you can go to via Team itself, click on "Add a Tab" to install Nimbus this way.

      Equal methods to add Nimbus to a team

      (tick) You might be requested to log-into your O365 account to confirm the installation.

  2. Select the team you want to Add Nimbus to:

    1. Read and confirm the License Terms. 
    2. Change or keep the "Service Name" (default = team name) and "UPN", then confirm. 
      (lightbulb) These details can be changed later via the Service Settings.

      Nimbus installation dialogue

At this point

→ Nimbus is now being installed and a Nimbus-Tab will appear within the team channel:

  • All team members will be able to see the Nimbus tab and a limited set of features.
  • A team UPN is configured but cannot yet be called yet. (→ Provisioning is required as described below )
  • Existing team roles (owner and member) are included as Nimbus users.
  • Calls from outside your tenant can't be made just yet. 

(tick) Further settings are required, e.g. to assign a PSTN → Continue with the next step which will venture into the newly created team's Service Settings.

Grant Consent

TENANT ADMIN recommended. Nimbus will ask each (new, individual) user for User Permissions. As a Tenant Admin you can give this consent once so new users are not required to do this individually. 

  1. Open the User Settings
  2. Under "Admin Permissions" review and grant all required permissions. → The status changes to a Checkmark (tick).

(question) Why is this required and what happens if these rights are not granted? Nimbus will only support basic MS Teams functionality. Check the Required User Permissions page for more details on how to manage and revoke these rights.

(warning) Until Admin consent is granted, every new Nimbus user is added as as Team owner. Without consent Nimbus cannot verify which user is a MS Teams "Team Owner" or "Team Member". "Team Owner" is applied as default to allow fast changes to service Configuration and Service Settings.  As soon as admin consent is granted the membership will be synced and only the "Team Owners" will have future access to service settings and configuration.

Adapt Service Details

Now it's time for some last adjustments to get the team publicly registered in Microsoft Azure (Cloud) and assign a PSTN (if required).
(lightbulb) This step should be done in conjunction with the (future) Service Team Owner and the Tenant Admin on standby.

(tick) Precondition: Nimbus has been added to a team → The Nimbus tab is visible for that team.

  1. When opening Nimbus via the Tab for the first time you are required to log in. Afterwards you will be presented with a screen like the following: 
  2. Go to the Service Settings > "General" Tab
  3. Double-Check Service Display Name and UPN and adapt as needed.
    (info) If you are hybrid deployment, use the online-only namespace such as "" to avoid issues. Also refer to our → preconditions on top of this page.
  4. Optionally you can also assign an external PSTN / E.164 number for your Nimbus team.  This requires additional licenses distributed by Microsoft. (Learn more → Refer to "Microsoft 365 Phone System - Virtual User")
  5. Confirm your changes with "Safe & Trigger". Your tenant admin will need to run the provisioning script to apply these changes

    (question) Why is this needed? The Script run will require Tenant Admin TENANT ADMIN permissions as it will connect to Azure and register the service or potential settings.
    (tick) Note that any changes will always require another Script Run / Runbook Re-Trigger. Details are explained in the next step.

Script Run & Test Call

  1. TENANT ADMIN required task: Each service settings change that affects the endpoint or licensing must be confirmed by a Tenant Administrator. When setting changes are complete, execute the PowerShell script and follow instructions inside

    Infos on the Script

    (info) Further details on this process can be found on Provisioning via Microsoft PowerShell. The script can be downloaded from within Administration or your User Settings.

    The Nimbus provisioning scripts are automatically propagated with the necessary team information, so there is no need for you to update or manipulate the script manually. 

    • Upon first execution the script may automatically download necessary dependencies on your system.
    • The script is version-controlled, so trying to execute an outdated version will result in an error message and a link where the latest version can be found.
    • Every change to the team (e.g. UPN, PSTN or other vital Service settings) will require a re-execution of the script by any user with tenant administrator rights. Other settings without script & execute indicators are applied immediately.
    • Changes to the PSTN / E.164 settings are depending on Microsoft's response time and outside of Nimbus "jurisdiction". Please allow for at least 5 minutes for any changes to apply to Azure.
  2. TEAM OWNER recommended task: Once the script was executed by an administrator all endpoint and necessary licenses should be established.

    You can now start a Test Call (available within Service Settings > "General" tab) to see if the bot is taking calls and routing them towards your new (service) team.

(lightbulb) Note that test calls are treated like any other call and are counted towards the Reporting metrics. They should be reflected in Nimbus reporting tabs accordingly.
(lightbulb) Note that test calls will only contact the UPN of the service. If you want to test PSTN functionality, you have to make a manual phone call.

All done? Some recommended next steps

  • Once basic setup is complete you can start the Configuration of your service, e.g. to test various Service SettingsWorkflows and other features.
  • We recommended to add further "Active" Nimbus service users to your team to handle the incoming test calls in a "closer to real life test scenario".
  • Once you are happy with the results, check out our List of Use Cases for.