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 76-100 of 188 flagged pages
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-endpoint-terraform.md ...cles/private-link/create-private-endpoint-terraform.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 presented as a primary tab. There are no explicit Linux shell (bash) examples for connecting to the SQL Database or verifying endpoints from a Linux VM, nor are there instructions for using native Linux tools (e.g., curl, dig, ssh) to test connectivity. The verification and resource cleanup steps rely on Azure CLI and PowerShell, which are available cross-platform, but PowerShell is traditionally associated with Windows. There is no mention of Linux-specific patterns or troubleshooting, and no explicit parity in examples for Linux users.
Recommendations
  • Add explicit bash/Linux shell examples for verifying connectivity to the SQL Database and private endpoint from the deployed VM (e.g., using ssh, curl, or dig).
  • Include instructions for using native Linux tools to test DNS resolution and connectivity, such as 'nslookup', 'dig', or 'curl' from the VM.
  • Ensure that verification steps are presented in a way that does not prioritize Windows/PowerShell over Linux/bash, possibly by listing bash examples first or side-by-side.
  • Add troubleshooting steps or notes relevant to Linux users, such as common issues with SSH keys, DNS resolution, or firewall rules on Linux VMs.
  • Clarify that both Azure CLI and PowerShell are cross-platform, and provide links or notes for installing them on Linux if needed.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/disable-private-endpoint-network-policy.md ...rivate-link/disable-private-endpoint-network-policy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions and code samples for managing network policies for Azure private endpoints using the Azure portal, Azure PowerShell, Azure CLI, and ARM templates. However, the PowerShell examples are given significant prominence, and there is no mention of Linux-specific tools or shell environments. The CLI examples are generic but do not clarify Linux usage or provide bash/zsh-specific guidance. There is an implicit Windows-first bias, as PowerShell is featured before CLI, and no explicit Linux shell or cross-platform scripting examples are provided.
Recommendations
  • Add explicit bash/zsh (Linux/macOS) shell examples for Azure CLI commands, including any differences in quoting, line continuation, or environment setup.
  • Clarify in the CLI sections that the commands work on Linux, macOS, and Windows, and provide notes on any OS-specific considerations.
  • Consider reordering the examples to present Azure CLI before PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Include a note or section on using Azure Cloud Shell, which supports both Bash and PowerShell, to emphasize cross-platform parity.
  • If relevant, mention or link to Linux-native tools or scripting approaches for managing Azure resources, such as using REST API with curl/jq.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/manage-private-endpoint.md .../main/articles/private-link/manage-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting PowerShell examples before Azure CLI examples, referencing PowerShell-specific cmdlets, and omitting explicit Linux shell (bash) or cross-platform scripting examples. While Azure CLI is included, there are no Linux-specific instructions, screenshots, or notes about platform differences. The use of PowerShell is emphasized, and the CLI examples are sometimes described in the context of PowerShell, further reinforcing the Windows-centric approach.
Recommendations
  • Alternate the order of examples, sometimes presenting Azure CLI (bash) before PowerShell to avoid Windows-first bias.
  • Include explicit bash shell examples, with Linux-specific notes or screenshots where appropriate.
  • Add a section discussing platform compatibility, clarifying that Azure CLI works on Linux, macOS, and Windows, and providing guidance for Linux users.
  • Avoid language that frames CLI examples in terms of PowerShell (e.g., 'uses an Azure PowerShell command' in the CLI section).
  • Where possible, provide cross-platform instructions for prerequisites and environment setup.
  • Consider adding troubleshooting notes for common Linux-specific issues (e.g., permissions, environment variables).
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-endpoint-dns-integration.md ...icles/private-link/private-endpoint-dns-integration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric DNS concepts (such as conditional forwarders and links to Windows Server DNS documentation), and by not providing any Linux-specific DNS configuration examples or mentioning Linux tools (e.g., BIND, dnsmasq, systemd-resolved). All DNS forwarder and conditional forwarding guidance is generic or references Windows terminology and documentation first, with no parity for Linux environments.
Recommendations
  • Add explicit Linux DNS server configuration examples (e.g., BIND, dnsmasq, Unbound) for conditional forwarding and DNS forwarding scenarios.
  • Include links to Linux DNS documentation and guides alongside or before Windows references.
  • Mention Linux DNS server options and their configuration steps in all relevant scenarios, especially where Windows Server DNS is referenced.
  • Provide sample configuration snippets for Linux DNS servers to match the Windows examples.
  • Clarify that the guidance applies to both Windows and Linux environments, and highlight any platform-specific considerations.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-endpoint-overview.md ...ain/articles/private-link/private-endpoint-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references 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 elsewhere. The documentation implicitly prioritizes Windows tooling and does not offer parity for Linux users.
Recommendations
  • When referencing command-line tools, always mention Azure CLI (az) first, as it is cross-platform, and provide Bash examples alongside PowerShell.
  • Include explicit Linux/Bash shell examples for common tasks, such as creating private endpoints, configuring DNS, and managing network policies.
  • Add notes clarifying that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each platform.
  • Where PowerShell is referenced, also provide equivalent Bash or Azure CLI commands to ensure parity.
  • Review all referenced documentation links to ensure they include cross-platform instructions and examples.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-link-disable-snat.md ...ain/articles/private-link/private-link-disable-snat.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows virtual machines as the default NVA example, prioritizing PowerShell examples before Azure CLI, and linking to Windows-specific VM deployment guides. There is no mention of Linux as an NVA platform, nor are Linux-specific tools or workflows discussed.
Recommendations
  • Include Linux as an example NVA platform in the prerequisites and throughout the guide.
  • Provide links to both Windows and Linux VM deployment guides (e.g., 'Quickstart: Create a Linux virtual machine in the Azure portal').
  • Ensure parity in command-line examples by offering Bash/Linux shell commands where relevant, and clarify that Azure CLI works cross-platform.
  • Avoid defaulting to Windows terminology or tools (such as PowerShell) as the primary or first example; alternate the order or present both equally.
  • Mention that the process is identical regardless of the VM OS, if applicable, to reassure Linux users.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-dns-on-premises-private-resolver.md ...vate-link/tutorial-dns-on-premises-private-resolver.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in several ways. The only explicit command-line example for DNS resolution uses Windows PowerShell, with no mention of Linux equivalents (e.g., dig or nslookup on Linux). The tutorial refers to 'Open Windows PowerShell' and 'Open Microsoft Edge' for testing, implicitly assuming the test VM is running Windows. There are no instructions or examples for performing the same steps on a Linux VM, nor are Linux tools or patterns mentioned. This may hinder Linux users or those using non-Windows environments from following the tutorial seamlessly.
Recommendations
  • Provide Linux-specific instructions and examples alongside Windows ones, such as using 'dig' or 'nslookup' on Linux for DNS resolution.
  • Clarify that the test VM can be either Windows or Linux, and offer guidance for both OS types.
  • Include screenshots or command outputs from Linux terminals where appropriate.
  • Mention cross-platform browsers (e.g., Firefox, Chrome) instead of only Microsoft Edge.
  • Explicitly state OS requirements or options for the test VM in the prerequisites section.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-private-endpoint-sql-powershell.md ...ivate-link/tutorial-private-endpoint-sql-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, and the tutorial assumes the use of Windows-based tools and workflows (e.g., Windows PowerShell, SQL Server Management Studio). There are no equivalent instructions or examples for Linux users, such as Bash/CLI commands, Linux VM creation, or alternative SQL clients. The VM creation steps specifically deploy a Windows Server image, and connectivity testing is performed using Windows PowerShell and SQL Server Management Studio, both Windows-centric tools.
Recommendations
  • Provide parallel examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include instructions for creating a Linux-based VM (e.g., Ubuntu) and show how to connect to Azure SQL using Linux tools such as sqlcmd or Azure Data Studio.
  • When testing connectivity, demonstrate DNS resolution and SQL connectivity using Linux shell commands (e.g., nslookup, dig, sqlcmd) in addition to Windows PowerShell.
  • Mention and link to cross-platform SQL client tools, such as Azure Data Studio, in addition to SQL Server Management Studio.
  • Clearly indicate in the prerequisites and throughout the tutorial which steps are platform-specific, and provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-private-endpoint-sql-cli.md ...cles/private-link/tutorial-private-endpoint-sql-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The tutorial exhibits a Windows bias in several ways: the only VM example uses a Windows Server image, connectivity testing is performed exclusively via Windows PowerShell, and SQL Server Management Studio (a Windows-only tool) is the sole database client mentioned. There are no Linux VM examples, nor are cross-platform tools (like sqlcmd or Azure Data Studio) suggested for connectivity testing. The documentation assumes a Windows environment for all hands-on steps.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., using Ubuntu or CentOS images) alongside the Windows VM example.
  • Include Linux shell commands (e.g., using bash and nslookup) for DNS testing.
  • Suggest and demonstrate cross-platform database clients such as Azure Data Studio or sqlcmd, with installation and usage instructions for both Windows and Linux.
  • Explicitly mention that the Azure CLI works on all major platforms and encourage users to follow steps on their preferred OS.
  • Add notes or sections highlighting differences or considerations for Linux users, especially for connectivity and tooling.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-private-endpoint-storage-portal.md ...ivate-link/tutorial-private-endpoint-storage-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias: all command-line examples use Windows PowerShell, and instructions for connectivity testing are exclusively Windows-centric. The use of Microsoft Azure Storage Explorer is referenced with Windows-specific installation instructions, and there are no Linux or cross-platform alternatives provided. The documentation does not mention or provide examples for Linux users, such as using Bash, Azure CLI, or Linux-compatible tools.
Recommendations
  • Provide Linux/Bash equivalents for command-line instructions, such as using 'dig' or 'nslookup' in Bash.
  • Include installation steps for Microsoft Azure Storage Explorer on Linux and macOS, or mention cross-platform compatibility.
  • Offer Azure CLI examples for connectivity testing and resource management, which work across platforms.
  • Clearly indicate when steps are platform-specific and provide parallel instructions for other operating systems.
  • Add screenshots or guidance for Linux desktop environments where applicable.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-network-security-perimeter-template.md ...ate-link/create-network-security-perimeter-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by providing only a PowerShell example for resource cleanup, omitting equivalent Azure CLI or Bash commands that would be more familiar to Linux or cross-platform users. The only command-line tool shown is Remove-AzResourceGroup, which is specific to Azure PowerShell (commonly used on Windows). No Linux-native or cross-platform command-line instructions are provided.
Recommendations
  • Add equivalent Azure CLI (az group delete) and/or Bash examples alongside the PowerShell command for deleting the resource group.
  • Explicitly mention that both Azure PowerShell and Azure CLI are supported, and provide links or instructions for both.
  • Wherever command-line instructions are given, ensure parity by presenting both Windows (PowerShell) and Linux (CLI/Bash) options.
  • Consider including a table or tabs to let users select their preferred environment (PowerShell, CLI, Bash, etc.).
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-link-service-bicep.md ...cles/private-link/create-private-link-service-bicep.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively describing how to connect to the VM using Remote Desktop Protocol (RDP), which is a Windows-centric approach. There are no instructions for connecting via SSH, which is the standard for Linux VMs. The example assumes the use of IIS (Internet Information Services), a Windows web server, and does not mention Linux alternatives. While both Azure CLI and PowerShell are provided for deployment and management, the post-deployment access and validation steps are Windows-specific.
Recommendations
  • Include instructions for connecting to Linux VMs using SSH, including example commands and expected outputs.
  • Provide examples using a Linux-based web server (e.g., Apache or Nginx) in addition to IIS.
  • Clarify that the steps for connecting and validating the deployment differ for Linux and Windows VMs, and provide parallel instructions for both.
  • Mention that RDP is specific to Windows VMs and suggest SSH for Linux VMs.
  • Ensure that screenshots and walkthroughs are not limited to Windows environments.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-link-service-template.md ...s/private-link/create-private-link-service-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for connecting to the VM using Remote Desktop Protocol (RDP), which is a Windows-centric tool. The cleanup step uses a PowerShell cmdlet (Remove-AzResourceGroup) without mentioning an equivalent Azure CLI or Bash command. There are no examples or guidance for Linux users (e.g., SSH access), and Windows tools and patterns are mentioned exclusively and before any Linux alternatives.
Recommendations
  • Add parallel instructions for connecting to the VM using SSH, including steps for Linux and macOS users.
  • Provide Azure CLI or Bash command examples for resource cleanup alongside the PowerShell example.
  • Mention both RDP (for Windows) and SSH (for Linux/macOS) as options for connecting to the VM, and clarify which OS images are used in the template.
  • Ensure that all steps that currently reference Windows tools or workflows have Linux/macOS equivalents presented with equal prominence.
  • Consider including screenshots or code snippets that reflect both Windows and Linux user experiences.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-private-endpoint-sql-powershell.md ...ivate-link/tutorial-private-endpoint-sql-powershell.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 command-line instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The virtual machine created is explicitly a Windows Server VM, and the connectivity test steps assume the use of Windows PowerShell and SQL Server Management Studio (a Windows-only tool). There are no examples or guidance for Linux users, nor are cross-platform tools (like Azure CLI or Data Studio) mentioned.
Recommendations
  • Provide parallel instructions using Azure CLI (az commands) and Bash for all resource creation steps.
  • Include an example for creating a Linux VM and connecting from it, using native Linux tools (e.g., sqlcmd, Azure Data Studio, or ODBC).
  • When testing connectivity, show how to use nslookup or dig on Linux, and how to connect to SQL Server using cross-platform tools.
  • Mention and link to cross-platform tools (e.g., Azure Data Studio) as alternatives to SQL Server Management Studio.
  • Avoid assuming the use of Windows-only tools or workflows; present both Windows and Linux options side by side.
  • Consider renaming the tutorial or clearly indicating its Windows focus if Linux parity is not intended.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-endpoint-bicep.md ...articles/private-link/create-private-endpoint-bicep.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed instructions for connecting to the VM using RDP (a Windows protocol), instructing users to open PowerShell (a Windows shell), and referencing SQL Server Management Studio (a Windows-only tool). There are no examples or alternatives for Linux users, such as SSH access, Bash shell usage, or cross-platform SQL tools. The CLI and PowerShell deployment instructions are presented, but the validation and usage steps are Windows-centric.
Recommendations
  • Add instructions for connecting to the VM using SSH for Linux/macOS users, including example SSH commands.
  • Provide examples of running DNS queries using Bash (e.g., 'dig' or 'nslookup' in Linux) in addition to PowerShell.
  • Suggest cross-platform SQL client tools (such as Azure Data Studio or sqlcmd) and provide connection instructions for those.
  • Include both RDP (Windows) and SSH (Linux/macOS) connection methods in the 'Connect to a VM' section.
  • Ensure that all validation and cleanup steps have both Windows and Linux command examples where applicable.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-private-endpoint-storage-portal.md ...ivate-link/tutorial-private-endpoint-storage-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows PowerShell commands for connectivity testing, referencing Windows-specific tools (such as Microsoft Azure Storage Explorer with a Windows tab), and omitting equivalent instructions or examples for Linux users. All command-line and tool installation steps assume a Windows environment, with no mention of Linux alternatives or parity.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using bash and nslookup or dig) alongside PowerShell examples.
  • Include instructions for installing and using Microsoft Azure Storage Explorer on Linux, or mention cross-platform compatibility.
  • Explicitly state that the tutorial applies to both Windows and Linux VMs, and provide steps for both where relevant.
  • When referencing tools or commands, avoid assuming a Windows environment by default; present both Windows and Linux options in parallel.
  • Add screenshots or terminal output examples from Linux environments to ensure parity and inclusivity.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-endpoint-template.md ...icles/private-link/create-private-endpoint-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows-based workflows: it instructs users to connect to the VM via RDP (a Windows protocol), open PowerShell (a Windows shell), and install SQL Server Management Studio (a Windows-only tool). No Linux alternatives or cross-platform instructions are provided for connecting to the VM, running DNS queries, or accessing the SQL database. The cleanup step uses a PowerShell cmdlet without mentioning Azure CLI or Bash equivalents.
Recommendations
  • Provide alternative instructions for connecting to the VM using SSH, which is standard on Linux and also available on Windows.
  • Include examples of running DNS queries using Linux tools (e.g., dig or nslookup in Bash) in addition to PowerShell.
  • Suggest cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) alongside SQL Server Management Studio.
  • Offer resource cleanup instructions using Azure CLI (az group delete) and Bash, not just PowerShell.
  • Clearly indicate when instructions are Windows-specific and provide parallel steps for Linux/macOS users.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-endpoint-dns-integration.md ...icles/private-link/private-endpoint-dns-integration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-centric DNS concepts (such as conditional forwarders and DNS forwarders) and linking to Windows Server documentation for DNS configuration. There are no explicit Linux or cross-platform DNS server examples, nor are Linux-native DNS solutions (like BIND or dnsmasq) mentioned. The guidance assumes familiarity with Windows DNS paradigms and omits Linux-specific configuration steps or references.
Recommendations
  • Include explicit examples and references for configuring DNS forwarding and conditional forwarding using popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
  • Provide links to both Windows and Linux DNS server documentation when discussing DNS forwarders and conditional forwarders.
  • Add sample configuration snippets for Linux-based DNS servers alongside any Windows Server or Azure Firewall examples.
  • Use neutral terminology (e.g., 'DNS server' instead of 'DNS forwarder') and clarify that both Windows and Linux DNS solutions are supported.
  • Ensure diagrams and scenario descriptions mention cross-platform DNS options, not just Windows-centric tools.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/manage-private-endpoint.md .../main/articles/private-link/manage-private-endpoint.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and PowerShell is referenced as a primary management tool throughout. There is no mention of Linux-specific shell usage or examples, and the CLI examples, while cross-platform, are not explicitly shown in a Linux/bash context. Additionally, some CLI example descriptions mistakenly refer to 'Azure PowerShell command' instead of 'Azure CLI command', reinforcing the Windows-centric perspective.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is cross-platform) first to better serve Linux users.
  • Explicitly mention that Azure CLI commands can be run in Bash (Linux/macOS) and provide sample commands in bash syntax (e.g., with export statements, bash variables).
  • Correct any mislabeling of CLI examples as 'Azure PowerShell command' to avoid confusion.
  • Where possible, include notes or examples for Linux/macOS users, such as using bash variables instead of PowerShell variables.
  • Add a section or note about installing and using Azure CLI on Linux/macOS, and clarify that PowerShell is optional for management tasks.
  • Ensure screenshots and output samples are not exclusively from Windows environments (e.g., avoid showing only PowerShell output).
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-endpoint-portal.md ...rticles/private-link/create-private-endpoint-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing PowerShell for command-line operations and omitting any Linux or cross-platform shell examples. The instructions for testing connectivity on the VM assume a Windows OS (PowerShell, Windows-style nslookup output, and browser usage), with no mention of Linux alternatives or commands. There is no guidance for users who may have deployed a Linux VM, nor are there Bash or Linux command equivalents provided.
Recommendations
  • Add parallel instructions and screenshots for Linux VMs, including how to open a terminal and run equivalent commands (e.g., 'nslookup' or 'dig' in Bash).
  • Provide both PowerShell and Bash command examples for connectivity testing.
  • Clarify that the test VM can be either Windows or Linux, and offer guidance for both scenarios.
  • Include notes or callouts for any OS-specific steps, such as opening a browser or interpreting command output.
  • Ensure that any referenced tools (e.g., PowerShell) are paired with their Linux equivalents (e.g., Bash, Terminal) where appropriate.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-dns-on-premises-private-resolver.md ...vate-link/tutorial-dns-on-premises-private-resolver.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by instructing users to open Windows PowerShell on the test VM and providing only a PowerShell-based workflow for DNS testing. There are no Linux or cross-platform command-line examples, and the test VM's OS is implicitly assumed to be Windows. This may disadvantage users who prefer or require Linux-based environments.
Recommendations
  • Include explicit instructions and examples for both Windows and Linux virtual machines when testing DNS resolution (e.g., show how to use nslookup or dig in Linux shells).
  • When instructing users to open a shell, use neutral language such as 'open a terminal' and specify both Windows PowerShell and Linux Bash equivalents.
  • Provide example outputs for both Windows and Linux command-line tools.
  • Clarify that the test VM can be either Windows or Linux, and offer guidance for both OS types throughout the tutorial.
  • Where browser instructions are given, note any differences in default browsers between Windows and Linux, or use browser-neutral language.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/increase-private-endpoint-vnet-limits.md .../private-link/increase-private-endpoint-vnet-limits.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell explicitly, while not offering equivalent examples for Linux environments (e.g., Bash scripting). The CLI example is present but lacks explicit Linux context or shell usage, and PowerShell is often listed before CLI. There are no Linux-specific instructions or considerations, and the validation steps focus on PowerShell and the Azure Portal, omitting Bash or cross-platform scripting guidance.
Recommendations
  • Add Bash shell examples alongside PowerShell for all command-line instructions, especially for enabling and validating High Scale Private Endpoints.
  • Ensure CLI examples are explicitly shown in a Linux/Bash context, including export statements and shell syntax.
  • When listing multiple command-line options, alternate the order or present CLI/Bash before PowerShell to avoid 'windows_first' bias.
  • Include a section or tab for Linux users, highlighting any OS-specific considerations or differences.
  • Review validation steps to ensure parity for Linux users, such as using Azure CLI in Bash to validate configuration.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/disable-private-endpoint-network-policy.md ...rivate-link/disable-private-endpoint-network-policy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated section with detailed examples, and its capabilities (such as selective enabling of policies) are highlighted. The PowerShell example appears before the CLI example, and the CLI section notes its limitations compared to PowerShell. There is no mention of Linux-specific tools or shell environments, and the CLI examples, while cross-platform, are presented after PowerShell and described as less capable.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., bash) to reinforce cross-platform support.
  • Where PowerShell-specific features are discussed, clarify if and how they can be achieved using Azure CLI or other cross-platform tools, or note the limitation clearly.
  • Consider including Bash or shell script snippets for common tasks, or at least acknowledge the typical Linux workflow.
  • Avoid language that positions PowerShell as the primary or most capable tool unless this is strictly true for the scenario.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-endpoint-bicep.md ...articles/private-link/create-private-endpoint-bicep.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing PowerShell and RDP-based instructions for connecting to the VM and SQL Database, with no equivalent Linux or cross-platform examples. The workflow assumes the use of Windows tools (RDP, PowerShell, SQL Server Management Studio) and omits guidance for Linux users (e.g., SSH, sqlcmd, Azure Data Studio). The order of examples and tool recommendations prioritize Windows environments.
Recommendations
  • Add explicit Linux/macOS instructions for connecting to the VM (e.g., using SSH instead of RDP).
  • Provide examples for validating DNS and connecting to SQL Database using cross-platform tools such as sqlcmd or Azure Data Studio.
  • Present CLI and PowerShell deployment instructions in parallel, or default to CLI (which is cross-platform) before PowerShell.
  • Mention and link to Linux-compatible tools for database access and VM management.
  • Include notes or tabs for both Windows and Linux users throughout the quickstart, especially in sections involving remote access and command-line operations.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-endpoint-portal.md ...rticles/private-link/create-private-endpoint-portal.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by instructing users to open PowerShell on the test VM and providing only PowerShell-based command examples (e.g., nslookup). There is no mention of Linux-based alternatives, nor are Linux shell commands or tools (such as bash, dig, or curl) provided. The workflow implicitly assumes the test VM is Windows-based, and no guidance is given for users who might deploy a Linux VM.
Recommendations
  • Include parallel instructions for both Windows and Linux VMs, specifying which OS to choose during VM creation.
  • Provide Linux shell command equivalents (e.g., using bash terminal, dig, or host for DNS lookup, and curl or wget for HTTP requests).
  • Explicitly mention that the test VM can be either Windows or Linux, and offer step-by-step instructions for both environments.
  • When referencing opening a terminal, use neutral language (e.g., 'open a terminal or command prompt') and clarify the steps for each OS.
  • Add screenshots or output examples from both Windows and Linux environments to ensure parity.
GitHub Create Pull Request
← Previous Page 4 of 8 Next →