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 26-50 of 188 flagged pages
Private Link Quickstart - Create a network security perimeter - ARM Template ...ate-link/create-network-security-perimeter-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a bias towards Windows environments by providing only a PowerShell example for resource cleanup and referencing the Azure PowerShell tool explicitly. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI or Bash), and Windows-centric tools are mentioned without Linux alternatives.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all operations, especially for resource cleanup.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and provide links to installation guides for Linux and macOS.
  • Add Bash script examples for common tasks where appropriate.
  • Ensure that references to tools (PowerShell, CLI, Portal) are presented in a neutral order or grouped together, rather than listing Windows tools first.
  • Add a note clarifying platform compatibility for all command-line instructions.
GitHub Create Pull Request
Private Link Increase Private Endpoint virtual network limits .../private-link/increase-private-endpoint-vnet-limits.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by prioritizing PowerShell examples and terminology, listing PowerShell before CLI in code tabs, and omitting explicit Linux/Bash examples or guidance. While Azure CLI is cross-platform, the CLI example is less prominent and lacks Bash-specific context, and there are no references to Linux-native tools or shell environments.
Recommendations
  • Add explicit Bash/Linux shell examples alongside PowerShell, using Bash syntax and environment variables.
  • When presenting code tabs, alternate the order or default to CLI/Bash rather than always listing PowerShell first.
  • Include notes clarifying that Azure CLI commands are cross-platform and provide any Linux-specific prerequisites or troubleshooting tips.
  • Where possible, reference Linux-native tools or patterns (e.g., using jq for JSON parsing) in validation steps.
  • Ensure screenshots or portal instructions do not assume a Windows environment (e.g., file paths, UI conventions).
GitHub Create Pull Request
Private Link Configure an application security group with a private endpoint ...rticles/private-link/configure-asg-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary automation option, and references to PowerShell modules and commands are prominent in both prerequisites and procedural sections. The prerequisites detail PowerShell installation and usage before mentioning CLI, and PowerShell-specific instructions are included even when functionality is limited (e.g., associating an ASG with an existing private endpoint is noted as unsupported in PowerShell). The CLI instructions are present and generally platform-agnostic, but the overall structure and language favor Windows/PowerShell tools and patterns.
Recommendations
  • Ensure CLI instructions are presented before or alongside PowerShell instructions to promote platform neutrality.
  • Clarify that Azure CLI works natively on Linux, macOS, and Windows, and provide explicit Linux/macOS terminal examples (e.g., bash syntax, environment setup).
  • Reduce emphasis on PowerShell-specific prerequisites unless necessary, and highlight CLI as the recommended cross-platform tool.
  • Add troubleshooting or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, using bash variables).
  • Where PowerShell functionality is limited, suggest alternative CLI workflows for Linux/macOS users.
GitHub Create Pull Request
Private Link Configure Private Link service Direct Connect ...-link/configure-private-link-service-direct-connect.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents PowerShell (a Windows-centric tool) examples before Azure CLI and Terraform, both in main and verification/cleanup sections. Prerequisites and feature flag registration instructions mention PowerShell before CLI, and do not clarify cross-platform usage. There are no explicit Linux shell examples (e.g., bash), nor any mention of Linux-specific considerations or parity. The documentation assumes familiarity with PowerShell, which is less common on Linux systems.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, while PowerShell is primarily Windows (with cross-platform support, but less common on Linux).
  • Add explicit bash shell examples for resource cleanup and verification, or clarify that CLI commands are suitable for Linux users.
  • In prerequisites, mention that Azure CLI is recommended for Linux/macOS users, and PowerShell for Windows users.
  • For feature flag registration, provide CLI instructions first, and clarify that PowerShell is optional for Windows users.
  • Add a note or section on Linux/macOS compatibility and best practices for Azure Private Link service Direct Connect.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Azure portal ...rticles/private-link/create-private-endpoint-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 in its testing instructions: it explicitly directs users to open PowerShell on the test VM and provides only PowerShell-based commands (nslookup) for connectivity testing. There are no Linux shell examples or instructions for users who may have deployed a Linux VM, nor is there mention of alternative tools or commands (e.g., dig, curl, wget) commonly used on Linux. The documentation implicitly assumes the test VM is running Windows, and does not provide parity for Linux users.
Recommendations
  • Include instructions and examples for testing connectivity from a Linux VM, such as using the Bash shell.
  • Provide equivalent Linux commands for DNS resolution (e.g., 'dig webapp-1.azurewebsites.net' or 'host webapp-1.azurewebsites.net') and HTTP requests (e.g., 'curl https://webapp-1.azurewebsites.net').
  • Explicitly state that the test VM can be either Windows or Linux, and offer guidance for both environments.
  • Avoid assuming PowerShell is the default shell; mention alternatives and provide cross-platform examples side-by-side.
  • Where screenshots or output are shown, include Linux equivalents to ensure parity.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Azure CLI ...n/articles/private-link/create-private-endpoint-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by exclusively using Windows-based VM images (Win2022Datacenter) in examples, referencing PowerShell for connectivity testing, and omitting any Linux VM or shell examples. The only connectivity test shown uses PowerShell, and there is no mention of Linux tools or alternative commands. Windows tools and patterns are presented as the default, with no Linux parity.
Recommendations
  • Include examples for creating a Linux VM (e.g., using --image UbuntuLTS) alongside the Windows VM example.
  • Provide connectivity test instructions using Linux shell commands (e.g., nslookup, dig, curl) in addition to PowerShell.
  • Explicitly mention that both Windows and Linux VMs can be used for testing, and provide guidance for both platforms.
  • Add screenshots or output samples from Linux terminals where appropriate.
  • Avoid assuming the user will use PowerShell; offer Bash or other shell alternatives.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Bicep ...articles/private-link/create-private-endpoint-bicep.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Windows bias in several ways: connection instructions to the VM are exclusively via RDP (a Windows protocol), and SQL Server Management Studio (a Windows-only tool) is used for database access. The instructions for accessing the VM and SQL Database are written with Windows users in mind, with no mention of Linux alternatives (e.g., SSH for VM access, Azure Data Studio or sqlcmd for database access). PowerShell is presented as a primary deployment method alongside CLI, but Linux-specific shell examples are absent.
Recommendations
  • Add instructions for connecting to the VM using SSH, which is standard for Linux VMs.
  • Include examples for accessing the SQL Database from Linux, such as using Azure Data Studio or sqlcmd.
  • Provide deployment and cleanup examples using Bash shell commands, not just PowerShell.
  • Mention cross-platform tools and clarify which steps are OS-specific.
  • Reorder or parallelize instructions so that Windows and Linux methods are presented together, rather than Windows-first.
GitHub Create Pull Request
Private Link Quickstart: Create a private link service - Bicep ...cles/private-link/create-private-link-service-bicep.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page 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 Linux users, such as SSH access or Linux-based web servers. The walkthrough assumes the use of IIS (Internet Information Services), a Windows web server, and does not mention Linux alternatives. All connection steps and screenshots are tailored to Windows environments, with no parity for Linux users.
Recommendations
  • Include instructions for connecting to the VM using SSH, which is standard for Linux VMs.
  • Provide examples of deploying a Linux VM and installing a web server such as Apache or Nginx.
  • Show how to access the private endpoint from a Linux VM, including relevant CLI commands and browser usage.
  • Mention both RDP and SSH options when describing how to connect to the VM, and clarify which OS each applies to.
  • Add screenshots or step-by-step guides for Linux users alongside Windows instructions.
GitHub Create Pull Request
Private Link Quickstart: Create a private link service - ARM template ...s/private-link/create-private-link-service-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 assume the use of Windows tools and workflows. The VM connection steps exclusively use Remote Desktop Protocol (RDP), which is native to Windows, and reference IIS (Internet Information Services), a Windows web server. The cleanup instructions use Azure PowerShell without mentioning Azure CLI or Bash alternatives. No Linux-based connection methods (such as SSH) or Linux web server examples (such as Apache or Nginx) are provided.
Recommendations
  • Add instructions for connecting to the VM using SSH for Linux-based VMs, including relevant portal and CLI steps.
  • Include examples of deploying and accessing a Linux web server (e.g., Apache or Nginx) alongside the IIS example.
  • Provide cleanup instructions using Azure CLI (e.g., 'az group delete') in addition to PowerShell.
  • Ensure that both Windows and Linux workflows are presented in parallel throughout the documentation, including screenshots and command examples.
  • Clarify in prerequisites or deployment steps how to select the OS type for the VM and what changes in the workflow depending on the OS.
GitHub Create Pull Request
Private Link Quickstart: Create a private endpoint - Terraform ...cles/private-link/create-private-endpoint-terraform.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is featured as a primary tab alongside CLI, and no explicit Linux shell (bash) or macOS examples are given. The PowerShell example uses Windows-centric syntax and tools, and there is no mention of Linux-specific verification steps or troubleshooting. The documentation implicitly assumes familiarity with Windows tools and does not address Linux users directly.
Recommendations
  • Add explicit bash/Linux shell examples for verification steps, including commands that work natively on Linux/macOS.
  • Clarify that Azure CLI works cross-platform and provide sample commands in bash syntax (e.g., export instead of set for environment variables).
  • Include troubleshooting steps or notes relevant to Linux environments, such as SSH key handling or file permissions.
  • Balance the presentation order so that Linux-compatible examples (Azure CLI in bash) are presented before or alongside PowerShell.
  • Mention any platform-specific considerations (e.g., differences in command syntax, file paths, or required tools) for Linux/macOS users.
GitHub Create Pull Request
Private Link Manage network policies for private endpoints ...rivate-link/disable-private-endpoint-network-policy.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell-specific cmdlets, which are primarily used on Windows. PowerShell is listed before Azure CLI in the example tabs, and there are no Linux shell (bash) or cross-platform scripting examples. The CLI examples use Azure CLI, which is cross-platform, but the documentation does not provide any Linux-specific context, such as bash scripting or differences in usage on Linux. There is also no mention of Linux-native tools or patterns.
Recommendations
  • Add bash shell script examples for Azure CLI commands to demonstrate usage on Linux systems.
  • Clarify that Azure CLI commands are cross-platform and provide notes on any OS-specific considerations.
  • Consider listing Azure CLI examples before PowerShell to emphasize cross-platform parity.
  • Include a section or note for Linux users, highlighting any differences or additional steps required.
  • Avoid exclusive reliance on PowerShell cmdlets; provide equivalent examples using bash and Azure CLI where possible.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as the first example and providing detailed PowerShell instructions, which are primarily used on Windows. The CLI example is present, but there is no explicit mention of Linux environments or shell-specific guidance (e.g., Bash). The PowerShell example is more verbose and detailed, potentially implying a preference for Windows tooling. There are no Linux-specific notes, nor is there parity in example ordering or environment context.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell context (e.g., Bash) for CLI examples.
  • Alternate the order of examples, sometimes listing CLI first to avoid implicit prioritization of Windows/PowerShell.
  • Add notes or sections for Linux users, such as how to install and use Azure CLI on Linux.
  • Ensure parity in example detail and clarity between PowerShell and CLI sections.
  • Consider including screenshots or walkthroughs for both Windows and Linux environments if relevant.
GitHub Create Pull Request
Private Link Manage Azure private endpoints .../main/articles/private-link/manage-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents Windows-oriented tools (PowerShell) before cross-platform alternatives (Azure CLI) in all code example sections. All command-line examples are limited to PowerShell and Azure CLI, with no mention of Linux-specific shell usage, nor any explicit Bash or Linux terminal examples. There is a tendency to describe actions using PowerShell terminology and screenshots, and the CLI examples sometimes reference PowerShell outputs. No Linux-native tools or patterns are discussed.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to emphasize cross-platform parity.
  • Include explicit Bash/Linux shell examples, showing how to use Azure CLI in a Linux environment (e.g., with environment variables, piping, jq for JSON parsing).
  • Add notes clarifying that Azure CLI commands work on Windows, Linux, and macOS, and provide sample outputs from Linux terminals.
  • Avoid referencing PowerShell outputs in CLI sections; instead, provide CLI-native output screenshots.
  • Where possible, mention Linux-native tools or scripting patterns that may be useful for managing Azure resources.
GitHub Create Pull Request
Private Link Azure Private Endpoint private DNS zone values ...lob/main/articles/private-link/private-endpoint-dns.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. It references the use of the 'host file' for DNS overrides, which is a Windows-centric term and pattern, without mentioning the Linux equivalent ('/etc/hosts'). Additionally, in the region code explanation, it links to a Microsoft Word document (.docx) for region codes, which is a Windows-preferred format. There are no explicit command-line examples, but where commands are mentioned (e.g., 'az account list-locations -o table'), they are cross-platform. However, the documentation does not provide Linux-specific terminology or examples, nor does it clarify that DNS configuration steps apply equally to Linux systems.
Recommendations
  • When mentioning the 'host file', also reference the Linux equivalent ('/etc/hosts') and clarify that the procedure applies to both Windows and Linux.
  • Provide explicit examples or notes for both Windows and Linux environments where manual DNS configuration is discussed.
  • When linking to region code lists, offer a plain text or CSV alternative to .docx files for better cross-platform accessibility.
  • Review terminology throughout the documentation to ensure platform-neutral language (e.g., 'host file' vs. 'hosts file').
  • If any step involves GUI tools or OS-specific utilities, provide parity for both Windows and Linux.
GitHub Create Pull Request
Private Link What is a private endpoint? ...ain/articles/private-link/private-endpoint-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell (New-AzPrivateEndpoint) before the Azure CLI (az network private-endpoint create) when describing how to create a private endpoint using an alias. There are no explicit Linux or bash examples, nor is there mention of Linux-specific tools or workflows. The documentation assumes familiarity with Windows-centric tooling and does not provide parity for Linux users.
Recommendations
  • Present Azure CLI (az) examples before or alongside PowerShell examples to ensure Linux parity.
  • Include explicit bash/Linux shell command examples for common tasks, such as creating private endpoints.
  • Reference cross-platform tools and workflows, and clarify when instructions are platform-agnostic.
  • Add a section or note highlighting how Linux users can perform the same operations, including any platform-specific considerations.
  • Ensure that links to command references include both PowerShell and Azure CLI documentation.
GitHub Create Pull Request
Private Link Azure Private Endpoint DNS Integration Scenarios ...icles/private-link/private-endpoint-dns-integration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric DNS concepts (such as conditional forwarders and links to Windows Server documentation), mentioning Windows tools and patterns (e.g., DNS forwarder as a VM, conditional forwarding), and omitting explicit Linux/BIND/unbound examples or guidance. The terminology and linked resources assume familiarity with Windows DNS management, and there are no Linux-specific instructions or parity in examples.
Recommendations
  • Include explicit Linux DNS server examples (e.g., BIND, Unbound) for conditional forwarding and DNS forwarding configurations.
  • Add links to Linux/BIND documentation for DNS forwarding and conditional forwarding, alongside Windows Server links.
  • Provide sample configuration snippets for both Windows DNS Manager and Linux DNS server config files (e.g., named.conf for BIND).
  • Clarify that DNS forwarders can be implemented using Linux-based solutions, not only Windows VMs or Azure Firewall.
  • Balance terminology to reference both Windows and Linux DNS solutions equally throughout the scenarios.
GitHub Create Pull Request
Private Link Tutorial: Connect to an Azure SQL server using an Azure Private Endpoint - PowerShell ...ivate-link/tutorial-private-endpoint-sql-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All code examples use Azure PowerShell cmdlets, and the tutorial assumes the use of Windows-based tools and workflows (e.g., SQL Server Management Studio, Windows PowerShell). There are no equivalent instructions or examples for Linux users (e.g., Bash/CLI, Azure CLI, or cross-platform SQL tools). The virtual machine creation defaults to Windows Server, and testing connectivity is described only via Windows tools.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell for all resource creation steps.
  • Include instructions for creating a Linux VM and connecting via SSH, not just Windows Server and Bastion.
  • Offer alternative SQL connectivity testing methods, such as using sqlcmd (cross-platform) or Azure Data Studio.
  • Document DNS resolution and connectivity testing using Linux tools (e.g., dig, nslookup in Bash).
  • Mention and demonstrate installation and use of cross-platform SQL management tools.
  • Clearly label sections as Windows-specific and provide parallel Linux/macOS workflows where possible.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively providing Windows PowerShell instructions for DNS testing and referencing Microsoft Edge for browser testing. There are no examples or guidance for performing equivalent steps on Linux-based virtual machines, such as using Bash, Linux terminal commands, or Linux browsers. The tutorial implicitly assumes the test VM is running Windows, with no mention of Linux alternatives or parity.
Recommendations
  • Provide Linux-based instructions for testing DNS resolution, such as using the 'dig' or 'nslookup' commands in a Bash shell.
  • Include steps for connecting to the test VM using SSH, which is standard for Linux VMs, alongside Bastion/Windows RDP instructions.
  • Mention and demonstrate browser testing using common Linux browsers (e.g., Firefox) in addition to Microsoft Edge.
  • Clarify that the test VM can be either Windows or Linux, and provide guidance for both environments.
  • Ensure that all example outputs and screenshots include both Windows and Linux variants where applicable.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
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 in the testing and connectivity steps. The only example for connecting to the VM and testing DNS resolution uses Windows PowerShell, and the VM is created with a Windows Server image. SQL Server Management Studio (SSMS), a Windows-only tool, is the sole client recommended for connecting to Azure SQL. There are no examples or instructions for Linux VMs, Linux command-line tools, or cross-platform SQL clients.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) and connecting to it via Bastion.
  • Include Linux shell commands (e.g., nslookup, dig) for DNS resolution testing.
  • Recommend and demonstrate cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) alongside SSMS.
  • Explicitly mention that the Azure CLI and Bastion support both Windows and Linux VMs.
  • Add screenshots or command snippets for Linux environments where appropriate.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias by providing only Windows PowerShell examples for connectivity testing, referencing Windows-specific tools (such as Microsoft Azure Storage Explorer with Windows tabs), and omitting equivalent Linux instructions or examples. The workflow assumes the use of a Windows VM and does not mention or provide guidance for Linux-based environments, shell commands, or cross-platform alternatives.
Recommendations
  • Add equivalent Linux instructions for connectivity testing, such as using 'nslookup' or 'dig' in bash.
  • Provide examples using Linux shell commands alongside PowerShell, with clear tabs or sections for each OS.
  • Include installation and usage steps for Microsoft Azure Storage Explorer on Linux, or mention alternative CLI tools (e.g., Azure CLI, azcopy) for blob access.
  • Explicitly state that the tutorial applies to both Windows and Linux VMs, and offer OS selection guidance during VM creation.
  • Ensure all screenshots and command outputs have Linux equivalents or are marked as OS-specific.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/tutorial-private-endpoint-sql-powershell.md ...ivate-link/tutorial-private-endpoint-sql-powershell.md
High Priority View Details →
Scanned: 2026-01-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 documentation is heavily biased toward Windows and PowerShell. All code examples use Azure PowerShell, and the VM created is explicitly a Windows Server. The connectivity test and SQL client instructions assume Windows (PowerShell and SQL Server Management Studio), with no mention of Linux equivalents or cross-platform tools. There are no Bash/CLI examples, and Linux VM creation is not covered.
Recommendations
  • Add parallel examples using Azure CLI (az) and Bash for all resource creation steps.
  • Include instructions for creating a Linux VM and connecting via SSH for testing the private endpoint.
  • Provide guidance for using cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) on both Windows and Linux.
  • Mention Linux-specific tools for DNS testing (e.g., dig, nslookup in Bash) in the connectivity test section.
  • Ensure that prerequisites and tool installation steps cover both Windows and Linux environments.
  • Rephrase sections that assume Windows-only workflows to be OS-agnostic or provide alternatives.
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-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 moderate Windows bias. PowerShell is consistently presented as the first example in every code tab, followed by Azure CLI and then Terraform. Prerequisites and instructions reference Azure PowerShell before Azure CLI, and installation links for PowerShell are listed first. There is a strong presence of PowerShell scripts and terminology throughout, and no explicit mention of Linux-specific shell environments or usage patterns. The CLI examples use Bash-style syntax, but there is no guidance for Linux users regarding shell compatibility, nor are there troubleshooting tips for Linux-specific issues. The documentation also refers to 'Azure PowerShell installed locally' as a prerequisite, which is more common on Windows.
Recommendations
  • Alternate the order of code tabs so that Azure CLI (Bash) examples appear before PowerShell, or make CLI the default/first shown example.
  • Explicitly mention Linux as a supported platform in prerequisites and provide guidance for using Azure CLI in Bash on Linux/macOS.
  • Add notes or troubleshooting sections for common Linux-specific issues (e.g., shell quoting, environment variables, file paths).
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux/macOS, possibly with screenshots or terminal prompts.
  • Where PowerShell is referenced, add a note that it is available cross-platform, but CLI may be more familiar to Linux users.
  • Ensure that all instructions (such as feature flag registration) include both CLI and PowerShell commands side-by-side, not PowerShell first.
  • Consider including Linux-specific terminology (e.g., 'run these commands in your Bash shell') and avoid Windows-centric phrasing.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary automation method, and references to installing and using PowerShell locally are given more detail than for other platforms. The prerequisites section discusses PowerShell before CLI, and the PowerShell instructions use Windows-centric patterns and terminology. There is no explicit mention of Linux or macOS platforms in the PowerShell section, and the CLI instructions, while cross-platform, do not receive equal emphasis or troubleshooting guidance. The documentation does not provide Linux-specific examples or clarify platform differences for PowerShell usage.
Recommendations
  • Add explicit Linux/macOS instructions for installing and using Azure PowerShell, including platform-specific troubleshooting.
  • Clarify that Azure CLI is cross-platform and provide parity in guidance and troubleshooting for CLI usage on Linux/macOS.
  • Include a note about running PowerShell Core on Linux/macOS, with links to installation guides.
  • Ensure that CLI examples are presented with equal prominence and detail as PowerShell examples.
  • Avoid assuming PowerShell is the default automation tool; present CLI and PowerShell as equal options.
  • Add a section or callout for platform-specific considerations, especially for users on Linux or macOS.
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-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 demonstrates a Windows bias by providing instructions and examples that prioritize Windows tools and workflows. The VM connection section exclusively describes connecting via RDP (Remote Desktop Protocol), which is a Windows-centric method, and instructs users to use PowerShell within the VM. It also recommends installing SQL Server Management Studio, a Windows-only application, for database access. There are no examples or guidance for Linux users, such as connecting via SSH, using Bash, or employing cross-platform database tools. The order of examples and instructions consistently favors Windows environments and tools.
Recommendations
  • Add instructions for connecting to the VM via SSH for Linux and macOS users, including relevant CLI commands.
  • Provide examples of running equivalent commands (e.g., nslookup) in Bash or other Linux shells.
  • Recommend cross-platform database clients (such as Azure Data Studio or sqlcmd) alongside SQL Server Management Studio.
  • Include screenshots and step-by-step guides for Linux/macOS workflows where applicable.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
GitHub Create Pull Request
Private Link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-network-security-perimeter-cli.md .../private-link/create-network-security-perimeter-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation primarily uses Azure CLI commands, which are cross-platform, but there are subtle signs of Windows bias. The use of `$key_vault_name="key-vault-$(date +%s)"` assumes Bash syntax, which is Linux-friendly, but the command block for deleting an access rule is labeled as 'azurepowershell-interactive', suggesting a PowerShell context. There is no explicit mention of Linux or macOS environments, nor are there examples for Linux-specific shells or command patterns. The documentation does not clarify differences in command usage between Windows (PowerShell) and Linux (Bash), and does not provide Linux-specific troubleshooting or environment setup guidance. The only tool mentioned outside Azure CLI is Azure Cloud Shell, which is cross-platform, but the labeling of a CLI command block as 'azurepowershell-interactive' may confuse Linux users.
Recommendations
  • Ensure all command blocks are correctly labeled for their intended shell (e.g., Bash vs PowerShell).
  • Provide explicit examples for both Bash (Linux/macOS) and PowerShell (Windows), especially for variable assignment and command syntax.
  • Clarify any differences in environment setup or command usage between Windows and Linux/macOS.
  • Include troubleshooting tips for common issues encountered on Linux/macOS (e.g., permissions, path issues).
  • Avoid labeling Azure CLI commands as 'azurepowershell-interactive' unless they are truly PowerShell-specific.
GitHub Create Pull Request
← Previous Page 2 of 8 Next →