Private Link

96
Total Pages
73
Linux-Friendly Pages
23
Pages with Bias
24.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

44 issues found
Showing 26-44 of 44 flagged pages
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 →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the connectivity testing section, where only Windows PowerShell is mentioned for DNS resolution and Microsoft Edge is referenced for browser testing. There are no examples or instructions for Linux/macOS users, such as using Bash, terminal commands, or alternative browsers. The tutorial implicitly assumes the test VM is running Windows, and does not provide parity for Linux-based environments.
Recommendations
  • Include Linux/macOS instructions for DNS resolution, such as using 'dig' or 'nslookup' in Bash.
  • Clarify that the test VM can be Windows or Linux, and provide steps for both OS types.
  • Mention alternative browsers (e.g., Firefox, Chrome) for web app testing.
  • Add screenshots or command outputs from Linux terminals.
  • Explicitly state OS requirements or options when creating the test VM.
GitHub Create Pull Request
Private Link Tutorial: Connect to an Azure SQL server using an Azure Private Endpoint - Azure CLI ...cles/private-link/tutorial-private-endpoint-sql-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias in the testing and connectivity sections. The only example for connecting to the SQL server uses a Windows VM image, instructs users to open Windows PowerShell, and relies on SQL Server Management Studio (SSMS), a Windows-only tool. There are no instructions or examples for Linux or macOS users, such as using a Linux VM, Bash shell, or cross-platform SQL clients. This may create friction for users on non-Windows platforms.
Recommendations
  • Add instructions and examples for creating a Linux VM (e.g., Ubuntu) and connecting via SSH.
  • Provide connectivity test examples using Bash (e.g., nslookup, dig) and cross-platform SQL clients like Azure Data Studio or sqlcmd.
  • Mention Linux/macOS alternatives to SSMS and provide installation and usage steps.
  • Present both Windows and Linux/macOS options side-by-side, or clarify that the tutorial is Windows-specific if parity is not feasible.
GitHub Create Pull Request
Private Link Tutorial: Connect to a storage account using an Azure Private Endpoint ...ivate-link/tutorial-private-endpoint-storage-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial demonstrates a notable Windows bias in the connectivity testing section: it instructs users to open Windows PowerShell and provides only a PowerShell example for DNS resolution. There are no Linux/macOS CLI or shell examples, nor any mention of alternative commands (e.g., 'nslookup' or 'dig' on Linux/macOS). The Storage Explorer installation instructions link to a Windows-specific tab and do not address Linux/macOS installation or usage. The overall flow assumes a Windows VM and user environment, with no guidance for Linux/macOS users.
Recommendations
  • Provide equivalent Linux/macOS instructions for connectivity testing (e.g., using 'nslookup', 'dig', or 'host' in bash/zsh).
  • Include screenshots and command examples for Linux/macOS terminals.
  • Add Storage Explorer installation steps for Linux/macOS, or link to cross-platform documentation.
  • Clarify that the VM can be Windows or Linux, and provide parity in instructions for both.
  • Avoid assuming the use of Windows PowerShell; use generic terminology like 'terminal' or 'command prompt' and offer platform-specific tabs.
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-12 00:00
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 Azure CLI instructions are shown first. Azure PowerShell is included as a separate tab, which may indicate a slight Windows bias. No Linux-specific tools or examples are missing, and all steps are cross-platform compatible, but the presence of PowerShell and its prominence may create a minor bias toward Windows users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or provide Bash-specific examples for Linux users.
  • Consider including a Bash script example for verification steps, especially for Linux/macOS users.
  • Ensure parity in troubleshooting and cleanup instructions by referencing cross-platform tools.
GitHub Create Pull Request
Private Link What is Azure Private Link service? ...articles/private-link/private-link-service-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page does not provide any explicit command-line examples, but in the 'Next steps' section, it lists 'Create a private link service using Azure PowerShell' before 'Create a private link service using Azure CLI'. Azure PowerShell is primarily a Windows-centric tool, while Azure CLI is cross-platform. This ordering subtly prioritizes Windows tooling over Linux/macOS equivalents.
Recommendations
  • List Azure CLI before Azure PowerShell in the 'Next steps' section to prioritize cross-platform tooling.
  • Ensure that all example links (in referenced articles) provide both PowerShell and CLI instructions, with CLI shown first or equally.
  • Consider adding a statement clarifying that Azure CLI is recommended for Linux/macOS users.
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-12 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 and terminology before Azure CLI (cross-platform) equivalents. PowerShell is referenced heavily, and screenshots are of PowerShell output. There is no mention of Linux/macOS-specific considerations, nor are there Bash or shell script examples. The CLI examples are present, but PowerShell is often described first and in more detail.
Recommendations
  • Alternate the order of examples so Azure CLI (cross-platform) appears before PowerShell in some sections.
  • Include explicit Bash/shell script examples for Linux/macOS users, especially for variable assignment and command chaining.
  • Add notes clarifying that Azure CLI is fully supported on Linux/macOS and provide links to installation instructions for those platforms.
  • Ensure screenshots and output examples include CLI output, not just PowerShell.
  • Avoid language that implies PowerShell is the default or preferred tool.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure Portal, PowerShell, and Azure CLI. PowerShell is featured as a primary automation method, which is most commonly used on Windows. There is explicit mention of installing and using PowerShell locally, with guidance focused on Windows-centric tools and patterns. The CLI instructions are present and suitable for Linux/macOS, but PowerShell is given equal prominence and is described in more detail. There is no explicit Linux/macOS bias, but the documentation leans toward Windows by including PowerShell instructions and setup steps.
Recommendations
  • Clarify that Azure CLI works natively on Linux/macOS and is cross-platform, and consider listing CLI instructions before PowerShell.
  • Add notes or examples for Bash scripting or other Linux-native automation approaches where appropriate.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell examples are retained, or provide parity with Bash examples.
  • Ensure installation instructions for CLI and PowerShell cover Linux/macOS platforms equally, with direct links to those guides.
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-12 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 instructions for deployment and cleanup, but PowerShell examples are shown alongside CLI examples in all critical steps. There is no explicit Linux/macOS bias, but PowerShell (a Windows-centric tool) is given equal prominence, and examples do not clarify cross-platform usage or recommend CLI for Linux/macOS users. The order of examples sometimes places CLI first, but PowerShell is always present and not marked as Windows-only.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add notes specifying that Azure PowerShell is primarily for Windows, and provide installation guidance for PowerShell Core if relevant for Linux/macOS.
  • Consider showing CLI examples first and PowerShell examples second, or in a separate section labeled for Windows users.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows.
  • If possible, add a short section on platform compatibility for the tools used.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell (Windows-centric) instructions before Azure CLI, and the PowerShell example is more detailed. While Azure CLI is cross-platform and included, the ordering and emphasis favor Windows/PowerShell users. No Linux/macOS-specific issues or missing examples, but the structure may subtly prioritize Windows workflows.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS and Windows.
  • Balance example detail between PowerShell and CLI sections.
  • Consider adding a short note or example for Bash scripting if relevant.
GitHub Create Pull Request
Private Link Azure Private Endpoint DNS Integration Scenarios ...icles/private-link/private-endpoint-dns-integration.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-centric DNS concepts and tools (such as conditional forwarders and links to Windows Server DNS documentation) before or instead of mentioning Linux equivalents. There are no explicit Linux/macOS examples, nor are cross-platform DNS server options discussed. However, the instructions are mostly conceptual and do not require Windows-only tooling, so Linux users can adapt the guidance.
Recommendations
  • Include explicit examples for configuring DNS forwarding and conditional forwarders using common Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
  • Reference Linux documentation or guides alongside Windows Server DNS links.
  • Add notes or sections clarifying that the described DNS patterns (forwarders, conditional forwarding) are supported on Linux and macOS DNS solutions, with links to relevant setup guides.
  • Provide sample configuration snippets for Linux-based DNS servers where appropriate.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily in the prerequisites section, where it links only to instructions for creating a Windows virtual machine, omitting Linux VM guidance. Throughout the rest of the document, the examples for tagging resources use Azure Portal, PowerShell, and Azure CLI, which are cross-platform and do not favor Windows. However, the initial VM deployment guidance is Windows-centric.
Recommendations
  • Include a link to the equivalent Linux VM creation guide alongside the Windows VM link in the prerequisites.
  • Clarify that Azure CLI and Portal instructions apply equally to Linux/macOS users.
  • Consider providing brief notes or links for Linux/macOS users regarding PowerShell usage (e.g., PowerShell Core compatibility) if relevant.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents the PowerShell (Windows-centric) example first, followed by Azure CLI and ARM template examples. While Azure CLI is cross-platform, the ordering and emphasis on PowerShell may subtly prioritize Windows users. No Linux/macOS-specific tools or shell examples are provided, but CLI coverage ensures basic parity.
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 provide example shell syntax (e.g., bash) if relevant.
  • Add a note clarifying platform compatibility for each method.
  • Consider including screenshots or guidance for Linux/macOS environments if UI or environment differences exist.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
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 is featured as a primary automation method, which is traditionally Windows-centric. The prerequisites section gives detailed instructions for installing and using PowerShell locally, including module version checks and connection commands, which are specific to Windows environments. PowerShell examples are presented before CLI examples in each technical section, and there is no mention of Bash, Linux shell, or macOS-specific considerations. However, the Azure CLI instructions are cross-platform and allow Linux/macOS users to complete all tasks.
Recommendations
  • Clarify that Azure PowerShell is available on macOS and Linux via PowerShell Core, and provide installation links for those platforms.
  • Present Azure CLI examples before PowerShell examples to reduce Windows-first bias.
  • Add explicit notes or examples for Linux/macOS users, such as using Bash for variable assignment in CLI examples.
  • Remove or minimize references to 'running PowerShell locally' as a default, and instead present CLI as the default cross-platform automation tool.
  • Ensure that all prerequisites and instructions mention cross-platform compatibility where relevant.
GitHub Create Pull Request
Private Link Configure Private Link service Direct Connect ...-link/configure-private-link-service-direct-connect.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents PowerShell examples first in each code tab, followed by Azure CLI and Terraform. PowerShell is a Windows-centric tool, and its prominence may suggest a Windows-first approach. There are no explicit Linux/macOS shell script examples (e.g., Bash), and installation instructions reference Azure PowerShell before Azure CLI. While Azure CLI and Terraform are cross-platform, the lack of native Linux/macOS shell examples and the ordering of examples may create friction for non-Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more widely used across Linux/macOS.
  • Add explicit Bash shell script examples for Linux/macOS users where appropriate.
  • Clarify in prerequisites that Azure CLI and Terraform are fully supported on Linux/macOS, and provide installation links for those platforms.
  • Consider balancing example order (e.g., rotate which tool appears first) or default to CLI for cross-platform parity.
  • Explicitly mention that all steps can be performed on Linux/macOS using CLI and Terraform.
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-11 06:20
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 is shown immediately after CLI in each section. There are no Linux/macOS-specific notes, nor are Linux shell patterns (e.g., bash scripting, environment variables) discussed. The order of examples does not prioritize Linux users, and PowerShell is presented as a primary option, which may suggest a slight Windows bias.
Recommendations
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide links or notes for installing CLI on those platforms.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI examples are cross-platform.
  • Consider showing CLI examples first in each section, as CLI is the most cross-platform tool.
  • Include troubleshooting tips for Linux/macOS users, such as file permissions or shell usage.
  • If relevant, mention how to install Bicep CLI on Linux/macOS.
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-11 06:20
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 example is given equal prominence and is included immediately after the CLI example. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since no Linux/macOS-specific shell examples (such as Bash or native Linux tools) are provided. The documentation does not mention Linux-specific patterns or troubleshooting, and the order of examples (CLI first, PowerShell second) is common but still reflects a slight Windows-first approach.
Recommendations
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are preferred for Linux/macOS users.
  • Add notes or examples for verifying results using Bash or other Linux-native tools where relevant.
  • Clarify that PowerShell is primarily for Windows users, and provide parity for Linux/macOS users in troubleshooting and verification steps.
  • Consider including a table or section that compares the commands for Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) to highlight cross-platform support.
GitHub Create Pull Request
Private Link Azure Private Endpoint DNS Integration Scenarios ...icles/private-link/private-endpoint-dns-integration.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias by referencing Windows-centric DNS concepts (such as conditional forwarders and links to Windows Server DNS documentation) and mentioning Windows tools (like Azure Firewall and Windows Server DNS) before Linux equivalents. There are no explicit PowerShell-only examples or CLI commands, but the terminology and linked resources favor Windows environments. Linux DNS solutions (e.g., BIND, dnsmasq) are not mentioned, and guidance for configuring DNS forwarding or conditional forwarding on Linux is absent.
Recommendations
  • Include examples and references for configuring DNS forwarding and conditional forwarding using popular Linux DNS servers (such as BIND, dnsmasq, or Unbound).
  • Provide links to Linux documentation for DNS concepts alongside Windows Server references.
  • Add a section or note clarifying that the described DNS forwarding and conditional forwarding concepts apply equally to Linux-based DNS servers, with pointers to relevant configuration guides.
  • Use neutral terminology (e.g., 'DNS server' instead of 'Windows DNS server') and avoid assuming Windows environments in examples.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-specific tools (PowerShell) before mentioning cross-platform alternatives (Azure CLI), and links to PowerShell cmdlets first in the 'Connect by using an alias' section. There are no explicit Linux/macOS examples or tool parity explanations, and the documentation does not clarify platform compatibility for the referenced commands.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side, clarifying that Azure CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide direct links to CLI documentation before or alongside PowerShell links.
  • Add notes or sections for Linux/macOS users, including any platform-specific considerations or troubleshooting.
  • Avoid referencing Windows tools (PowerShell) exclusively or first when cross-platform alternatives exist.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows virtual machines as the default NVA example and linking only to Windows VM deployment guides in the prerequisites. The first quickstart link is for creating a Windows VM, with no mention or link to Linux VM equivalents. However, the core instructions for tagging resources use Azure Portal, PowerShell, and Azure CLI, which are cross-platform, and CLI examples are provided for Linux/macOS users.
Recommendations
  • Add a link to the 'Quickstart: Create a Linux virtual machine in the Azure portal' in the prerequisites alongside the Windows VM link.
  • Clarify that the NVA can be either a Windows or Linux VM, and provide examples or notes for both.
  • Ensure that examples and terminology do not imply Windows is the default or only supported platform for NVAs.
  • Consider alternating the order of examples or providing parity in references to both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →