Skip to content

Commit 1dd2108

Browse files
authored
Update kafka-output.md
1 parent 5389ed0 commit 1dd2108

File tree

1 file changed

+10
-13
lines changed

1 file changed

+10
-13
lines changed

articles/stream-analytics/kafka-output.md

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,12 @@ ms.topic: conceptual
88
ms.date: 09/26/2023
99
---
1010

11-
# Kafka Output from Azure Stream Analytics (Preview)
11+
# Kafka output from Azure Stream Analytics (Preview)
1212

1313
Azure Stream Analytics allows you to connect directly to Kafka clusters as a producer to output data. The solution is low code and entirely managed by the Azure Stream Analytics team at Microsoft, allowing it to meet business compliance standards. The Kafka Adapters are backward compatible and support all versions with the latest client release starting from version 0.10. Users can connect to Kafka clusters inside a VNET and Kafka clusters with a public endpoint, depending on the configurations. The configuration relies on existing Kafka configuration conventions.
14-
15-
### Kafka Event Compression
16-
1714
Supported compression types are None, Gzip, Snappy, LZ4, and Zstd.
1815

19-
## Authentication and Encryption
16+
## Authentication and encryption
2017

2118
You can use four types of security protocols to connect to your Kafka clusters:
2219

@@ -30,25 +27,25 @@ You can use four types of security protocols to connect to your Kafka clusters:
3027

3128

3229
> [!IMPORTANT]
33-
> Confluent Cloud supports authenticating using API Keys, OAuth, or SAML single sign-on (SSO). Azure Stream Analytics does not currently support these authentication options. There will be an update shortly to support authenticating to the confluent cloud using API Keys.
30+
> Confluent Cloud supports authenticating using API Keys, OAuth, or SAML single sign-on (SSO). Azure Stream Analytics does not currently support these authentication options.
3431
>
3532
3633

37-
### Key Vault Integration
34+
### Key vault integration
3835

3936
> [!NOTE]
40-
> When using trust store certificates with mTLS or SASL_SSL security protocols, you must have Azure KeyVault and managed identity configured for your Azure Stream Analytics job.
37+
> When using trust store certificates with mTLS or SASL_SSL security protocols, you must have Azure Key vault and managed identity configured for your Azure Stream Analytics job.
4138
>
42-
Azure Stream Analytics integrates seamlessly with Azure Key Vault to access stored secrets needed for authentication and encryption when using mTLS or SASL_SSL security protocols. Your Azure Stream Analytics job connects to Azure Key Vault using managed identity to ensure a secure connection and avoid the exfiltration of secrets.
39+
Azure Stream Analytics integrates seamlessly with Azure Key vault to access stored secrets needed for authentication and encryption when using mTLS or SASL_SSL security protocols. Your Azure Stream Analytics job connects to Azure Key vault using managed identity to ensure a secure connection and avoid the exfiltration of secrets.
4340

44-
You can store the certificates as Key Vault certificates or Key Vault secrets. Private keys are in PEM format.
41+
You can store the certificates as Key Vault certificates or Key vault secrets. Private keys are in PEM format.
4542

46-
### Key Vault Integration
43+
### VNET integration
4744
When configuring your Azure Stream Analytics job to connect to your Kafka clusters, depending on your configuration, you may have to configure your job to access your Kafka clusters, which are behind a firewall or inside a virtual network. You can visit the Azure Stream Analytics VNET documentation to learn more about configuring private endpoints to access resources inside a virtual network or behind a firewall.
4845

4946

5047
### Configuration
51-
The following table lists the property names and their description for creating a Kafka Output:
48+
The following table lists the property names and their description for creating a Kafka output:
5249

5350
| Property name | Description |
5451
|------------------------------|-------------------------------------------------------------------------------------------------------------------------|
@@ -62,7 +59,7 @@ The following table lists the property names and their description for creating
6259

6360
### Limitations
6461
* When configuring your Azure Stream Analytics jobs to use VNET/SWIFT, your job must be configured with at least six (6) streaming units.
65-
* When using mTLS or SASL_SSL with Azure Key Vault, you must convert your Java Key Store to PEM format.
62+
* When using mTLS or SASL_SSL with Azure Key vault, you must convert your Java Key Store to PEM format.
6663
* The minimum version of Kafka you can configure Azure Stream Analytics to connect to is version 0.10.
6764

6865
> [!NOTE]

0 commit comments

Comments
 (0)