For Experts / Testing purposes only
The following content is meant is for power users that want to test upcoming (non-certified) Power Automate Use Cases on their Tenant.
The Nimbus Power Automate connector can also be installed via Microsoft Store. If you want to use the latest Certified Connector, please visit Nimbus Power Automate Connector.
Connector variants
Luware Nimbus uses Microsoft Power Automate as an interface for the integration of third-party applications. The Nimbus Power Automate Connector comes in multiple variants. On this page we highlight the differences and in which case you should opt for a specific version.
| Certified Connector |
The advantage of the certified connector is that it is directly available in Microsoft in the Power Platform without the need to be manually registered on the customer’s tenant. The certified connector is the stable and supported version and recommended for the use in production systems. However, the release cycle is irregular, as recertification by Microsoft is required for each release. The certified connector can be directly retrieved (and updated) via the Microsoft Store. However, to test (pre-production) functionality on your Tenant you can download the connector manually from our Nimbus hosting source. → Read more further below. |
|---|---|
| Custom Connector |
The advantage of the custom connector is that it contains the most recent updates. The custom connector is a preview version of new features to be released for Nimbus. It needs to be installed on the customer’s tenant and can be used for testing new features early on. However, the up-to-date version is experimental as it does not undergo any particular release cycle or the certification by Microsoft. |
Connector update / migration path
When already using the custom connector, Luware customers can either chose to continue updating manually or perform a Connector Migration to the Microsoft-Store certified connector. The following graphic is illustrating the choices.
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. |
Connector download
✅ Manual Admin Action: Luware provides both a to be certified (v1) and custom (v0) connector for download. Either connector variant needs to be manually downloaded and installed on your Tenant.
-
☝Please note: Connectors download URLs are region-specific. The region is determined during your first Nimbus service onboarding. If you don't know your Nimbus cluster region:
- Log into Nimbus Admin.
- Check the URL on your browser address bar to identify the region you were redirected towards.
- Refer to the URLs below to see which matches with your cluster region.
- Finally, check the table below. Replace the last part of the “File Path” column to retrieve the corresponding connector.
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.
Upcoming V1 and Custom V0 Connector differences
The table below lists the differences between the “to be certified (v1)” and “legacy custom (v0)” connector available for download.
| Version | Audience | File Path (to append to domain) | Notes |
|---|---|---|---|
| Upcoming Connector (v1) | Customers that need latest development features in PowerAutomate and don't want/can't wait for the Certified Connector to be released. |
Single Json
|
The Upcoming Connector is our to be certified version for testing purposes.
💡 When to use: ☝ We DO NOT recommend to use this connector for productive flows as last-minute (breaking) changes could occur. ☝ A changeover to the officially Certified Connector still requires a manual Connector Migration of your flows. Use this when you want to test upcoming preview functionality, which is not available on the Certified Connector yet.
You can install the “To be Upcoming Connector” in the same way as a Custom Connector → See Power Automate Connector Introduction → Installation chapter |
|
Custom Connector (v0, Legacy) |
Customers that already set up flows before March 2024
OR
Customers that want to remain on existing features and want to delay the migration. |
Single Json
|
The Legacy Connector was our existing way of providing integrations to Nimbus. It will receive bugfixes, but no new functionality.
💡When to use: If you are already using the Custom Connector, continue to use the v0 version until you are ready to switch your flows using the certified connector. ☝ A changeover to the officially Certified Connector requires a manual Connector Migration of your flows. |
FAQ - Frequently asked questions
🤔 I got the connector files. How do I install them on my Tenant? |
We have provided detailed steps on the entry page for our Nimbus Power Automate Connector → Installation → Custom Connector chapters. |
🤔 I already had a connector manually installed on my Tenant. How do I update it? |
Refer to Update your Nimbus Power Automate Connector. Note that these steps are required whenever an update or replacement of your connector files is necessary. |
🤔 What are the technical differences between the Custom and Certified Connector? |
New naming conventions of Flow Actions, Trigger Events and related System Fields and Parameters require a split between connectors. Flow / Trigger actions are also split up differently in their feature scope, making the connectors incompatible. 🔎 Refer to Connector Migration for some examples. |
🤔 Why are there two variants and why is the migration needed? |
The change was necessary to meet Microsoft certification standards, while also allowing more flexibility for development in parallel, e.g. to allow Customers to test and preview new functionality and upcoming features without a “big-bang” enforced update. |
🤔Can I switch my existing flows to a different connector? |
Only a Microsoft store-installed flow can be updated automatically. Any existing flows that don't use the store-installed Certified Connector require a Connector Migration. 💡 This is due to how connectors are authenticated on your Tenant, each using their own actions and triggers with changed data structure. While Luware is aiming to make any migration as seamless as possible, manual effort (and thorough re-testing) of existing flows cannot be avoided. |
🤔 What if I can't switch from the Custom Connector yet? |
Don't worry! Your legacy Custom Connectors will continue running, but not receive any feature updates – just essential bugfixes and improvements. 🔎 We will communicate reliances and future update paths via our Latest Release Notes and provide advance communication via Customer Success and Support teams respectively. |