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 151-175 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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides verification steps using both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence and detail as the CLI example. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) can indicate a subtle Windows bias, especially since no Linux-specific shell examples (such as Bash) or explicit Linux verification steps are provided. There are no references to Linux tools or patterns, and the documentation does not mention or prioritize Linux environments or troubleshooting.
Recommendations
  • Add explicit Bash shell examples for verification steps, showing how to run Azure CLI commands on Linux.
  • Clarify that Azure CLI commands work cross-platform, and provide notes or links for installing CLI on Linux.
  • If PowerShell is included, add a note that PowerShell Core is available on Linux and macOS, or provide examples using Bash/zsh.
  • Include troubleshooting tips or resource cleanup steps specific to Linux environments.
  • Consider reordering verification steps to present Azure CLI (cross-platform) before PowerShell, or provide a Linux-first example.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-endpoint-dns.md ...lob/main/articles/private-link/private-endpoint-dns.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias primarily through its terminology and references. The DNS zone names, public DNS forwarders, and examples are heavily oriented toward Microsoft/Windows-centric domains (e.g., *.windows.net, *.azure.com), and the only explicit mention of host file modification refers to 'the host file on a virtual machine' without specifying platform, but the context and Azure's historical documentation patterns imply Windows as the default. There are no explicit PowerShell or Windows-only command examples, but the documentation does not provide parity examples or guidance for Linux environments (e.g., /etc/hosts, Linux DNS tools). Additionally, the references to region codes and retrieval commands use Azure CLI, which is cross-platform, but the overall framing and naming conventions are Windows-centric.
Recommendations
  • Explicitly mention both Windows and Linux methods for host file overrides (e.g., C:\Windows\System32\drivers\etc\hosts and /etc/hosts).
  • Provide example DNS configuration steps for both Windows (using PowerShell, Windows DNS Manager) and Linux (using dig, resolvectl, systemd-resolved, BIND, etc.).
  • Clarify that Azure CLI commands are cross-platform and provide any OS-specific caveats if relevant.
  • Where possible, avoid assuming Windows as the default platform; use neutral language such as 'on your operating system' or 'on your VM (Windows or Linux)'.
  • Add explicit notes or links to Linux DNS management documentation for parity.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/private-link-service-overview.md ...articles/private-link/private-link-service-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell (a Windows-centric tool) as the first method for creating a Private Link Service in the 'Next steps' section, before mentioning Azure CLI (which is cross-platform). There are no explicit Linux-specific examples, nor are Linux-native tools or shell patterns referenced anywhere in the main content. The page implicitly prioritizes Windows tooling and patterns, which may disadvantage Linux users.
Recommendations
  • List Azure CLI (cross-platform) before Azure PowerShell in 'Next steps' to avoid implying Windows-first workflows.
  • Add explicit Linux shell examples or references (e.g., bash, zsh) when discussing command-line operations.
  • Include links or sections for Linux-specific guidance, such as using Azure CLI on Linux, or integrating with Linux-based backend services.
  • Ensure parity in examples and instructions for both Windows and Linux environments throughout the documentation.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing PowerShell for command-line operations and omitting any Linux-specific instructions or examples. The connectivity test assumes the use of PowerShell within the VM, with no mention of Bash, Linux terminal, or cross-platform alternatives. This may disadvantage users who deploy Linux-based VMs or prefer non-Windows environments.
Recommendations
  • Include Linux/Bash equivalents for command-line instructions, such as using 'nslookup' or 'dig' in a Linux terminal.
  • Clarify that the VM used for testing can be either Windows or Linux, and provide steps for both.
  • Avoid assuming PowerShell as the default shell; mention alternatives like Bash or sh.
  • Add screenshots or output examples from Linux environments where relevant.
  • Explicitly state cross-platform compatibility for all steps involving VM connectivity and testing.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents PowerShell as the first example, followed by Azure CLI and ARM template examples. PowerShell is a Windows-centric tool, and its prioritization may suggest a Windows bias. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific patterns or considerations. The CLI example is cross-platform, but the ordering and emphasis favor Windows users.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell to avoid Windows-first bias.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Provide Bash script examples or usage notes for Linux users where relevant.
  • Clarify that PowerShell is primarily for Windows, and suggest alternatives for Linux users.
  • Add a section or note highlighting Linux-specific considerations or troubleshooting.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell example is given equal prominence to the CLI example, and both are presented as primary options. There is no explicit Linux shell (bash) example, and the CLI example uses generic 'console' syntax, which may not be fully Linux-specific. The documentation does not mention or show Linux-specific tools or patterns, and PowerShell (a Windows-centric tool) is given a dedicated section.
Recommendations
  • Explicitly provide Linux shell (bash) examples for all command-line steps, especially for verification and resource management.
  • Clearly indicate which commands are cross-platform and which are Windows-specific.
  • If PowerShell is included, ensure that bash/Linux shell examples are given equal or greater prominence, ideally listed first.
  • Mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any necessary notes for Linux users (e.g., differences in environment variable syntax).
  • Consider adding a 'Linux/macOS' tab or section for verification steps, demonstrating the same workflow in a Linux-native environment.
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents the PowerShell example before the Azure CLI example, which may suggest a Windows-first approach. The PowerShell section is more detailed, and there is no explicit mention of Linux or Bash environments, even though Azure CLI is cross-platform. There are no Linux-specific instructions or clarifications.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash-specific context or examples if there are any differences or prerequisites for Linux users.
  • Balance the level of detail between PowerShell and CLI sections to avoid favoring Windows users.
  • Consider including a short note or section for Linux users, especially if there are environment-specific considerations.
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation shows a mild Windows bias by referencing Windows resources first and linking only to Windows-specific VM creation guides. While both PowerShell and Azure CLI examples are provided (ensuring cross-platform command-line parity), the prerequisite section and example ordering prioritize Windows tools and patterns.
Recommendations
  • In the prerequisites, provide links to both Windows and Linux VM creation guides, not just Windows.
  • When referencing PowerShell and Azure CLI, clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider alternating the order of PowerShell and CLI examples or explicitly noting that both are supported on all platforms.
  • Add a note or section for Linux administrators, highlighting that all features and steps are equally applicable to Linux-based NVAs and VMs.
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits a mild Windows bias. In the section describing how to create a private endpoint using an alias, the PowerShell cmdlet (New-AzPrivateEndpoint) is mentioned before the Azure CLI equivalent (az network private-endpoint create). No Linux-specific tools or examples are provided, and the documentation does not mention or link to Bash or Linux shell scripting. However, the overall content is mostly platform-neutral, with the only notable bias being the order of tool references and the use of PowerShell cmdlets.
Recommendations
  • When referencing command-line tools, list Azure CLI (az) examples before or alongside PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux.
  • Include explicit Linux/Bash shell examples where relevant, especially in sections that mention command-line operations.
  • Where possible, clarify that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, and provide links to platform-specific installation guides.
  • Review other related articles (such as quickstarts and tutorials) to ensure Linux parity in examples and screenshots.
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents the PowerShell (Windows-centric) example before the Azure CLI example, and provides detailed PowerShell instructions. While Azure CLI is cross-platform, the ordering and emphasis on PowerShell may suggest a Windows-first bias. No Linux-specific shell or environment details are mentioned.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider providing bash shell context or notes for Linux users, such as environment setup or prerequisites.
  • If PowerShell is shown, clarify that PowerShell Core is cross-platform, or provide bash equivalents where appropriate.
  • Ensure parity in explanation detail and troubleshooting notes for both PowerShell and CLI sections.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell example is given equal prominence and is included directly after the CLI example. There are no explicit Linux shell (bash) or cross-platform command-line examples beyond Azure CLI, and PowerShell is a Windows-centric tool (despite cross-platform support, it is still most familiar to Windows users). There are no references to Linux-specific tools or workflows, and no mention of running commands in a Linux environment or using bash scripts.
Recommendations
  • Clearly indicate that Azure CLI commands work on both Windows and Linux, and provide bash-specific examples or notes where relevant.
  • If including PowerShell, clarify that it is available cross-platform, or provide bash equivalents for all PowerShell commands.
  • Consider adding a section or tab specifically for Linux/bash users, especially for verification and troubleshooting steps.
  • Avoid presenting PowerShell as the default or only alternative to Azure CLI; mention bash or Linux shell usage explicitly.
  • Where possible, use generic shell commands (e.g., export instead of $var=...) in addition to PowerShell syntax.
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows virtual machines first and exclusively in the prerequisites, and by linking only to the Windows VM creation quickstart. There is no mention or example of deploying or managing Linux-based NVAs, nor are Linux-specific resources or patterns referenced. While the command-line examples use Azure CLI (which is cross-platform) and PowerShell (which is available on both Windows and Linux), the overall framing and examples prioritize Windows environments.
Recommendations
  • Add a link to the 'Quickstart: Create a Linux virtual machine in the Azure portal' alongside the Windows VM quickstart in the prerequisites.
  • Explicitly mention that NVAs can be Linux-based and provide guidance or examples for Linux VM scenarios.
  • Ensure that references to VM creation, management, and tagging are not Windows-specific, and clarify that the steps apply equally to Linux and Windows NVAs.
  • Where possible, provide parity in documentation for both Windows and Linux environments, including troubleshooting or validation steps that may differ between OS types.
GitHub Create Pull Request
Private Link Quickstart - Create a network security perimeter - Bicep ...rivate-link/create-network-security-perimeter-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and cleaning up resources. However, PowerShell examples are given equal prominence to CLI, and the CLI instructions do not mention Linux/macOS explicitly. There is a slight Windows-first bias in the ordering and presentation, as PowerShell (a Windows-centric tool) is presented as a primary option alongside CLI, and no explicit mention is made of Bash or Linux/macOS environments.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh) for Linux/macOS users.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
  • Add notes or links for installing Azure CLI on Linux/macOS.
  • If relevant, mention any OS-specific considerations for file paths or command syntax.
GitHub Create Pull Request
Private Link Configure an application security group with a private endpoint ...rticles/private-link/configure-asg-private-endpoint.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation displays moderate Windows bias: PowerShell examples are provided alongside Azure CLI, and PowerShell is referenced in prerequisites and instructions. PowerShell is a Windows-centric tool, and its mention precedes CLI in some sections. However, Azure CLI examples are present and are cross-platform, and the portal instructions are platform-neutral. There are no critical sections that are Windows-only, and Linux/macOS users can complete all tasks using CLI or portal.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Present CLI examples before PowerShell examples to reduce Windows-first perception.
  • Clarify that PowerShell can be used on macOS/Linux, or link to installation guides for those platforms.
  • Add a note for Linux/macOS users highlighting CLI as the recommended automation tool.
  • Ensure that all instructions referencing PowerShell also mention CLI as an alternative.
GitHub Create Pull Request
Private Link Disable network policies for Azure Private Link service source IP address ...te-link/disable-private-link-service-network-policy.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation presents PowerShell (Windows-centric) instructions first, followed by Azure CLI and JSON template examples. The PowerShell example is detailed and assumes familiarity with Windows tools, while the CLI example is more succinct. There is no explicit mention of Linux/macOS environments or shell-specific considerations, and no Bash or cross-platform scripting guidance is provided.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash or shell scripting examples for Linux/macOS users where appropriate.
  • Clarify any platform-specific requirements or differences in the introductory section.
  • Consider removing the ordering bias by using tabs or grouping examples without prioritizing Windows tools.
GitHub Create Pull Request
Private Link Manage Azure private endpoints .../main/articles/private-link/manage-private-endpoint.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major tasks, ensuring Linux/macOS users can follow along. However, PowerShell (a Windows-centric tool) is consistently presented first in each section, and screenshots are only shown for PowerShell output. The narrative and examples often reference PowerShell commands and parameters before their CLI equivalents, and some descriptive text mistakenly refers to CLI examples as PowerShell. No Linux/macOS-specific shell examples (e.g., Bash) or screenshots are provided.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so CLI is sometimes shown first.
  • Provide output screenshots for both PowerShell and Azure CLI commands.
  • Correct narrative errors that refer to CLI examples as PowerShell.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider adding Bash script examples where appropriate.
  • Add a short section on tool choice for different platforms (Windows, Linux, macOS).
GitHub Create Pull Request
Private Link Disable SNAT requirement for Azure private endpoint traffic through NVA ...ain/articles/private-link/private-link-disable-snat.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows virtual machines as the default NVA example and linking only to the Windows VM creation guide. The prerequisites and examples prioritize Windows tools and patterns, with no mention of Linux VM deployment or Linux-specific considerations. However, the actual configuration steps (tagging via Portal, PowerShell, and Azure CLI) are cross-platform and do not prevent Linux/macOS users from completing the task.
Recommendations
  • Include links to both Windows and Linux VM deployment guides in the prerequisites.
  • Clarify that the NVA can be any supported OS, not just Windows.
  • Add a note or section highlighting Linux VM scenarios and any OS-specific considerations.
  • Ensure examples and references are balanced between Windows and Linux where applicable.
GitHub Create Pull Request
Private Link Quickstart - Create a network security perimeter - Bicep ...rivate-link/create-network-security-perimeter-bicep.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup, but PowerShell (a Windows-centric tool) is given equal prominence and shown immediately after CLI. There is no explicit mention of Linux/macOS environments, nor are there any platform-specific notes or guidance for non-Windows users. The CLI examples are cross-platform, but the inclusion and prominence of PowerShell may signal a slight Windows bias.
Recommendations
  • Clearly state that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform users.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
  • Consider listing CLI examples first to emphasize cross-platform compatibility.
  • If relevant, mention installation instructions or prerequisites for CLI and PowerShell on different operating systems.
  • Include a brief section or link for Linux/macOS users, confirming that all steps are supported on those platforms.
GitHub Create Pull Request
Private Link Configure an application security group with a private endpoint ...rticles/private-link/configure-asg-private-endpoint.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for configuring an application security group with a private endpoint using the Azure Portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to CLI, but PowerShell is a Windows-centric tool and is referenced before CLI in some sections. The prerequisites section details PowerShell installation and usage, which is primarily relevant for Windows users, and mentions Windows-specific patterns (e.g., Get-Module, Connect-AzAccount) before CLI equivalents. However, Azure CLI instructions are present and cross-platform, and no critical functionality is locked to Windows-only tools.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform.
  • Clarify that PowerShell Core is available on Linux/macOS, or link to installation guides for non-Windows platforms.
  • Where PowerShell is mentioned in prerequisites, add equivalent CLI instructions or highlight CLI as the preferred cross-platform tool.
  • Explicitly state that all tasks can be completed on Linux/macOS using Azure CLI.
  • Add notes or links for Linux/macOS users to ensure parity in installation and usage instructions.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Terraform ...cles/private-link/create-private-endpoint-terraform.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is present and PowerShell is a Windows-centric tool. The CLI example uses bash syntax, which is cross-platform, but the PowerShell example is given equal prominence, and no explicit Linux/macOS-specific instructions or troubleshooting are provided. There is a slight Windows-first bias in the inclusion of PowerShell, but not to the exclusion of Linux users.
Recommendations
  • Add explicit instructions or tabs for Linux/macOS users, such as using Bash or Zsh.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider including troubleshooting steps or notes for common Linux/macOS issues (e.g., SSH key permissions, CLI installation).
  • If PowerShell is shown, mention that PowerShell Core is available cross-platform, or provide a Bash-only example.
  • Ensure that any referenced scripts or commands do not assume Windows paths or conventions.
GitHub Create Pull Request
Private Link Disable network policies for Azure Private Link service source IP address ...te-link/disable-private-link-service-network-policy.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation presents PowerShell instructions first, which are most relevant to Windows users, followed by Azure CLI and ARM template examples. While Azure CLI is cross-platform, the ordering and initial emphasis on PowerShell may signal a Windows-centric approach. No Linux/macOS-specific shell examples (e.g., bash) or notes about platform compatibility are provided.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
  • Add a note clarifying platform compatibility for each method.
  • Consider including bash-specific usage notes or troubleshooting tips for Linux/macOS users if relevant.
GitHub Create Pull Request
Private Link Manage Azure private endpoints .../main/articles/private-link/manage-private-endpoint.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Windows/PowerShell examples before Azure CLI equivalents, and uses PowerShell as the primary scripting tool in explanations and screenshots. References to PowerShell modules and output images are prominent, with CLI examples sometimes described as 'using PowerShell' (likely a copy-paste error), and no mention of Bash, Linux shell, or macOS-specific considerations. There is no explicit Linux bias, but the structure and language favor Windows/PowerShell users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first in some sections.
  • Ensure CLI examples are described accurately and do not reference PowerShell in their descriptions.
  • Include notes or tips for Linux/macOS users, such as shell compatibility, environment setup, or differences in command usage.
  • Add screenshots or output examples from Azure CLI, not just PowerShell.
  • Clarify that both PowerShell and CLI are cross-platform, and provide links to installation guides for Linux/macOS.
  • Consider including Bash script examples for common tasks.
GitHub Create Pull Request
Private Link What is a private endpoint? ...ain/articles/private-link/private-endpoint-overview.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references both PowerShell and Azure CLI for creating private endpoints, but PowerShell (a Windows-centric tool) is mentioned first and more prominently. There are no Linux/macOS-specific examples or tools highlighted, and the documentation does not clarify cross-platform compatibility for command-line instructions.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
  • Include example commands for both PowerShell and Azure CLI in relevant sections.
  • Add a note clarifying that all management tasks can be performed from Linux/macOS using Azure CLI.
GitHub Create Pull Request
Private Link Troubleshoot Azure Private Endpoint connectivity problems ...ate-link/troubleshoot-private-endpoint-connectivity.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides troubleshooting steps for Azure Private Endpoint connectivity but does not include any OS-specific command-line examples or tooling references. However, it implicitly assumes use of the Azure Portal and GUI tools, with no mention of Linux-specific troubleshooting methods, CLI commands, or cross-platform guidance. There are no references to Windows-specific tools, but the absence of Linux command-line examples or parity is notable.
Recommendations
  • Add troubleshooting steps using Azure CLI and/or PowerShell, with explicit examples for both Windows and Linux environments.
  • Include guidance for performing DNS checks and network connectivity tests from Linux VMs, such as using dig, nslookup, curl, or traceroute.
  • Reference cross-platform tools and commands for validating network routes and connectivity (e.g., ip route, netstat, ping).
  • Clarify that troubleshooting can be performed from both Windows and Linux VMs, and provide OS-agnostic instructions where possible.
GitHub Create Pull Request
← Previous Page 7 of 8 Next →