Skip to content

Commit 97c441d

Browse files
committed
Add feedback
1 parent 832c1ab commit 97c441d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +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

2626
> [!IMPORTANT]
27-
> Currently, one data flow profile is supported for the [operations experience portal](https://iotoperations.azure.com/). The default data flow profile is used for all data flows.
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.
2828
2929
# [Bicep](#tab/bicep)
3030

0 commit comments

Comments
 (0)