Release Notes
October 2026
We now validate the Function App name more strictly for Azure Functions connections. In line with Microsoft's Azure naming rules, the name must be 2-64 characters long, can contain only letters, digits, and hyphens, and can't start or end with a hyphen. If your Function App name includes Azure-generated, dot-separated parts (for example, <app-name>.<region>-01), those parts can contain only letters, digits, hyphens, and dots. This ensures Fivetran sends requests only to your Function App's azurewebsites.net address.
If your connection uses a name that doesn't follow these rules, the connection test or sync fails with an invalid input error. To fix it, enter only the Function App name exactly as it appears in the Azure portal, without https://, paths, ports, or query strings, in the Function App field of the connection setup form. For more information, see our setup instructions.
December 2025
We now support the Source naming feature for the following connectors:
| Application Connectors | Database Connectors | File Connectors | Event Connectors | Function Connectors |
|---|---|---|---|---|
|
February 2025
The Retrieve Function Connection State and Update Function Connection State endpoints in our REST API that allow you to get and update the state of Functions and Connector SDK connections are generally available.
November 2023
You can now specify custom payloads as key-value pairs when you configure the Azure Functions connector using our REST API.
You can now add custom payloads as key-value pairs when you configure the Azure Functions connector. For more information, see our Azure Functions setup guide.
September 2023
You can now specify secrets as key-pair values when you configure the Azure Functions connector using our REST API.
August 2023
You can now Add secrets as key-pair values while configuring the Azure Functions connector. Previously, you had to enter your secrets in JSON format. We will continue to support secret(s) in JSON format for Azure Functions connections created before August 9, 2023. For more information, see our Azure Functions setup guide.
July 2023
We have implemented two new endpoints in our REST API, Retrieve Function Connection State and Update Function Connection State that allow you to get and update the state of Functions connections, respectively.
This feature is in beta.
We have added support for Azure Private Link connections to Azure Functions. If you're on a Business Critical plan, you can now opt to use Azure Private Link to connect to Fivetran. In the connector setup form, select the Connection Method as Connect via Private Link. For more information, see our setup instructions.
We now support custom error handling for Azure functions. You can add an error handling mechanism in your Azure Function response to report an error on your Fivetran dashboard. For more information, see our setup instructions and REST API config.
May 2023
We have added support for the soft delete sync mode. For more information, see our Function connectors' overview documentation.
February 2023
We have added an optional field, sync_id, to Fivetran's request format. sync_id is the Fivetran sync identifier (UUID). You can use the sync_id to debug and link function logs with connector logs. For more information, see our Request format documentation. We are gradually rolling out this feature to all existing connections.
August 2018
Azure Functions is a serverless computing platform that runs code in response to events and automatically manages the compute resources required by that code.