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 1-25 of 188 flagged pages
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-14 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 Windows bias in several areas: connection instructions to the VM are exclusively via Remote Desktop Protocol (RDP), which is a Windows-centric tool, and the example web service is IIS, a Windows-only web server. There are no Linux/macOS alternatives or SSH-based connection instructions. The deployment and resource management examples do include both Azure CLI and PowerShell, but the critical VM access and service validation steps assume a Windows environment.
Recommendations
  • Add instructions for connecting to the VM using SSH, including steps for Linux and macOS users.
  • Provide an example of deploying a Linux VM and installing a cross-platform web server (e.g., Apache or Nginx) in addition to IIS.
  • Include browser-based Azure portal access instructions for VM management that do not rely on RDP.
  • Explicitly mention how Linux/macOS users can complete each step, or provide parallel instructions.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The tutorial is heavily biased toward Windows and PowerShell usage. All code examples use Azure PowerShell cmdlets, and the VM created for testing is explicitly a Windows Server instance. The connectivity test instructs users to use Windows PowerShell and SQL Server Management Studio (a Windows-only tool), with no mention of Linux/macOS alternatives or CLI equivalents. There are no Bash, Azure CLI, or cross-platform instructions provided, making it difficult for Linux/macOS users to follow the tutorial without significant adaptation.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all resource creation steps.
  • Provide instructions for creating a Linux VM and connecting via SSH, including how to test DNS resolution and SQL connectivity using cross-platform tools (e.g., nslookup, sqlcmd, Azure Data Studio).
  • Mention and demonstrate SQL Server Management Studio alternatives such as Azure Data Studio, which is cross-platform.
  • Explicitly note which steps/tools are Windows-only and provide Linux/macOS equivalents where possible.
  • Consider reordering examples so that cross-platform options are presented first or in parallel with Windows-specific instructions.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: remote access instructions exclusively use RDP (Remote Desktop Protocol), which is Windows-specific, and reference IIS (Internet Information Services) as the default web server, also Windows-centric. There are no instructions for connecting to the VM via SSH (the standard for Linux/macOS) or for accessing a Linux-based web server. All examples for connecting to the VM and verifying the service are tailored to Windows users, with no Linux/macOS alternatives provided.
Recommendations
  • Add instructions for connecting to the VM using SSH, including example commands for Linux/macOS users.
  • Include examples for deploying and accessing a Linux-based web server (e.g., Apache or Nginx) in addition to IIS.
  • Provide parity in remote access instructions, such as using Azure Bastion or SSH tunnels, which work across platforms.
  • Clearly indicate when steps are Windows-specific and offer equivalent steps for Linux/macOS environments.
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-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 is heavily focused on Windows and PowerShell, with all examples and instructions using Azure PowerShell cmdlets and Windows-centric tooling. The virtual machine created is explicitly a Windows Server VM, and the connectivity test is performed using Windows PowerShell and SQL Server Management Studio, both Windows-specific tools. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform SQL clients.
Recommendations
  • Add parallel instructions and code samples using Azure CLI (az) for resource creation and management, which is cross-platform.
  • Provide examples for creating and connecting to a Linux VM, including instructions for installing and using cross-platform SQL clients (e.g., sqlcmd, Azure Data Studio).
  • Include connectivity testing steps using Bash (e.g., nslookup, dig) and Linux/macOS terminal commands.
  • Clearly indicate which steps are Windows-specific and offer alternatives for Linux/macOS users.
  • Consider restructuring the tutorial so that Windows and Linux/macOS instructions are presented side-by-side or selectable via tabs.
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 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 is heavily biased toward Windows and PowerShell. All code examples use Azure PowerShell cmdlets, and the virtual machine created is explicitly a Windows Server instance. The connectivity test and management steps assume the use of Windows PowerShell and SQL Server Management Studio, both Windows-centric tools. There are no examples or guidance for Linux users, such as using Bash/CLI, connecting from a Linux VM, or using cross-platform SQL tools.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all resource creation and management steps.
  • Include instructions for creating a Linux VM and connecting to Azure SQL from Linux (e.g., using sqlcmd, Azure Data Studio, or other cross-platform tools).
  • Add connectivity test steps using Bash or Linux shell commands (e.g., nslookup, dig) and SQL connection examples for Linux.
  • Mention cross-platform management tools (Azure Data Studio, sqlcmd) alongside SQL Server Management Studio.
  • Clearly indicate which steps are Windows-specific and provide Linux alternatives where appropriate.
GitHub Create Pull Request
Private Link Manage network policies for private endpoints ...rivate-link/disable-private-endpoint-network-policy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page displays a Windows bias by providing detailed PowerShell examples and referencing PowerShell modules, which are native to Windows. The PowerShell tab appears before the CLI tab, and there is no mention of Linux-specific shell usage or examples (e.g., Bash). The CLI examples use Azure CLI, which is cross-platform, but do not provide any Linux-specific context or shell integration tips. No Linux-native tools or workflows are discussed, and PowerShell is presented as a primary automation method.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage, including Linux-specific command-line patterns and environment considerations.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample commands using Bash syntax (with environment variables, piping, etc.).
  • Consider adding a section or tab for Linux automation (e.g., using Bash scripts or cloud-init) to balance the PowerShell-heavy approach.
  • Mention cross-platform compatibility for all tools and clarify any differences in behavior or prerequisites between Windows and Linux.
  • Reorder tabs so that CLI (cross-platform) appears before PowerShell, or provide equal prominence to both.
GitHub Create Pull Request
Private Link Azure Private Endpoint DNS Integration Scenarios ...icles/private-link/private-endpoint-dns-integration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias in its DNS forwarder scenario, referencing Windows Server DNS concepts and conditional forwarding, but does not provide Linux/BIND equivalents or examples. The terminology and linked resources are Windows-centric, and there are no explicit Linux configuration steps or mentions of common Linux DNS tools (e.g., BIND, dnsmasq, systemd-resolved). All examples and guidance assume familiarity with Windows DNS management patterns, leaving out Linux system administrators.
Recommendations
  • Add explicit Linux/BIND examples for DNS forwarder and conditional forwarding scenarios, including configuration file snippets and command-line instructions.
  • Reference Linux DNS documentation (e.g., BIND, dnsmasq, systemd-resolved) alongside Windows Server DNS links.
  • Clarify that DNS forwarders can be implemented using both Windows and Linux-based solutions, and provide parity in guidance for both platforms.
  • Include sample configuration steps for popular Linux DNS servers in relevant sections.
  • Use platform-neutral language when describing DNS concepts, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Private Link What is a private endpoint? ...ain/articles/private-link/private-endpoint-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell (New-AzPrivateEndpoint) before the Azure CLI (az network private-endpoint create) when describing how to create a private endpoint using an alias. No Linux-specific tools, shell examples, or cross-platform command-line instructions are provided. The documentation does not mention Linux or provide parity for Linux users in terms of examples or guidance.
Recommendations
  • Present Azure CLI (az) examples before or alongside PowerShell examples to ensure cross-platform parity.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh shell examples where appropriate.
  • Include references to Linux-native tools or environments (e.g., Bash, cloud-init, etc.) when discussing command-line operations.
  • Add a section or note clarifying platform compatibility for all tools and commands mentioned.
  • Avoid using Windows-specific terminology or tools exclusively, and ensure all instructions are accessible to Linux users.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial demonstrates a clear Windows bias by providing only Windows PowerShell commands for connectivity testing, referencing Windows-specific tools (such as Microsoft Azure Storage Explorer with Windows installation instructions), and omitting any Linux or cross-platform alternatives. All example commands and screenshots assume a Windows environment, and there are no instructions for performing equivalent steps on Linux VMs or using Linux-native tools.
Recommendations
  • Include Linux-specific instructions and examples, such as using Bash or the Azure CLI on Linux VMs for connectivity testing (e.g., using 'dig', 'nslookup', or 'curl').
  • Provide installation and usage guidance for Microsoft Azure Storage Explorer on Linux, or suggest alternative cross-platform tools.
  • Present command-line examples for both Windows and Linux side-by-side, or use tabs to allow users to select their OS.
  • Avoid assuming the use of Windows PowerShell; mention Bash, zsh, or other common Linux shells where appropriate.
  • Reference Linux VM creation and connection steps, including SSH access, alongside Windows Bastion/PowerShell instructions.
GitHub Create Pull Request
Private Link Manage Azure private endpoints .../main/articles/private-link/manage-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-11 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-centric tools (PowerShell) before cross-platform alternatives (Azure CLI), and all command-line examples are given only for PowerShell and Azure CLI. There are no explicit Linux shell (bash) examples, nor are there references to Linux-specific patterns or tools. The structure and language reinforce a Windows-first approach, with PowerShell commands and terminology featured prominently and sometimes described before CLI equivalents.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell, or at least alternate the order to avoid Windows-first bias.
  • Add explicit bash shell examples for Azure CLI commands, demonstrating usage in a Linux environment (e.g., variable assignment, piping, jq usage for JSON parsing).
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Where PowerShell-specific features or syntax are discussed, provide equivalent bash/Linux shell guidance.
  • Include notes or sections on Linux-specific considerations, such as authentication, environment setup, or scripting best practices.
  • Review screenshots and output examples to ensure they are not exclusively from Windows environments.
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
High Priority View Details →
Scanned: 2026-01-11 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 clear Windows bias in the test connectivity section: it creates a Windows VM (Win2019Datacenter), instructs users to open Windows PowerShell, and exclusively uses Windows tools (PowerShell and SQL Server Management Studio) for connectivity testing. There are no Linux VM creation options, nor are Linux-native tools (such as sqlcmd or Azure Data Studio) mentioned. The instructions for connecting to the SQL server and verifying DNS resolution are Windows-centric, with no parity for Linux users.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) and connecting via SSH.
  • Include Linux-native commands for DNS resolution (e.g., nslookup, dig) and SQL connectivity (e.g., sqlcmd, Azure Data Studio, or ODBC tools).
  • Mention installation and usage of cross-platform SQL tools (such as Azure Data Studio) in addition to SQL Server Management Studio.
  • Offer a choice between Windows and Linux VM images in the VM creation step.
  • Explicitly state that the tutorial applies to both Windows and Linux environments, and provide side-by-side examples where appropriate.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Azure portal ...rticles/private-link/create-private-endpoint-portal.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively referencing PowerShell for connectivity testing and omitting Linux-specific instructions or examples. The workflow assumes a Windows environment (PowerShell, Bastion, browser usage) and does not mention or prioritize Linux alternatives for command-line or browser-based testing.
Recommendations
  • Include Linux-specific instructions for connectivity testing, such as using Bash, curl, wget, or dig/nslookup from a Linux shell.
  • Provide explicit examples for both Windows (PowerShell) and Linux (Bash) environments when testing DNS resolution and web app connectivity.
  • Clarify that the VM used for testing can be either Windows or Linux, and offer guidance for both OS types.
  • Mention cross-platform tools and commands in parallel, rather than assuming PowerShell as the default.
  • Add screenshots or command outputs from Linux terminals to improve parity and inclusivity.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - ARM template ...icles/private-link/create-private-endpoint-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Windows-centric instructions and examples. It exclusively references RDP for VM access, PowerShell for DNS validation, and SQL Server Management Studio for database connection, without mentioning or providing alternatives for Linux users. Cleanup instructions use PowerShell cmdlets, with no Azure CLI or Bash equivalents. There is no guidance for connecting via SSH, using Linux command-line tools, or cross-platform database clients.
Recommendations
  • Add Linux-specific instructions for connecting to the VM (e.g., SSH access using Azure CLI or native SSH).
  • Provide examples using Azure CLI for resource cleanup (e.g., az group delete) alongside PowerShell.
  • Include Linux command-line tools (e.g., dig, nslookup) for DNS validation from the VM.
  • Suggest cross-platform database clients (e.g., Azure Data Studio, sqlcmd) for connecting to SQL Database.
  • Clearly indicate parity between Windows and Linux workflows in all steps, ensuring both are covered equally.
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-11 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 by exclusively providing instructions for connecting to the VM using Remote Desktop Protocol (RDP), which is a Windows-centric tool. There are no examples or guidance for Linux users, such as connecting via SSH or using Linux-based tools. The walkthrough assumes the VM is running Windows (IIS web server, RDP connection), and does not mention Linux alternatives or parity in deployment or validation steps.
Recommendations
  • Add instructions for connecting to the VM using SSH for Linux-based VMs, including example commands and authentication steps.
  • Include deployment and validation steps for both Windows and Linux VMs, such as installing Apache/Nginx on Linux and accessing the web service.
  • Provide examples for Linux users in the 'Connect to a VM' section, such as using the Azure CLI or SSH clients.
  • Clarify that the Bicep template can be used to deploy either Windows or Linux VMs, and offer guidance for both scenarios.
  • Mention Linux equivalents for any Windows-specific tools or patterns (e.g., RDP vs SSH, IIS vs Apache/Nginx).
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Terraform ...cles/private-link/create-private-endpoint-terraform.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides verification steps using Azure CLI and Azure PowerShell, with PowerShell examples included as a separate tab. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. The presence of PowerShell examples and the lack of Linux shell commands or troubleshooting steps suggest a Windows bias, especially for users who may be working on Linux or macOS systems.
Recommendations
  • Add explicit bash/Linux shell examples for verification steps, alongside Azure CLI and PowerShell.
  • Ensure that instructions for running Terraform and connecting via SSH are platform-neutral, or provide platform-specific guidance for both Windows and Linux/macOS.
  • Include troubleshooting steps relevant to Linux environments, such as common SSH or DNS issues on Linux.
  • Mention cross-platform tools (e.g., WSL, native bash) where appropriate, and avoid assuming PowerShell as the default shell.
  • Review all code snippets and ensure parity between Windows and Linux usage patterns, especially for environment variable syntax and command-line operations.
GitHub Create Pull Request
Private Link Quickstart: Create a private link service - ARM template ...s/private-link/create-private-link-service-template.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by providing only Windows-centric instructions for connecting to the VM (using RDP and referencing IIS), exclusively using PowerShell for resource cleanup, and omitting Linux-based alternatives such as SSH access or Bash/Azure CLI commands. Windows tools and patterns (RDP, IIS, PowerShell) are mentioned without Linux equivalents, and Windows methods are presented first and exclusively.
Recommendations
  • Add instructions for connecting to the VM using SSH for Linux-based VMs, including details on how to obtain the public IP and use an SSH client.
  • Provide examples for cleaning up resources using Azure CLI (az group delete) and Bash scripts, not just PowerShell.
  • Include steps for accessing the web service from a Linux VM, such as using curl or a browser, and mention Apache/nginx as alternatives to IIS.
  • Clarify whether the template supports Linux VM deployment and, if so, provide parallel instructions for Linux users.
  • Ensure that both Windows and Linux tools and patterns are presented side-by-side or in separate sections, giving equal prominence.
GitHub Create Pull Request
Private Link Disable network policies for Azure Private Link service source IP address ...te-link/disable-private-link-service-network-policy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell (a Windows-centric tool) first among the example methods, providing detailed PowerShell instructions, and referencing PowerShell before Azure CLI and ARM templates. There is no mention of Linux-specific tools or shell environments, and the CLI example does not clarify cross-platform usage or provide Linux shell context.
Recommendations
  • Alternate the order of example sections so that Azure CLI (cross-platform) appears before PowerShell.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell contexts (e.g., Bash).
  • Include notes or examples for Linux users, such as running Azure CLI in Bash or using Cloud Shell.
  • Avoid referring to PowerShell as the default or primary method unless justified by user data.
  • Add clarification that all methods are supported on multiple platforms where applicable.
GitHub Create Pull Request
Private Link Increase Private Endpoint virtual network limits .../private-link/increase-private-endpoint-vnet-limits.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell examples, listing PowerShell before CLI in code tabs, and omitting explicit Linux/Bash shell examples. The CLI example is present but lacks a Bash context, and there are no references to Linux-specific tools or shell environments. Portal instructions are platform-neutral, but scripting guidance is skewed toward Windows/PowerShell users.
Recommendations
  • Add explicit Bash/Linux shell examples alongside PowerShell and CLI, using standard Bash variable syntax and export statements.
  • Reorder code tabs to present CLI/Bash examples before or alongside PowerShell to avoid the perception of Windows-first bias.
  • Include notes clarifying that the Azure CLI works cross-platform and provide sample commands in both Windows (CMD/PowerShell) and Linux (Bash) syntax.
  • Where possible, mention or link to Linux-specific guidance for Azure networking tasks.
  • Ensure terminology and instructions are inclusive of both Windows and Linux administrators.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Bicep ...articles/private-link/create-private-endpoint-bicep.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by prioritizing Windows-centric tools and workflows. Examples for connecting to the VM use RDP and PowerShell, both Windows-specific. The instructions for accessing the SQL Database from the VM assume the use of SQL Server Management Studio, a Windows-only tool, and do not provide Linux alternatives for connecting to the VM (e.g., SSH) or querying the database. Linux equivalents, such as SSH for VM access or sqlcmd for database interaction, are missing throughout the guide.
Recommendations
  • Add instructions for connecting to the VM using SSH, which is standard on Linux.
  • Include examples for running nslookup or querying the SQL Database from a Linux VM, using native Linux tools (e.g., sqlcmd, Azure Data Studio).
  • Mention and provide steps for installing and using cross-platform database clients.
  • Present CLI and PowerShell examples side-by-side, rather than listing PowerShell after CLI, to avoid Windows-first ordering.
  • Clarify that the VM can be deployed with either Windows or Linux OS, and provide guidance for both.
GitHub Create Pull Request
Private Link Configure an application security group with a private endpoint ...rticles/private-link/configure-asg-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for the Azure Portal, PowerShell, and Azure CLI. PowerShell is featured prominently, with detailed example scripts, and is referenced in prerequisites and installation instructions. PowerShell is a Windows-centric tool, and its inclusion and prominence may indicate a Windows bias. The prerequisites section discusses PowerShell before CLI, and the custom metadata includes 'devx-track-azurepowershell' before 'devx-track-azurecli'. There are no explicit Linux-specific instructions or examples, and no mention of Linux shell scripting or tools. However, the CLI examples are cross-platform, and the documentation does not entirely exclude Linux users.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
  • Include Linux-specific instructions or shell scripting examples (e.g., bash) where appropriate, especially in the prerequisites and installation sections.
  • Balance the order of tool presentation: mention Azure CLI before PowerShell, or present both equally.
  • Avoid language that assumes PowerShell is the default or preferred tool; clarify that CLI is cross-platform and often preferred on Linux.
  • Consider adding troubleshooting or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, using bash variables).
GitHub Create Pull Request
Private Link Configure Private Link service Direct Connect ...-link/configure-private-link-service-direct-connect.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently listing Azure PowerShell instructions and examples before Azure CLI and Terraform, both in the main workflow and in verification and cleanup sections. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux users. There are no explicit Linux shell examples (e.g., bash scripts), nor are there notes about running PowerShell on Linux or macOS. The prerequisites and troubleshooting sections also mention PowerShell before CLI, reinforcing the Windows-first pattern.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or list CLI first to improve parity for Linux users.
  • Add explicit notes that both Azure PowerShell and Azure CLI are cross-platform, and provide links to installation instructions for Linux and macOS.
  • Include bash script examples for common tasks, especially for verification and cleanup, to help Linux users.
  • Clarify that all CLI commands are compatible with Linux/macOS terminals and provide troubleshooting tips for those environments.
  • Mention that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained, and provide guidance for installation on those platforms.
GitHub Create Pull Request
Private Link Quickstart - Create a network security perimeter - ARM Template ...ate-link/create-network-security-perimeter-template.md
High Priority View Details →
Scanned: 2026-01-11 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 bias toward Windows environments by providing only a PowerShell example for resource cleanup, mentioning Azure PowerShell before Azure CLI, and omitting equivalent Linux/bash instructions. No Linux or cross-platform command-line examples are given for key operations such as deleting resources, which may hinder users on non-Windows platforms.
Recommendations
  • Include Azure CLI (bash) examples alongside PowerShell for all command-line operations, especially for resource cleanup.
  • Present Azure CLI and PowerShell options together or in parallel sections, rather than listing PowerShell first.
  • Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux/macOS users.
  • Add notes or links to documentation for using ARM templates via Azure CLI on Linux/macOS.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Azure CLI ...n/articles/private-link/create-private-endpoint-cli.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively using Windows-based VM images (Win2022Datacenter) in examples, referencing PowerShell as the shell for connectivity testing, and omitting any Linux VM creation or Linux shell/command examples. All instructions for testing connectivity assume a Windows environment, with no mention of Linux alternatives or parity.
Recommendations
  • Include examples for creating a Linux VM (e.g., using --image UbuntuLTS) alongside the Windows VM example.
  • Provide Linux shell (bash) equivalents for connectivity testing, such as using 'dig' or 'nslookup' in bash.
  • Explicitly mention that the steps can be performed on both Windows and Linux VMs, and provide guidance for both platforms.
  • When referencing tools (e.g., PowerShell), also mention Linux-native tools and commands.
  • Ensure screenshots and walkthroughs include both Windows and Linux scenarios where applicable.
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
High Priority View Details →
Scanned: 2026-01-11 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 bias toward Windows environments by exclusively using Windows PowerShell for DNS testing, referencing Microsoft Edge for browser testing, and omitting Linux-based instructions or examples. There are no Linux shell commands (e.g., dig, host, nslookup in bash), nor is there guidance for connecting to the test VM from Linux or macOS clients. The documentation assumes a Windows-centric workflow for both command-line and GUI steps.
Recommendations
  • Provide Linux and macOS equivalents for command-line DNS testing, such as using 'dig' or 'nslookup' in bash.
  • Include instructions for connecting to the test VM from Linux/macOS clients, possibly using SSH instead of Bastion/Windows RDP.
  • Mention cross-platform browsers (e.g., Firefox, Chrome) in addition to Microsoft Edge.
  • Add screenshots or output examples from Linux terminals where appropriate.
  • Explicitly state that the steps can be performed from non-Windows environments and provide relevant guidance.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - ARM template ...icles/private-link/create-private-endpoint-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Windows-centric instructions and tooling. All example commands use PowerShell, and the workflow relies on Remote Desktop Protocol (RDP) to connect to a Windows VM. SQL Server Management Studio (SSMS), a Windows-only tool, is used for database access. There are no examples or instructions for Linux users, such as connecting via SSH, using Azure CLI, or accessing the database with cross-platform tools. Windows tools and patterns are mentioned exclusively and before any Linux equivalents, which are absent.
Recommendations
  • Add instructions for connecting to the VM via SSH for Linux and macOS users.
  • Provide examples using Azure CLI for resource management and cleanup, alongside PowerShell.
  • Include cross-platform database access tools such as Azure Data Studio or sqlcmd, with usage examples.
  • Explicitly mention both Windows and Linux workflows in validation and cleanup steps.
  • Ensure that all steps (connection, validation, cleanup) have Linux/macOS equivalents and are presented with parity to Windows instructions.
GitHub Create Pull Request
← Previous Page 1 of 8 Next →