Configure data flow endpoints for local storage

1. In the operations experience, select the Data flow endpoints tab.

2. Under Create new data flow endpoint, select Local Storage > New.

   

3. Enter the following settings for the endpoint:

   Setting	Description
   Name	The name of the data flow endpoint.
   Persistent volume claim name	The name of the PVC to use for local storage.

4. Select Apply to provision the endpoint.

Create or replace

Use the az iot ops dataflow endpoint create fabric-onelake command to create or replace a local storage data flow endpoint.

az iot ops dataflow endpoint create local-storage --resource-group <ResourceGroupName> --instance <AioInstanceName> --name <EndpointName> --pvc-ref <PersistentVolumeClaimName>

The --pvc-ref parameter is the name of the PVC to use for local storage. The PVC must be in the same namespace as the data flow endpoint.

The following example command creates or replaces a local storage data flow endpoint named local-storage-endpoint:

az iot ops dataflow endpoint create local-storage --resource-group myResourceGroup --instance myAioInstance --name local-storage-endpoint --pvc-ref mypvc

Create or change

Use the az iot ops dataflow endpoint apply command to create or change a local storage data flow endpoint.

az iot ops dataflow endpoint apply --resource-group <ResourceGroupName> --instance <AioInstanceName> --name <EndpointName> --config-file <ConfigFilePathAndName>

The --config-file parameter is the path and file name of a JSON configuration file that contains the resource properties.

In this example, assume that a configuration file named local-storage-endpoint.json with the following content is stored in the user's home directory:

{
    "endpointType": "LocalStorage",
    "localStorageSettings": {
        "persistentVolumeClaimRef": "<PersistentVolumeClaimName>"
    }
}

The following example command creates a new local storage data flow endpoint named local-storage-endpoint:

az iot ops dataflow endpoint apply --resource-group myResourceGroupName --instance myAioInstanceName --name local-storage-endpoint --config-file ~/local-storage-endpoint.json

Create a .bicep file with the following content:

param aioInstanceName string = '<AIO_INSTANCE_NAME>'
param customLocationName string = '<CUSTOM_LOCATION_NAME>'
param endpointName string = '<ENDPOINT_NAME>'
param persistentVCName string = '<PERSISTENT_VC_NAME>'

resource aioInstance 'Microsoft.IoTOperations/instances@2026-03-01' existing = {
  name: aioInstanceName
}
resource customLocation 'Microsoft.ExtendedLocation/customLocations@2021-08-31-preview' existing = {
  name: customLocationName
}
resource localStorageDataflowEndpoint 'Microsoft.IoTOperations/instances/dataflowEndpoints@2026-03-01' = {
  parent: aioInstance
  name: endpointName
  extendedLocation: {
    name: customLocation.id
    type: 'CustomLocation'
  }
  properties: {
    endpointType: 'LocalStorage'
    localStorageSettings: {
      persistentVolumeClaimRef: persistentVCName
    }
  }
}

Deploy the file via the Azure CLI:

az deployment group create --resource-group <RESOURCE_GROUP> --template-file <FILE>.bicep

Create a Kubernetes manifest .yaml file with the following content:

apiVersion: connectivity.iotoperations.azure.com/v1
kind: DataflowEndpoint
metadata:
  name: <ENDPOINT_NAME>
  namespace: azure-iot-operations
spec:
  endpointType: LocalStorage
  localStorageSettings:
    persistentVolumeClaimRef: <PVC_NAME>

Apply the manifest file to the Kubernetes cluster:

kubectl apply -f <FILE>.yaml