TENANT ADMIN Actions on this page require MS Teams administrator rights to access the Microsoft Teams admin center and perform app updates on your tenant.
INC App Manifest Update notice
Update Notice - Nimbus App Manifest
In March 2024 the new Microsoft Teams client will be unavoidable and rolled out by Microsoft for all users. Older versions of the Nimbus App Manifest will not support SSO (Single-Sign-On) and will cause problems on the new Teams client.
✅ Tenant Admin Action required: If your Nimbus App in use is lower than version 1.0.23166 you must update the Nimbus Personal App on your tenant immediately. After the Teams client rollout your App will be rendered inoperable.
You can retrieve the newest app manifest here:
Nimbus App Manifest URLs
Manifest Upload
For Nimbus to be available in your tenant (and to allow your users to install it from MS Teams Apps list), the app manifest needs to be uploaded first. To do so, perform the following steps:
- Retrieve the Nimbus manifest ZIP file from Luware. 💡 You can have a look inside, but you don't need to unzip the archive for the next steps.
INC Nimbus App Manifest URLs
- Login to MS Teams Admin Center as Tenant Admin
- Go to Teams apps → Manage apps
- Select the option Upload new app
-
Click the Upload button and select the manifest ZIP file
⮑A "New app added" message should confirm the successful upload - Verify the App's entry and new version within the Manage apps Screen.
Need to update an existing Manifest?
To update an existing Nimbus app (e.g. with a new manifest):
- Using a Tenant Admin account, login to the MS Teams admin center
- Go to Teams apps > Manage apps
- Select the existing Nimbus app entry
- Under "New version", select "Upload file"
Check app permission policies
- Still within Teams Admin Center, go to Teams Apps → Permission policies
- Add a new permission policy entry to the list
- For each app permission policy that will be assigned to your Nimbus administrators and end-users, check the settings for custom apps. This must be set to either Allow all apps or Allow specific apps. If this is not the case, please amend it to one of above.
💡Note that changes may take a while before fully replicated throughout MS Teams, eventually making the Nimbus app become visible to your users.
Inform your userbase to adopt the update
- After each successful app manifest change, you may want to inform your local Nimbus users about the update. Pop-ups in MS Teams will also inform users that new versions are available.
- Note that users with the Nimbus Personal App installed will need to click View update and install the app via Update.
- The update notice may also appear for Teams using the Nimbus Teams Tab. In this case, the update needs to be confirmed by either a tenant admin or team owner.
Manifest updates and end-user experience
While optional in most cases, app updates are always disruptive to an extend. To keep impacts low, we will inform you in our Release Notes, and communicate significant changes in advance whenever your app manifest should or must be updated.
In any case, be aware of the following changes after an app update:
- Permission changes: App updates may entail changed User Permissions and App Permissions as well as changes to the available User Login and Settings experience. Make sure to read the Introduction to Nimbus and our Security Whitepapers to learn how Nimbus uses this data.
-
Single sign-on (SSO): Nimbus supports single sign-on, reducing the amount of necessary logins for Nimbus, especially in a multi-service-participation scenario for your MS Teams users.
🔍 After initial consent, the login token from MS Teams will be used for Nimbus as well. See also User Preferences (Portal). - ✅ SSO requires the latest app manifest to be installed on your tenant. Note that after a new manifest update, each Nimbus user needs to confirm the Nimbus app update as described in the step above. This will grant permissions for individual login token usage and enable the latest single sign-on features.
- @Manifest Update
💡 Good to know: When your userbase exclusively uses Nimbus in-browser, the manifest update and notify procedures described on this page do not apply. However, users will always need to sign-on every time they open Nimbus in a browser, regardless of their login status in MS Teams.