This page will always reflect the latest Release Notes, recent improvements and changes made to Nimbus.
Other Information Resources:
- Our Release Note History contains information on all previous releases from this year.
- Updates on our Nimbus Power BI Template are distributed on request. Please refer to the Nimbus BI Template Release Notes for updates.
- Also visit the following sources to stay up-to-date on Nimbus in both features and (upcoming) maintenance:
INC External News Resources
📣Important Announcements
Please take note of the following long-term and ongoing announcements below:
INC PSTN License Check Enforcement Notice
☝Ahead Notice: Microsoft licensing changes
Amendment 03.09.2025: Added Operator Connect as affected customer base. Added clarification that Direct Routing customers are not affected.
Microsoft Licensing Change: What Nimbus Customers Need to Know About Calling Plan and Operator Connect Changes.
🔍 What’s changing?
Effective November 1, 2025:
- Microsoft will enforce a significant licensing change that directly impacts how outbound PSTN calls are handled in Microsoft Teams—especially for services like Call Queues (CQ) and Auto Attendants (AA).
- This change affects all organizations using Microsoft Calling Plans for telephony and it might affect organizations using Operator Connect.
-
The change has direct implications for Luware Nimbus customers in the following scenarios:
- When using Outbound Call functionality, including Call On Behalf.
- When using the Attendant Console for transfers to PSTN numbers.
- When doing Workflow Transfers to PSTN numbers.
🔍 What’s not affected?
- There is no change for Direct Routing phone numbers.
🔍 You will find the full announcement on the MSFT Learn page, specifically “Changes to licensing required for Auto attendant and Call queue outbound PSTN calling”. Excerpt quoted below - important parts highlighted:
Calling Plan
Starting November 1, 2025, a Pay-As-You-Go license will be required for Teams Voice Applications (Call Queues and Auto Attendants) Resource Accounts that use Calling Plan numbers for outbound PSTN calls.
The following scenarios will require a Pay-As-You-Go license:
- Outbound PSTN calls made by Teams Call Queue agents on behalf of a Resource Account
- Outbound PSTN calls made by Auto Attendants or Call Queues
- Callback PSTN calls initiated from Teams Call Queue or Teams Auto Attendant
- On-behalf-of calls made via Graph API and Phone System Extensibility
If Pay-As-You-Go licenses aren't assigned to the relevant Call Queue or Auto Attendant Resource Accounts by November 1, 2025, outbound calls will fail.
Operator Connect
On November 1, 2025, the following outbound calling scenarios may no longer be available depending on your carrier/operator:
- Outbound PSTN calls made by Teams Call Queue agents on behalf of a Resource Account
- Outbound PSTN calls made by Auto Attendants or Call Queues
- Callback PSTN calls initiated from Teams Call Queue or Teams Auto Attendant
- On-behalf-of calls made via Graph API and Phone System Extensibility
Coordinate with your carrier/operator to ensure you continue to have uninterrupted service for these on-behalf-of outbound PSTN call scenarios. If the appropriate arrangements aren't made with your carrier/operator, then outbound calls made by agents on behalf of resource accounts, by auto attendants or call queues or via the Graph API and Phone System Extensibility will fail.
Your carrier/operator provides the details on what adjustments may be required.
🤔How does this affect Nimbus?
Nimbus uses bots to initiate and monitor conferences well as monitor and report any Outbound Call calls and Call On Behalf of a Nimbus Service. Any transfer scenario also requires the Nimbus bot to take calls back safely.
This includes:
- CQ agents making calls on behalf of a Resource Account (RA)
- Callback scenarios configured in Call Queues
- Auto Attendants transferring calls externally
- Calls initiated via Graph API or Phone System extensibility
🧭 What is the Impact for Luware Nimbus Users?
For customers using Microsoft Telephony exclusively and leveraging Call On Behalf features via Luware Nimbus, this change means:
- You must replace existing Calling Plan / Operator connect licenses on resource accounts with Pay-As-You-Go licenses.
- Failure to do so will result in service interruptions for Outbound Calls initiated by Nimbus services, e.g. within either Attendant Console, Workflows in Contact Center routing.
- As highlighted in internal discussions with Microsoft, this enforcement aims to curb misuse but inadvertently affects legitimate use cases like those supported by Luware Nimbus.
✅ What you need to do
✅To ensure uninterrupted service: We urgently recommend for Customers begin transitioning to Pay-As-You-Go licenses well before November 1st to avoid last-minute disruptions.
- Review all resource accounts configured for outbound PSTN calls.
- Assign Pay-As-You-Go calling plan licenses to these accounts via the Microsoft 365 Admin Center.
- Validate license coverage for all users and services involved in call transfers.
- Consider setting up Communication Credits to fund Pay-As-You-Go usage if needed.
📞 Need Help?
If you’re unsure how this change affects your setup or need assistance updating your licensing, please reach out to your Luware Customer Success Manager or contact our Support Team.
INC Luware Support Address
| Luware Website | https://luware.com/support/ |
|---|---|
| Luware Helpdesk | https://helpdesk.luware.cloud |
| Cloud Service Status | https://status.luware.cloud/ |
INC Power Automate Connector Change Notice
📆Upcoming change: New Power Automate connector user role validation
We're introducing an important enhancement to the Nimbus Power Automate Connector, rollout planned on 15th of January 2026. This update is designed to improve security and ensure that flows are only triggered by users with valid permissions.
☝What is changing:
- Currently, users must hold a Power Automate Role in Nimbus - either Service Owner or Administrator. The role is validated when creating a flow.
- With this upcoming update, an additional step will be introduced, validating roles at each execution of a flow. This effectively prevents flow-execution by users who no longer have the appropriate access.
✅Action required: We recommend for all our customers using the Power Automate Connector to review and confirm their flow configuration to avoid any disruption. Keep in mind that the new validation will not just check the role but also the Organization Unit scope under which the user operates. Any later changes in the user's OU scope will also affect existing flows - e.g. the services that the user can see and impact.
End of announcements. Regular release notes continue below.
29 October 2025 - 1.119 Release Notes
🔖 This is a major update, bringing many new changes and improvements into Nimbus. This update is rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United States 01 | 29/10/2025 |
| Australia 01 | 30/10/2025 |
| United Kingdom 01 | 04/11/2025 |
| Switzerland 02 / Germany 02 | 06/11/2025 |
| Switzerland 01 | 09/11/2025 |
| Europe 01 | 12/11/2025 |
| Germany 01 | 16/11/2025 |
Task Parallelization is here - handle two task simultaneously
Task Parallelization enables users to handle multiple tasks simultaneously within the Nimbus platform. This includes e.g. managing Audio/Video (AV) calls and External Tasks without blocking the user from receiving a new Audio/Video task. Task Parallelization introduces a more flexible and scalable approach to task handling, especially for service agents working with multiple communication channels simultaneously.
GETTING STARTED
🔎Learn more: After our initial preview phase, Task Parallelization has made its way into the public Nimbus build for all users. We highly recommend reading into the concept page to understand related prerequisites – such as Parking and the supported modality combinations – so you can prepare and train your users accordingly.
✅Enabling the feature: Task Parallelization is enabled on user level via General User Settings (per default disabled).
☝Note that enabling this feature will disable After-Call Work (ACW) for the User. We therefore strongly recommend to …
- … change this setting outside of working hours, as Users might be confused about the sudden change in their daily workflow.
- … inform Supervisors concerned with Reporting Data, as ACW time is now absent from Nimbus KPI Calculations and reflected in the User's Nimbus Reporting Session data.
Companion: Summarization (of existing transcriptions)
INC Public Preview Beta Feature
This feature is in PREVIEW and may not yet be available to all customers. Functionality, scope and design may change considerably.
Summarization was added to the Nimbus Companion features. It integrates AI summarization as part of a broader suite of Transcription features, aimed at improving service performance and agent efficiency. During a call, Nimbus transcribes the conversation in real time. After the call, the transcript is processed by an AI service to generate a summary with the following aspects:
| Aspect | Description |
|---|---|
| Title | A title generated from Call Direction, Service, and User that accepted the task. |
| Issue | Shortened problem description by the Customer. |
| Resolution | Summary of how the issue was resolved. |
| Recap | A brief paragraph summarizing the interaction. |
| Narrative | Detailed call notes or chat summary of the entire Customer/User Interaction. |
💡Good to know: Summarization outputs can be presented to the agent either via My Sessions > Companion widget. All aspects shown within the Companion Widget > Summarization can be hovered over and copied. The fields may be blank when there is insufficient data to work with.
Companion - Summarization is an optional user feature:
- The Transcription feature must be enabled on the Companion Service Settings, as the Summarization is derived from it.
- The user needs a Companion License, applied via General User Settings.
Companion: Codes & Tags Suggestions
INC Public Preview Beta Feature
This feature is in PREVIEW and may not yet be available to all customers. Functionality, scope and design may change considerably.
💡With Transcription features enabled: the customer-user conversation can now be analyzed, allowing Nimbus Companion to auto-suggest Codes and Tags in My Sessions after the session is concluded. By clicking on the suggestions they can be added to the list of existing items.
💡Unchanged functionality: With the feature disabled, users can select codes and tags manually as before.
Companion - Codes & Tags suggestions are an optional user feature: AI-driven automatic code suggestions require a Companion license on the user. Transcription must be enabled for the service and a (voice to text) Transcriber set up within in Companion Service Settings to get code suggestions.
Other Changes and Improvements
-
Nimbus Power Automate Connector - page rework and related updates:
- New descriptions for Companion Trigger Events and Flow Actions.
-
Knowledge Base:
-
Task Parallelization: Updated several concept pages to mention the co-depedencies and considerations when Task Parallelization is enabled:
- Attendant - Park and Unpark - steps and notes added.
- RONA - added Task Parallelization notes.
- Call On Behalf - added Task Parallelization notes.
- Nimbus Features matrix updated to reflect new Companion capabilities.
- Transcription - page reworked, updated preconditions, limitations and design notes to include Summarization.
- Updated Use Case - Analyzing a Transcript to include the latest Power Automate actions.
- Updated Use Case - Defining and Using Codes
-
Task Parallelization: Updated several concept pages to mention the co-depedencies and considerations when Task Parallelization is enabled: