DNS

144
Total Pages
96
Linux-Friendly Pages
48
Pages with Bias
33.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

124 issues found
Showing 76-100 of 124 flagged pages
DNS Quickstart - Create an Azure private DNS zone using the Azure portal ...lob/main/articles/dns/private-dns-getstarted-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the test VM, referencing RDP for access, and providing only PowerShell-based examples for command execution and DNS testing. There are no instructions or examples for Linux VMs, Linux command-line tools, or SSH access, which may hinder Linux/macOS users from following the guide seamlessly.
Recommendations
  • Include parallel instructions for creating and configuring a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide examples for accessing the Linux VM via SSH, rather than only RDP for Windows.
  • Show how to test DNS resolution using Linux commands (e.g., ping, dig, nslookup) both from the portal (using RunShellScript) and via SSH.
  • Mention Azure CLI and Bash options for scripting and command execution, not just PowerShell.
  • Clarify that the steps can be performed on Linux/macOS and provide screenshots or terminal outputs from those platforms.
GitHub Create Pull Request
DNS Resolve Azure and on-premises domains. .../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Examples and procedures for configuring on-premises DNS focus exclusively on Windows DNS servers, with no mention of Linux-based DNS solutions (e.g., BIND, dnsmasq, Unbound). Quickstarts and next steps prioritize PowerShell and Windows-centric tools, with CLI options mentioned but not emphasized. There are no Linux/macOS-specific instructions or screenshots, and conditional forwarder configuration is only shown for Windows DNS.
Recommendations
  • Add equivalent instructions and screenshots for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
  • Include Linux/macOS CLI examples for DNS queries (e.g., using dig or nslookup) in the demonstration sections.
  • Mention Linux DNS server options explicitly in the 'Configure on-premises DNS conditional forwarders' section.
  • Balance quickstart links by including Linux-focused guides and examples alongside PowerShell/Windows ones.
  • Clarify that the procedures are applicable to both Windows and Linux environments, and provide parity in troubleshooting steps.
GitHub Create Pull Request
DNS Create and manage reverse DNS zones in Azure Private DNS ...ure-docs/blob/main/articles/dns/private-reverse-dns.md
Medium 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 provides only a Windows-centric example for testing DNS resolution, using the Windows command prompt and nslookup output. There are no Linux or macOS command-line examples, nor is there mention of equivalent Linux tools or output formats. The use of PowerShell-style output and Windows paths further reinforces the bias.
Recommendations
  • Include Linux/macOS command-line examples for testing DNS resolution, such as using 'nslookup', 'dig', or 'host' commands.
  • Show sample output from Linux/macOS terminals alongside Windows examples.
  • Explicitly mention that the DNS resolution steps can be performed on any OS, and provide cross-platform instructions.
  • Avoid using only Windows paths (e.g., 'C:\>') in command examples; use generic prompts or show both Windows and Unix-style prompts.
GitHub Create Pull Request
DNS Tutorial - Set up DNS failover using private resolvers ...articles/dns/tutorial-dns-private-resolver-failover.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the section on configuring on-premises DNS forwarding. Only Windows Server and PowerShell examples are provided for setting up conditional forwarders, with no mention of equivalent Linux/BIND configurations or commands. The use of Windows terminology and tools (PowerShell, DNS console) is exclusive, and Windows examples are presented first and solely, leaving Linux/macOS users without direct guidance for completing the task.
Recommendations
  • Add step-by-step instructions for configuring conditional forwarders on common Linux DNS servers (e.g., BIND/named.conf).
  • Provide Linux command-line examples (such as editing /etc/bind/named.conf.options and using systemctl to reload BIND) alongside Windows PowerShell examples.
  • Include notes or links to official documentation for Linux DNS server configuration.
  • Explicitly state that the procedure applies to both Windows and Linux environments, and clarify any differences.
  • Consider reordering or parallelizing examples so that Windows and Linux instructions are presented together.
GitHub Create Pull Request
DNS Tutorial: Create an alias record to support apex domain name with Traffic Manager ...azure-docs/blob/main/articles/dns/tutorial-alias-tm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server virtual machines and IIS for the web server setup, with all instructions, screenshots, and configuration steps tailored to Windows. There are no examples or guidance for deploying Linux-based VMs or web servers (e.g., Ubuntu with Apache or Nginx), nor any mention of Linux-specific setup or parity. This creates friction for users who prefer or require Linux environments.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) and installing a web server (Apache or Nginx), including CLI commands and portal steps.
  • Include screenshots and configuration details for Linux-based web server setup.
  • Provide guidance on editing the default web page for Apache/Nginx, analogous to the IIS steps.
  • Explicitly mention that either Windows or Linux VMs can be used, and link to relevant Linux setup documentation.
  • Ensure testing steps include Linux scenarios (e.g., using curl or browser to access Apache/Nginx).
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure portal ...ocs/blob/main/articles/dns/dns-import-export-portal.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by mentioning Windows DNS and its zone file location before mentioning BIND (the most common Linux DNS server). The Windows DNS path is given in detail, while the BIND section is brief and less explicit. No Linux command-line examples or tools (such as dig, named, or shell commands) are provided for obtaining zone files, whereas the Windows DNS console and file path are described. There are no PowerShell examples, but Windows-centric patterns are referenced first.
Recommendations
  • Present Linux/BIND instructions before or alongside Windows DNS instructions when describing how to obtain zone files.
  • Provide explicit Linux/BIND file path examples (e.g., /etc/bind/zones or /var/named) and mention how to locate them using named.conf.
  • Include Linux shell command examples for exporting or viewing zone files (e.g., cat, less, or named-compilezone).
  • Add references to common Linux DNS tools and workflows to balance the documentation.
  • Ensure parity in troubleshooting notes (e.g., error messages or file handling) for both Windows and Linux environments.
GitHub Create Pull Request
DNS Tutorial: Host your domain in Azure DNS ...lob/main/articles/dns/dns-delegate-domain-azure-dns.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line verification instructions using nslookup, referencing a 'command prompt' without specifying platform. This implicitly assumes Windows, as 'command prompt' is a Windows term, and nslookup is available on both platforms but no Linux-specific context (e.g., 'terminal', 'dig' command) is given. There are no Linux or macOS examples, nor are alternative tools or instructions for those platforms mentioned.
Recommendations
  • Include Linux/macOS terminology (e.g., 'terminal') alongside 'command prompt'.
  • Provide equivalent verification examples using the 'dig' command, which is commonly used on Linux/macOS.
  • Explicitly state that nslookup is available on multiple platforms, and provide installation instructions if needed.
  • Add a note or section for Linux/macOS users, ensuring parity in instructions and tool recommendations.
GitHub Create Pull Request
DNS Tutorial: Create an alias record to refer to a resource record in a zone ...azure-docs/blob/main/articles/dns/tutorial-alias-rr.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-centric instructions for testing DNS records (using nslookup from 'a command prompt'), without mentioning Linux or cross-platform alternatives. No Linux-specific tools or terminal commands are referenced, and the example assumes a Windows environment for verification steps.
Recommendations
  • Include Linux-specific instructions for testing DNS records, such as using 'dig' or 'host' commands.
  • Clarify that 'nslookup' is available on both Windows and Linux, and provide example commands for both platforms.
  • Replace references to 'command prompt' with 'terminal or command prompt', or specify steps for both Windows and Linux environments.
  • Add screenshots or terminal output examples from Linux systems to demonstrate parity.
  • Mention cross-platform DNS testing tools and provide guidance for macOS users as well.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver - Azure Resource Manager template (ARM template) ...icles/dns/dns-private-resolver-get-started-template.md
Medium Priority View Details →
Scanned: 2026-01-10 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 deploying the ARM template, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There is no explicit Linux shell (bash) example, nor is there any mention of Linux-specific tools or patterns. The validation steps are exclusively portal-based and do not reference cross-platform command-line validation.
Recommendations
  • Add explicit bash shell examples alongside Azure CLI and PowerShell, demonstrating deployment from a Linux/macOS environment.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and consider making CLI the default or first example.
  • Include validation steps using Azure CLI or REST API to verify deployment, not just portal screenshots.
  • Avoid presenting PowerShell as the only or primary alternative to CLI; mention other cross-platform automation options.
GitHub Create Pull Request
DNS What is a virtual network link subresource of Azure DNS private zones ...main/articles/dns/private-dns-virtual-network-links.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing PowerShell as a primary method for creating private DNS zones. This ordering can imply a preference for Windows-centric tooling, as PowerShell is traditionally associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux and macOS.
Recommendations
  • List Azure CLI before Azure PowerShell in examples and 'Next steps' to signal cross-platform parity.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for each platform.
  • Include example commands for both Azure CLI and PowerShell side-by-side in relevant sections to ensure equal visibility.
  • Add a note clarifying that users can choose either tool based on their operating system and preference.
GitHub Create Pull Request
DNS Delegate a subdomain - Azure DNS ...zure-docs/blob/main/articles/dns/delegate-subdomain.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-centric instructions for testing DNS delegation (using 'nslookup' at a command prompt) and referencing Azure PowerShell for automation, without mentioning Linux equivalents or CLI alternatives. There are no examples or instructions for Linux users, such as using Bash, dig, or Azure CLI.
Recommendations
  • Include Linux-specific instructions for testing DNS delegation, such as using 'dig' or 'nslookup' from a Bash terminal.
  • Mention Azure CLI as an alternative to Azure PowerShell for managing DNS zones and records, with example commands.
  • When referencing command-line tools, provide both Windows and Linux usage examples side-by-side.
  • Clarify that the steps can be performed from any OS, and link to cross-platform installation guides for Azure CLI and PowerShell.
GitHub Create Pull Request
DNS Integrate Azure DNS with your Azure resources - Azure DNS ...azure-docs/blob/main/articles/dns/dns-custom-domain.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-centric validation instructions, specifically referencing the 'nslookup' command and showing screenshots of its use in Windows CMD. There are no examples or instructions for performing DNS validation on Linux or macOS systems, nor are alternative tools (like 'dig') mentioned. This creates a subtle Windows bias by assuming the user is on a Windows environment and omitting Linux/macOS parity.
Recommendations
  • Include Linux/macOS equivalents for DNS validation, such as examples using the 'dig' command.
  • Add screenshots or terminal output from Linux/macOS environments to complement the Windows CMD examples.
  • Explicitly mention that DNS validation can be performed on any OS and provide cross-platform instructions.
  • Where 'nslookup' is referenced, note that it is available on multiple platforms, but also suggest alternatives like 'host' or 'dig' for Linux/macOS users.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Azure CLI ...zure-docs/blob/main/articles/dns/dns-getstarted-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in the 'Test the name resolution' section, where instructions refer to 'opening a command prompt' and show a screenshot of the Windows command prompt. The use of 'nslookup' is presented generically, but the context and visuals are Windows-centric. There are no Linux-specific instructions or screenshots, and alternative tools (e.g., 'dig') commonly used on Linux are not mentioned.
Recommendations
  • Include explicit instructions for testing DNS resolution on Linux and macOS, such as using 'nslookup' or 'dig' in a terminal.
  • Add screenshots or example outputs from Linux/macOS terminals alongside the Windows command prompt screenshot.
  • Replace 'Open a command prompt' with platform-neutral language like 'Open a terminal or command prompt'.
  • Mention that 'nslookup' is available on most platforms, and suggest alternatives like 'dig' for Linux users.
  • Ensure that all steps and examples are clearly applicable to all supported platforms, not just Windows.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver using Terraform ...cles/dns/dns-private-resolver-get-started-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 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 PowerShell is presented as a primary tab alongside CLI, and PowerShell-specific commands are included. There is no explicit mention of Linux-specific shell environments or examples, and PowerShell is a Windows-centric tool, which may signal a Windows bias. The instructions for running Terraform do not specify platform-specific commands, but the verification steps could be improved for Linux parity.
Recommendations
  • Add explicit Bash/Linux shell examples for verification steps, especially for variable assignment and command usage.
  • Clarify that Azure CLI commands work cross-platform and provide example shell syntax for Linux/macOS (e.g., export instead of $var=...).
  • Consider listing Azure CLI (which is cross-platform) before PowerShell, or clarify that PowerShell Core is available on Linux/macOS.
  • Include notes or tabs for Linux/macOS users where command syntax or environment setup differs.
  • Avoid presenting PowerShell as a default or primary option unless parity is ensured for Linux users.
GitHub Create Pull Request
DNS Quickstart: Use Terraform to configure private DNS zones in Azure ...s/blob/main/articles/dns/dns-private-zone-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively creating Windows virtual machines in the Terraform example and omitting Linux VM creation. The customer intent and checklist both specify Windows VMs only, and there are no Linux-specific instructions, examples, or parity in the resource creation steps.
Recommendations
  • Add parallel examples and instructions for creating Linux virtual machines alongside Windows VMs.
  • Update the checklist and customer intent to mention both Windows and Linux VM scenarios.
  • Provide sample Terraform code and output examples for Linux VM creation.
  • Include verification steps that demonstrate connecting to and managing Linux VMs (e.g., using SSH).
  • Clarify that the process applies to both Windows and Linux VMs, or provide separate quickstarts for each.
GitHub Create Pull Request
DNS What is autoregistration feature in Azure DNS private zones? ...blob/main/articles/dns/private-dns-autoregistration.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page mentions Azure PowerShell before Azure CLI in the 'Next steps' section, which may suggest a Windows-first bias. The primary example for creating a private zone is given using PowerShell, a Windows-centric tool, before mentioning the cross-platform Azure CLI. No explicit Linux examples or Linux-specific tools are provided.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to ensure cross-platform parity.
  • Explicitly mention that Azure CLI is available on Linux and macOS, and provide links or notes for Linux users.
  • Include screenshots or instructions that demonstrate the process on Linux environments, not just Windows.
  • Add a note clarifying that both PowerShell and CLI are supported on multiple platforms, and provide guidance for Linux users where relevant.
GitHub Create Pull Request
DNS Tutorial: Create an Azure DNS alias record to refer to an Azure public IP address ...zure-docs/blob/main/articles/dns/tutorial-alias-pip.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server for the virtual machine example, including instructions for installing IIS via Windows GUI and connecting via RDP. There are no examples or instructions for deploying a Linux VM, installing a web server (e.g., Apache or Nginx), or connecting via SSH. All screenshots and step-by-step guidance are Windows-centric, and Linux alternatives are not mentioned.
Recommendations
  • Add parallel instructions for creating a Linux-based VM (e.g., Ubuntu) and installing a web server (Apache or Nginx) using SSH and command-line tools.
  • Include screenshots and steps for Linux VM setup and web server verification.
  • Explicitly mention that the tutorial applies to both Windows and Linux VMs, and provide links to relevant Linux documentation.
  • Where possible, use generic Azure portal steps that apply to both OS types, or clearly indicate OS-specific differences.
GitHub Create Pull Request
DNS Import and export a domain zone file for Azure private DNS - Azure CLI ...cs/blob/main/articles/dns/private-dns-import-export.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation mentions Windows DNS and its default zone file location before mentioning BIND (Linux), and provides specific Windows paths and console instructions. There is a slight prioritization of Windows tooling and conventions when describing how to obtain zone files, with Windows DNS discussed before BIND. However, the CLI examples themselves are cross-platform and do not show PowerShell or Windows-only commands.
Recommendations
  • Present Linux/BIND and Windows DNS sources in parallel or alternate the order to avoid Windows-first bias.
  • Include explicit Linux file path examples for BIND (e.g., /etc/bind/zones/) alongside Windows paths.
  • Clarify that the Azure CLI commands work identically on Linux, macOS, and Windows, and consider showing example CLI usage on Linux (e.g., using bash).
  • Add notes or examples for verifying zone files using Linux-native tools (e.g., dig) in addition to nslookup.
  • Ensure that any references to file paths or system tools are balanced between Windows and Linux environments.
GitHub Create Pull Request
DNS Tutorial: Create an Azure child DNS zone ...b/main/articles/dns/tutorial-public-dns-zones-child.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all instructions and does not provide any command-line examples. While it avoids explicit Windows tools or PowerShell, the absence of CLI instructions (such as Azure CLI or Bash) means Linux users are not given parity. The UI-centric approach implicitly favors Windows users, who are more likely to use graphical interfaces, and omits guidance for those who prefer or require command-line automation, common in Linux environments.
Recommendations
  • Add equivalent Azure CLI commands for all major steps (creating child DNS zone, verifying NS records, deleting resources), with example usage in Bash.
  • Explicitly mention that all steps can be performed via CLI and provide links to relevant Azure CLI documentation.
  • Include a section comparing portal and CLI workflows, highlighting cross-platform options.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid references to Windows-only features or terminology).
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver using Terraform ...cles/dns/dns-private-resolver-get-started-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 both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is present and shown alongside CLI, which is often associated with Windows environments. There is no explicit mention of Linux/macOS-specific tools or shell patterns, nor are there any examples using Bash or other Linux-native commands. The CLI examples are cross-platform, but PowerShell is Windows-centric, and its inclusion may suggest a slight Windows bias. However, Linux users can complete all tasks using the CLI instructions.
Recommendations
  • Clearly indicate that Azure CLI commands work on Linux/macOS as well as Windows.
  • Add explicit Bash shell examples for variable assignment and command usage, especially for Linux/macOS users.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest CLI for cross-platform use.
  • Consider listing CLI examples before PowerShell, or defaulting to CLI as the primary example.
GitHub Create Pull Request
DNS Fallback to internet for Azure Private DNS zones ...re-docs/blob/main/articles/dns/private-dns-fallback.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 mild Windows bias. DNS query examples consistently use Windows command prompt syntax (e.g., 'C:\>dig ...') and nslookup output from Windows, even though the dig command is cross-platform and commonly used on Linux/macOS. Screenshots and instructions reference the Azure portal, which is platform-neutral, and Azure CLI examples are also cross-platform. However, Windows-style command prompts are shown first and exclusively, and there is no explicit mention or illustration of running equivalent commands on Linux/macOS (e.g., using a Bash shell).
Recommendations
  • Provide DNS query examples using both Windows (cmd.exe) and Linux/macOS (bash) shells, e.g., show '$ dig ...' or '$ nslookup ...' in addition to 'C:\>'.
  • Clarify that the dig command is available on Linux/macOS by default, and provide installation instructions for Windows users if needed.
  • Include screenshots or output examples from Linux/macOS terminals where appropriate.
  • Avoid using Windows-specific prompt notation ('C:\>') as the default; use generic or platform-appropriate prompts.
  • Explicitly state that all Azure CLI commands work on Linux/macOS as well as Windows.
GitHub Create Pull Request
DNS What is a virtual network link subresource of Azure DNS private zones ...main/articles/dns/private-dns-virtual-network-links.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references Azure PowerShell before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach and a bias towards PowerShell, which is traditionally associated with Windows. No Linux/macOS-specific tools or examples are mentioned, and PowerShell is listed before CLI, which is more cross-platform.
Recommendations
  • Present Azure CLI and PowerShell options together, or list CLI first to reflect its cross-platform nature.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
  • Add links or notes about using Azure CLI on Linux/macOS to encourage parity.
  • Ensure that examples and walkthroughs are balanced between PowerShell and CLI, or provide Bash examples where appropriate.
GitHub Create Pull Request
DNS Delegate a subdomain - Azure DNS ...zure-docs/blob/main/articles/dns/delegate-subdomain.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by providing command-line testing instructions using 'nslookup' at a 'command prompt', which is a Windows-centric term. No Linux/macOS terminal instructions or alternative tools (e.g., 'dig') are mentioned. All examples and screenshots are from the Azure portal, which is cross-platform, but the only CLI example is Windows-focused.
Recommendations
  • Include Linux/macOS terminal instructions for testing DNS delegation, e.g., using 'nslookup' or 'dig' in a bash shell.
  • Replace 'command prompt' with 'terminal' or specify both Windows and Linux/macOS environments.
  • Add examples using Linux tools (such as 'dig') alongside 'nslookup'.
  • Clarify that the Azure portal steps are platform-agnostic.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Bicep ...e-docs/blob/main/articles/dns/dns-get-started-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 examples for all deployment, validation, and cleanup steps. However, PowerShell is featured equally alongside CLI, and there is no mention of Linux-specific shell environments (e.g., Bash) or macOS. The CLI examples are cross-platform, but PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since it is presented as an equal alternative without clarifying platform compatibility.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS, while Azure PowerShell is primarily for Windows (though cross-platform versions exist).
  • Consider listing Azure CLI examples first, as it is the most cross-platform tool.
  • Add explicit notes or links for Linux/macOS users, such as installation instructions for Azure CLI on those platforms.
  • Avoid presenting PowerShell as an equal default for all users; indicate its platform specificity.
  • Include Bash or shell script examples where appropriate, or mention that CLI commands can be run in Bash, Zsh, etc.
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure CLI ...azure-docs/blob/main/articles/dns/dns-import-export.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in several areas. When discussing how to obtain an existing DNS zone file, the Windows DNS file location is described in detail and mentioned before the BIND/Linux equivalent. In the verification section, the use of Windows Command Prompt for nslookup is explicitly shown, with no equivalent Linux/macOS example (e.g., Bash shell). The nslookup example uses Windows-specific syntax and output, and there is no mention of Linux or macOS command-line usage for this step.
Recommendations
  • Provide Linux/macOS equivalents for all command-line examples, especially for nslookup verification (e.g., show how to run nslookup in Bash or Terminal).
  • When listing DNS zone file locations, present BIND/Linux and Windows options in parallel, or mention Linux/BIND first to avoid Windows-first ordering.
  • Clarify that Azure CLI commands work identically across platforms and show sample commands in a cross-platform shell (e.g., Bash, PowerShell, zsh) where appropriate.
  • Avoid referencing Windows-specific tools or folders without also mentioning Linux/macOS equivalents.
GitHub Create Pull Request
← Previous Page 4 of 5 Next →