Skip to content

Commit d093b83

Browse files
Merge pull request #295909 from PatAltimore/patricka-dataflow-profile
Add support for one data flow profile
2 parents c06c8f6 + 97c441d commit d093b83

File tree

1 file changed

+4
-34
lines changed

1 file changed

+4
-34
lines changed

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

Lines changed: 4 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: patricka
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: how-to
9-
ms.date: 11/11/2024
9+
ms.date: 03/06/2025
1010

1111
#CustomerIntent: As an operator, I want to understand how to I can configure a a data flow profile to control a data flow behavior.
1212
---
@@ -21,9 +21,10 @@ The most important setting is the instance count, which determines the number of
2121

2222
## Default data flow profile
2323

24-
By default, a data flow profile named "default" is created when Azure IoT Operations is deployed. This data flow profile has a single instance count. You can use this data flow profile to get started with Azure IoT Operations.
24+
By default, a data flow profile named *default* is created when Azure IoT Operations is deployed. This data flow profile has a single instance count. You can use this data flow profile to get started with Azure IoT Operations.
2525

26-
Currently, when using the [operations experience portal](https://iotoperations.azure.com/), the default data flow profile is used for all data flows.
26+
> [!IMPORTANT]
27+
> Currently, the default data flow profile is the only profile supported by the [operations experience portal](https://iotoperations.azure.com/). All data flows created using the operations experience portal use the default data flow profile.
2728
2829
# [Bicep](#tab/bicep)
2930

@@ -69,37 +70,6 @@ spec:
6970
7071
---
7172
72-
Unless you need additional throughput or redundancy, you can use the default data flow profile for your data flows. If you need to adjust the instance count or other settings, you can create a new data flow profile.
73-
74-
## Create a new data flow profile
75-
76-
To create a new data flow profile, specify the name of the profile and the instance count.
77-
78-
# [Bicep](#tab/bicep)
79-
80-
```bicep
81-
resource dataflowProfile 'Microsoft.IoTOperations/instances/dataflowProfiles@2024-11-01' = {
82-
parent: aioInstance
83-
name: '<NAME>'
84-
properties: {
85-
instanceCount: <COUNT>
86-
}
87-
}
88-
```
89-
90-
# [Kubernetes (preview)](#tab/kubernetes)
91-
92-
```yaml
93-
apiVersion: connectivity.iotoperations.azure.com/v1
94-
kind: DataflowProfile
95-
metadata:
96-
name: '<NAME>'
97-
namespace: azure-iot-operations
98-
spec:
99-
instanceCount: <COUNT>
100-
```
101-
102-
---
10373
10474
## Scaling
10575

0 commit comments

Comments
 (0)