Before you start
The Nimbus Installation must be completed before you can start with Service Provisioning.
☝Please note that Service Provisioning is not possible until your Tenant is configured on Luware side. Read the Installation Prerequisites to learn about related concepts such as Required App Permissions and License Management for Nimbus Apps and Services. Note that additional User Permissions will be requested from all onboarded Nimbus users during service team provisioning and first user login.
Once you are ready, get in touch with your Customer Success contact.
INC Nimbus External Access Requirement
EXTERNAL ACCESS REQUIRED
TENANT ADMIN You need your tenant to allow external communications with the "luware.com" domain.
Learn more about managing external access
🔍 The necessary configuration steps are described in the Microsoft Teams Documentation: Manage external Access.
You will also need to disable the "Enhanced Presence Privacy Mode" policy which prevents visibility of the Teams Presence.
About the "Enhanced Presence Privacy Mode"
The "Enhanced Presence Privacy Mode" is a global configuration which, if enabled, prevents all external organizations from viewing the Teams Presence status of your users via Teams Federation.
If this mode is enabled, Nimbus will see all users as permanently Offline, and thus won't be able to distribute calls to them.
☝ This is a legacy configuration option used in Lync / Skype for Business which is not available anymore in the Microsoft Teams Admin Center. It can only be viewed and configured via PowerShell. As a global setting it applies to all users and cannot be deactivated or bypassed for individual users.
✅ To check whether this is enabled in your tenant by running the following PowerShell command:
Get-CsPrivacyConfiguration | Select EnablePrivacyModeThe command will return "True" if the Enhance Presence Privacy Mode is enabled, or "False" (default value) if it is disabled.
✅ To deactivate it, run the following PowerShell command:
Set-CsPrivacyConfiguration -EnablePrivacyMode $false🤔 Why are these steps necessary? Without being able to read the Teams presence data of your users, Nimbus will consider them as Offline and thus not available for call distribution. They will not be able to receive any inbound calls or place any outbound calls via Nimbus.
Provisioning Steps
GOOD TO KNOW
Nimbus can be added to any existing Team within MS Teams. If not marked otherwise, all steps below can be done performed either by a TENANT ADMIN or TEAM OWNER.
🔍 Determine who can provision services: Administrators may change the minimum role needed or completely disable provisioning of new teams via Tenant Administration > Provisioning.
💡 License Management Note: Provisioning a service according to steps below will automatically apply the Advanced Routing license to your service the default set of Nimbus Features. Contact your service partner or Luware support if you need any other Service types with the according license contingency.
☝Before starting your provisioning, please note:
| First time Nimbus installation | Existing Nimbus installation |
|---|---|
TENANT ADMIN - Make sure you are the FIRST person to provision the first new Nimbus service on your tenant. Only during the first installation you will be prompted to select a region for all your (future) tenant data. Refer to the Introduction to Nimbus and our Whitepapers in the Documents section for more details on which data gets stored. ☝ After this decision is made, tenant data is stored on the corresponding region. This first selection cannot be changed, as all your future Nimbus service teams and their call data are automatically stored under that tenant. 💡 We recommend to pick the region mainly for billing (currency) and data-law / compliance 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, future Service Provisioning can be done without having to pick a region again. |
Add Nimbus to a Team
-
There are two methods to add Nimbus to a Team:
- Go to the store and search for Nimbus. Locate the Nimbus app and click "Add "
OR - Navigate to the Team itself, click on "Add a Tab" to install Nimbus this way.
- Go to the store and search for Nimbus. Locate the Nimbus app and click "Add "
Equal methods to add Nimbus to a team
💡You might be requested to log-into your O365 account to confirm the installation.
💡If a Nimbus service already existed for this team, the previous tab will be restored.
-
Select the team you want to add Nimbus to:
- Read and confirm the License Terms.
- Change or keep the "Service Name" (default = team name) and "UPN", then confirm. 💡 These details can be changed later via General Service Settings
-
Select an Organization Unit (OU) for your new service.
🤔 What is this? The OU determines placement and visibility of the new service, its users and related Configuration resources. 💡 This can be changed later via General Service Settings.
💡 When uncertain what to select here, leave this setting at its default.
💡 Note that this field may be disabled or hidden depending on your logged-in user rights.
→ 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 can access Nimbus Features.
- Note that the Service UPN is defined but cannot yet be called yet. (→ A script provisioning script run is required as described below)
- Existing MS Teams roles (owner and member) are included as Nimbus users. More on this in Role Access Concept.
- Calls from outside your tenant can't be made just yet. This requires a PSTN license assignment.
✅ 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) user for Required User Permissions. As a Tenant Admin you can give this consent once so users are not required to do this individually.
- Open the User Preferences (Portal)
- Under "Admin Permissions" review and grant all required permissions. → The status changes to a Checkmark ✅.
🤔 Why is this required and what happens if these rights are not granted? Nimbus will only support basic MS Teams functionality. Read Required User Permissions for more details on how to manage and revoke these rights.
Adapt Service Details
Now it's time for some last adjustments to get the team publicly registered in Microsoft Azure (Cloud) and assign and – if required – add an externally reachable PSTN.
✅ Precondition: Nimbus has already been added to a team → The Nimbus tab is visible for that team. This step should be done in conjunction with the (future) Service Team Owner and the Tenant Admin on standby.
- 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:
- Go to the Service Settings > "General" Tab
-
Double-Check Service Display Name and SIP-address and adapt them as needed.
💡 If you are hybrid, use the online-only namespace such as lunifico.microsoft.com to make it simpler. - 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")
-
Confirm your changes with "SAVE & APPLY".
- TENANT ADMIN Your tenant admin needs to run the provisioning script to apply changes marked with a ☝ warning sign.
🤔 Why is this needed? The Script run will require Tenant Admin permissions as it will connect to Azure and register the service or potential settings.
✅ Note that future changes will always require another Script Run. Details are explained in the next step.
Script Run & Test Call
|
TENANT ADMIN required. Each service settings change that affects the call endpoints or phone number licensing must be confirmed by a Tenant Administrator: When all settings are to your liking, execute the PowerShell script and follow instructions inside. |
TEAM OWNER Optionally: Once the script was executed by an administrator the call endpoints and necessary licenses should be established. |
|
The script can be downloaded via your User Preferences (Portal) page or by using the following links: Nimbus Provisioning Script URLs
|
RECOMMENDED: TEST CALL
You can now start a Test Call (also available within General Service Settings) to see if the bot is taking calls and routing them towards your new (service) team. Read the next steps below to configure your new service. 
|
|
💡 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.
|
💡Note that test calls are made to the UPN of the service. PSTN calls you need to test with manually dialing from a user with an according PSTN license or using your cell phone. 🔍Test calls are treated like any other call and are counted towards the Reporting metric. They should be reflected in Nimbus service reporting tabs accordingly. |
Recommended next steps
- Familiarize yourself with the Role Access Concept system of Nimbus.
- Test the Login to the Nimbus front- and admin panels either in the Teams App or a separate browser window.
Frontend (Portal) URLs |
Admin Panel URLs |
||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Nimbus Portal URLs
✅ Make sure to configure your web proxies to allow access to these domains or whitelist the complete *.luware.cloud domain.
|
Nimbus Admin URLs
✅ Make sure to configure your web proxies to allow access to these domains or whitelist the complete *.luware.cloud domain.
|
-
Start customizing Nimbus to your liking:
- Once basic setup is complete you can start the Configuration of your service, e.g. to test various Service Settings, Workflows, Opening Hours.
- As a great starter we recommend Use Case - Creating a Call Workflow. Check out our Use Cases category for further inspiration.
- We recommended adding more Nimbus users to your new service team to verify any changes to your settings in a test call scenario.
- Once you are familiar with your first service, learn more about the other Service types and their related features.