@@ -537,6 +537,25 @@ Specify the **Output** schema when you add the destination dataflow endpoint.
537
537
538
538
# [Bicep](#tab/bicep)
539
539
540
+ ` ` ` bicep
541
+ {
542
+ operationType: 'BuiltInTransformation'
543
+ builtInTransformationSettings: {
544
+ // ...
545
+ schemaRef: 'aio-sr://${opcuaSchemaName}:${opcuaSchemaVer}'
546
+ serializationFormat: 'Parquet' // can also be 'Delta'
547
+ }
548
+ }
549
+ ` ` `
550
+
551
+ To specify the schema, you can create a Schema custom resource with the schema definition.
552
+
553
+ For more information about schema registry, see [Understand message schemas](concept-schema-registry.md).
554
+
555
+ Currently, Azure IoT Operations experience only supports Parquet output for output schemas.
556
+
557
+ Note : The Delta schema format is used for both Parquet and Delta output.
558
+
540
559
# [Kubernetes](#tab/kubernetes)
541
560
542
561
@@ -585,6 +604,48 @@ To configure a destination for the dataflow, specify the endpoint reference and
585
604
586
605
# [Bicep](#tab/bicep)
587
606
607
+ For example, to configure a destination using the Microsoft Fabric OneLake endpoint and a static MQTT topic, use the following configuration :
608
+
609
+ ` ` ` bicep
610
+ resource oneLakeEndpoint 'Microsoft.IoTOperations/instances/dataflowEndpoints@2024-08-15-preview' = {
611
+ parent: aioInstance
612
+ name: 'onelake-ep'
613
+ extendedLocation: {
614
+ name: customLocation.id
615
+ type: 'CustomLocation'
616
+ }
617
+ properties: {
618
+ endpointType: 'FabricOneLake'
619
+ fabricOneLakeSettings: {
620
+ authentication: {
621
+ method: 'SystemAssignedManagedIdentity'
622
+ systemAssignedManagedIdentitySettings: {}
623
+ }
624
+ oneLakePathType: 'Tables'
625
+ host: 'https://msit-onelake.dfs.fabric.microsoft.com'
626
+ names: {
627
+ lakehouseName: '<EXAMPLE-LAKEHOUSE-NAME>'
628
+ workspaceName: '<EXAMPLE-WORKSPACE-NAME>'
629
+ }
630
+ batching: {
631
+ latencySeconds: 5
632
+ maxMessages: 10000
633
+ }
634
+ }
635
+ }
636
+ }
637
+ ` ` `
638
+
639
+ ` ` ` bicep
640
+ {
641
+ operationType: 'Destination'
642
+ destinationSettings: {
643
+ endpointRef: oneLakeEndpoint.name
644
+ dataDestination: 'sensorData'
645
+ }
646
+ }
647
+ ` ` `
648
+
588
649
# [Kubernetes](#tab/kubernetes)
589
650
590
651
For example, to configure a destination using the MQTT endpoint created earlier and a static MQTT topic, use the following configuration :
0 commit comments