INC Upcoming Connector Feature Certification

⌛Pending Connector Certification: Features or functional changes described in the following are still undergoing a Microsoft review and certification process. Your Power Automate UI may differ until the changes are certified and rolled out for the latest official Nimbus Power Automate Connector.


Available Connector Update Paths

Connector Update Paths

As the connector certification by Microsoft is a continuous process, you can either opt to manually update to the latest “custom” connector OR wait for automatic updates after certification:

Nimbus Power Automate connector - Release cycle and Update path
Customer Tenant Admin Procedures

Nimbus Customers can choose between following upgrade paths for the Power Automate connector: 

A: Update Path B: Migration Path
From the Custom Connector page, retrieve the V1 connector. Install it locally on your Tenant as a “custom connector”. When you are already using the custom connector, you need to migrate all your existing Flows to the certified connector from the Microsoft Power Automate store.
Benefits: Newest connector functionality is available as soon as the custom connector is installed. Benefits: Once migrated, future connector updates are rolled out automatically.
Drawbacks: Manual future Connector Migration effort. Drawbacks: Initial migration effort. Due to the Microsoft recertification process, the certified connector will get new features later.
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.

  • Once this approval is done, the submitted V1 connector becomes the new “certified connector" directly available in the Microsoft Store. Customers already using the certified connector get updates automatically. 
  • Flows may need minor adjustments (e.g. to make use of new Flow Actions / Trigger Events features).

💡Note: Each update triggers a re-certification process by Microsoft and takes ~4-6 weeks.

 
 

Accessing the Latest Connector

When to test Connector functionality

Luware development implements changes in the upcoming Nimbus Power Automate Connector (v1) and starts a certification process with Microsoft right after every major Nimbus release.

🤔When do I need to manually update a custom connector? If the official Nimbus Release Notes mention new connector features which 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.

Learn more…

Nimbus Power Automate connector - Release cycle and Update path
Customer Tenant Admin Procedures

Nimbus Customers can choose between following upgrade paths for the Power Automate connector: 

A: Update Path B: Migration Path
From the Custom Connector page, retrieve the V1 connector. Install it locally on your Tenant as a “custom connector”. When you are already using the custom connector, you need to migrate all your existing Flows to the certified connector from the Microsoft Power Automate store.
Benefits: Newest connector functionality is available as soon as the custom connector is installed. Benefits: Once migrated, future connector updates are rolled out automatically.
Drawbacks: Manual future Connector Migration effort. Drawbacks: Initial migration effort. Due to the Microsoft recertification process, the certified connector will get new features later.
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.

  • Once this approval is done, the submitted V1 connector becomes the new “certified connector" directly available in the Microsoft Store. Customers already using the certified connector get updates automatically. 
  • Flows may need minor adjustments (e.g. to make use of new Flow Actions / Trigger Events features).

💡Note: Each update triggers a re-certification process by Microsoft and takes ~4-6 weeks.

 
 

💡Good to know:  If you performed a Connector Migration before now use the Microsoft store-certified connector, you can skip the update steps shown below. After each V1 connector update re-certification by Microsoft, your connector updates automatically.

 

Manual Connector Update Steps

  1. 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.

Switzerland 01 https://portal.ch-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
Switzerland 02 https://portal.ch-02.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
Germany 01 https://portal.dewe-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
Germany 02 https://portal.dewe-02.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
United Kingdom 01 https://portal.ukso-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
Australia 01 https://portal.aue-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
West Europe 01 https://portal.euwe-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
East United States 01 https://portal.use-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json
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.

  1. Go to https://make.powerautomate.com/ and expand Data > Custom Connectors.
  2. Select your Nimbus Custom Connector from the list.
  3. Click on the Context menu (three dots) at the end of the line. 
  4. Select “Update from OpenAPI file”.
  5. Click the "Import" button and select the new file.
  6. Finally click “Continue”.
    ⮑ The connector is now updated and should be visible on your Tenant.
 
 

Table of Contents