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 126-150 of 188 flagged pages
Private Link Tutorial: Connect to an Azure SQL server using an Azure Private Endpoint - Azure CLI ...cles/private-link/tutorial-private-endpoint-sql-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The tutorial demonstrates a notable Windows bias in its VM creation and connectivity testing steps. It creates a Windows Server VM (Win2019Datacenter) and instructs users to use Windows PowerShell and SQL Server Management Studio (SSMS), both Windows-specific tools, for connectivity verification. No Linux VM option, Linux shell commands, or cross-platform SQL client alternatives are provided. This may hinder Linux/macOS users from following the tutorial seamlessly.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) and connecting via SSH.
  • Include Linux/macOS shell commands (e.g., nslookup, dig) for DNS verification.
  • Suggest cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) for database connectivity testing.
  • Explicitly mention that the VM image can be changed to a Linux distribution and provide example commands.
  • Clarify any platform-specific differences in Bastion usage or connectivity steps.
GitHub Create Pull Request
Private Link Tutorial: Connect to a storage account using an Azure Private Endpoint ...ivate-link/tutorial-private-endpoint-storage-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial demonstrates a notable Windows bias, especially in the connectivity testing section. It instructs users to open Windows PowerShell and provides only a PowerShell example for DNS resolution. The installation instructions for Microsoft Azure Storage Explorer reference Windows, and there are no equivalent Linux/macOS command-line examples (e.g., using bash, nslookup, or dig) or guidance for installing Storage Explorer on non-Windows platforms. The tutorial implicitly assumes the VM is running Windows, with no mention of Linux VM workflows.
Recommendations
  • Provide parallel instructions for Linux/macOS users, including command-line examples using bash and tools like nslookup or dig.
  • Clarify that Storage Explorer is available for Linux/macOS and provide installation links and steps for those platforms.
  • When instructing users to connect to the VM, specify how to do so for both Windows and Linux VMs (e.g., using SSH for Linux).
  • Offer example outputs for Linux/macOS commands where PowerShell output is currently shown.
  • Avoid assuming the OS of the VM; explicitly state when instructions differ by platform.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - ARM template ...icles/private-link/create-private-endpoint-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All connection and validation instructions for the VM use RDP (Remote Desktop Protocol), which is a Windows-centric tool, and PowerShell is used for command-line examples. There are no instructions for connecting to the VM from Linux/macOS (e.g., via SSH), nor are there examples using Linux-native tools or command-line interfaces. The cleanup step uses a PowerShell cmdlet without providing an Azure CLI equivalent, further reinforcing the Windows preference.
Recommendations
  • Add instructions for connecting to the VM using SSH, which is standard for Linux/macOS users.
  • Provide Azure CLI commands alongside PowerShell for resource cleanup and other operations.
  • Include examples of using Linux-native tools (e.g., terminal, sqlcmd) to validate connectivity to the SQL Database.
  • Explicitly mention cross-platform alternatives and ensure steps are not Windows-exclusive.
GitHub Create Pull Request
Private Link Quickstart - Create a network security perimeter - ARM Template ...ate-link/create-network-security-perimeter-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a Windows PowerShell example for resource cleanup and references Azure PowerShell as a primary automation method. There are no equivalent Azure CLI or Bash examples for Linux/macOS users, nor are Linux-specific tools or patterns mentioned. This creates friction for non-Windows users, especially for command-line operations.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all command-line instructions, especially for resource cleanup.
  • Explicitly mention that Azure CLI is cross-platform and provide links or guidance for Linux/macOS users.
  • Where PowerShell is referenced, also reference CLI alternatives and provide parity in step-by-step instructions.
  • Consider listing CLI examples before or alongside PowerShell to avoid implicit Windows-first bias.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Bicep ...articles/private-link/create-private-endpoint-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It provides deployment instructions for both Azure CLI and PowerShell, but when it comes to connecting to the VM and accessing the SQL Database, it exclusively describes Windows-centric workflows: connecting via RDP, using PowerShell, and installing SQL Server Management Studio (SSMS). There are no instructions for Linux/macOS users (e.g., SSH access, using sqlcmd or Azure Data Studio), nor are alternative connection methods mentioned. Windows tools and patterns are presented exclusively and first, creating friction for non-Windows users.
Recommendations
  • Add instructions for connecting to the VM via SSH for Linux/macOS users.
  • Include examples of using sqlcmd or Azure Data Studio to connect to SQL Database from Linux/macOS.
  • Provide guidance on running equivalent DNS resolution commands (e.g., 'dig' or 'nslookup' in Linux/macOS terminals).
  • Present connection options for both RDP (Windows) and SSH (Linux/macOS) side-by-side.
  • Explicitly mention cross-platform alternatives to SSMS for database access.
GitHub Create Pull Request
Private Link Configure Private Link service Direct Connect ...-link/configure-private-link-service-direct-connect.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents Windows-oriented tools (PowerShell) first in code tabs and instructions, with PowerShell examples preceding Azure CLI and Terraform. There is a strong emphasis on PowerShell in prerequisites and usage, and no explicit Linux/macOS shell examples (e.g., bash scripts or Linux-specific notes) are provided. While Azure CLI and Terraform are cross-platform, the lack of Linux/macOS-specific guidance and the ordering of examples may create friction for non-Windows users.
Recommendations
  • Present Azure CLI examples first, as CLI is natively cross-platform and preferred by many Linux/macOS users.
  • Add explicit bash shell examples or notes for Linux/macOS users, especially in sections where environment setup or command syntax may differ.
  • Clarify that Azure PowerShell is available in Azure Cloud Shell (browser-based, cross-platform) and not limited to Windows.
  • In prerequisites, mention Linux/macOS installation steps for Azure CLI and Terraform, and link to platform-specific guides.
  • Ensure that all instructions and troubleshooting steps are equally clear for Linux/macOS users, not just Windows/PowerShell users.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Azure CLI ...n/articles/private-link/create-private-endpoint-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the virtual machine creation and connectivity testing sections. The VM is created using a Windows image (Win2022Datacenter) without mention of Linux alternatives, and connectivity testing is described using PowerShell and Windows GUI steps. There are no Linux/macOS-specific instructions or examples for VM creation, shell usage, or DNS testing.
Recommendations
  • Include Linux VM creation examples (e.g., using Ubuntu or CentOS images) alongside the Windows example.
  • Provide Linux/macOS command-line alternatives for connectivity testing, such as using 'dig' or 'nslookup' in bash.
  • Clarify that Azure Bastion and the Azure CLI are cross-platform, and provide steps for connecting to Linux VMs via SSH.
  • Present both Windows and Linux/macOS instructions in parallel or in tabs, rather than only Windows-focused steps.
  • Avoid assuming the use of PowerShell or Windows GUI; mention terminal/shell access for Linux/macOS users.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Azure portal ...rticles/private-link/create-private-endpoint-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing PowerShell for command-line operations and omitting Linux/macOS equivalents. The connectivity test assumes the use of PowerShell, without mentioning alternatives like Bash or Linux terminal commands. No Linux/macOS-specific instructions or screenshots are provided, and the example workflow implicitly assumes a Windows VM for testing, even though Azure VMs can run Linux.
Recommendations
  • Include equivalent Linux/macOS command-line instructions (e.g., using Bash and the 'dig' or 'nslookup' commands).
  • Clarify that the test VM can be either Windows or Linux, and provide steps for both.
  • Provide screenshots or terminal output examples from Linux/macOS environments.
  • Avoid referencing PowerShell exclusively; use cross-platform commands where possible or offer alternatives.
GitHub Create Pull Request
Private Link Quickstart: Create a private link service - ARM template ...s/private-link/create-private-link-service-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. VM connection instructions exclusively use Remote Desktop Protocol (RDP), a Windows-centric tool, with no mention of SSH or Linux/macOS alternatives. The cleanup step provides only a PowerShell example (Remove-AzResourceGroup), omitting Azure CLI or Bash equivalents. Throughout, Windows tools and patterns are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add instructions for connecting to the VM using SSH, including steps for Linux/macOS users.
  • Provide Azure CLI and Bash examples for resource group deletion alongside the PowerShell example.
  • Mention cross-platform tools (e.g., Azure CLI, SSH) wherever possible, not just Windows-specific ones.
  • Clarify whether the deployed VM is Windows or Linux, and tailor connection instructions accordingly.
  • Where RDP is referenced, include a note about alternatives for non-Windows users (e.g., using an RDP client on Linux/macOS, or SSH if the VM is Linux).
GitHub Create Pull Request
Private Link Increase Private Endpoint virtual network limits .../private-link/increase-private-endpoint-vnet-limits.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided and referenced first, with CLI examples present but not as detailed. There are no explicit Linux/macOS shell examples (e.g., Bash), and the validation section only provides PowerShell and Portal instructions, omitting Linux-native approaches. The use of PowerShell as a primary scripting tool and its placement before CLI alternatives may create friction for Linux/macOS users.
Recommendations
  • Include Bash or shell script examples for Linux/macOS users alongside PowerShell and CLI.
  • Present CLI (az) examples before or alongside PowerShell to avoid Windows-first ordering.
  • Add validation steps using az CLI or Bash commands for Linux/macOS parity.
  • Explicitly mention platform compatibility for each example and tool.
  • Ensure all critical tasks (enable, validate) have CLI and Bash equivalents.
GitHub Create Pull Request
Private Link Manage network policies for private endpoints ...rivate-link/disable-private-endpoint-network-policy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples and references to PowerShell cmdlets, which are Windows-specific tools. PowerShell is presented as a primary automation method alongside the Azure portal, with no mention of Bash, Linux shell scripting, or cross-platform alternatives for scripting. The CLI examples are present, but PowerShell is given equal or greater prominence, and there is no explicit guidance for Linux/macOS users regarding scripting or tool installation. The documentation does not address platform-specific nuances or recommend cross-platform approaches.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for automation tasks.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS, and provide installation links.
  • Clarify that PowerShell examples are Windows-centric and suggest alternatives for non-Windows environments.
  • Consider listing CLI examples before PowerShell, or grouping them together with notes on platform compatibility.
  • Provide troubleshooting or usage notes for Linux/macOS users where PowerShell cmdlets are referenced.
GitHub Create Pull Request
Private Link Azure Private Endpoint DNS Integration Scenarios ...icles/private-link/private-endpoint-dns-integration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Windows-centric DNS concepts and tools (such as DNS forwarders and conditional forwarders) and links to Windows Server documentation for DNS forwarding. It uses terminology and patterns familiar to Windows administrators, and does not provide explicit Linux/macOS DNS server examples or guidance. The examples and instructions assume familiarity with Windows-based DNS solutions, with no mention of Linux alternatives like BIND, dnsmasq, or Unbound.
Recommendations
  • Add explicit examples and configuration guidance for popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound) in DNS forwarder and conditional forwarding scenarios.
  • Include links to Linux DNS documentation and resources alongside Windows Server references.
  • Clarify that DNS forwarders can be implemented on both Windows and Linux platforms, and provide parity in instructions.
  • Where possible, provide cross-platform CLI examples (e.g., Azure CLI, PowerShell, and Linux shell commands) for DNS zone management.
  • Avoid assuming the reader is using Windows-based DNS solutions; use neutral terminology and provide platform-agnostic steps.
GitHub Create Pull Request
Private Link Disable SNAT requirement for Azure private endpoint traffic through NVA ...ain/articles/private-link/private-link-disable-snat.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by referencing Windows virtual machines as the primary example for deploying an NVA and linking only to the Windows VM quickstart. The order of examples and references to PowerShell also reinforce a Windows-centric approach, although Azure CLI and Portal instructions (which are cross-platform) are included. There is no mention of Linux-specific VM deployment or Linux tools, and the initial VM deployment guidance is Windows-only.
Recommendations
  • Include a link to the Linux VM quickstart alongside the Windows VM quickstart in the prerequisites.
  • Explicitly mention that the instructions apply to both Windows and Linux NVAs.
  • Add a note clarifying that Azure CLI and Portal instructions are suitable for Linux/macOS users.
  • Consider providing a Linux VM deployment example or referencing Linux-specific documentation for parity.
GitHub Create Pull Request
Private Link Tutorial: Create a private endpoint DNS infrastructure with Azure Private Resolver for an on-premises workload ...vate-link/tutorial-dns-on-premises-private-resolver.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial demonstrates a notable Windows bias in the testing and verification steps. The only example for DNS resolution uses Windows PowerShell, and the instructions explicitly direct users to open Windows PowerShell and Microsoft Edge. There are no equivalent Linux/macOS command-line examples (e.g., using 'dig' or 'nslookup' in a Linux shell), nor is there mention of connecting to the test VM with SSH or using non-Windows browsers. This may create friction for users who deploy Linux-based workloads or use non-Windows environments.
Recommendations
  • Add Linux/macOS command-line examples for DNS resolution (e.g., using 'dig' or 'nslookup' in bash).
  • Clarify that the test VM can be Windows or Linux, and provide instructions for connecting via SSH as well as Bastion.
  • Mention that browsers other than Microsoft Edge can be used for web app testing.
  • Where PowerShell is referenced, also provide bash/zsh equivalents.
  • Explicitly state that the steps apply to both Windows and Linux VMs, and highlight any OS-specific differences.
GitHub Create Pull Request
Private Link Tutorial: Connect to an Azure SQL server using an Azure Private Endpoint - Azure CLI ...cles/private-link/tutorial-private-endpoint-sql-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The tutorial demonstrates a notable Windows bias: the VM is created with a Windows image (Win2019Datacenter) only, and all connectivity and testing instructions use Windows PowerShell and SQL Server Management Studio (SSMS), both Windows-specific tools. No Linux VM creation example, nor instructions for Linux/macOS users (e.g., using sqlcmd, Azure Data Studio, or Bash) are provided. This creates friction for non-Windows users and may prevent them from completing the tutorial as written.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) and provide equivalent connectivity testing steps using Bash (e.g., nslookup or dig).
  • Include examples for connecting to Azure SQL from Linux/macOS using cross-platform tools like sqlcmd (available via the mssql-tools package) or Azure Data Studio.
  • Explicitly mention that the VM image can be changed to a Linux distribution and provide the necessary CLI flags.
  • List both Windows and Linux/macOS options for testing DNS and SQL connectivity, with step-by-step instructions.
  • Clarify that SQL Server Management Studio is Windows-only and suggest alternatives for other platforms.
GitHub Create Pull Request
Private Link Tutorial: Connect to a storage account using an Azure Private Endpoint ...ivate-link/tutorial-private-endpoint-storage-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial demonstrates a notable Windows bias, especially in the connectivity testing section. It instructs users to open Windows PowerShell and provides only a PowerShell example for DNS resolution. There are no Linux/macOS equivalents (e.g., Bash, Terminal, or 'nslookup' on Linux), and the installation instructions for Azure Storage Explorer reference only Windows. The workflow assumes a Windows VM and does not mention Linux or macOS alternatives, making it less accessible to non-Windows users.
Recommendations
  • Provide Linux/macOS command-line examples (e.g., Bash/Terminal commands for DNS resolution such as 'nslookup' or 'dig').
  • Clarify that Azure Storage Explorer is available for Linux/macOS and provide installation instructions or links for those platforms.
  • Explicitly mention that the virtual machine can be Linux-based and include steps for connecting via SSH and running equivalent commands.
  • Avoid assuming the use of Windows PowerShell; use cross-platform terminology like 'open a terminal' and provide parallel instructions for different OSes.
GitHub Create Pull Request
Private Link What is Azure Private Link service? ...articles/private-link/private-link-service-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias primarily by listing Azure PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section. There are no direct Linux-specific examples, nor are Linux-native tools or workflows mentioned. The documentation does not provide parity in example ordering or tool recommendations for Linux users.
Recommendations
  • List Azure CLI instructions before or alongside Azure PowerShell in 'Next steps', as CLI is cross-platform and preferred by many Linux users.
  • Explicitly mention that Azure CLI is available on Linux and macOS, and provide links or notes for installation on those platforms.
  • Add example workflows or references for Linux environments, such as using Bash scripts or Linux-native automation tools.
  • Avoid defaulting to Windows-centric tools (PowerShell) when cross-platform alternatives (CLI) exist.
  • Consider including a section or callout for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Private Link Quickstart - Create a network security perimeter - Bicep ...rivate-link/create-network-security-perimeter-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and cleaning up resources, but PowerShell is presented as a primary option alongside CLI, and is mentioned in the introductory list before Azure CLI. There are no Linux-specific instructions, nor is there mention of Linux shell environments (e.g., Bash). The use of PowerShell may imply a Windows-centric approach, especially for users unfamiliar with cross-platform PowerShell.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is available cross-platform but may require installation on Linux/macOS.
  • Add a note or section clarifying how to run Azure CLI commands in Bash or other Linux shells, including any environment setup steps.
  • Consider listing Azure CLI before PowerShell in introductory lists to reflect its cross-platform nature.
  • Include links to installation guides for Azure CLI and PowerShell on Linux/macOS.
  • If possible, provide a Bash script example for deployment and cleanup to further demonstrate Linux parity.
GitHub Create Pull Request
Private Link Azure Private Endpoint private DNS zone values ...lob/main/articles/private-link/private-endpoint-dns.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias. It frequently references Windows-centric DNS zone names (e.g., *.windows.net), and the terminology and examples are heavily oriented toward Microsoft/Azure conventions, which are rooted in Windows environments. The only explicit tooling command given is 'az account list-locations -o table', which is cross-platform, but there are no Linux-specific examples, nor are Linux tools or patterns mentioned. The 'host file' override is described generically, but does not provide platform-specific instructions or examples for Linux. The documentation does not provide parity for Linux administrators in terms of examples, troubleshooting, or DNS configuration steps.
Recommendations
  • Add explicit Linux examples for DNS configuration, such as how to edit /etc/hosts or configure BIND/unbound for private DNS zones.
  • Include troubleshooting steps or references for common Linux DNS tools (e.g., dig, nslookup, systemd-resolved) alongside Windows equivalents.
  • Clarify that the DNS concepts and procedures apply equally to Linux and Windows, and provide platform-specific instructions where relevant.
  • Mention Linux-specific considerations for Azure File Shares (e.g., remounting via CIFS/NFS on Linux) when private endpoints are used.
  • Where host file overrides are mentioned, provide both Windows (C:\Windows\System32\drivers\etc\hosts) and Linux (/etc/hosts) file paths and editing instructions.
GitHub Create Pull Request
Private Link Disable SNAT requirement for Azure private endpoint traffic through NVA ...ain/articles/private-link/private-link-disable-snat.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in its prerequisites and examples. The prerequisites section links only to the Windows VM creation guide, omitting any reference to Linux VM deployment. Although the step-by-step instructions for tagging resources use Azure Portal, PowerShell, and Azure CLI (which are cross-platform), the initial VM deployment guidance is Windows-centric, and PowerShell is a Windows-native tool. There are no Linux-specific examples or references.
Recommendations
  • Add a link to the Linux VM creation guide in the prerequisites section alongside the Windows VM link.
  • Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide Bash shell examples where relevant.
  • Include a note or example for users deploying Linux-based NVAs, clarifying that the tagging process is identical regardless of OS.
  • Ensure parity in documentation by referencing both Windows and Linux tools and workflows when discussing VM deployment and management.
GitHub Create Pull Request
Private Link Disable SNAT requirement for Azure private endpoint traffic through NVA ...ain/articles/private-link/private-link-disable-snat.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows virtual machines as the default example for deploying a network virtual appliance (NVA) and linking specifically to the 'Quickstart: Create a Windows virtual machine' guide. There is no mention of Linux-based NVAs or guidance for deploying Linux VMs, nor are Linux-specific tools or patterns discussed. While the configuration steps use Azure CLI and PowerShell (both cross-platform), the initial context and examples prioritize Windows environments.
Recommendations
  • Include references and links to both Windows and Linux VM deployment guides in the prerequisites section.
  • Clarify that NVAs can be based on either Windows or Linux, and provide examples for both.
  • If relevant, mention Linux-specific considerations or tools (such as Bash scripting or cloud-init) for tagging resources.
  • Ensure parity in examples and guidance for both operating systems throughout the documentation.
GitHub Create Pull Request
Private Link Quickstart - Create a network security perimeter - Azure CLI .../private-link/create-network-security-perimeter-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation uses Azure CLI throughout, which is cross-platform, but there are subtle signs of Windows bias. The variable assignment for the key vault name uses $(date +%s), which is a Bash/Linux pattern, but there is no explicit mention of how to run these commands on Windows (e.g., in Command Prompt or PowerShell). The deletion example uses the code block type 'azurepowershell-interactive', which may suggest PowerShell, but the command shown is Azure CLI. There are no PowerShell or Windows Command Prompt examples, but also no explicit Linux or macOS instructions. The documentation does not mention platform-specific considerations, nor does it clarify how to adapt CLI commands for Windows environments.
Recommendations
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and note any differences in shell syntax (e.g., variable assignment).
  • Provide examples or notes for running Azure CLI commands in Windows Command Prompt or PowerShell, especially for variable assignment and command chaining.
  • Correct the code block type for CLI commands (avoid using 'azurepowershell-interactive' for Azure CLI commands).
  • Add a section on platform-specific tips for Azure CLI usage, such as using 'set' for variable assignment in Windows CMD or '$env:' in PowerShell.
  • Ensure parity by including both Bash and PowerShell variable assignment examples where relevant.
GitHub Create Pull Request
Private Link Quickstart - Create a network security perimeter - Bicep ...rivate-link/create-network-security-perimeter-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and cleanup, but PowerShell is presented as a primary option alongside CLI, and is not explicitly marked as Windows-specific. There is no mention of Linux shell or Bash alternatives, nor any guidance for Linux users regarding environment setup or command differences. The order of examples sometimes places PowerShell before or alongside CLI, which may imply parity but can be confusing for non-Windows users.
Recommendations
  • Clearly label Azure PowerShell examples as Windows-specific, and recommend CLI for cross-platform usage.
  • Add explicit Bash/Linux shell examples where appropriate, especially for steps involving local file handling or scripting.
  • In the prerequisites, mention that Azure CLI is available on Windows, Linux, and macOS, and link to installation instructions for each platform.
  • When listing deployment options, present Azure CLI first as the default cross-platform method, and PowerShell as an alternative for Windows users.
  • Include troubleshooting notes for common Linux issues (e.g., file permissions, path formats) when saving and deploying Bicep files.
GitHub Create Pull Request
Private Link What is Azure Private Link service? ...articles/private-link/private-link-service-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias. In the 'Next steps' section, the PowerShell (Windows-centric) example is listed before the Azure CLI (cross-platform) example, suggesting a Windows-first approach. Additionally, the only explicit example link for creating a Private Link Service is for Azure PowerShell, which is primarily used on Windows, before mentioning Azure CLI. No Linux-specific tools, shell examples, or platform parity notes are present.
Recommendations
  • List Azure CLI (cross-platform) instructions before or alongside PowerShell in 'Next steps' to avoid Windows-first impression.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide Bash or shell examples where appropriate.
  • If possible, add examples or links for using ARM templates or REST API, which are platform-agnostic.
  • Include a note that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Review other related documentation pages to ensure Linux parity in example ordering and tool recommendations.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-network-security-perimeter-bicep.md ...rivate-link/create-network-security-perimeter-bicep.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and cleaning up resources, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is mentioned before Linux or cross-platform considerations. There is no explicit mention of Linux or macOS environments, nor any guidance for users on those platforms. The documentation does not reference Linux-specific tools or shell environments, and the structure (tabbed CLI/PowerShell) may implicitly favor Windows users by listing PowerShell as a primary option.
Recommendations
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
  • Add notes or links for installing Azure CLI on Linux/macOS.
  • Consider listing Azure CLI examples before PowerShell, or clarifying that PowerShell is primarily for Windows users.
  • Include a brief section or callout for Linux/macOS users to ensure parity and inclusivity.
  • Avoid implying parity between PowerShell and CLI for all platforms; clarify platform suitability.
GitHub Create Pull Request
← Previous Page 6 of 8 Next →