Document Details
Transport Layer Security Configure Minimum Version
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page exhibits several signs of Windows bias. It references Windows-specific tools (ARMClient.exe), provides PowerShell examples, and omits equivalent Linux-native instructions or tools (e.g., using curl/jq for REST API calls, or az CLI for token retrieval). The order of presentation also often places Windows/PowerShell approaches before cross-platform or Linux-friendly alternatives. There are no explicit Linux or bash examples for key tasks such as querying the ARM API or obtaining tokens.
Recommendations
- Provide Linux/bash-native examples for all command-line operations, such as using curl and jq to query the ARM API and az CLI to obtain tokens.
- Mention and demonstrate cross-platform tools (e.g., az CLI, curl) before or alongside Windows-specific tools like ARMClient.exe.
- Where PowerShell is shown, also provide bash/zsh equivalents.
- Clarify that ARMClient.exe is a Windows-only tool and suggest alternatives for Linux/macOS users.
- Audit all screenshots and instructions to ensure they are not Windows-centric unless the feature is truly Windows-only.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
Flagged Code Snippets
5. Save the template. 6. Specify resource group parameter, then choose the **Review + create** button to deploy the template and create a namespace with the `MinimumTlsVersion` property configured. > [!NOTE] > After you update the minimum TLS version for the Service Bus namespace, it may take up to 30 seconds before the change is fully propagated. Configuring the minimum TLS version requires api-version 2022-01-01-preview or later of the Azure Service Bus resource provider. ## Check the minimum required TLS version for a namespace To check the minimum required TLS version for your Service Bus namespace, you can query the Azure Resource Manager API. You will need a Bearer token to query against the API, which you can retrieve using [ARMClient](https://github.com/projectkudu/ARMClient) by executing the following commands.
## Use Azure PowerShell To **create a namespace with minimum TLS version set to 1.3**, use the [`New-AzServiceBusNamespace`](/powershell/module/az.servicebus/new-azservicebusnamespace) command with `-MinimumTlsVersion` set to `1.3`.