TENANT ADMIN Actions on this page require MS Teams Administrator rights to access "Microsoft Teams admin center" and perform app updates on your tenant.

To update an existing Nimbus app (e.g. with a new manifest):

  1. Using a Tenant Admin account, login to the MS Teams admin center
  2. Go to Teams apps > Manage apps
  3. Select the existing Nimbus app entry
  4. Under "New version", select "Upload file"
  5. Select and upload the new manifest ZIP archive

(info) Learn more about the versioning and data concept of the app in our Introduction to Nimbus. You also might want to inform your users after you roll out an update.

Manifest upload steps

Upload app manifest

For Nimbus to be available in your Tenant (to allow your users to install it from MS Teams Apps list), the app manifest needs to be uploaded first

  1. Retrieve the Nimbus manifest ZIP file from Luware. Your Nimbus onboarding team will provide you with a download link.
    (lightbulb)You can have a look inside, but you don't need to unzip the archive for the next steps.
    Luware Support
    Websitehttps://luware.com/support/
    Helpdeskhttps://helpdesk.luware.cloud 
    Service Statushttps://status.luware.cloud/

  2. Login to MS Teams Admin Center as Tenant Admin 
    1. Go to Teams apps > Manage apps

    2. Select the Upload new app option

    3. Click the Upload button and select the manifest ZIP file → A "New app added" message should confirm the successful upload

  3. Verify the App's entry and new version within the "Manage Apps" Screen.
    (info) Also read on how to update an existing app further below.

    Luware Nimbus successfully added to the Teams Apps

Check app permission policies

  1. Still within Teams Admin Center, go to Teams Apps > Permission policies

  2. Add a new permission policy entry to the list

    Permission policy entry for the Nimbus custom app

  3. For each App Permission policy that will be assigned to your Nimbus administrators and end-users, check the settings for "Custom apps"

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

    2. Note that changes may take a while before fully replicated throughout MS Teams, eventuallymaking the Nimbus App become visible to your users.

    Allowing the Nimbus custom App

Inform your userbase to adopt the update 

  1. After each successful App manifest change you may want to inform your local Nimbus users of the update. Pop-Ups in MS Teams will also inform users that new versions are available.

  2. Note that Users with the Nimbus Personal App installed will need to click "View update" and install the app via "Update".

    Pending Nimbus Personal App update for a user


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

    Pending Nimbus update in a Teams Channel

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 in our Release Notes and communicate significant changes in advance whenever your App manifest should or must to 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: 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.
    (info) After initial consent, the login token from MS Teams will be used for Nimbus as well. → Also see User Settings.
    (tick) 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 (SSO) features.

(lightbulb) 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 browser, regardless of their login status in MS Teams.