Skip to content

Commit 681206d

Browse files
authored
Update stream-analytics-define-kafka-input.md
1 parent 1dd2108 commit 681206d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/stream-analytics/stream-analytics-define-kafka-input.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Azure Stream Analytics lets you connect directly to Kafka clusters to ingest dat
2525

2626
Supported compression types are None, Gzip, Snappy, LZ4, and Zstd.
2727

28-
## Authentication and Encryption
28+
## Authentication and encryption
2929

3030
You can use four types of security protocols to connect to your Kafka clusters:
3131

@@ -43,7 +43,7 @@ You can use four types of security protocols to connect to your Kafka clusters:
4343
>
4444
4545

46-
### Key Vault Integration
46+
### Key Vault integration
4747

4848
> [!NOTE]
4949
> 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.
@@ -53,7 +53,7 @@ Azure Stream Analytics integrates seamlessly with Azure Key Vault to access stor
5353

5454
You can store the certificates as Key Vault certificates or Key Vault secrets. Private keys are in PEM format.
5555

56-
### Key Vault Integration
56+
### Key Vault integration
5757
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.
5858

5959

0 commit comments

Comments
 (0)