Modalities Tenant Settings

Instant Message (Private Preview) External Task Here you can configure modality behavior that affect all services with the according Features enabled.

🔍 Note that services are immediately affected by these configuration parameters, e.g. when enabling their corresponding features in the Modality Service Settings.

Instant Messaging

Once enabled this feature allows to configures Chat Handling capabilities and related features of Nimbus.

Option / Element Description
Instant Messaging Required to enable the feature and show further options
Grant Permission As Tenant Administrator you need to grant permissions once. Paste this link into your browsers address bar or pass it on to a Tenant Administrator with according privileges.
Primary Account / Secondary Account

Guest accounts to invite on your Tenant to enable Instant Messaging capabilities. 

✅ This should be done in tandem with your Luware customer success partner. For more details, refer to Use Case - Setting up Instant Messaging.

Test UPN Use this (after the successful user invite) to send test messages to any user within your tenant.
Max concurrent IM Tasks per Service

Max limit of concurrent Instant messaging tasks per service (similar to ET)

  • Default: 20
  • Min: 1
  • Max: 50
Use your own ACS Instance

Optional step. Only required when you don't want to use the default Nimbus ACS instance. 

Learn how to set up your own ACS Instance

INC ACS Instance Setup

INC ACS Instance Setup

The following steps describe how an ACS instance can be setup. Which is required for Nimbus Assistant and/or Interact.


Usage of Interact will cause additional monthly ACS (Azure Communication Services) cost depending on modality (IM/AV) used. These cost are determined by Microsoft. Also see:

  • Before enabling additional modality features for your services, get in touch with your Luware Customer Success specialist to discuss terms, usage scenarios and necessary setup procedures.
  • Please note that Nimbus and Interact support does not cover pricing discussions or make recommendations based on Microsoft Azure infrastructure.

Create new Azure Communication Service

To create a new Azure Communication Service perform the steps:

  1. Head to Azure Portal and login with tenant admin rights.
  2. Search for "Azure Communication Service" component and click "Create".   
    ☝ Make sure not to use any underline/underscores within the name.
  3. Switch to the Keys tab and copy the connection string  





ACS connection string

Connection string for Azure Communication Services. Required to use Chat Handling with your own ACS instance.

🔍 Learn how to generate this string via the Microsoft Documentation .

💡 Once a string is entered a "Check" option verifies if it's possible to create a token for the user using this string. If the connection fails (with a correct string) it most likely means there are insufficient permissions.

ACS Resource ID

Connection ID for Azure Communication Services. Required to use Chat Handling with your own ACS instance.

🔍 Learn how to retrieve this ID via the Microsoft Documentation .


External Task

Option / Element Description
Max concurrent External Tasks per Service

Limits the maximum External Tasks per service that can be simultaneously scheduled / in progress

  • Default 20 / Min 1 / Max 50

🔍 External Tasks – same as inbound or outbound tasks – are distributed among available Nimbus users and shown in the Personal Dashboards > in the "External Tasks Tabular" widget. Tasks are scheduled using the Microsoft Power Automate Connector > Flow Actions. Once the limit is reached, a flow error is returned and the task will be discarded.

🔍 Why is this field read only? As external tasks can be created in bulk via external flow loop, they underly a fair-use policy. This limit is also in place to ensure that potential erroneous loop conditions don't create a large amount of "stuck" tasks, blocking up service queues.

Table of Contents