What you can find here
This page will always reflect the latest Release Notes, improvements and changes made to Nimbus.
Other areas of interest:
- Refer to the Release Note History for previous releases earlier 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
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/
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.
🤔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.
✅Required Action for Tenant Administrators / Service Owners: This change mandates the use of a PSTN License on all Users you either transfer to or start a consultation call with.
15 May 2025 - 1.111 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 | 15/05/2025 |
| United Kingdom 01 | 19/05/2025 |
| Switzerland 02 / Germany 02 | 21/05/2025 |
| Switzerland 01 | 25/05/2025 |
| Europe 01 | 28/05/2025 |
| Germany 01 | 01/06/2025 |
✅ Admin action required: Assistant installer certificate renewal
Assistant Installation - Assistant Setups (Nimbus Assistant Client Setup.msi) got recertified on 12.05.2025 as previous certificates have expired. Due to this, any older installers may no longer work by the end of May.
- If you intend to (re)install Assistant in the near future, please request the newest installers via Customer Success.
- Already existing installations of Nimbus Assistant will continue to work unaffected.
Power BI Template Download
It is now possible to request the latest Power BI template version directly from the Luware Website.
INC Nimbus Power BI Files
📊Power BI Template Files
✅Template Download: Luware provides Power BI Files on request. To get the latest version, visit our BI Template request site | Luware.com.
✅ Usage Instructions:
- First Time Users: To connect the Template to your Nimbus data source, read Setting Up Power BI. While setting up the Template (.pbit), you need to provide connection parameters and your Reporting Role User credentials to perform a first query.
- Performance: Once setup is done, save your template as a .pbix report, as it will use considerably lower RAM/CPU than a template.
- Daily Usage: Visit Nimbus Power BI Template for further details on the template itself.
Attendant Console 1.0 Deprecation
INC Attendant Console Deprecation Notice
Deprecation Notice: Attendant Console 1.0
☝ With an upcoming release by end of June 2025 Attendant Console 1.0 will be discontinued in favor of the new Attendant Console 2.0 design.
- AC1 functionality and toggles within the Attendant Settings will be removed. This rollout will be gradual across our Nimbus clusters, defaulting all Nimbus Users who haven't switched yet into the new Attendant Console 2.0 design.
- As part of the transition, AC1 parts of the KB (Screenshots in particular) may mismatch with the current design. Related pages of the KB will not be updated anymore and gradually removed as well.
Related to this Change - “Park” renaming to “On Hold” on AC1:
- Attendant - Session Hold and Retrieve - All instances of “Park, Parked, Park Time, Unpark, Call Parking, etc.” wordings have been renamed to “On Hold” to avoid confusion in how the feature operates.
- Attendant Console 1.0: Related “Park” Buttons and UI labels have been changed to “Hold” as well.
- The related functionality and call scenario for AC1.0 is unchanged.
- No wording or UI changes to Attendant Console 2.0, which was already using “Hold” and “Retrieve”.
Attendant Console Consultation: Dialout / Busy tone and automatic retrieval
Attendant - Consultation Call - both AC1 and AC2 - Changed Consultation Call behavior:
- New: When starting a Consultation Call, a dialout tone is played to the Nimbus User.
- New: When the consulted destination declines or the invitation times out, a busy tone is played for the Nimbus User to inform that the call will be taken back.
- Changed: The session between Customer and User now persists. On Consultation (Contact) decline / timeout the call is now resumed automatically, and both parties can immediately talk with each other again.
Other Changes and Improvements
- Service Operations - Removed restriction, that Partner Administrators couldn't remove tasks from customer tenant. Partner Administrators can now remove tasks, even when User identifier masking is enabled.
- KB: Nimbus Power BI Template / Facts - Columns and Data Types > "Unified Sessions". Added a note on the Update frequency of Unified Session tables, specifying when end-to-end-interactions become visible in the OData Feed.
- Data Aggregation - OData > UserStatesAggregates: Data will be reprocessed, so gaps from missing records in the history since this table was first released, are now being closed. 💡Note that this is a long-running process. If you work with Data Aggregates, talk to Support to get a validation report and get notified when backfilling is complete.