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 51-75 of 188 flagged pages
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for resource cleanup and refers to Azure PowerShell as a primary automation option, with no equivalent Linux shell (bash) or Azure CLI examples for key operations. This suggests a bias towards Windows tooling and usage patterns, potentially making it less accessible for Linux users.
Recommendations
  • Add equivalent Azure CLI (bash) commands for resource cleanup, such as 'az group delete --name <your resource group name>'.
  • Ensure that all procedural steps (deployment, validation, cleanup) include both PowerShell and CLI/bash examples side by side.
  • Mention Linux/macOS compatibility explicitly where relevant, and avoid assuming PowerShell as the default automation tool.
  • Where multiple tools are referenced (Azure portal, PowerShell, CLI), present them in a neutral order or highlight parity in capabilities.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias in several ways: the VM creation example uses a Windows image (Win2022Datacenter) without mentioning or providing a Linux alternative; connectivity testing instructions exclusively reference PowerShell and Windows GUI steps, omitting Linux shell equivalents; and the workflow assumes familiarity with Windows tools and patterns, such as PowerShell and Bastion connections, without addressing Linux SSH or shell usage.
Recommendations
  • Provide parallel examples for creating a Linux VM (e.g., using --image UbuntuLTS) alongside the Windows VM example.
  • Include Linux-based connectivity testing instructions, such as using SSH to connect to the VM and running nslookup or curl from a Bash shell.
  • Mention and demonstrate Linux command-line tools (e.g., Bash, curl, dig) for DNS and connectivity tests, not just PowerShell.
  • Clarify that Bastion can be used to connect to both Windows and Linux VMs, and provide steps for both operating systems.
  • Where GUI steps are described (such as opening a browser), note how to perform equivalent actions on Linux desktops or via command-line tools.
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: 2026-01-09 00:34
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 uses PowerShell for command-line operations, references Remote Desktop Protocol (RDP) for VM access, and recommends SQL Server Management Studio (a Windows application) for database connectivity. There are no Linux or cross-platform alternatives mentioned for connecting to the VM, querying DNS, or managing resources. The cleanup step uses a PowerShell cmdlet without mentioning Azure CLI or Bash equivalents.
Recommendations
  • Provide Linux and macOS instructions for connecting to the VM, such as using SSH instead of RDP.
  • Include Azure CLI and Bash examples for resource management tasks (e.g., deleting the resource group).
  • Suggest cross-platform database clients (such as Azure Data Studio or sqlcmd) for connecting to SQL Database.
  • Show how to perform DNS queries using Linux/macOS tools (e.g., `dig` or `nslookup` in Bash).
  • Ensure that examples and tools are presented in a platform-neutral order, or explicitly offer both Windows and Linux options side-by-side.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates bias towards Windows by exclusively referencing PowerShell for command-line operations and omitting Linux or cross-platform alternatives. The connectivity test instructions assume a Windows VM and PowerShell usage, with no mention of Linux VMs, Bash, or other shells. There are no Linux-specific examples or guidance, and Windows-centric tools and patterns are presented first and exclusively.
Recommendations
  • Include instructions for testing connectivity using a Linux VM, such as opening a Bash shell and using commands like 'nslookup' or 'curl'.
  • Provide both PowerShell and Bash command examples for DNS resolution and HTTP requests.
  • Clarify that the VM used for testing can be either Windows or Linux, and provide steps for both.
  • Reference cross-platform tools (e.g., curl, dig) alongside PowerShell.
  • Add screenshots or output examples from Linux environments where appropriate.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/disable-private-link-service-network-policy.md ...te-link/disable-private-link-service-network-policy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 listing Azure PowerShell (a Windows-centric tool) first among the example options, providing detailed PowerShell instructions, and referencing PowerShell before Azure CLI. There is no mention of Linux-specific shell environments or alternative scripting approaches, and the CLI example does not clarify compatibility with Bash or other Linux shells.
Recommendations
  • Alternate the order of example sections so that Azure CLI (cross-platform) appears before PowerShell.
  • Explicitly state that Azure CLI commands work in Bash, Cloud Shell, and other Linux environments.
  • Add notes or examples for running Azure CLI commands in Linux/macOS terminals.
  • Avoid referring to PowerShell as the primary or default method unless justified by usage data.
  • Include troubleshooting or environment setup notes for Linux users where relevant.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and referencing PowerShell validation steps, with CLI examples present but less emphasized. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell is presented before CLI in enablement and validation instructions. No Linux-specific tools or patterns are mentioned.
Recommendations
  • Add bash shell examples for enabling and validating High Scale Private Endpoints using Azure CLI, with explicit Linux syntax and environment notes.
  • Present CLI and PowerShell examples side-by-side or in parallel tabs, rather than listing PowerShell first.
  • Include notes on cross-platform compatibility for all commands, clarifying which steps work identically on Linux, macOS, and Windows.
  • Reference Linux-native tools (e.g., jq for JSON validation) where appropriate, especially in validation steps.
  • Ensure that portal instructions do not assume Windows-only conventions (e.g., file paths, UI screenshots).
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: 2026-01-09 00:34
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 in several ways. The instructions for connecting to the VM exclusively use Remote Desktop Protocol (RDP), which is primarily a Windows tool, and reference the default IIS page, which is a Windows web server. There are no examples or instructions for connecting via SSH (the standard for Linux VMs) or for deploying/test-driving Linux-based services. The walkthrough assumes the user is working with Windows VMs and tools, omitting Linux alternatives.
Recommendations
  • Add instructions for connecting to a Linux VM using SSH, including example commands for Windows, macOS, and Linux clients.
  • Include deployment and validation steps for a Linux-based web server (e.g., Apache or Nginx) in addition to IIS.
  • Provide examples for both RDP and SSH connections, and clarify which VM image is being used (Windows or Linux).
  • Mention cross-platform tools and patterns (e.g., using Azure CLI from Bash, PowerShell, or Cloud Shell) and avoid assuming a Windows-only workflow.
  • Ensure screenshots and walkthroughs are representative of both Windows and Linux 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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-centric instructions for VM connectivity (RDP, IIS), referencing Windows tools (Remote Desktop, .rdp files), and using PowerShell for resource cleanup. There are no Linux-specific examples or alternatives (e.g., SSH for VM access, Apache/Nginx for web service, Bash/Azure CLI for cleanup), and Windows patterns are presented exclusively and first.
Recommendations
  • Add instructions for connecting to Linux VMs using SSH, including example commands and expected behavior.
  • Include examples of deploying and validating Linux-based web servers (e.g., Apache or Nginx) in addition to IIS.
  • Provide Azure CLI and Bash examples for resource cleanup alongside PowerShell.
  • Mention cross-platform tools and workflows, ensuring Linux and macOS users can follow the quickstart without relying on Windows-only tools.
  • Clearly indicate when instructions are OS-specific, and offer parity for both Windows and Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell cmdlets, which are primarily used on Windows. The PowerShell tab and examples are presented before the Azure CLI tab, and there is no mention of Linux-specific tools or shell environments. While Azure CLI is cross-platform, the documentation does not explicitly provide Linux shell examples or address Linux-specific usage patterns. There are no Bash or Linux-native command examples, and the PowerShell approach is given prominence.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including sample shell syntax and environment notes.
  • Reorder the example tabs so that Azure CLI (which is cross-platform) appears before PowerShell, or at least clarify that CLI examples work on Linux, macOS, and Windows.
  • Mention that PowerShell examples are primarily for Windows users, and provide guidance for Linux users (e.g., using Azure CLI or Azure Cloud Shell).
  • Include notes or sections about using these commands in Linux environments, such as running Azure CLI in Bash or using ARM templates with Linux tools.
  • Where possible, avoid Windows-centric terminology or tools unless necessary, and strive for parity in instructions for both Windows and Linux users.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell (Windows-centric) examples before Azure CLI (cross-platform) examples, and all code samples are either PowerShell or Azure CLI. There is no mention of Linux-specific tools, shell environments, or workflows, nor are there any Bash or Linux-native command examples. The text and screenshots reference PowerShell outputs and commands, reinforcing a Windows-first perspective. There is no explicit guidance or parity for Linux users beyond the Azure CLI, and no mention of how to perform these tasks in a Linux shell environment.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
  • Include explicit Bash/Linux shell examples where possible, especially for scripting and automation tasks.
  • Add notes or sections clarifying that Azure CLI is fully supported on Linux and macOS, and provide links to installation guides for those platforms.
  • Where screenshots are used, include CLI output from a Linux terminal in addition to PowerShell output.
  • Mention that PowerShell Core is available cross-platform, and provide guidance for its use on Linux/macOS if PowerShell examples are retained.
  • Ensure terminology and instructions do not assume a Windows environment (e.g., avoid references to Windows-specific paths, tools, or UI conventions).
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-09 00:34
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 in several ways. References to DNS forwarders and conditional forwarding link to Windows Server documentation and concepts, such as Active Directory DNS and Windows DNS server configuration. There are no explicit examples or guidance for Linux-based DNS solutions (e.g., BIND, dnsmasq, Unbound), nor are Linux tools or patterns mentioned. The documentation assumes familiarity with Windows DNS tooling and does not provide parity for Linux administrators, making it less accessible for cross-platform environments.
Recommendations
  • Include examples and configuration steps for popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound) when describing DNS forwarders and conditional forwarding.
  • Add links to Linux DNS documentation and guides alongside Windows Server references.
  • Explicitly mention that DNS forwarders and conditional forwarding can be implemented on both Windows and Linux platforms, and provide sample configuration snippets for each.
  • Ensure diagrams and scenario descriptions do not implicitly assume Windows-only environments.
  • Add troubleshooting and best practices sections for Linux DNS solutions in Azure Private Endpoint scenarios.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows evidence of Windows bias in its cross-platform guidance. References to command-line tooling for creating private endpoints mention PowerShell (New-AzPrivateEndpoint) before the Azure CLI (az network private-endpoint create), and do not provide explicit Linux shell examples or guidance. There are no examples or instructions for Linux-specific tools, nor is there parity in demonstrating how to perform tasks on Linux versus Windows. The documentation assumes familiarity with Windows-centric tools and patterns, and omits Linux-first or cross-platform instructions.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell, especially when referencing Azure CLI commands.
  • List Azure CLI (cross-platform) commands before PowerShell commands to avoid Windows-first ordering.
  • Include notes or sections on how to perform private endpoint operations on Linux systems, including installation and usage of Azure CLI.
  • Avoid referencing PowerShell exclusively; ensure all command-line instructions are cross-platform or have platform-specific variants.
  • Add troubleshooting and configuration guidance relevant to Linux environments, such as DNS setup or network interface inspection using Linux tools.
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-09 00:34
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, providing PowerShell instructions before Azure CLI, and linking to a Windows VM creation guide. There is no explicit mention of Linux as an NVA platform, nor are there Linux-specific examples or references.
Recommendations
  • Include Linux as an example NVA platform in the prerequisites and throughout the guide.
  • Provide a link to the 'Create a Linux virtual machine in the Azure portal' quickstart alongside the Windows VM link.
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform.
  • Explicitly mention that the Azure CLI commands work on Linux, macOS, and Windows.
  • Where relevant, include Linux-specific considerations or troubleshooting tips for tagging resources.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments. The only explicit example for testing DNS resolution uses Windows PowerShell, with no mention of Linux equivalents (e.g., Bash, dig, or nslookup on Linux). The instructions for connecting to the test VM assume a Windows OS (PowerShell, Microsoft Edge) and do not provide steps for Linux users. There is no guidance for performing the same DNS resolution or connectivity tests from a Linux VM, nor are Linux command-line tools referenced.
Recommendations
  • Provide Linux-specific instructions and examples for testing DNS resolution (e.g., using 'dig' or 'nslookup' in Bash).
  • Include steps for connecting to the test VM using SSH, which is standard for Linux environments, in addition to Bastion/PowerShell.
  • Mention Linux browsers (e.g., Firefox, Chrome) when testing web app connectivity, or clarify that any browser can be used.
  • Add a note or section explaining how to perform all verification steps on a Linux VM, including command syntax and expected output.
  • Ensure parity by listing both Windows and Linux options for all command-line and connectivity steps.
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-09 00:34
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 Windows bias by exclusively providing instructions and examples for Windows environments. The connectivity test uses Windows PowerShell, and the installation instructions for Microsoft Azure Storage Explorer reference Windows tabs. There are no examples or guidance for Linux users, such as using Bash, Linux terminal commands, or Linux-specific installation steps for Storage Explorer. Windows tools and patterns are mentioned first and exclusively, with no Linux parity.
Recommendations
  • Add Linux-specific instructions for connecting to the VM, such as using SSH from a Linux terminal.
  • Provide Bash or Linux shell equivalents for the nslookup command and other connectivity tests.
  • Include installation steps for Microsoft Azure Storage Explorer on Linux, referencing the appropriate download and installation method.
  • Present examples for both Windows and Linux platforms side-by-side, or use tabs to allow users to select their OS.
  • Avoid referencing Windows tools exclusively; mention cross-platform alternatives where possible.
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-09 00:34
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: the VM is created with a Windows image (Win2019Datacenter) only, all connectivity and DNS verification steps use Windows PowerShell, and SQL Server Management Studio (a Windows-only tool) is the exclusive client for database connectivity. There are no examples or instructions for Linux VMs, Linux command-line tools, or cross-platform SQL clients. Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., using Ubuntu or CentOS images) alongside the Windows VM example.
  • Include Linux-based connectivity testing steps, such as using 'dig' or 'nslookup' in a Bash shell to verify DNS resolution.
  • Suggest cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd, DBeaver) and provide connection instructions for those tools.
  • Explicitly mention that the Azure CLI commands work on all platforms and clarify any OS-specific steps.
  • Where PowerShell is used, offer equivalent Bash or shell commands for Linux users.
  • Add a section or callout for MacOS users, if relevant.
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: 2026-01-08 00:53
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 uses PowerShell for command-line operations, references Remote Desktop Protocol (RDP) for VM access, and recommends SQL Server Management Studio (a Windows-only tool) for database connectivity. There are no Linux or cross-platform alternatives mentioned for connecting to the VM, querying DNS, or accessing the SQL database. The cleanup step uses a PowerShell cmdlet without offering an Azure CLI or Bash equivalent.
Recommendations
  • Provide Linux and macOS instructions for connecting to the VM, such as using SSH if the VM is Linux-based, or using open-source RDP clients for non-Windows platforms.
  • Include Azure CLI and Bash examples alongside PowerShell for resource group deletion and other command-line operations.
  • Suggest cross-platform database clients (e.g., Azure Data Studio, DBeaver) in addition to SQL Server Management Studio.
  • Add nslookup or dig command examples for DNS resolution on Linux/macOS.
  • Clearly indicate when instructions are Windows-specific and offer parity for other operating systems.
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: 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 page demonstrates Windows bias by providing PowerShell examples and referencing PowerShell validation steps, with no explicit Bash or Linux shell alternatives. The CLI example is present, but PowerShell is listed first in the enablement section and is the only method shown for validation outside the portal. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Add Bash/Linux shell examples for all CLI commands, including validation steps.
  • Present Azure CLI (cross-platform) examples before PowerShell examples, or side-by-side, to avoid Windows-first ordering.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide command syntax for Bash.
  • Include troubleshooting and validation steps using Bash/CLI, not just PowerShell.
  • Avoid assuming users have access to PowerShell; clarify platform compatibility for all commands.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing instructions and examples that prioritize Windows tools and workflows. The VM connection steps exclusively use Remote Desktop Protocol (RDP), which is a Windows-centric technology, and reference IIS (Internet Information Services), a Windows web server. The cleanup instructions use Azure PowerShell cmdlets without mentioning Azure CLI or Bash alternatives. There are no examples or guidance for Linux users, such as SSH access or Linux-based web servers.
Recommendations
  • Add instructions for connecting to the VM using SSH, which is standard for Linux VMs.
  • Include examples for accessing a Linux-based web server (e.g., Apache or Nginx) in addition to IIS.
  • Provide cleanup instructions using Azure CLI (e.g., 'az group delete') alongside PowerShell.
  • Mention both RDP and SSH options for VM access, and clarify which OS images are used in the ARM template.
  • Ensure that examples and screenshots reflect both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/configure-private-link-service-direct-connect.md ...-link/configure-private-link-service-direct-connect.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 demonstrates a Windows bias by consistently listing PowerShell instructions and examples before Azure CLI and Terraform, and by referencing PowerShell as a primary tool for configuration. There is an assumption of PowerShell availability, and no explicit mention or examples of Linux-native shell environments (e.g., Bash) outside of Azure CLI. The prerequisites and FAQs also reference PowerShell and CLI, but do not clarify cross-platform usage or provide Linux-specific guidance for prerequisites or troubleshooting.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI (Bash) first to avoid implicit Windows-first bias.
  • Explicitly state that Azure CLI commands can be run natively on Linux/macOS and in Bash shells, and provide any necessary Linux-specific installation or usage notes.
  • Add troubleshooting and prerequisite notes for Linux users, such as how to install Azure CLI and Terraform on Linux, and clarify that PowerShell Core is available cross-platform but is not required for Linux users.
  • Where PowerShell is referenced, clarify that it is optional and provide equivalent Bash/CLI instructions for all steps, including feature registration and resource cleanup.
  • Consider adding a table or section that compares usage across Windows, Linux, and macOS environments, highlighting any differences or platform-specific considerations.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias towards Windows environments by providing only a PowerShell example for resource cleanup, omitting equivalent Linux shell or Azure CLI commands. The use of the Remove-AzResourceGroup cmdlet is specific to PowerShell, which is most commonly used on Windows. There are no bash or Azure CLI examples for Linux/macOS users, and no mention of cross-platform alternatives for resource management.
Recommendations
  • Include Azure CLI examples for resource cleanup (e.g., az group delete --name <your resource group name>) alongside PowerShell commands.
  • Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide links to installation guides for each platform.
  • Where possible, provide bash script examples for common operations to improve accessibility for Linux users.
  • Review other command-line instructions to ensure parity between Windows and Linux/macOS environments.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. The instructions for connecting to the VM use RDP (Remote Desktop Protocol), which is primarily a Windows technology, and do not mention SSH or Linux-based access methods. The example for accessing the SQL Database from the VM assumes the use of PowerShell and SQL Server Management Studio, both Windows-centric tools, with no mention of Linux alternatives (such as Bash, sqlcmd, or Azure Data Studio). Throughout, Windows tools and patterns are presented exclusively, with no parity for Linux users.
Recommendations
  • Add instructions for connecting to the VM via SSH, including steps for Linux and macOS users.
  • Provide examples of accessing the SQL Database from the VM using cross-platform tools such as sqlcmd or Azure Data Studio.
  • Include Bash shell commands alongside PowerShell for deployment and validation steps.
  • Mention and demonstrate Linux-compatible remote desktop clients (e.g., Remmina, rdesktop) if RDP is required, or suggest using Linux VMs for testing.
  • Ensure that all steps (deployment, validation, cleanup) have both Windows and Linux command-line examples.
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: 2026-01-08 00:53
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 by exclusively providing instructions for connecting to the VM via Remote Desktop Protocol (RDP), which is a Windows-centric tool. There are no examples or guidance for connecting from Linux or macOS systems (e.g., using SSH). The web server installed is IIS, which is also Windows-specific, and there is no mention of Linux alternatives. The deployment and resource management examples do use both Azure CLI and PowerShell, but the VM access and validation steps are focused solely on Windows workflows.
Recommendations
  • Include instructions for connecting to the VM from Linux and macOS, such as using SSH if the VM is running Linux, or using RDP clients available on those platforms.
  • Provide examples of deploying a Linux VM and installing a web server such as Apache or Nginx, alongside the IIS example.
  • When describing how to access the service privately, include browser access instructions from Linux/macOS as well as Windows.
  • Clarify whether the Bicep template supports both Windows and Linux VMs, and if so, provide parallel steps for both OS types.
  • Add notes or tabs for platform-specific steps, ensuring parity between Windows and Linux/macOS users.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/configure-asg-private-endpoint.md ...rticles/private-link/configure-asg-private-endpoint.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 Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured as a primary automation example, and references to installing and using PowerShell locally are prominent in the prerequisites. The PowerShell tab is presented before the CLI tab in code examples, and the prerequisites section gives detailed instructions for PowerShell setup, including module installation and account connection, which are Windows-centric. While Azure CLI examples are provided (which are cross-platform), the documentation's structure and language favor Windows users and tools.
Recommendations
  • Present CLI examples before PowerShell examples to emphasize cross-platform parity.
  • Clarify that Azure CLI works natively on Linux and macOS, and provide explicit instructions for those platforms in the prerequisites.
  • Reduce the prominence of PowerShell-specific instructions, or move them to a dedicated Windows section.
  • Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI and any platform-specific considerations.
  • Ensure that references to tools and commands are balanced between Windows and Linux/macOS environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas. The VM creation example uses a Windows image (Win2022Datacenter) exclusively, and all connectivity testing instructions reference PowerShell and Windows GUI navigation. There are no Linux VM creation examples, nor instructions for testing connectivity using Linux tools (e.g., bash, dig, curl). The documentation assumes the reader is using Windows, both for the test VM and for command-line interaction, with no mention of Linux alternatives.
Recommendations
  • Include parallel examples for creating a Linux VM (e.g., using Ubuntu or CentOS images) alongside the Windows VM example.
  • Provide instructions for testing connectivity on Linux VMs, using bash commands such as 'dig', 'nslookup', or 'curl'.
  • When referencing opening a shell, specify both PowerShell (for Windows) and bash (for Linux), and provide equivalent commands.
  • Avoid assuming the use of Windows tools or GUI navigation; offer CLI-only steps that work cross-platform.
  • Explicitly mention that the Azure CLI works on both Windows and Linux, and provide guidance for both environments.
GitHub Create Pull Request
← Previous Page 3 of 8 Next →