Private Link

96
Total Pages
73
Linux-Friendly Pages
23
Pages with Bias
24.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

44 issues found
Showing 1-25 of 44 flagged pages
Private Link Quickstart: Create a private endpoint - Bicep ...articles/private-link/create-private-endpoint-bicep.md
High Priority View Details →
Scanned: 2026-01-12 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 demonstrates a notable Windows bias. Connection instructions to the VM are exclusively via RDP (a Windows protocol), and subsequent steps require opening PowerShell and installing SQL Server Management Studio (a Windows-only tool). There are no Linux/macOS alternatives for connecting to the VM (e.g., SSH) or for accessing the SQL Database (e.g., Azure Data Studio, sqlcmd, or other cross-platform tools). Example commands for deployment are provided for both Azure CLI and PowerShell, but all post-deployment validation and usage instructions assume a Windows environment.
Recommendations
  • Add instructions for connecting to the VM using SSH for Linux/macOS users.
  • Provide examples for validating DNS resolution and SQL connectivity using cross-platform tools such as Azure Data Studio, sqlcmd, or psql.
  • Mention alternatives to SQL Server Management Studio for non-Windows platforms.
  • Ensure that all steps can be completed on Linux/macOS, or clearly indicate any platform-specific requirements.
GitHub Create Pull Request
Private Link Quickstart: Create a private link service - Bicep ...cles/private-link/create-private-link-service-bicep.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, especially in the VM connection and service validation sections. It exclusively describes connecting to the VM via Remote Desktop Protocol (RDP), a Windows-centric tool, and references IIS (Internet Information Services), which is a Windows web server. There are no instructions or examples for connecting via SSH (typical for Linux/macOS) or for validating the service using Linux tools or browsers. The deployment and resource management sections do provide both Azure CLI and PowerShell examples, but the critical VM access and service validation steps are Windows-only.
Recommendations
  • Add instructions for connecting to the VM using SSH, including example commands for Linux/macOS users.
  • Provide guidance for validating the HTTP service from a Linux VM (e.g., using curl, wget, or a browser).
  • Clarify whether the VM is Windows or Linux, and offer parallel steps for both OS types.
  • If IIS is used, mention Linux alternatives (e.g., Apache, Nginx) and how to access their default pages.
  • Ensure that all critical steps (deployment, access, validation, cleanup) have both Windows and Linux/macOS examples.
GitHub Create Pull Request
Private Link Tutorial: Connect to an Azure SQL server using an Azure Private Endpoint - PowerShell ...ivate-link/tutorial-private-endpoint-sql-powershell.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The tutorial exclusively uses Azure PowerShell for all steps, with commands and instructions tailored to Windows environments. The virtual machine created is specifically a Windows Server, and the connectivity test relies on Windows PowerShell and SQL Server Management Studio, both Windows-centric tools. There are no examples or guidance for performing these tasks on Linux or macOS, nor are cross-platform alternatives mentioned.
Recommendations
  • Provide equivalent Azure CLI commands for all steps, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Include instructions for creating a Linux VM and testing connectivity using Linux-native tools (e.g., bash, nslookup, sqlcmd).
  • Mention and demonstrate SQL client tools available on Linux/macOS, such as sqlcmd or Azure Data Studio.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
  • Reorder or parallelize examples so that Linux/macOS options are presented alongside Windows instructions, not only after or omitted.
GitHub Create Pull Request
Private Link Tutorial: Connect to an Azure SQL server using an Azure Private Endpoint - PowerShell ...ivate-link/tutorial-private-endpoint-sql-powershell.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The tutorial is heavily focused on Windows and PowerShell, with all code examples using Azure PowerShell cmdlets and instructions for connecting to the VM and SQL Server using Windows tools (PowerShell, SQL Server Management Studio). There are no CLI/bash examples, nor any mention of Linux/macOS alternatives for VM creation, connectivity testing, or SQL client usage. The VM created is explicitly a Windows Server, and the connectivity test assumes Windows PowerShell and SSMS, which are not available on Linux/macOS.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource creation steps, which work cross-platform.
  • Include instructions and examples for creating a Linux VM and connecting via SSH, in addition to the Windows VM/Bastion workflow.
  • Offer alternative SQL client options (e.g., Azure Data Studio, sqlcmd) that are available on Linux/macOS, and show how to use them to test connectivity.
  • When showing connectivity tests, include bash commands (e.g., nslookup, dig) for DNS resolution, and clarify how Linux/macOS users can perform these steps.
  • Explicitly note which steps are Windows-specific and provide parity guidance for Linux/macOS users.
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-12 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 demonstrates a notable Windows bias. All connection instructions to the VM use RDP (Windows-only), and the validation steps exclusively reference PowerShell and SQL Server Management Studio, both Windows-centric tools. There are no Linux/macOS alternatives or examples for connecting to the VM (e.g., SSH), running DNS queries (e.g., dig or nslookup on Linux), or accessing SQL Server (e.g., sqlcmd, Azure Data Studio). The resource cleanup step uses a PowerShell cmdlet without mentioning Azure CLI or other cross-platform options.
Recommendations
  • Add instructions for connecting to the VM via SSH for Linux/macOS users, especially if the VM image supports it.
  • Provide Linux/macOS equivalents for DNS queries (e.g., using 'nslookup' or 'dig' in a terminal).
  • Include cross-platform SQL client options such as Azure Data Studio or 'sqlcmd', with example commands.
  • For resource cleanup, offer Azure CLI commands (e.g., 'az group delete') alongside PowerShell.
  • Explicitly state if the VM image is Windows-only, or offer an option to deploy a Linux VM for parity.
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-12 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 PowerShell (Windows-centric) examples before Azure CLI and Terraform, and references Azure PowerShell as a primary tool in prerequisites and instructions. There are no explicit Linux/macOS shell script examples, and PowerShell is mentioned as a local installation option, which is primarily relevant for Windows users. While Azure CLI and Terraform are cross-platform, the ordering and emphasis favor Windows/PowerShell users, and there is no mention of Bash or Linux-specific nuances.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Clarify that Azure CLI and Terraform work natively on Linux/macOS, and provide Bash-specific notes or troubleshooting tips where relevant.
  • Add explicit Bash script examples for resource cleanup and verification steps, or clarify that Azure CLI commands are suitable for Bash/zsh.
  • In prerequisites, mention that PowerShell Core is available for Linux/macOS, or de-emphasize PowerShell in favor of CLI for cross-platform parity.
  • Where PowerShell is referenced, note its cross-platform availability (PowerShell Core) and link to installation for Linux/macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias toward Windows by exclusively using Windows-based VM images (Win2022Datacenter) in examples, referencing PowerShell for connectivity testing, and omitting Linux/macOS alternatives for VM creation and command-line usage. No Linux VM creation example or Linux shell commands are provided, and the connectivity test is described only with PowerShell, not with bash or other cross-platform tools.
Recommendations
  • Include parallel examples for creating a Linux VM (e.g., using --image UbuntuLTS) alongside the Windows VM example.
  • Provide instructions for connectivity testing using bash commands (e.g., nslookup, dig, curl) in addition to PowerShell.
  • Explicitly mention that the Azure CLI commands work on Linux/macOS, and clarify any OS-specific steps.
  • Order VM creation examples so that Linux and Windows are presented equally, or offer a choice.
  • Add notes or sections for Linux/macOS users, especially for steps that differ (e.g., shell variable syntax, remote access methods).
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-12 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, omitting equivalent Azure CLI or bash commands for Linux/macOS users. The use of the Remove-AzResourceGroup cmdlet is Windows/PowerShell-centric, and no Linux/macOS-specific instructions or examples are provided in the cleanup section.
Recommendations
  • Add Azure CLI and/or bash examples for resource group deletion, such as 'az group delete --name <your resource group name> --yes --no-wait'.
  • Wherever PowerShell is referenced, provide equivalent CLI commands and note cross-platform compatibility.
  • Explicitly mention that Azure CLI is available on Windows, Linux, and macOS, and link to installation instructions if needed.
  • Review other sections for implicit Windows assumptions and ensure parity in instructions and tooling.
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-12 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 Windows bias in its connectivity testing section, where only PowerShell is mentioned for command-line interaction, and no Linux/macOS alternatives (such as Bash or terminal) are provided. The instructions implicitly assume the VM is running Windows, as evidenced by the use of PowerShell and the absence of Linux-specific guidance. This may create friction for users deploying Linux VMs or accessing from non-Windows environments.
Recommendations
  • Add Linux/macOS equivalent instructions for connectivity testing, such as using Bash and the 'nslookup' command.
  • Clarify whether the VM can be Windows or Linux, and provide steps for both operating systems.
  • Include screenshots or output examples from Linux terminals alongside PowerShell.
  • Explicitly mention that the Bastion host and VM can be Linux, and provide guidance for those scenarios.
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-12 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 demonstrates a notable Windows bias. Connection instructions to the VM are exclusively via RDP (Remote Desktop Protocol), which is a Windows-centric tool, and the validation steps reference IIS (Internet Information Services), a Windows web server. The cleanup instructions use Azure PowerShell cmdlets without mentioning Azure CLI equivalents. There are no Linux/macOS connection examples (e.g., SSH), nor is there guidance for Linux users on accessing the VM or cleaning up resources.
Recommendations
  • Add SSH-based connection instructions for Linux/macOS users, including how to obtain the public IP and connect via SSH.
  • Include Azure CLI commands for resource cleanup alongside PowerShell examples.
  • Mention Linux-compatible web servers (e.g., Apache, Nginx) in the validation steps or clarify if the template supports Linux VMs.
  • Provide guidance for accessing the VM from non-Windows platforms, such as using Remote Desktop clients available for Linux/macOS or alternatives.
  • Ensure examples and instructions are presented in a cross-platform manner, or at least give Linux/macOS options equal prominence.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Windows-centric instructions for testing DNS resolution and connectivity, specifically referencing Windows PowerShell and Microsoft Edge. There are no examples or guidance for performing equivalent steps on Linux or macOS virtual machines, nor are alternative tools or commands mentioned. This creates friction for users who prefer or require non-Windows environments.
Recommendations
  • Include instructions for connecting to the test VM using SSH (for Linux/macOS VMs) in addition to Bastion/Windows.
  • Provide equivalent DNS resolution commands for Linux/macOS (e.g., using 'dig' or 'nslookup' in a Linux shell).
  • Mention alternative browsers (e.g., Firefox, Chrome) or clarify that any browser can be used.
  • Explicitly state that the test VM can be Windows or Linux, and provide example commands for both.
  • Add a note or section for troubleshooting on Linux/macOS platforms.
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-12 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-centric. PowerShell is presented as a primary automation method alongside the Azure portal, with no mention of Bash, shell scripting, or Linux-native tools. The CLI example is present, but its capabilities are noted as limited compared to PowerShell. The PowerShell tab appears before the CLI tab, and there is no explicit guidance for Linux/macOS users regarding prerequisites or alternative approaches.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users where appropriate.
  • Clarify that Azure CLI is cross-platform and provide parity in CLI functionality or document CLI limitations and possible workarounds.
  • Consider presenting CLI examples before PowerShell, or at least equally, to avoid Windows-first perception.
  • Explicitly mention platform compatibility for each method (e.g., PowerShell is Windows-centric, CLI is cross-platform).
  • Provide links or guidance for installing and using Azure CLI on Linux/macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both PowerShell and Azure CLI examples for enabling High Scale Private Endpoints, but PowerShell (typically Windows-centric) is presented first and in more detail. The validation section includes a PowerShell example but omits an equivalent Azure CLI or Bash/Linux shell example. There is no mention of Linux/macOS-specific tools or guidance, and the CLI instructions use variable syntax that is more familiar to Windows/PowerShell users than Bash/Linux users.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell, or side-by-side.
  • Add explicit Bash/Linux shell examples for validation steps (e.g., using 'az network vnet show').
  • Clarify variable usage in CLI examples to match Bash/Linux conventions (e.g., $vnetName should be $vnetName or ${vnetName} in Bash, or use export).
  • Include notes on how to perform equivalent tasks on Linux/macOS, especially for validation and scripting.
  • Ensure all steps have CLI or REST API alternatives, not just PowerShell.
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-12 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 equivalent Linux/macOS instructions (e.g., using 'nslookup' or 'dig' in a Linux shell), and the installation steps for Microsoft Azure Storage Explorer reference only Windows, omitting Linux/macOS guidance. The VM creation and connection steps implicitly assume a Windows environment.
Recommendations
  • Provide Linux/macOS equivalents for connectivity testing, such as using 'nslookup' or 'dig' in a bash shell.
  • Include instructions for installing Microsoft Azure Storage Explorer on Linux/macOS, or link to cross-platform installation guides.
  • Clarify that the VM can be Windows or Linux, and provide OS-agnostic steps where possible.
  • Present examples for both Windows and Linux/macOS, or use tabs to separate platform-specific instructions.
  • Avoid referencing Windows tools (like PowerShell) exclusively; mention alternatives for other platforms.
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-12 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 notable Windows bias, especially in the 'Test connectivity to private endpoint' section. The only example for testing DNS resolution uses Windows PowerShell, and the instructions for connecting to SQL Server exclusively reference SQL Server Management Studio (a Windows-only tool). The VM created for testing uses a Windows image (Win2019Datacenter) without mentioning Linux alternatives or providing equivalent Linux commands (e.g., using dig/nslookup in bash, or connecting via sqlcmd). This may create friction for users on Linux/macOS platforms.
Recommendations
  • Provide parallel instructions for Linux/macOS users, including examples using bash and Linux tools (e.g., nslookup, dig, sqlcmd).
  • Offer the option to create a Linux VM (e.g., Ubuntu) for testing, with corresponding CLI commands.
  • Mention cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) and provide connection instructions for them.
  • Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented together or Linux is not always secondary.
  • Clarify that the tutorial is cross-platform and highlight any platform-specific steps.
GitHub Create Pull Request
Private Link Quickstart: Create a private link service - Bicep ...cles/private-link/create-private-link-service-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a notable Windows bias, especially in the VM connection and service validation sections. Only Windows Remote Desktop (RDP) is described for connecting to the VM, with no mention of SSH or Linux/macOS access methods. The example VM runs IIS (a Windows-only web server), and the workflow assumes users are on Windows, omitting Linux/macOS alternatives for remote access and web server setup.
Recommendations
  • Add instructions for connecting to the VM using SSH, suitable for Linux/macOS users.
  • Include examples of deploying a Linux VM and installing a web server such as Apache or Nginx.
  • Provide parity in connection steps (e.g., using Azure CLI or SSH for Linux/macOS) alongside RDP for Windows.
  • Clarify that IIS is Windows-specific and offer Linux web server alternatives.
  • Present CLI and PowerShell examples in parallel, not with PowerShell as a secondary tab.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing PowerShell for command-line operations and omitting equivalent Linux/macOS shell instructions. The VM connectivity test assumes a Windows environment, with no mention of Linux tools or workflows (e.g., Bash, curl, dig). Windows tools and patterns are presented first and solely, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS command-line examples alongside PowerShell, such as using Bash and tools like 'dig' or 'nslookup' in Linux.
  • Clarify that the VM can be either Windows or Linux, and offer instructions for both environments when testing connectivity.
  • Include screenshots or terminal output from Linux/macOS where appropriate.
  • Explicitly mention cross-platform compatibility in prerequisites and testing steps.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias toward Windows environments by providing only a PowerShell example for resource cleanup, omitting equivalent instructions for Azure CLI or Bash. The use of the Remove-AzResourceGroup cmdlet is specific to PowerShell, which is predominantly used on Windows. There are no Linux/macOS-specific examples or guidance, and the documentation does not mention alternative tools or commands for non-Windows users.
Recommendations
  • Add Azure CLI and Bash examples for resource cleanup (e.g., az group delete --name <your resource group name>).
  • Clearly state that PowerShell is one option and provide parity for Linux/macOS users.
  • Wherever a Windows-specific tool or command is shown, offer the equivalent for other platforms.
  • Consider reordering or grouping examples so that Windows and Linux/macOS instructions are presented together.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates notable Windows bias: connection instructions to the VM are exclusively via RDP (Windows-only), and all examples for accessing the SQL Database from the VM use PowerShell and SQL Server Management Studio (Windows tools). There are no Linux/macOS alternatives for connecting to the VM (e.g., SSH) or querying the SQL Database (e.g., sqlcmd, Azure Data Studio). Windows tools and patterns are mentioned first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add instructions for connecting to the VM using SSH for Linux/macOS users.
  • Provide examples for querying the SQL Database using cross-platform tools such as sqlcmd or Azure Data Studio.
  • Include Linux/macOS command-line equivalents for deployment and validation steps.
  • Present connection options for both RDP and SSH, and database access options for both SSMS and cross-platform tools, ideally in parallel tabs or sections.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. It exclusively provides instructions for connecting to the VM via RDP (a Windows protocol), uses PowerShell for command-line examples, and recommends SQL Server Management Studio (a Windows-only tool) for database access. There are no Linux/macOS alternatives or examples for connecting to the VM (e.g., SSH), querying DNS, or accessing the SQL database. The cleanup step uses a PowerShell cmdlet without mentioning Azure CLI or other cross-platform options.
Recommendations
  • Add instructions for connecting to the VM using SSH for Linux/macOS users.
  • Provide equivalent command-line examples using Bash/Azure CLI for DNS queries (e.g., 'dig' or 'nslookup').
  • Suggest cross-platform database clients (e.g., Azure Data Studio, sqlcmd) for accessing SQL Database.
  • Include cleanup instructions using Azure CLI (e.g., 'az group delete').
  • Clearly indicate when steps are Windows-specific and offer alternatives for other platforms.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias in several areas: the VM creation example uses a Windows image (Win2022Datacenter) exclusively, and the connectivity test instructions specify opening PowerShell and using Windows-centric tools (nslookup in PowerShell) without mentioning Linux alternatives. There are no examples for creating a Linux VM or testing connectivity from a Linux shell, which may create friction for Linux/macOS users.
Recommendations
  • Provide parallel examples for creating a Linux VM (e.g., using --image UbuntuLTS) alongside the Windows VM example.
  • Include instructions for testing connectivity using Linux tools (e.g., using dig or nslookup in a bash shell) and clarify that these steps work on both Windows and Linux VMs.
  • When referencing shell commands, use platform-neutral language or show both bash and PowerShell syntax where relevant.
  • Explicitly mention that Azure Bastion supports both Windows and Linux VMs, and provide guidance for connecting to Linux VMs via Bastion.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for managing network policies, which are Windows-centric. PowerShell is presented before Azure CLI, and the CLI section notes limitations compared to PowerShell. There is no mention of Bash, Linux shell, or cross-platform scripting alternatives. The examples and tool references (PowerShell cmdlets) are primarily Windows-focused, potentially creating friction for Linux/macOS users.
Recommendations
  • Add Bash or shell script examples using Azure CLI to demonstrate parity and usage on Linux/macOS.
  • Clarify that Azure CLI is cross-platform and provide guidance for installing and using it on Linux/macOS.
  • Where PowerShell is referenced, mention that PowerShell Core is available on Linux/macOS, and provide equivalent examples if syntax differs.
  • Avoid presenting Windows-centric tools (PowerShell) before cross-platform alternatives (CLI) unless there is a technical reason.
  • Explicitly state platform compatibility for each tool and example.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both PowerShell and Azure CLI examples for enabling High Scale Private Endpoints, but PowerShell (a Windows-centric tool) is presented first and in more detail. There are no explicit Linux/macOS shell examples (e.g., Bash), and validation steps are shown for PowerShell and Portal only, omitting Linux-native alternatives. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell, or side-by-side.
  • Include Bash or shell script examples for validation steps, using Azure CLI.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Add notes or links for installing Azure CLI on Linux/macOS.
  • Where PowerShell is used for validation, provide equivalent Azure CLI commands.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. Connection instructions to the VM are exclusively via Remote Desktop Protocol (RDP), a Windows-centric tool, with no mention of SSH or Linux/macOS connection methods. The cleanup step uses a PowerShell cmdlet without providing an Azure CLI equivalent. Windows tools and patterns (RDP, PowerShell) are mentioned exclusively and before any Linux alternatives, which are absent.
Recommendations
  • Add instructions for connecting to the VM via SSH, including steps for Linux and macOS users.
  • Provide Azure CLI commands for resource group deletion alongside PowerShell examples.
  • Mention cross-platform tools (e.g., SSH, Azure CLI) wherever possible, and avoid assuming Windows as the default environment.
  • Present examples for both Windows and Linux/macOS users in parallel, or clarify OS-specific steps.
GitHub Create Pull Request
Private Link Manage Azure private endpoints .../main/articles/private-link/manage-private-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell (Windows-centric) examples before Azure CLI (cross-platform) examples, and relies heavily on PowerShell commands and screenshots. There is a notable emphasis on Windows tooling and patterns, with PowerShell being the primary scripting language demonstrated, and CLI examples sometimes referencing PowerShell output. No Linux/macOS-specific instructions, troubleshooting, or shell scripting patterns are provided.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is shown before PowerShell in some sections.
  • Add explicit notes clarifying that Azure CLI works on Linux/macOS and provide bash/zsh shell scripting patterns where appropriate.
  • Include screenshots of CLI output alongside PowerShell output.
  • Avoid referring to CLI output as 'PowerShell output' in alt-text or captions.
  • Add troubleshooting tips or environment setup instructions for Linux/macOS users.
  • Where possible, mention that all operations can be performed from Linux/macOS using the CLI.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →