Private Link
48
Total Pages
20
Linux-Friendly Pages
28
Pages with Bias
58.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
188 issues found
Showing 176-188 of 188 flagged pages
Private Link
Quickstart - Create a network security perimeter - Azure CLI
.../private-link/create-network-security-perimeter-cli.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation uses Azure CLI commands throughout, which are cross-platform, but the shell scripting examples (e.g., variable assignment with $(date +%s)) implicitly assume a Bash-like environment typical of Linux/macOS. There is no explicit mention of Windows-specific tools (like PowerShell), nor are PowerShell examples provided. However, the documentation does not clarify shell compatibility or provide Windows/PowerShell equivalents for variable assignment and command chaining, which may confuse Windows users.
Recommendations
- Explicitly state which shell environments (Bash, PowerShell, CMD) the examples are compatible with.
- Provide PowerShell equivalents for variable assignment and command substitution (e.g., $key_vault_name).
- Add notes or tabs for both Bash (Linux/macOS) and PowerShell (Windows) users, showing how to run the commands in each environment.
- Ensure that all example commands work as written on both Linux/macOS and Windows, or provide alternatives where necessary.
Create Pull Request
Private Link
Export DNS records for a private endpoint - Azure portal
...n/articles/private-link/private-endpoint-export-dns.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation describes exporting DNS records via the Azure portal and downloading a 'host file' but does not provide any platform-specific instructions or examples. However, it implicitly assumes users will know how to use the downloaded host file, which is a format most commonly associated with Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention how to use or apply the file on Linux systems (e.g., /etc/hosts). There are no PowerShell or Windows tool references, but the lack of Linux-specific guidance constitutes a bias.
Recommendations
- Add instructions or examples for how to use the downloaded host file on Linux systems, such as appending entries to /etc/hosts.
- Clarify that the host file format is compatible with both Windows and Linux, and provide steps for both platforms.
- Include a note about required permissions for editing hosts files on Linux (e.g., using sudo).
- If relevant, mention how to automate the process using shell commands for Linux users.
Private Link
Troubleshoot Azure Private Endpoint connectivity problems
...ate-link/troubleshoot-private-endpoint-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides troubleshooting steps for Azure Private Endpoint connectivity but does not include any OS-specific command-line examples or tooling. However, it implicitly assumes use of the Azure Portal and Azure tools without mentioning platform-specific methods (e.g., PowerShell, Windows tools, or Linux CLI). There are no explicit Windows or PowerShell examples, but there is also a lack of parity for Linux users, as no CLI or shell commands are provided for validation or troubleshooting.
Recommendations
- Add Azure CLI examples for key troubleshooting steps, such as checking private endpoint configuration, DNS resolution, and effective routes, to support Linux and cross-platform users.
- Include sample commands for DNS resolution (e.g., nslookup, dig) and network connectivity (e.g., curl, telnet) that work on both Windows and Linux.
- Where GUI steps are described, provide equivalent CLI instructions for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
- Explicitly mention that troubleshooting can be performed from any supported OS and provide links to cross-platform tools.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/troubleshoot-private-endpoint-connectivity.md
...ate-link/troubleshoot-private-endpoint-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting commands or examples. However, it omits practical examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash, curl, dig, nslookup). The absence of Linux-specific tools or instructions means Linux users may not have clear guidance for validating connectivity, DNS, or routing from their environment.
Recommendations
- Add example commands for both Windows (PowerShell, Command Prompt) and Linux (Bash, curl, dig, nslookup) to validate connectivity, DNS resolution, and routing.
- Explicitly mention how to perform troubleshooting steps from Linux VMs, such as checking effective routes, testing DNS, and connectivity.
- Ensure parity by listing both Windows and Linux methods side-by-side when referencing VM-level diagnostics.
- Reference Azure CLI commands, which are cross-platform, for relevant troubleshooting steps.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-link-service-overview.md
...articles/private-link/private-link-service-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page does not provide explicit command-line examples or tooling references within the main content, but in the 'Next steps' section, it lists 'Create a private link service using Azure PowerShell' before 'Create a private link service using Azure CLI'. This ordering subtly prioritizes Windows/Powershell workflows over cross-platform CLI usage, which may be perceived as Windows-first bias.
Recommendations
- List Azure CLI instructions before Azure PowerShell in the 'Next steps' section, as CLI is cross-platform and more inclusive for Linux/macOS users.
- Explicitly mention that both Azure PowerShell and Azure CLI are supported and provide parity for all major platforms.
- Where possible, provide direct links to Linux/macOS-specific instructions or troubleshooting guides to ensure equal visibility.
- Review future documentation updates to ensure that examples and tool references do not default to Windows-centric tools or ordering.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-network-security-perimeter-cli.md
.../private-link/create-network-security-perimeter-cli.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation uses Azure CLI throughout, which is cross-platform, but all shell scripting examples use Bash syntax (e.g., $(date +%s), variable assignment with key_vault_name="...") without any mention of Windows-specific alternatives (such as PowerShell syntax). There is no explicit Windows bias in terms of prioritizing Windows tools or examples, but there is a lack of parity for Windows users, as PowerShell examples are not provided for commands involving shell scripting or variable assignment.
Recommendations
- Add equivalent PowerShell examples for all CLI commands that use Bash scripting, such as variable assignment and dynamic naming (e.g., using $key_vault_name = "key-vault-$(Get-Date -UFormat %s)").
- Include a note or section indicating how to run these commands in PowerShell on Windows, especially for commands that use Bash-specific syntax.
- Ensure that all CLI examples are presented in both Bash and PowerShell formats, or clarify that the examples are for Bash and provide links to PowerShell equivalents.
- Explicitly state that Azure CLI works on both Windows and Linux, and provide guidance for users on each platform.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/troubleshoot-private-endpoint-connectivity.md
...ate-link/troubleshoot-private-endpoint-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides troubleshooting steps for Azure Private Endpoint connectivity but does not include any OS-specific examples or commands. However, it implicitly assumes use of the Azure Portal and Azure tools without mentioning or providing parity for Linux-specific troubleshooting methods (such as CLI commands, shell scripts, or Linux networking tools). There are no PowerShell or Windows tool references, but the absence of Linux examples or explicit cross-platform guidance constitutes a subtle bias.
Recommendations
- Include CLI-based troubleshooting steps using Azure CLI, which is cross-platform and commonly used on Linux.
- Provide examples of using Linux networking tools (e.g., curl, dig, nslookup, traceroute) to validate connectivity and DNS resolution.
- Explicitly mention that the troubleshooting steps apply to both Windows and Linux VMs, and highlight any OS-specific considerations.
- Add sample commands for checking effective routes and network configuration from a Linux VM.
- Ensure that references to Azure Portal actions are complemented by equivalent CLI or REST API instructions.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-link-service-overview.md
...articles/private-link/private-link-service-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists 'Create a private link service using Azure PowerShell' before 'Create a private link service using Azure CLI' in the 'Next steps' section. Azure PowerShell is primarily associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux. No explicit Windows-only tools, commands, or examples are present in the main content, and there are no missing Linux examples. However, the ordering in 'Next steps' subtly prioritizes the Windows-centric tool.
Recommendations
- List Azure CLI instructions before Azure PowerShell in the 'Next steps' section, as CLI is cross-platform and more widely used in Linux environments.
- Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, if applicable.
- Where possible, provide example commands for both Azure CLI and PowerShell within the main documentation body, or link to both equally.
- Review other related documentation to ensure Linux parity in examples and tool recommendations.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/troubleshoot-private-endpoint-connectivity.md
...ate-link/troubleshoot-private-endpoint-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting commands or examples, but it also does not mention or demonstrate any Windows- or Linux-specific tools, commands, or patterns. However, it implicitly assumes use of the Azure Portal and Azure-provided tools without addressing command-line troubleshooting (e.g., PowerShell, CMD, Bash, or Linux tools like dig, nslookup, traceroute, etc.), resulting in a lack of parity for Linux users who may prefer or require CLI-based diagnostics.
Recommendations
- Add explicit troubleshooting steps using both Windows and Linux command-line tools (e.g., show how to use PowerShell, CMD, and Bash to test connectivity, DNS resolution, and routing).
- Include examples of using common Linux tools such as dig, nslookup, curl, traceroute, and ip route to diagnose private endpoint connectivity.
- Where Azure Portal steps are described, provide equivalent Azure CLI or Azure PowerShell commands, and clarify which commands work on both Windows and Linux.
- Add a section or callout noting that all steps can be performed from either Windows or Linux VMs, and provide links to relevant OS-specific documentation where appropriate.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/how-to-approve-private-link-cross-subscription.md
...link/how-to-approve-private-link-cross-subscription.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. While this avoids explicit Windows or PowerShell bias, it also omits Azure CLI or scripting examples, which are commonly used on Linux and cross-platform environments. There is an implicit bias in not providing parity for users who prefer or require command-line automation, especially on Linux.
Recommendations
- Add Azure CLI examples for each step (e.g., registering resource providers, creating resource groups, obtaining resource IDs, creating private endpoints, approving connections).
- Ensure that CLI examples are cross-platform and do not rely on PowerShell-specific syntax.
- Clearly indicate that all steps can be performed via the Azure CLI on Windows, Linux, or macOS.
- Consider including Bash script snippets for automation scenarios.
- If PowerShell examples are added, always provide equivalent Azure CLI examples.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-link-service-overview.md
...articles/private-link/private-link-service-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists 'Create a private link service using Azure PowerShell' before 'Create a private link service using Azure CLI' in the 'Next steps' section. Azure PowerShell is primarily associated with Windows environments, while Azure CLI is cross-platform and widely used on Linux. No command-line examples are present in the main content, and no explicit Windows-only tools or patterns are described. However, the ordering in 'Next steps' subtly prioritizes the Windows-centric tool.
Recommendations
- List Azure CLI before Azure PowerShell in the 'Next steps' section to reflect cross-platform parity and the prevalence of CLI usage on Linux.
- Consider adding explicit Linux-focused or cross-platform examples in the main documentation body, if procedural steps or code snippets are included in the future.
- Wherever possible, clarify that both Azure CLI and PowerShell are supported on all platforms, and link to platform-agnostic instructions.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/how-to-approve-private-link-cross-subscription.md
...link/how-to-approve-private-link-cross-subscription.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). While this avoids explicit Windows bias (e.g., PowerShell-only examples or Windows tools), it implicitly disadvantages Linux users who often prefer or require CLI-based workflows. There is no mention of Azure CLI or Bash, which are cross-platform and commonly used on Linux.
Recommendations
- Add Azure CLI examples for each major step (e.g., resource provider registration, resource group creation, storage account creation, private endpoint creation, approval of connections).
- Ensure that all CLI examples are cross-platform (work on Windows, macOS, and Linux).
- If PowerShell examples are added, always provide Azure CLI equivalents and present them either together or with CLI first.
- Explicitly mention that the Azure CLI can be used as an alternative to the portal, and link to relevant Azure CLI documentation.
- Consider including Bash script snippets for automation scenarios.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/troubleshoot-private-endpoint-connectivity.md
...ate-link/troubleshoot-private-endpoint-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting commands or examples, but it implicitly assumes use of the Azure Portal and Azure tools without mentioning or demonstrating parity for Linux-based workflows (e.g., CLI commands, Linux troubleshooting steps). There are no PowerShell or Windows-specific tools referenced, but there is also a lack of Linux-specific guidance or examples.
Recommendations
- Add explicit examples for both Windows and Linux environments when suggesting troubleshooting steps (e.g., show how to use Azure CLI or Linux networking tools like dig, nslookup, curl, or traceroute for connectivity and DNS checks).
- Include command-line alternatives to portal-based steps, especially for common Linux administration scenarios.
- Mention or link to documentation for using Azure CLI and Bash for troubleshooting, in addition to the Azure Portal.
- If referencing VM-based troubleshooting, clarify that instructions apply to both Windows and Linux VMs, and provide OS-specific command examples where relevant.