Basic config examples for Azure Functions

Basic configuration examples

Enable on a service

Enable on a route

Enable on a consumer

Enable globally

The following examples provide some typical configurations for enabling the azure-functions plugin on a service.

Kong Admin API

Konnect API

Kubernetes

Declarative (YAML)

Make the following request:

curl -X POST http://localhost:8001/services/{serviceName|Id}/plugins \
    --data "name=azure-functions"  \
    --data "config.functionname=<AZURE_FUNCTIONNAME>"  \
    --data "config.appname=<AZURE_APPNAME>"  \
    --data "config.hostdomain=azurewebsites.net"  \
    --data "config.apikey=<AZURE_APIKEY>"

Replace SERVICE_NAME|ID with the id or name of the service that this plugin configuration will target.

Make the following request, substituting your own access token, region, control plane ID, and service ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/services/{serviceId}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"azure-functions","config":{"functionname":"<AZURE_FUNCTIONNAME>","appname":"<AZURE_APPNAME>","hostdomain":"azurewebsites.net","apikey":"<AZURE_APIKEY>"}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

First, create a KongPlugin resource:

echo "
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: azure-functions-example
plugin: azure-functions
config:
  functionname: "<AZURE_FUNCTIONNAME>"
  appname: "<AZURE_APPNAME>"
  hostdomain: azurewebsites.net
  apikey: "<AZURE_APIKEY>"
" | kubectl apply -f -

Next, apply the KongPlugin resource to an ingress by annotating the service as follows:

kubectl annotate service SERVICE_NAME konghq.com/plugins=azure-functions-example

Replace SERVICE_NAME with the name of the service that this plugin configuration will target. You can see your available ingresses by running kubectl get service.

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: azure-functions
  service: SERVICE_NAME|ID
  config:
    functionname: "<AZURE_FUNCTIONNAME>"
    appname: "<AZURE_APPNAME>"
    hostdomain: azurewebsites.net
    apikey: "<AZURE_APIKEY>"

Replace SERVICE_NAME|ID with the id or name of the service that this plugin configuration will target.

The following examples provide some typical configurations for enabling the azure-functions plugin on a route.

Kong Admin API

Konnect API

Kubernetes

Declarative (YAML)

Make the following request:

curl -X POST http://localhost:8001/routes/{routeName|Id}/plugins \
    --data "name=azure-functions"  \
    --data "config.functionname=<AZURE_FUNCTIONNAME>"  \
    --data "config.appname=<AZURE_APPNAME>"  \
    --data "config.hostdomain=azurewebsites.net"  \
    --data "config.apikey=<AZURE_APIKEY>"

Replace ROUTE_NAME|ID with the id or name of the route that this plugin configuration will target.

Make the following request, substituting your own access token, region, control plane ID, and route ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/routes/{routeId}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"azure-functions","config":{"functionname":"<AZURE_FUNCTIONNAME>","appname":"<AZURE_APPNAME>","hostdomain":"azurewebsites.net","apikey":"<AZURE_APIKEY>"}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

First, create a KongPlugin resource:

echo "
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: azure-functions-example
plugin: azure-functions
config:
  functionname: "<AZURE_FUNCTIONNAME>"
  appname: "<AZURE_APPNAME>"
  hostdomain: azurewebsites.net
  apikey: "<AZURE_APIKEY>"
" | kubectl apply -f -

Next, apply the KongPlugin resource to an ingress by annotating the ingress as follows:

kubectl annotate ingress INGRESS_NAME konghq.com/plugins=azure-functions-example

Replace INGRESS_NAME with the name of the ingress that this plugin configuration will target. You can see your available ingresses by running kubectl get ingress.

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: azure-functions
  route: ROUTE_NAME|ID
  config:
    functionname: "<AZURE_FUNCTIONNAME>"
    appname: "<AZURE_APPNAME>"
    hostdomain: azurewebsites.net
    apikey: "<AZURE_APIKEY>"

Replace ROUTE_NAME|ID with the id or name of the route that this plugin configuration will target.

The following examples provide some typical configurations for enabling the azure-functions plugin on a consumer.

Kong Admin API

Konnect API

Kubernetes

Declarative (YAML)

Make the following request:

curl -X POST http://localhost:8001/consumers/{consumerName|Id}/plugins \
    --data "name=azure-functions"  \
    --data "config.functionname=<AZURE_FUNCTIONNAME>"  \
    --data "config.appname=<AZURE_APPNAME>"  \
    --data "config.hostdomain=azurewebsites.net"  \
    --data "config.apikey=<AZURE_APIKEY>"

Replace CONSUMER_NAME|ID with the id or name of the consumer group that this plugin configuration will target.

Make the following request, substituting your own access token, region, control plane ID, and consumer ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/consumers/{consumerId}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"azure-functions","config":{"functionname":"<AZURE_FUNCTIONNAME>","appname":"<AZURE_APPNAME>","hostdomain":"azurewebsites.net","apikey":"<AZURE_APIKEY>"}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

First, create a KongPlugin resource:

echo "
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: azure-functions-example
plugin: azure-functions
config:
  functionname: "<AZURE_FUNCTIONNAME>"
  appname: "<AZURE_APPNAME>"
  hostdomain: azurewebsites.net
  apikey: "<AZURE_APIKEY>"
" | kubectl apply -f -

Next, apply the KongPlugin resource to an ingress by annotating the KongConsumer object as follows:

kubectl annotate KongConsumer CONSUMER_NAME konghq.com/plugins=azure-functions-example

Replace CONSUMER_NAME with the name of the consumer that this plugin configuration will target. You can see your available consumers by running kubectl get KongConsumer.

To learn more about KongConsumer objects, see Provisioning Consumers and Credentials .

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: azure-functions
  consumer: CONSUMER_NAME|ID
  config:
    functionname: "<AZURE_FUNCTIONNAME>"
    appname: "<AZURE_APPNAME>"
    hostdomain: azurewebsites.net
    apikey: "<AZURE_APIKEY>"

Replace CONSUMER_NAME|ID with the id or name of the consumer that this plugin configuration will target.

A plugin which is not associated to any service, route, consumer, or consumer group is considered global, and will be run on every request.

In self-managed Kong Enterprise, the plugin applies to every entity in a given workspace.
In self-managed Kong Gateway (OSS), the plugin applies to your entire environment.
In Konnect, the plugin applies to every entity in a given control plane.

Read the Plugin Reference and the Plugin Precedence sections for more information.

The following examples provide some typical configurations for enabling the Azure Functions plugin globally.

Kong Admin API

Konnect API

Kubernetes

Declarative (YAML)

Make the following request:

curl -X POST http://localhost:8001/plugins/ \
    --data "name=azure-functions"  \
    --data "config.functionname=<AZURE_FUNCTIONNAME>"  \
    --data "config.appname=<AZURE_APPNAME>"  \
    --data "config.hostdomain=azurewebsites.net"  \
    --data "config.apikey=<AZURE_APIKEY>"

Make the following request, substituting your own access token, region, and control plane ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/plugins/ \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"azure-functions","config":{"functionname":"<AZURE_FUNCTIONNAME>","appname":"<AZURE_APPNAME>","hostdomain":"azurewebsites.net","apikey":"<AZURE_APIKEY>"}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

Create a KongClusterPlugin resource and label it as global:

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: <global-azure-functions>
  annotations:
    kubernetes.io/ingress.class: kong
  labels:
    global: "true"
config:
  functionname: "<AZURE_FUNCTIONNAME>"
  appname: "<AZURE_APPNAME>"
  hostdomain: azurewebsites.net
  apikey: "<AZURE_APIKEY>"
plugin: azure-functions

Add a plugins entry in the declarative configuration file:

plugins:
- name: azure-functions
  config:
    functionname: "<AZURE_FUNCTIONNAME>"
    appname: "<AZURE_APPNAME>"
    hostdomain: azurewebsites.net
    apikey: "<AZURE_APIKEY>"

Previous Azure Functions Configuration

Next Azure Functions Changelog