DNS

73
Total Pages
24
Linux-Friendly Pages
49
Pages with Bias
67.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

323 issues found
Showing 76-100 of 323 flagged pages
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-traffic-log-how-to.md ...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell-based instructions and examples, referencing Windows-specific tools and file paths (e.g., C:\bin\PSRepo), and omitting equivalent Linux CLI or shell examples for key tasks such as creating and managing DNS security policies. The PowerShell tab is the only CLI automation option presented, and there are no Bash/Azure CLI or Linux-native workflow examples. Additionally, Windows-centric terminology and patterns (such as environment variables and error messages) are used throughout, with no guidance for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) and Bash examples for all PowerShell commands, including resource creation, policy management, and diagnostics.
  • Include Linux file paths and environment variable usage in examples, or clarify cross-platform differences.
  • Provide instructions for installing and using Azure CLI on Linux/macOS, and reference Linux package managers where appropriate.
  • Ensure that all screenshots and sample outputs include Linux terminal examples alongside Windows/PowerShell.
  • Explicitly mention cross-platform compatibility and provide troubleshooting tips for Linux users.
  • Consider adding a 'Linux/macOS' tab alongside 'PowerShell' and 'Portal' for parity in step-by-step guides.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dnssec-how-to.md ...ocs/azure-docs/blob/main/articles/dns/dnssec-how-to.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples, referencing Windows-specific tools (e.g., dig.exe), and presenting Windows-centric command-line instructions. The CLI and PowerShell tabs are both present, but Linux-specific guidance (such as bash, shell, or Linux-native dig usage) is missing. The use of Windows tools and terminology is prioritized, and there are no explicit Linux or macOS examples or instructions.
Recommendations
  • Add Linux/macOS-specific command-line examples, such as using bash or zsh shells.
  • Reference and provide examples for the dig command as used on Linux/macOS (not just dig.exe).
  • Include instructions for installing required tools (e.g., dig) on Linux distributions.
  • Ensure parity by providing equivalent steps for Linux environments, such as using Azure CLI in bash and showing output formatting with jq or grep.
  • Clarify that Azure CLI commands work cross-platform and provide sample outputs for Linux/macOS terminals.
  • Avoid using Windows-specific terminology (e.g., dig.exe) when referring to cross-platform tools.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dnssec.md ...rosoftDocs/azure-docs/blob/main/articles/dns/dnssec.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools (PowerShell's Resolve-DnsName) and Windows-specific concepts (Group Policy, NRPT) in both explanations and examples. Command-line examples are given first in PowerShell, with dig.exe (the standard cross-platform DNS tool) shown second and labeled as 'dig.exe', which is a Windows naming convention. There are no explicit Linux or macOS command-line examples, and Linux-native usage patterns (such as 'dig' on Linux/macOS, or 'host', or 'drill') are not mentioned. Windows administrative tools and policies are referenced without Linux equivalents, and the documentation assumes familiarity with Windows environments.
Recommendations
  • Provide Linux/macOS command-line examples using 'dig' and/or 'host' alongside or before Windows PowerShell examples.
  • Refer to 'dig' as simply 'dig', not 'dig.exe', to reflect its cross-platform nature.
  • Mention how to install and use these tools on Linux/macOS (e.g., 'apt install dnsutils', 'brew install bind').
  • Balance references to Windows-specific tools (e.g., Group Policy, NRPT) with Linux equivalents or note their absence.
  • Explicitly state that the instructions and examples apply to both Windows and Linux/macOS, and clarify any OS-specific differences.
  • Consider including a table or section comparing DNSSEC validation and troubleshooting steps on Windows, Linux, and macOS.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-getstarted-cli.md ...s/blob/main/articles/dns/private-dns-getstarted-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias in several ways: all VM creation examples use Windows images, all test and verification steps (firewall configuration and ping) use Windows PowerShell commands and Windows output, and there are no Linux VM creation or Linux command examples. The instructions for configuring ICMP and testing DNS resolution are exclusively Windows-focused, with no mention of Linux equivalents or cross-platform alternatives.
Recommendations
  • Include examples for creating Linux VMs (e.g., using --image UbuntuLTS) alongside Windows VM creation.
  • Provide Linux command equivalents for configuring firewalls to allow ICMP (e.g., using ufw or firewall-cmd).
  • Show Linux shell commands and output for DNS resolution tests (e.g., using ping and dig from a bash shell).
  • Add notes or sections highlighting differences or additional steps for Linux users.
  • Ensure that cross-platform parity is maintained throughout, especially in verification and troubleshooting steps.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-import-export-portal.md .../main/articles/dns/private-dns-import-export-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page mentions Windows DNS and its default zone file location before mentioning BIND (the most common Linux DNS server). It provides explicit details for Windows DNS administrators (folder path, console tab) but only briefly references BIND's configuration file. There are no concrete Linux or BIND-based examples, screenshots, or step-by-step instructions. The page does not mention Linux tools or commands for obtaining zone files, and the only explicit file path given is Windows-specific.
Recommendations
  • Add explicit instructions and examples for obtaining zone files from BIND and other Linux DNS servers, including typical file paths (e.g., /etc/bind/).
  • Provide sample commands for copying or exporting zone files on Linux (e.g., using cp, scp, or named tools).
  • Include screenshots or walkthroughs for BIND/Linux environments where relevant.
  • Mention Linux file system conventions alongside Windows paths when discussing zone file locations.
  • Ensure parity in detail and clarity between Windows and Linux guidance for DNS administrators.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-migration-guide.md .../blob/main/articles/dns/private-dns-migration-guide.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 page exhibits a strong Windows bias. The migration process is described exclusively in terms of PowerShell scripts and modules, with all step-by-step instructions assuming the use of Windows and PowerShell. There are no equivalent Bash, Azure CLI, or Linux-native instructions for running the migration, installing required tools, or verifying DNS resolution. The prerequisites and script installation steps reference Windows administrative privileges and PowerShell Gallery, with no mention of Linux alternatives or cross-platform compatibility.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for the migration process, ensuring Linux users can perform the migration without relying on PowerShell.
  • Include instructions for installing required modules and running scripts on Linux/macOS environments, using cross-platform tools where possible.
  • Clarify whether the migration script can run on PowerShell Core (pwsh) on Linux/macOS, and provide troubleshooting steps for non-Windows platforms.
  • Add explicit examples for verifying DNS resolution using Linux tools (e.g., dig, nslookup on Linux) and mention how to perform each step on Linux VMs.
  • Reorder documentation so that cross-platform or CLI approaches are presented alongside or before Windows/PowerShell-specific instructions.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-resolver-architecture.md ...lob/main/articles/dns/private-resolver-architecture.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where instructions for creating an Azure DNS Private Resolver are provided only for Azure PowerShell and Azure Portal, with no mention of Linux CLI tools (such as Azure CLI or Bash). The examples and architectural guidance do not reference platform-specific DNS client configuration or troubleshooting, but the absence of Linux-specific guidance and the prioritization of PowerShell (a Windows-centric tool) indicate a Windows-first approach.
Recommendations
  • Add instructions and examples for creating and managing Azure DNS Private Resolver using Azure CLI (az), which is cross-platform and widely used on Linux.
  • Include references or links to documentation for configuring DNS on Linux VMs (e.g., using resolv.conf, systemd-resolved, or netplan) in Azure environments.
  • Provide troubleshooting steps or examples for both Windows and Linux clients to ensure parity in operational guidance.
  • When listing tools or methods (e.g., PowerShell, Portal), mention Azure CLI first or alongside PowerShell to avoid Windows-first bias.
  • Consider adding explicit notes or sections for Linux administrators to clarify any platform-specific considerations.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-getstarted-portal.md ...lob/main/articles/dns/private-dns-getstarted-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias primarily by guiding users to create a Windows Server VM for testing, providing only Windows-based examples (such as using PowerShell and RDP), and omitting Linux VM creation or Linux command-line examples for DNS resolution. The test and verification steps are exclusively Windows-centric, with no mention of Linux alternatives.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows Server VM example.
  • Provide Linux command-line examples for DNS resolution (e.g., using 'ping', 'dig', or 'nslookup' in a Linux shell) in addition to PowerShell.
  • Mention SSH as an access method for Linux VMs, and show how to use the Azure portal's 'Run command' feature for Bash scripts.
  • Where PowerShell is referenced, also reference Bash/CLI equivalents for Linux users.
  • Ensure screenshots and command outputs reflect both Windows and Linux environments to improve parity and inclusivity.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-overview.md ...re-docs/blob/main/articles/dns/private-dns-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. The mention of 'Familiar tools' highlights Azure PowerShell as a primary management tool, which is more commonly associated with Windows environments. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific tools or patterns, which may leave Linux users underserved.
Recommendations
  • Present Azure CLI and PowerShell equally, or list Azure CLI first to avoid Windows-first perception.
  • Include explicit examples or links for Linux/Bash usage, such as shell scripts or command-line instructions for Linux users.
  • Mention cross-platform compatibility of Azure CLI and PowerShell, and clarify that both can be used on Windows, Linux, and macOS.
  • Add references to Linux-specific DNS management scenarios or tools where relevant.
  • Ensure that screenshots and walkthroughs include Linux terminal examples alongside PowerShell.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-resiliency.md ...-docs/blob/main/articles/dns/private-dns-resiliency.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the link to creating a Private DNS zone specifically references a PowerShell-based guide. There is no mention of Linux tools, CLI, or cross-platform alternatives, nor are Linux-specific examples or instructions provided. This prioritizes Windows/PowerShell workflows and omits guidance for users on Linux or macOS platforms.
Recommendations
  • Include links to Azure CLI and REST API guides for creating Private DNS zones, which are cross-platform and commonly used on Linux.
  • Add explicit examples or instructions for Linux users, such as using Bash with Azure CLI.
  • Ensure that documentation references both Windows and Linux workflows equally, or provide a unified, platform-neutral approach.
  • Review related documentation pages to ensure parity in example coverage and tool recommendations.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-resolver-endpoints-rulesets.md ...in/articles/dns/private-resolver-endpoints-rulesets.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Azure PowerShell as the main automation/configuration example, with no mention of Linux CLI equivalents (such as Azure CLI or Bash scripting). The 'Next steps' section lists PowerShell before the portal and omits Linux-oriented tooling. There are no examples or instructions for Linux users, and no mention of cross-platform command-line tools or patterns.
Recommendations
  • Add Azure CLI (az) examples alongside or before PowerShell examples to ensure Linux parity.
  • Explicitly mention that configuration can be performed from Linux, macOS, and Windows using Azure CLI.
  • Include Bash scripting examples for automation scenarios.
  • In 'Next steps', list Azure CLI and cross-platform tools before or alongside PowerShell.
  • Clarify that the Azure portal and CLI are available on all major platforms.
  • Review screenshots and instructions to ensure they are not Windows-specific (e.g., avoid showing only Windows UI elements).
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-resolver-hybrid-dns.md .../blob/main/articles/dns/private-resolver-hybrid-dns.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing examples and procedures primarily for Windows DNS servers, referencing Windows DNS tools and configuration steps, and omitting equivalent Linux/BIND DNS server instructions. All on-premises DNS configuration examples use Windows DNS, and there are no Linux/BIND examples or mentions. Additionally, PowerShell is referenced before CLI in several places.
Recommendations
  • Add equivalent Linux/BIND DNS server configuration steps for conditional forwarders, including screenshots or command-line examples.
  • Include CLI and Linux-based examples alongside PowerShell and Windows instructions, ensuring both are presented with equal prominence.
  • Explicitly mention that the procedures apply to both Windows and Linux environments, and provide links to relevant Linux/BIND documentation.
  • Where possible, alternate the order of Windows and Linux examples to avoid 'windows_first' bias.
  • Clarify tool requirements for both platforms (e.g., PowerShell for Windows, dig/nsupdate for Linux) in the prerequisites.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-dns-private-resolver-failover.md ...articles/dns/tutorial-dns-private-resolver-failover.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. The only example for configuring DNS forwarding is provided for Windows Server using PowerShell, with no equivalent instructions for Linux-based DNS servers (such as BIND or dnsmasq). Windows terminology and tools (PowerShell, DNS console) are used exclusively, and Windows-specific procedures are described before any mention of alternatives. There is no guidance for Linux administrators, nor are Linux tools or commands referenced.
Recommendations
  • Add step-by-step instructions for configuring DNS forwarding on common Linux DNS servers (e.g., BIND, dnsmasq, Unbound), including example configuration file snippets.
  • Provide Linux command-line examples (such as using dig or nslookup from a Linux shell) alongside Windows examples.
  • Include notes or sections that address cross-platform differences and considerations for both Windows and Linux environments.
  • Avoid assuming Windows as the default platform; present both Windows and Linux procedures in parallel or clearly indicate platform-specific steps.
  • Reference Linux documentation or external resources for further guidance on DNS configuration in non-Windows environments.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-reverse-dns.md ...ure-docs/blob/main/articles/dns/private-reverse-dns.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its example for testing DNS resolution, showing only a Windows command prompt (C:\>) and using nslookup in a PowerShell-style code block. There are no Linux or cross-platform examples for verifying reverse DNS, and the only command-line example is Windows-centric. No Linux tools (e.g., dig) or Linux shell prompts are mentioned.
Recommendations
  • Include equivalent Linux/macOS examples for testing DNS resolution, such as using 'nslookup' or 'dig' from a Bash shell.
  • Show both Windows (C:\>) and Linux ($) command prompts in example blocks to clarify cross-platform usage.
  • Mention that the Azure portal steps are platform-agnostic, but command-line verification can be done on any OS.
  • Add a note or section highlighting Linux tools and commands for DNS testing, ensuring parity with Windows instructions.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-get-started-template.md ...ocs/blob/main/articles/dns/dns-get-started-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell and Windows command prompt (cmd) examples for deploying and validating the ARM template. Linux equivalents, such as Azure CLI or bash shell instructions, are missing. The use of PowerShell is emphasized throughout, and the validation step uses Windows cmd syntax for nslookup without mentioning Linux/macOS alternatives.
Recommendations
  • Add Azure CLI examples for deploying the ARM template, using bash syntax.
  • Include Linux/macOS terminal instructions for running nslookup (e.g., 'nslookup www.<dns zone name> <name server name>' in bash).
  • Present deployment and validation steps for both Windows and Linux platforms, ideally side-by-side or with clear headings.
  • Mention that Azure Cloud Shell supports both PowerShell and Bash, and provide guidance for users to select their preferred shell.
  • Where screenshots or output are shown, clarify if they are from Windows or Linux, and provide Linux equivalents if possible.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-traffic-log-how-to.md ...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell-based instructions and examples, referencing Windows filesystem paths (e.g., C:\bin\PSRepo), and using Windows-specific tools like Resolve-DnsName. There are no equivalent Linux CLI or shell examples for creating or managing DNS security policies, nor is there guidance for using Azure CLI, Bash, or Linux-native tools. The PowerShell tab is detailed and comprehensive, while Linux users are left to infer or adapt from Windows-centric instructions.
Recommendations
  • Add Linux/Bash/Azure CLI examples for all major operations, including resource creation, policy management, and testing DNS queries.
  • Include instructions for installing and using Azure CLI on Linux, and provide parity in example scripts.
  • Show how to use Linux-native DNS query tools (e.g., dig, nslookup) for testing and validation, with sample outputs.
  • Reference Linux filesystem conventions (e.g., /home/user/PSRepo) alongside Windows paths where relevant.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users in each section.
  • Consider adding a 'Linux' tab alongside 'PowerShell' and 'Portal' for step-by-step parity.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-web-sites-custom-domain.md .../blob/main/articles/dns/dns-web-sites-custom-domain.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples and terminology are prominent throughout, and Windows-centric tools (such as nslookup with Windows prompt) are used for DNS testing. In several sections, PowerShell instructions precede Azure CLI, and the CLI examples use syntax (e.g., cut) that may not be universally portable to all Linux shells. There is no explicit mention or example of Linux-native DNS tools (like dig), nor guidance for Linux users outside Azure CLI.
Recommendations
  • Provide Linux-native DNS testing examples (e.g., using dig) alongside nslookup.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes where needed.
  • Avoid Windows-centric prompt notation (e.g., 'PS C:\>') in generic DNS testing sections.
  • Ensure parity in ordering: present Azure CLI examples before or alongside PowerShell, not after.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and link to platform-specific setup guides for Azure CLI and PowerShell.
  • Add troubleshooting notes for common Linux issues (e.g., DNS caching, shell differences) where relevant.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-protect-zones-recordsets.md ...blob/main/articles/dns/dns-protect-zones-recordsets.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently providing Azure PowerShell examples before Azure CLI, and in some cases (record set level resource locks), only PowerShell is supported or documented. There are no explicit Linux shell examples (e.g., bash), and the use of PowerShell-centric patterns and terminology may disadvantage Linux users. The documentation does not mention Linux-specific tooling or provide parity for scenarios where CLI or portal support is missing.
Recommendations
  • Where only PowerShell is supported (e.g., record set level resource locks), explicitly note the lack of CLI/Linux support and provide workarounds or alternatives if possible.
  • Provide bash/Linux shell equivalents for Azure CLI examples, including environment variable usage and scripting patterns common in Linux.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Add notes or links to Linux-specific guidance for managing Azure DNS resources, especially for scenarios where PowerShell is required.
  • Review and update screenshots and UI instructions to clarify cross-platform availability (e.g., note when features are portal-only, PowerShell-only, or CLI-supported).
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-scenarios.md ...e-docs/blob/main/articles/dns/private-dns-scenarios.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where the link to 'create a Private DNS zone' points to a PowerShell-based guide, implicitly prioritizing Windows tooling. There are no examples or references to Linux command-line tools (such as Azure CLI or Bash), nor are Linux-specific patterns or instructions provided. The absence of Linux examples and the exclusive mention of PowerShell suggest a bias towards Windows users.
Recommendations
  • Include links to equivalent Linux/Azure CLI guides for creating and managing Private DNS zones.
  • Provide example commands using Azure CLI and Bash alongside PowerShell examples.
  • Explicitly mention cross-platform support and direct users to documentation for both Windows and Linux environments.
  • Ensure that all scenarios and instructions are presented in a way that is platform-neutral, or that both Windows and Linux approaches are given equal prominence.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-resolver-hybrid-dns.md .../blob/main/articles/dns/private-resolver-hybrid-dns.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing examples and procedures primarily for Windows environments. PowerShell is featured as a main automation method, and the only on-premises DNS configuration example uses Windows DNS Manager. There are no Linux/BIND examples or references, and Windows tools and terminology are presented first and exclusively in several sections.
Recommendations
  • Add equivalent Linux/BIND DNS server configuration steps for conditional forwarders.
  • Include CLI examples using Azure CLI and bash for all Azure resource creation steps.
  • Provide screenshots or command-line output from Linux environments where DNS queries are demonstrated.
  • Explicitly mention support for non-Windows DNS servers and link to relevant documentation.
  • Reorder examples so that Windows and Linux approaches are presented side-by-side or Linux is not always secondary.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-private-resolver-overview.md ...lob/main/articles/dns/dns-private-resolver-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Azure PowerShell and the Azure portal as the primary methods for setup and management, with no mention of Linux-native tools or CLI examples. PowerShell is highlighted both in quickstart links and in the 'Next steps' section, while Linux-friendly alternatives such as Azure CLI or Bash scripts are absent. There are no examples or guidance for Linux administrators, nor are Linux DNS tools (e.g., dig, resolv.conf) discussed in the context of DNS configuration.
Recommendations
  • Add Azure CLI-based quickstart and setup instructions alongside PowerShell and portal examples.
  • Include Linux/Bash command examples for DNS resolution and configuration, such as using dig or nslookup.
  • Explicitly mention cross-platform support and provide guidance for both Windows and Linux environments.
  • Ensure parity in troubleshooting and operational guidance for Linux-based DNS servers and clients.
  • Reference Linux DNS configuration files (e.g., /etc/resolv.conf) when discussing DNS client settings.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-reverse-dns-for-azure-services.md ...ain/articles/dns/dns-reverse-dns-for-azure-services.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell and classic PowerShell examples, using Windows-centric tooling and terminology, and omitting Linux-native command-line examples (such as Bash or shell scripting). All code samples use PowerShell or Azure CLI, with no mention of Linux-specific tools or usage patterns. The PowerShell examples are presented first in each section, reinforcing Windows as the default environment. There are no instructions for configuring reverse DNS using Linux-native tools or workflows, nor any guidance for users working in non-Windows environments.
Recommendations
  • Add explicit Bash and shell scripting examples for Azure CLI commands, demonstrating usage in Linux environments.
  • Clarify that Azure CLI is cross-platform and provide instructions for installing and using it on Linux and macOS.
  • Reorder examples so that Azure CLI (cross-platform) instructions appear before PowerShell, or present them side-by-side.
  • Include troubleshooting tips and environment setup steps for Linux users (e.g., authentication, environment variables).
  • Reference Linux-native DNS tools (such as dig, nslookup) for validation and verification steps.
  • Avoid using Windows/PowerShell-specific terminology (such as 'DomainNameLabel' property in PowerShell) without cross-referencing equivalent CLI parameters.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md ...ocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed instructions and code samples for PowerShell and Azure CLI, but lacks explicit Linux shell examples (e.g., bash). The CLI section uses the 'azurepowershell-interactive' code block, which may be confusing for Linux users. The PowerShell tab is present and detailed, while there is no equivalent bash or Linux shell tab. Windows tools (PowerShell) are mentioned and demonstrated, but Linux-native tools or usage patterns are not addressed.
Recommendations
  • Add a dedicated Linux/bash tab with equivalent Azure CLI commands using standard bash syntax and conventions.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide examples of command-line usage in bash.
  • Avoid using 'azurepowershell-interactive' as the code block language for Azure CLI examples; use 'bash' or 'azurecli' instead.
  • Explicitly mention cross-platform compatibility for CLI commands and provide troubleshooting tips for Linux users.
  • Ensure that Linux and macOS users are addressed in prerequisites and instructions, not just Windows/PowerShell users.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-import-export.md ...azure-docs/blob/main/articles/dns/dns-import-export.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows DNS file locations before BIND (Linux), providing explicit instructions for Windows Command Prompt and nslookup, and omitting Linux-specific verification examples (e.g., using dig or Linux shell commands). The only verification example is for Windows Command Prompt, and there is no mention of Linux equivalents or usage patterns.
Recommendations
  • Present BIND (Linux) zone file locations before or alongside Windows DNS locations.
  • Include Linux shell examples for verifying DNS records, such as using dig or nslookup in a Linux terminal.
  • Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and show sample commands in a Linux shell context (e.g., bash).
  • Add instructions for viewing exported/imported zone files using common Linux tools (cat, less, grep).
  • Provide parity in troubleshooting and verification steps for both Windows and Linux environments.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-protect-private-zones-recordsets.md ...n/articles/dns/dns-protect-private-zones-recordsets.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently providing Azure PowerShell examples before Azure CLI, referencing PowerShell-specific tools and patterns, and omitting Linux-specific shell or scripting examples. Resource lock operations for record sets are only documented for PowerShell, with no CLI or Linux alternatives. There is no mention of Linux-native tools, nor are bash or shell script examples provided, despite Azure CLI being cross-platform.
Recommendations
  • Provide Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Include bash/shell script snippets for Azure CLI commands to demonstrate usage on Linux/macOS.
  • Explicitly state platform compatibility for each tool and example, clarifying when features are Windows-only or cross-platform.
  • Where functionality is unavailable in Azure CLI (e.g., record set locks), acknowledge the limitation and suggest workarounds for Linux users.
  • Add a section or note on using these tools from Linux/macOS, including installation and environment setup guidance.
  • Avoid language or ordering that implies PowerShell is the default or preferred method, unless required by Azure platform limitations.
GitHub Create Pull Request
← Previous Page 4 of 13 Next →