Skip to content

Commit e8c78c8

Browse files
quick update
1 parent ec8d41f commit e8c78c8

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/iot-operations/connect-to-cloud/howto-create-dataflow.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -401,6 +401,10 @@ Currently, the enrich operation isn't available in the operations experience por
401401

402402
# [Bicep](#tab/bicep)
403403

404+
```bicep
405+
406+
```
407+
404408
# [Kubernetes](#tab/kubernetes)
405409

406410
For example, you could use the `deviceId` field in the source data to match the `asset` field in the dataset:
@@ -522,8 +526,6 @@ When the dataflow resource is created, it includes a schemaRef value that points
522526

523527
Currently, Azure IoT Operations experience only supports Parquet output for output schemas.
524528

525-
Note: The Delta schema format is used for both Parquet and Delta output.
526-
527529
```bicep
528530
{
529531
operationType: 'BuiltInTransformation'

0 commit comments

Comments
 (0)