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


External access required

TENANT ADMIN You need your tenant to allow external communications with Luware.com

(tick) Necessary configuration steps are described in the Microsoft Teams Documentation: Manage external Access.


(question) Why is this necessary? If this is not done then Nimbus calls won't get through as the presence cannot be read.  All Nimbus users will be shown as offline and cannot get call invitations.

Provisioning Steps

Add Nimbus to a Team

(tick) Precondition: The Nimbus Installation was done by your Tenant Administrator. Your future Teams Channel which are to use Nimbus must already exist.


  1. Go to the store again and search for Nimbus
  2. Locate the Nimbus app and click "Add"
    (lightbulb)Alternatively you can go to via Team itself, click on "Add a Tab" to install Nimbus this way.


    (tick) You might be requested to log-into your O365 account to confirm the installation.
    → (lightbulb) Note: Depending on your partnership Luware and the App installed the name variant of the Nimbus App may vary.

  3. Select / Search for 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 is now being installed and a Nimbus-Tab will appear within the team channel. 

At this point:

  • All team members will be able to see the Nimbus tab and access some features.
  • A team UPN is configured but cannot yet be called yet. (→ the next "Provisioning" step required)
  • 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.

Adapt Service Details

TEAM OWNER or TENANT ADMIN  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. TEAM OWNERWhen 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:
    1. Double-Check Service Display Name and SIP-address and adapt as needed.
      (lightbulb) If you are hybrid, use the online-only namespace such as lunifico.microsoft.com to make it simpler.
    2. 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")
  3. Confirm your changes with "Safe & Trigger". An automatic trigger of Runbook works only when Microsoft Runbook has been deployed by your TENANT ADMIN

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

Service Changes / Script Run & Test Call

TENANT ADMIN required: Each Service change must be confirmed by the Tenant Administrator. Either by Runbook confirmation or Provisioning via Microsoft PowerShell.

  1. When all settings are made, 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.

    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. You can also retrieve the latest version of the script from the corresponding Nimbus Team Service Settings.
    • Every change to the team (e.g. Name, UPN or other Service settings) will require a re-execution of the script by any user with tenant administrator rights.
    • 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 Optionally you can now start a Test Call (also from within the Service Settings) to your team to see if the bot is taking calls.

    (tick) We recommended to add further "Active" Nimbus service users to your team to handle the incoming test call. 
    (tick) You can now start Configuration of your service, e.g. to test various Service SettingsWorkflows and other features.
    (lightbulb) Note that test calls are treated like any other call and are counted towards the Reporting metric. They should be reflected in Nimbus tabs accordingly.