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 101-125 of 188 flagged pages
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for connecting to the VM using RDP (a Windows protocol), opening PowerShell (a Windows shell), and using SQL Server Management Studio (a Windows-only tool). There are no Linux or cross-platform alternatives mentioned for connecting to the VM, running DNS queries, or accessing the SQL database. The cleanup instructions also use a PowerShell cmdlet without providing an Azure CLI equivalent.
Recommendations
- Include instructions for connecting to the VM using SSH, which is standard on Linux and cross-platform environments.
- Provide examples for running DNS queries using Linux tools such as 'dig' or 'nslookup' in a Bash shell.
- Mention cross-platform database tools (e.g., Azure Data Studio, sqlcmd) for connecting to SQL Database from the VM.
- Add Azure CLI commands for resource cleanup alongside the PowerShell example.
- Explicitly state when steps are Windows-specific and offer equivalent Linux/macOS guidance where possible.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing only a PowerShell example (`Remove-AzResourceGroup`) for resource cleanup, with no equivalent Azure CLI or Bash command. There is no mention of Linux-native tools or examples, and the only command-line example uses a Windows-centric tool (Azure PowerShell).
Recommendations
- Add equivalent Azure CLI (az group delete) and Bash examples alongside PowerShell for resource cleanup.
- Wherever PowerShell is mentioned, also mention Azure CLI as an alternative, and provide both command syntaxes.
- Explicitly state that all steps can be performed from any OS using Azure CLI or the Azure Portal, not just PowerShell.
- Consider including a table or section comparing PowerShell and CLI commands for common tasks to improve Linux parity.
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 →
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 tool. There are no instructions for connecting to Linux VMs (e.g., via SSH), nor any mention of Linux-based scenarios. The example assumes the deployed VM is running Windows (IIS web server, RDP connection), and does not provide parity for Linux users.
Recommendations
- Include parallel instructions for deploying and connecting to a Linux VM (e.g., using SSH instead of RDP).
- Provide examples for installing and accessing a web server on Linux (such as Apache or Nginx) in addition to IIS.
- Clarify in the Bicep file review section whether the template supports both Windows and Linux VMs, and if so, provide guidance for both.
- When listing connection methods, mention SSH and RDP equally, and provide step-by-step instructions for both.
- Ensure screenshots and walkthroughs reflect both Windows and Linux scenarios where applicable.
Private Link
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-endpoint-cli.md
...n/articles/private-link/create-private-endpoint-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: the VM creation example uses a Windows image (Win2022Datacenter) without mentioning or providing a Linux alternative; the connectivity test instructs users to open PowerShell and does not mention Linux shells or commands; and the overall flow assumes a Windows environment for testing and interaction. There are no Linux-specific instructions or parity in examples, and Windows tools (PowerShell) are referenced exclusively.
Recommendations
- Provide parallel Linux examples throughout, such as creating a VM with a popular Linux image (e.g., UbuntuLTS) alongside the Windows example.
- In the connectivity test section, include Linux shell commands (e.g., using bash and nslookup or dig) and clarify that the steps apply to both Windows and Linux VMs.
- Explicitly mention that the Azure CLI commands work cross-platform and that users can choose either Windows or Linux VMs for testing.
- Where PowerShell is referenced, also mention the equivalent Linux shell (bash) and provide command syntax for both.
- Consider alternating the order of Windows and Linux examples or presenting them side-by-side to avoid a 'windows_first' impression.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by providing only Windows-centric instructions for connecting to the VM (using RDP and .rdp files), referencing Windows tools (IIS, RDP), and giving a PowerShell-only example for resource cleanup. There are no Linux/SSH examples or mentions of Linux tools, and Windows patterns are presented exclusively.
Recommendations
- Add parallel instructions for connecting to the VM via SSH for Linux-based VMs, including how to obtain the public IP and use an SSH client.
- Include examples for cleaning up resources using Azure CLI (az group delete) and Bash scripts, not just PowerShell.
- Mention Linux-based web servers (such as Apache or Nginx) as alternatives to IIS, or clarify if the template can deploy Linux VMs.
- When referencing connection methods, present both Windows (RDP) and Linux (SSH) options, or clarify OS-specific steps.
- Ensure that all code snippets and tool references have Linux equivalents or alternatives.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides step-by-step instructions and code samples for managing network policies using the Azure portal, Azure PowerShell, Azure CLI, and ARM templates. PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, and is listed before the Azure CLI. There are no Linux shell (bash) or cross-platform scripting examples, and the CLI section is less detailed regarding selective policy enablement. The documentation assumes familiarity with PowerShell and Windows tooling, which may disadvantage Linux users.
Recommendations
- Add bash shell examples for Azure CLI commands, demonstrating usage in a typical Linux environment.
- Clarify that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux, reducing the perceived need for PowerShell.
- Consider listing Azure CLI examples before PowerShell, as CLI is more platform-agnostic.
- Provide notes or links for installing and using Azure CLI on Linux/macOS.
- Where PowerShell is used, mention cross-platform PowerShell Core if relevant, or clarify OS requirements.
- Ensure parity in feature explanation between PowerShell and CLI sections, especially regarding selective policy enablement.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell examples and referencing the Azure Portal UI, both of which are more familiar to Windows users. While an Azure CLI example is included, it is presented after PowerShell, and there are no explicit Linux shell (bash) or cross-platform scripting examples. There is also no mention of Linux-specific tools or guidance for Linux administrators.
Recommendations
- Present Azure CLI (which is cross-platform) examples before PowerShell to avoid implying Windows-first workflows.
- Include bash shell examples for common tasks, especially for validation steps, to assist Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for Linux users where appropriate.
- Where PowerShell is used, clarify if the commands are compatible with PowerShell Core on Linux/macOS, or provide alternative bash/CLI scripts.
- Expand validation instructions to include command-line methods (e.g., using az CLI and jq) for Linux users, not just Portal and PowerShell.
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias, particularly in its references to DNS forwarders and conditional forwarding. It references Windows Server DNS concepts and documentation, and does not provide explicit Linux/BIND/unbound examples or mention Linux DNS solutions. The term 'DNS forwarder' is used generically, but links and explanations are Windows-centric. There are no command-line or configuration examples for either platform, but the only external DNS implementation guidance points to Windows Server. Linux DNS solutions are not mentioned, and there are no Linux-specific configuration links or examples.
Recommendations
- Include explicit references to Linux DNS solutions (e.g., BIND, dnsmasq, Unbound) alongside Windows DNS when discussing DNS forwarders and conditional forwarding.
- Provide links to documentation for configuring conditional forwarding on common Linux DNS servers.
- Add example configuration snippets for both Windows Server DNS and Linux-based DNS servers.
- Use neutral language when describing DNS solutions (e.g., 'DNS server' instead of 'Windows DNS server'), and avoid linking only to Windows documentation.
- Where diagrams or scenarios mention DNS forwarders, clarify that both Windows and Linux DNS servers are supported, and provide parity in guidance.
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 →
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 PowerShell-based instructions for DNS testing. There is no mention of Linux alternatives or examples, and the test VM is implicitly assumed to be running Windows. No Linux command-line examples (such as using 'dig' or 'nslookup' on Linux) are provided, nor is there guidance for Linux-based test VMs.
Recommendations
- Include instructions for both Windows and Linux test VMs, specifying how to open a terminal or shell on each platform.
- Provide equivalent Linux commands for DNS resolution testing (e.g., 'nslookup' and 'dig' on Linux).
- Explicitly state that the test VM can be either Windows or Linux, and provide steps for both.
- Avoid assuming the use of Windows tools (like PowerShell or Microsoft Edge) exclusively; mention alternatives such as Bash shell and Firefox/Chromium for Linux.
- Where possible, present Linux examples before or alongside Windows examples to ensure parity.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell, and the tutorial assumes the use of Windows-based tools and workflows throughout. The virtual machine created is explicitly a Windows Server VM, and the connectivity test instructions rely on Windows PowerShell and SQL Server Management Studio, both of which are Windows-centric. There are no examples or guidance for using Azure CLI, Bash, Linux VMs, or cross-platform SQL tools.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside or as an alternative to the PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include instructions for creating and using a Linux-based virtual machine, with examples for both Windows and Linux VMs.
- Offer connectivity test steps using Bash (e.g., nslookup or dig) and cross-platform SQL clients such as sqlcmd or Azure Data Studio.
- Mention and demonstrate installation and use of cross-platform tools, not just Windows-specific ones like SQL Server Management Studio.
- Structure the tutorial so that Linux and Windows options are presented equally, or provide clear sections for each platform.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and in some cases, the narrative and screenshots are PowerShell-focused. There is no mention of Linux-native tools or shell scripting, and the CLI examples, while cross-platform, are sometimes described as 'PowerShell commands' or use Windows-style variable assignment. The documentation assumes familiarity with PowerShell, which may disadvantage Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh syntax for variable assignment in CLI examples.
- Ensure screenshots and output samples are not PowerShell-specific, or provide CLI/Linux equivalents.
- Avoid referring to CLI examples as 'PowerShell commands' and clarify the shell context for each example.
- Consider including links or references to Linux-native tools or scripting environments where relevant.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All command-line examples use Windows PowerShell, and there are no Linux or cross-platform shell equivalents. The instructions for testing connectivity and installing Microsoft Azure Storage Explorer are written as if the user is on a Windows VM, with no mention of Linux or macOS alternatives. The Storage Explorer installation link defaults to Windows, and there are no Bash or Linux command examples for DNS resolution or connectivity testing.
Recommendations
- Provide equivalent Linux (Bash) and macOS command-line examples alongside PowerShell, such as using 'nslookup' or 'dig' in Bash.
- Clarify that Microsoft Azure Storage Explorer is available on Windows, Linux, and macOS, and provide installation instructions or links for all platforms.
- When instructing users to open a shell, specify both PowerShell (for Windows) and Bash/Terminal (for Linux/macOS), with corresponding commands.
- Avoid assuming the VM is running Windows; include steps for both Windows and Linux VMs, or specify OS-agnostic instructions where possible.
- Where possible, use cross-platform tools and commands, or clearly indicate platform-specific steps.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The tutorial demonstrates a strong Windows bias in the testing and connectivity sections. The only example for connecting to the test VM uses a Windows Server image, instructs users to open Windows PowerShell, and uses Windows-specific tools like SQL Server Management Studio (SSMS). There are no instructions or examples for Linux-based VMs, nor for using cross-platform tools (e.g., sqlcmd, Azure Data Studio) to connect to the SQL server. The documentation assumes a Windows environment for testing and omits Linux alternatives.
Recommendations
- Provide parallel instructions for creating a Linux-based VM (e.g., Ubuntu) in the 'Create test virtual machine' section, including the appropriate --image parameter.
- In the 'Test connectivity to private endpoint' section, include Linux shell equivalents for DNS resolution (e.g., using 'nslookup' or 'dig' in bash) and SQL connectivity (e.g., using 'sqlcmd' or Azure Data Studio).
- Mention and demonstrate cross-platform tools (such as Azure Data Studio and sqlcmd) for connecting to Azure SQL, not just Windows-only tools like SSMS.
- Avoid assuming the use of Windows PowerShell; provide bash or shell command alternatives where appropriate.
- Explicitly state that the tutorial can be followed on both Windows and Linux, and provide branching instructions or notes where steps differ.
Private Link
Configure Private Link service Direct Connect
...-link/configure-private-link-service-direct-connect.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently and is listed first in all code example tabs, followed by Azure CLI and Terraform. Prerequisites and instructions frequently mention Azure PowerShell and provide links to its installation, which is primarily a Windows-centric tool (though available cross-platform). Azure CLI examples are present and cross-platform, but PowerShell's placement and emphasis may signal a Windows-first approach. There are no Linux/macOS-specific shell examples (e.g., bash scripts), and no mention of Linux-specific considerations or troubleshooting. All tooling is Azure-centric, but the ordering and emphasis favor Windows users.
Recommendations
- Rotate the order of example tabs so that Azure CLI (which is cross-platform) appears first, or randomize tab order.
- Explicitly state that Azure CLI and Terraform are fully supported on Linux/macOS and provide links to their installation for those platforms.
- Add bash script examples for common tasks (resource creation, cleanup) to demonstrate parity and usability for Linux/macOS users.
- Mention that Azure PowerShell is available on Linux/macOS, and provide installation instructions for those platforms.
- Include troubleshooting notes relevant to Linux/macOS environments (e.g., shell differences, permissions, path issues).
Private Link
Quickstart - Create a network security perimeter - ARM Template
...ate-link/create-network-security-perimeter-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell example for resource cleanup, omitting equivalent Azure CLI or Bash commands commonly used on Linux/macOS. The explicit use of the Remove-AzResourceGroup cmdlet and lack of cross-platform alternatives demonstrates a Windows/PowerShell bias, especially in the 'Clean up resources' section. No Linux/macOS-specific instructions or examples are given.
Recommendations
- Add Azure CLI and Bash examples for resource group deletion (e.g., 'az group delete --name <your resource group name> --yes --no-wait').
- Wherever PowerShell is used, provide equivalent CLI commands side-by-side.
- Explicitly mention that both PowerShell and CLI are supported and link to relevant cross-platform documentation.
- Review other sections for implicit Windows-first assumptions and ensure parity in tooling and instructions.
Private Link
Quickstart: Create a private endpoint - Azure CLI
...n/articles/private-link/create-private-endpoint-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias primarily in the virtual machine creation and connectivity testing sections. The VM is created using a Windows image (Win2022Datacenter) with no mention of Linux alternatives. The connectivity test instructs users to open PowerShell and run nslookup, which is a Windows-centric workflow. There are no Linux/macOS examples or instructions for connecting to the VM or running equivalent commands (e.g., using SSH and a Linux shell).
Recommendations
- Provide parallel instructions for creating a Linux VM (e.g., using Ubuntu or CentOS images) alongside the Windows VM example.
- Include connectivity test steps for Linux/macOS users, such as connecting via SSH and running nslookup or dig from a Bash shell.
- Mention cross-platform tools and workflows, ensuring that Linux/macOS users can follow all steps without needing to adapt Windows-specific instructions.
- Clarify that the Azure CLI is cross-platform and provide shell-agnostic command examples where possible.
Private Link
Quickstart: Create a private endpoint - Bicep
...articles/private-link/create-private-endpoint-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The instructions for connecting to the VM and accessing the SQL Database are exclusively Windows-centric, relying on RDP and PowerShell, with no mention of Linux/macOS alternatives (e.g., SSH, Bash, or cross-platform SQL clients). Windows tools and patterns (RDP, PowerShell, SQL Server Management Studio) are presented as the default and only options, leaving Linux/macOS users without clear guidance for completing the quickstart.
Recommendations
- Add instructions for connecting to the VM using SSH, which is the standard method for Linux/macOS users.
- Provide examples for running deployment commands in Bash (Azure CLI) and clarify that Azure CLI works cross-platform.
- Suggest cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) for accessing the SQL Database from the VM.
- Include notes or tabs for Linux/macOS users in all relevant sections, especially for remote access and command-line operations.
- Explicitly mention that the VM can be deployed with Linux images and provide equivalent steps for those scenarios.
Private Link
Quickstart: Create a private endpoint - Azure portal
...rticles/private-link/create-private-endpoint-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the connectivity testing section, where only PowerShell is mentioned for command-line operations 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 lack of mention of Linux tools or workflows. This may create friction for users deploying Linux VMs or accessing from non-Windows environments.
Recommendations
- Include equivalent Linux/macOS instructions for connectivity testing, such as using Bash and the 'nslookup' or 'dig' commands.
- Clarify whether the VM can be Windows or Linux, and provide guidance for both scenarios.
- When referencing command-line operations, offer both PowerShell and Bash/Terminal examples side by side.
- Explicitly state that the Bastion connection supports both Windows and Linux VMs, if applicable.
Private Link
Quickstart: Create a private endpoint - Terraform
...cles/private-link/create-private-endpoint-terraform.md
Medium Priority
View Details →
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 shown after CLI. However, there are no explicit Linux/macOS shell examples for resource verification, and PowerShell is a Windows-centric tool. The cleanup and troubleshooting sections do not mention OS-specific steps, but the verification section could be more inclusive for Linux/macOS users.
Recommendations
- Add explicit Bash/Linux/macOS shell examples for verification steps, especially for users who may not use PowerShell.
- Clarify that Azure CLI commands work cross-platform and provide sample output for both Windows (CMD/PowerShell) and Linux/macOS (Bash).
- If PowerShell is included, mention that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
- Ensure that any references to tools or scripts do not assume a Windows environment by default.
Private Link
Quickstart: Create a private endpoint - ARM template
...icles/private-link/create-private-endpoint-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates notable Windows bias by exclusively providing instructions for connecting to the VM via RDP (a Windows protocol), using PowerShell for DNS validation, and recommending 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 (e.g., dig or nslookup in Linux/macOS), or accessing the SQL database (e.g., Azure Data Studio, sqlcmd, or other cross-platform tools). The 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, including how to retrieve SSH credentials and use the SSH client.
- Provide Linux/macOS equivalents for DNS resolution (e.g., using 'nslookup' or 'dig' in a Linux terminal).
- Recommend cross-platform database clients such as Azure Data Studio or 'sqlcmd', and provide connection instructions for these tools.
- Include Azure CLI commands for resource cleanup alongside PowerShell examples.
- Clearly indicate which steps are Windows-specific and offer alternatives for other platforms.
Private Link
Quickstart: Create a private link service - ARM template
...s/private-link/create-private-link-service-template.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page exhibits a notable Windows bias. Remote Desktop Protocol (RDP) is presented as the sole method for connecting to the VM, with no mention of SSH or Linux/macOS alternatives. The cleanup step exclusively uses the PowerShell Remove-AzResourceGroup cmdlet, omitting Azure CLI or Bash equivalents. All connection instructions and tooling references assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
- Add SSH connection instructions for Linux/macOS users, including how to obtain the VM's public IP and connect via ssh.
- Provide Azure CLI examples for resource group deletion (e.g., az group delete --name <name>) alongside PowerShell.
- Mention cross-platform tools and workflows where possible, and avoid assuming RDP is the only access method.
- Present examples for both Windows and Linux/macOS users, or clarify platform requirements at the start.
Private Link
Manage network policies for private endpoints
...rivate-link/disable-private-endpoint-network-policy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides detailed PowerShell examples for managing network policies, which are primarily Windows-centric. PowerShell is featured as a main method, with explicit code samples and references to Windows-specific cmdlets. There is no mention of Linux/macOS equivalents for PowerShell, nor any guidance for using PowerShell Core cross-platform. The Azure CLI is included, which is cross-platform, but its example is less flexible and lacks parity with the PowerShell example. PowerShell examples are presented before CLI examples, reinforcing a Windows-first approach.
Recommendations
- Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, and provide installation instructions or links.
- Provide Bash and/or shell script examples for Linux/macOS users where possible, especially for tasks that are more flexible in PowerShell.
- Ensure CLI examples have feature parity with PowerShell examples, or note limitations and provide workarounds.
- Consider presenting CLI examples before PowerShell, or in parallel, to avoid Windows-first ordering.
- Explicitly state platform compatibility for each method (Portal, PowerShell, CLI, ARM template).
Private Link
Increase Private Endpoint virtual network limits
.../private-link/increase-private-endpoint-vnet-limits.md
Medium Priority
View Details →
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, but not for Bash or other Linux-native tools. The CLI example uses Azure CLI, which is cross-platform, but the overall pattern prioritizes Windows tooling and workflows.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell, or side-by-side.
- Add Bash shell examples for validation steps (e.g., using az CLI to check properties).
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Include notes for Linux/macOS users on how to install and use Azure CLI.
- Avoid using only PowerShell for validation; provide equivalent az CLI or REST API examples.
Private Link
Azure Private Endpoint DNS Integration Scenarios
...icles/private-link/private-endpoint-dns-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Windows-centric DNS concepts and tools, such as conditional forwarders and DNS forwarders, with links to Windows Server documentation. It uses terminology and patterns familiar to Windows administrators (e.g., conditional forwarders, referencing Windows Server DNS documentation) and does not provide Linux-specific examples or mention Linux DNS solutions (such as BIND, dnsmasq, or systemd-resolved). The examples and configuration steps are generic but implicitly assume a Windows environment for on-premises DNS, creating friction for Linux users.
Recommendations
- Add explicit examples and guidance for configuring DNS forwarding and conditional forwarding using common Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
- Include references to Linux documentation for DNS concepts alongside Windows Server links.
- Clarify that DNS forwarders and conditional forwarders can be implemented on both Windows and Linux platforms, and provide sample configuration snippets for each.
- Mention cross-platform tools and best practices for DNS management in hybrid environments.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its testing and verification instructions. The only explicit example for DNS resolution uses Windows PowerShell, and there are no Linux/macOS command-line equivalents (e.g., dig, nslookup in bash) or instructions for connecting to the test VM from non-Windows systems. The tutorial implicitly assumes the test VM is running Windows, and Windows tools (PowerShell, Microsoft Edge) are mentioned exclusively.
Recommendations
- Include Linux/macOS command-line examples for DNS resolution, such as using 'dig' or 'nslookup' in bash.
- Clarify whether the test VM can be Linux-based, and provide instructions for both Windows and Linux VM scenarios.
- Provide guidance for connecting to the VM from Linux/macOS clients, not just via Bastion/Edge.
- Mention cross-platform browsers (e.g., Chrome, Firefox) instead of only Microsoft Edge.
- Ensure all steps that reference OS-specific tools have equivalent instructions for Linux/macOS users.