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 enforcing PSTN license checks for bot calls
Amendment 07.05.2025: Microsoft has moved the date from June to end of September.
From: https://devblogs.microsoft.com/microsoft365dev/enforcement-of-license-checks-for-pstn-bot-calls/
🔍 What’s changing?
Effective September 30, 2025:
- Teams users will still have the option to transfer calls to other Teams users manually even if they don’t have a PSTN phone system license.
- Bot-initiated transfers and add participant requests to non-phone system enabled users will be blocked.
🤔How does this affect Nimbus?
Nimbus uses bots to initiate and monitor (safe) transfers and create call conferences. If Microsoft decides to pull through with this change by September 30, 2025, all Nimbus transfers and consultation calls will be blocked and fail without any possible workaround or error handling.
Topic: Microsoft announced changes to PSTN license checks for bots. From the Blog Post of Microsoft:
As part of Microsoft’s feature parity with Teams Phone extensibility, we’re announcing the enforcement of Phone System license checks for Bot-initiated transfers to Teams users. This current gap in our systems will be addressed in September 2025.
Microsoft Teams requires that Teams users behind applications such as queue applications require a phone system license and the user to be Enterprise Voice Enabled. We’re aligning the Microsoft Graph API with that requirement.
What is the change?
Effective September 30, 2025:
- Teams users will still have the option to transfer calls to other Teams users manually even if they don’t have a PSTN phone system license.
- Bot-initiated transfers and add participant requests to non-phone system enabled users will be blocked.
🧭 What is the Impact for Luware Nimbus Users?
- Transfers Within Nimbus: Transfers to users without a Teams Phone license will no longer work. This includes internal transfers between agents or service users.
- Supervision Features: Supervisors must have a Teams Phone license to monitor or intervene in calls. Without it, supervision capabilities are disabled.
- Workflow Transfers: Any transfer initiated from a Nimbus workflow to a user lacking the appropriate license will fail. This disrupts automated routing logic and impacts service continuity.
- Attendant Console Transfers: Transfers via the Attendant Console to unlicensed users are blocked. This affects manual call handling and redirection.
✅ What you need to do
✅To ensure uninterrupted service:
This change mandates the use of a PSTN License on all Users you either transfer to or start a consultation call with.
- Audit User Licenses: Verify that all users involved in call handling, transfers, and supervision have the Microsoft Teams Phone license assigned.
- Update Workflows: Adjust workflows to route calls only to licensed users. This includes adjusting any Distribution Policies and Agent Service Settings for Agents with the according skills and responsibilities.
- Train Supervisors: Ensure supervisors understand the licensing requirements and have the necessary access.
- Monitor License Status: Implement checks or alerts to identify users without valid licenses.
☝Ahead Notice: Pay-as-you-go Calling Plan licensing changes
Microsoft Licensing Change: What Nimbus Users Need to Know About Pay-As-You-Go Calling Plans
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 has direct implications for Luware Nimbus users using Outbound Call functionality.
You will find the full announcement on the MSFT Learn page.
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.
🔍 What’s changing?
If PAYG licenses are not assigned by November 1, 2025, these outbound calls will fail.
🤔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 licenses on resource accounts with PAYG (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 PAYG licenses well before November 1st to avoid last-minute disruptions.
- Review all resource accounts configured for outbound PSTN calls.
- Assign PAYG 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 PAYG 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/ |
End of announcements. Regular release notes continue below.
19 August 2025 - 1.116 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 / Australia 01 | 28.08.2025 |
United Kingdom 01 | 01.09.2025 |
Switzerland 02 / Germany 02 | 03.09.2025 |
Switzerland 01 | 07.09.2025 |
Europe 01 | 10.09.2025 |
Germany 01 | 14.09.2025 |
Service Bulk Editing - Distribution Settings
-
Bulk Editing > Services: Now supports changing settings within the “Distribution” tab.
- ✅ Precondition: In order to enter the Distribution Tab the User Assignment Type of your selected Services need to match.
- Descriptions and details can be found on the Bulk Editing page under > Bulk Editing Services > Distribution.
- KB: Best Practices - Bulk Editing > Considerations: chapter updated with “Services: Feature and Configuration dependencies” chapter to reflect the new possibilities.

Power Automate: Flow Actions and Trigger Events Update
INC Upcoming Connector Feature
⌛Pending Connector Certification: Features described in the following are still undergoing the Microsoft certification process. As such they are not yet part of the officially certified Nimbus Power Automate Connector.
✅To test this functionality early, you can manually download and install the latest upcoming (V1) connector as Custom Connector on your tenant.
☝Note that Custom-installed connectors will not update automatically. Once the functionality becomes available in the certified connector you need to perform a manual Connector Migration of your flows.
Learn more about the available Connector update paths….
INC Power Automate Connector Update Path

Customer Tenant Admin Procedures |
Nimbus Customers can choose between following upgrade paths for the Power Automate connector:
|
||||||||
Luware Development |
Whenever Luware releases a Nimbus Version, the “Upcoming V1” connector can be retrieved as a Luware-hosted download.
|
||||||||
Luware / Microsoft connector Certification Process |
The V1 download package is submitted to Microsoft for Store Certification.
💡Note: Each update triggers a re-certification process by Microsoft and takes ~4-6 weeks. |
Learn how to update the Custom Connector
Updating the Nimbus Custom Power Automate Connector
🤔 When do I need to update the custom connector? Luware development implements changes in the Nimbus Custom Connector (v1) and starts a certification process with Microsoft right after a major Nimbus release. If the Release Notes state any features that you would like to try out ahead of time – e.g. by adding new actions and triggers – you can perform a manual update and install the V1 connector as Custom Connector on your Tenant.
💡 If you are using the certified connector, you don't need to update it manually. Once the certification of a new version is completed on Microsoft side, it will be available automatically.
Update Steps
-
Retrieve the latest connector file from your Nimbus cluster region:
💡 Uncertain? You can find out your region by logging into Nimbus Portal / Admin and see how the URL changes.
INC Nimbus Power Automate Connector URLs
☝Legacy (v0) Custom Connector users: Replace the /v1/ part of the URL above with /v0/ to download the legacy connector (e.g. to Update your existing Connector) with new files. Note that the legacy connector will not receive feature updates anymore.
☝Migration note for all custom-installed connectors: You can install the v1 to-be-certified connector as Custom Connector. However, when switching to the certified connector within Microsoft Power Automate, a Connector migration is necessary for all existing custom connectors.
- Go to https://make.powerautomate.com/ and expand Data > Custom Connectors.
- Select your Nimbus Custom Connector from the list.
- Click on the Context menu (three dots) at the end of the line.
- Select “Update from OpenAPI file”.
- Click the "Import" button and select the new file.
-
Finally click “Continue”.
⮑ The connector is now updated and should be visible on your Tenant.
-
Renaming: "Virtual User" Flow Actions and Trigger Events changed naming to "Companion".
- 💡 Properties and design intent have not been changed - this is just a naming change to match the “Companion” license wording.
- Trigger Events: “When the virtual user assistant has an update” renamed to → “When the companion has an update”.
- Flow Actions > Nimbus Companion: "Get Virtual Assistant Data" renamed to → "Get Task Data from Companion".
- ☝Deprecation Notice: This change will only take effect after the next Nimbus Power Automate Connector certification. Once complete, users will get a deprecation notice shown in the respective flow items, and asked to switch to the newest elements respectively. After that point, the legacy flow items cannot be used again, only replaced. Any existing flows will continue to run in legacy support.
- 💡 Properties and design intent have not been changed - this is just a naming change to match the “Companion” license wording.
-
New Flow Action > Service Opening Hours > “Get next calendar block”:
- Searches for a matching Opening Hours calendar block (period) of a specified Service.
- Allows multiple calendar period types to be searched for.
- The first status meeting the criteria will be returned as output. The output for the block has the following fields:
-
Opening Hours Status
- The status of the calendar block -
Block Start Time (UTC)
- The time the block starts - when the found block started earlier, the "Start Time” takes precedence. -
Block End Time (UTC)
- The time the block ends
-
-
Updated Flow Action: Get Opening Hours (V2).
- UPDATE: Replaces the previous version (V1) to work together with the new “Get next Calendar block” action.
💡The old V1 endpoint will be supported for backwards compatibility with existing flows. The deprecated block cannot be replaced in existing flows. - NEW: The output for the block now supports the following fields:
-
Opening Hours Status
: The Service's status (Open, Closed, Holiday, Special 1-4) at a given time. -
Status Change Time (UTC)
- The Time of the next status change – or put differently: the time until the current status will last. This can be used for example to inform customers about a remaining closure or holiday duration.
-
- UPDATE: Replaces the previous version (V1) to work together with the new “Get next Calendar block” action.
Other Changes and Improvements
- Attendant Console - Contact Groups and Contacts have been doubled. You can now have 20 Contact Groups (up from 10) and 100 Contacts per group (up from 50).
- Virtual Users - Speech Recognizers related license handling checks and UI error messages have been improved.
-
Companion Service Settings:
- Speech Recognizers are now moved up in the settings, as they are a general prerequisite to using either Transcription and Live Captioning.
- Added new warnings and precondition checks to inform users.