Get-CsPrivacyConfiguration | Select EnablePrivacyMode

Set-CsPrivacyConfiguration -EnablePrivacyMode $false

Provisioning Steps

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 "          
      OR
   2. Navigate to the Team itself, click on "Add a Tab" to install Nimbus this way.

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.

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. 💡 These details can be changed later via General Service Settings
   3. 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.

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. 

1. Open the User Preferences (Portal)
2. 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.

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    

1. 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.
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 "SAVE & APPLY".    
    
4. 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 Switzerland 01 https://portal.ch-01.luware.cloud/api/manifests/NimbusProvisioning.ps1 Switzerland 02 https://portal.ch-02.luware.cloud/api/manifests/NimbusProvisioning.ps1 Germany 01 https://portal.dewe-01.luware.cloud/api/manifests/NimbusProvisioning.ps1 Germany 02 https://portal.dewe-02.luware.cloud/api/manifests/NimbusProvisioning.ps1 United Kingdom 01 https://portal.uk-01.luware.cloud/api/manifests/NimbusProvisioning.ps1 Australia 01 https://portal.aue-01.luware.cloud/api/manifests/NimbusProvisioning.ps1 West Europe 01 https://portal.euwe-01.luware.cloud/api/manifests/NimbusProvisioning.ps1 East United States 01 https://portal.use-01.luware.cloud/api/manifests/NimbusProvisioning.ps1	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. Upon first execution the script will automatically download and install 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 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.	💡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

1. Familiarize yourself with the Role Access Concept system of Nimbus. 
2. Test the Login to the Nimbus front- and admin panels either in the Teams App or a separate browser window. 

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

Add Nimbus to your MS Teams sidebar

In Teams, open the "..." Options dialog and search for "Nimbus"	Adding the Nimbus App to MS Teams
Locate the Nimbus app and click on it for more information. 💡 Depending on your partnership Luware and the App installed the name variant of the Nimbus App may vary
Read and confirm the Licensing agreement. 💡 Nimbus stores personal information during use. Make sure you read the privacy policy and terms of use carefully.	Pinning the installed Nimbus App to the sidebar
To add the app to your sidebar, click "Add". 💡 You might be requested to log in to your O365 account to confirm the installation. 🔍 Please note that Nimbus will ask for Required User Permissions which might change with future updates and expanded Nimbus Features. Make sure to review the permissions on a regular basis.
At this point you should be able to access the Personal App directly from the sidebar. 💡 We recommend pinning it to the sidebar so you always have quick access.