Provisioning Tenant Settings

In the Provisioning tab in Tenant Administration, you can configure the Service Provisioning default settings which apply when new Nimbus services are created.

Default OU for MS Teams creation

Sets the default Organization Unit (OU) for new services during their first provisioning.

🔍 Please Note:

  • During Service Provisioning users can still change the default to any provided "sub" level OU during installation. The OU can also be changed later in General Service Settings of that service. 
  • When the OU gets deleted, the OU default selection is moved one level higher (up to root). 
  • If either user or service are completely new in Nimbus – or the OU cannot be selected for other reasons – both the user and service are placed in a "Default Organization Unit for Microsoft Teams-based teams". Both can be moved to other Organization Units via the User Administration and Service Administration respectively.
Allow service provisioning via MS Teams

Set the minimum roles required to Provision a new Nimbus team directly from the MS-Teams UI.

Settings are: 

  • Everyone (default)
  • Tenant & Organization Unit Administrators
  • Tenant Administrators
  • No one → provisioning disabled on MS Teams side

💡 This setting does not prevent users from installing the Nimbus Personal App.

🔍 Non MS-Teams synched Service types can still be provisioned via the backend by any administrator, regardless of the setting made here.

Users without the permission to Provision new services may still remove the Nimbus tab from MS Teams (as Nimbus cannot impact or restrict the default MS Teams interface). However, they can not trigger a removal of the service itself and its data and the Nimbus tab can be re-added.

Default Team Owner Role

The default role assigned to a new user when a new Nimbus team is provisioned directly from the MS-Teams UI. Options are: 

  • Team Owner (Default) with full team settings and configuration rights.
  • Team Owner Limited (a Nimbus specific role with a reduced set of User Roles).

💡 Existing services are not affected by this change and changing this setting will only affect future services provisioned via MS Teams

Enable Multihoming

INC Upcoming Feature

UPCOMING FEATURE

This is an upcoming feature and not yet available for use.

 

💡We are working with selected customers to test and improve this feature before a wider rollout.

If multihoming is enabled, you can spread your tenant over multiple clusters. This is convenient especially for large tenants with users located in different locations.

This field is read-only as multihoming must be set up for your tenant by a System Administrator.

Table of Contents