Contents

Trying the new Azure Functions managed connectors - Dataverse trigger

Managed connectors in Azure Functions

Azure Functions just got a major upgrade: managed connectors are officially here! Just like the ones you love in Logic Apps, these connectors bridge the gap between code and your favorite cloud services.

You can now build function triggers that listen directly to:

  • Power Platform
  • Microsoft 365
  • Microsoft Teams
  • SharePoint

Wondering how to set up these connections since we are dealing with code?

Since this feature is currently in preview, it may not be the final approach yet. You won’t find a built-in template for it inside Visual Studio 2026. Instead, the best place to kick things off is the official samples page here: Azure-Samples/functions-connectors-net: Azure Functions samples showcasing Connector triggers and bindings.

./azure_functions_managed_connectors.assets/image.png

If you observe the templates, we have Dataverse from Power Platform, and the rest are apps that use the Graph API.

You will need to have all of this:

curl -fsSL https://aka.ms/connector-namespace-cli-install | sh

or

# PowerShell

irm https://aka.ms/connector-namespace-cli-install-ps | iex

Once you clone the sample and install all the above, open “local.settings.json” and add the organisation URL (something.crm#.dynamics.com) and the entity you want to listen to. Plural name.

You do not need to worry about the connector just yet! We will get there soon.

./azure_functions_managed_connectors.assets/image-3.png

Now, just to run the sample (feel free to add more code to do something with the trigger data if you want) save it all and run this command sequence:

cd dataverseApp

azd auth login

az login

# Configure the trigger (name is auto-resolved to the org URL; or set the URL directly).
azd env set DATAVERSE_ENVIRONMENT_NAME "Contoso (default)"
azd env set DATAVERSE_TABLE_NAME "accounts"

azd up

line 3 and 5 are simple authentication. will prompt you to authenticate.

./azure_functions_managed_connectors.assets/image-4.png

The next 2 you add the name of the organisation as you see in make.powerautomate.com and again the entity name

AZD UP will start the deployment. It will provision the function app,

./azure_functions_managed_connectors.assets/image-5.png ./azure_functions_managed_connectors.assets/image-6.png ./azure_functions_managed_connectors.assets/image-7.png ./azure_functions_managed_connectors.assets/image-8.png

After the provisioning, it will prompt this

./azure_functions_managed_connectors.assets/image-9.png

And there you go!

./azure_functions_managed_connectors.assets/image-10.png

cnsc-kpuwyyzsfiqly-ondataverserowchanged

The control panel has the connector details and can display something similar to the logic apps execution views

Open make.power.com and add a few rows to Account. Remember this trigger for now only capture “Create”.

./azure_functions_managed_connectors.assets/image-11.png

Top of the page there is an edit button that doesn’t do as much as the edit.

./azure_functions_managed_connectors.assets/image-12.png

Use Edit Json to change the recurrence if you want. Default is 5 min. Bit long to debug.

./azure_functions_managed_connectors.assets/image-13.png