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 Azure should be configured for Interact.

AZURE BILLING

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: https://learn.microsoft.com/en-us/azure/communication-services/concepts/pricing

  • 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 recomendations based on Microsoft Azure infrastructure.
 

🔍 IDs, users and strings generated below will be needed within Nimbus Tenant Administration.

To create a new Azure Communication Service:

  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.

  1. Switch to the Keys tab and copy the connection string

1.Create a new, dedicated O365 User. 💡 We recommend a general name to describe the purpose: e.g. meetingCreator@contoso.onmicrosoft.com.

NOTES

  • Don't re-use an existing user , as it will get constant meeting request notifications. 
  • Make sure to login least once with this user account to set the password and overwrite the initial password.
 

2. Assign a Teams license  to that user.   
3. Copy and keep the GUID of the user for later use.

  1. Use one of the following links to grant admin consent for the interact application.   
    ✅ Replace the <tenantId> with your own before pasting the link to your browser
https://login.microsoftonline.com/<tenantId>/adminconsent?client_id=78e2af0a-9a4e-46c7-abb5-d6ecf794ee3f (Prod CH)
https://login.microsoftonline.com/<tenantId>/adminconsent?client_id=3a9af5b9-4cd5-4538-9bb4-803f5a651a39 (Prod DE)
https://login.microsoftonline.com/<tenantId>/adminconsent?client_id=a2234937-bb9d-4cee-b0f3-73f054518144 (Prod UK)

You might get a non-critical error message as follows.

"AADSTS500113: No reply address is registered for the application."

This can be ignored.

 

1. Use Powershell as a Global Azure Administrator and run the following command:

Connect-MicrosoftTeams

POWERSHELL

Connect-MicrosoftTeams

2. Create a new Application Access Policy and make use of the corresponding Environment AppId (Use the correct one from the step above)

New-CsApplicationAccessPolicy

POWERSHELL

New-CsApplicationAccessPolicy -Identity Nimbus-Interact-policy -AppIds "<AppId>" -Description "This policy is used to create meetings on behalf for the environment"
                

3. Grant the Application Access Policy to the dedicated O365 User

Grant-CsApplicationAccessPolicy

POWERSHELL

Grant-CsApplicationAccessPolicy -PolicyName Nimbus-Interact-policy -Identity "<O365-User-GUID>"
  1. Log into Nimbus Admin Portal
  2. Select your tenant or create a new one
  3. Within the Tenant Administration > Interact, fill out all the required fields
    1. ACS connection with the string and test the connection
    2. UserOnBehalf with the O365-User-GUID
    3. Leave other fields at their defaults for now.
  4. Save your changes

 

 
 

 

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