Skip to content

Commit ec52a92

Browse files
committed
Remove preview notes
1 parent 016784b commit ec52a92

5 files changed

Lines changed: 4 additions & 6 deletions

File tree

articles/iot-operations/connect-to-cloud/concept-dataflow-enrich.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.service: azure-iot-operations
1616
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
1717

1818
> [!TIP]
19-
> Data flow graphs support enrichment with expanded capabilities including enrichment in filter and branch transforms. For new projects that use MQTT, Kafka, or OpenTelemetry endpoints, see [Enrich with external data in data flow graphs](howto-dataflow-graphs-enrich.md) (preview).
19+
> Data flow graphs support enrichment with expanded capabilities including enrichment in filter and branch transforms. For new projects that use MQTT, Kafka, or OpenTelemetry endpoints, see [Enrich with external data in data flow graphs](howto-dataflow-graphs-enrich.md).
2020
2121
You can enrich data by using the *contextualization datasets* function. When incoming records are processed, you can query these datasets based on conditions that relate to the fields of the incoming record. This capability allows for dynamic interactions. Data from these datasets can be used to supplement information in the output fields and participate in complex calculations during the mapping process.
2222

articles/iot-operations/connect-to-cloud/concept-dataflow-graphs.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,6 @@ Azure IoT Operations provides two ways to process data in a pipeline:
3333
| Time-based aggregation | Not available | Window transforms with tumbling windows |
3434
| Conditional routing | Not available | Branch and concat transforms |
3535
| Endpoint support | All endpoint types | MQTT, Kafka, and OpenTelemetry only |
36-
| Status | Generally available | Preview |
3736

3837
For new projects that use supported endpoint types, we recommend data flow graphs. Data flows remain fully supported for all scenarios, and they support the full range of endpoint types.
3938

articles/iot-operations/connect-to-cloud/concept-dataflow-mapping.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.service: azure-iot-operations
1717
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
1818

1919
> [!TIP]
20-
> Data flow graphs offer an expanded mapping language with additional functions, composable transforms, and features like conditional routing and time-based aggregation. For new projects that use MQTT, Kafka, or OpenTelemetry endpoints, see [Transform data with map in data flow graphs](howto-dataflow-graphs-map.md) (preview).
20+
> Data flow graphs offer an expanded mapping language with additional functions, composable transforms, and features like conditional routing and time-based aggregation. For new projects that use MQTT, Kafka, or OpenTelemetry endpoints, see [Transform data with map in data flow graphs](howto-dataflow-graphs-map.md).
2121
2222
Use the data flow mapping language to transform data in Azure IoT Operations. The syntax is a simple, yet powerful, way to define mappings that transform data from one format to another. This article provides an overview of the data flow mapping language and key concepts.
2323

articles/iot-operations/connect-to-cloud/overview-dataflow-comparison.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Data flows are generally available and support all endpoint types.
2626

2727
A [data flow graph](concept-dataflow-graphs.md) is a composable, graph-based pipeline that connects multiple transforms in any topology you define. You can chain, branch, and merge processing steps. Each transform is a pre-built processing unit (map, filter, branch, window, enrichment) that you configure with rules. You configure a data flow graph by creating a `DataflowGraph` custom resource.
2828

29-
Data flow graphs are in preview and support MQTT, Kafka, and OpenTelemetry endpoints.
29+
Data flow graphs support MQTT, Kafka, and OpenTelemetry endpoints.
3030

3131
## Comparison
3232

@@ -41,7 +41,6 @@ Data flow graphs are in preview and support MQTT, Kafka, and OpenTelemetry endpo
4141
| Dynamic destination topics | `${inputTopic}` (source topic passthrough) | `$metadata.topic` + `${outputTopic}` (content-based routing) |
4242
| Schema | On source and transformation | On node connections |
4343
| Disk persistence | Supported | Supported |
44-
| Status | Generally available | Preview |
4544

4645
## Shared infrastructure
4746

articles/iot-operations/connect-to-cloud/overview-dataflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ You can apply transformations to data during the processing stage to perform var
4646
- **Contextualizing data**: Add reference data to messages for enrichment and driving insights.
4747

4848
> [!TIP]
49-
> For richer processing capabilities including conditional routing, time-based aggregation, and composable transform pipelines, see [Data flow graphs](concept-dataflow-graphs.md) (preview).
49+
> For richer processing capabilities including conditional routing, time-based aggregation, and composable transform pipelines, see [Data flow graphs](concept-dataflow-graphs.md).
5050
5151
### Configuration and deployment
5252

0 commit comments

Comments
 (0)