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 51-75 of 323 flagged pages
DNS Quickstart - Create an Azure private DNS zone using the Azure CLI ...s/blob/main/articles/dns/private-dns-getstarted-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 Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a clear Windows bias in several areas. All virtual machine creation examples use Windows images exclusively, and all testing instructions (firewall configuration, ping commands, and output) are provided only for Windows/PowerShell environments. There are no Linux VM creation examples, nor any Linux-specific instructions for configuring firewalls or testing DNS resolution. The use of Windows PowerShell commands and screenshots further reinforces the bias toward Windows users.
Recommendations
  • Include Linux VM creation examples (e.g., using --image UbuntuLTS) alongside Windows examples.
  • Provide Linux-specific instructions for configuring firewalls to allow ICMP (e.g., using ufw or iptables).
  • Show how to test DNS resolution and ping from a Linux shell (bash), including sample output.
  • Present both Windows and Linux command-line examples in parallel throughout the guide.
  • Clarify that the Azure CLI works cross-platform and highlight any OS-specific considerations.
  • Avoid assuming the user is on Windows; use neutral language and examples where possible.
GitHub Create Pull Request
DNS Azure Private DNS: Secure DNS for Virtual Networks ...re-docs/blob/main/articles/dns/private-dns-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 a Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. There is a lack of explicit Linux or cross-platform examples, and no mention of Linux-specific tools or patterns. The documentation references 'familiar tools' but does not provide parity in example order or highlight Linux usage, which may make Linux users feel secondary.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell to emphasize cross-platform support.
  • Explicitly mention Linux compatibility and provide Linux-specific usage notes where relevant.
  • Include example commands for both Windows (PowerShell) and Linux (Bash/CLI) in quickstarts and tutorials.
  • Reference Linux administration tools and patterns where appropriate, not just Windows-centric ones.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and link to installation guides for those platforms.
GitHub Create Pull Request
DNS Scenarios for Azure Private DNS zones ...e-docs/blob/main/articles/dns/private-dns-scenarios.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 by referencing only the PowerShell-based getting started guide for creating a Private DNS zone, without mentioning or linking to equivalent Linux/CLI/Bash instructions. There are no Linux-specific examples, tools, or command-line patterns provided, and the only explicit next step for hands-on setup is PowerShell-focused. This may lead Linux or cross-platform users to feel unsupported or unclear about how to proceed.
Recommendations
  • Add links to Azure CLI and/or Bash-based tutorials for creating and managing Private DNS zones alongside the PowerShell guide.
  • Explicitly mention that Azure DNS management can be performed from Windows, Linux, and macOS using the Azure CLI, and provide relevant documentation links.
  • Include example commands or code snippets for both PowerShell and Azure CLI/Bash in relevant sections.
  • Ensure that all hands-on or 'Next steps' sections offer parity between Windows and Linux tooling and instructions.
GitHub Create Pull Request
DNS Azure Private DNS zone resiliency ...-docs/blob/main/articles/dns/private-dns-resiliency.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 exhibits Windows bias by referencing a PowerShell-based guide for creating a Private DNS zone in the 'Next steps' section, without mentioning or linking to equivalent Linux or cross-platform CLI instructions. The example and instructions prioritize Windows tooling and do not provide parity for Linux users.
Recommendations
  • Include links to Azure CLI and/or Bash-based instructions for creating and managing Private DNS zones alongside the PowerShell guide.
  • Explicitly mention cross-platform options (e.g., Azure CLI, REST API) in 'Next steps' to ensure Linux users are aware of alternatives.
  • Review the documentation for other sections where Windows tools or patterns are referenced first, and provide Linux equivalents in parallel.
GitHub Create Pull Request
DNS Private resolver architecture ...lob/main/articles/dns/private-resolver-architecture.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 a Windows bias primarily in its 'Next steps' section, where instructions for creating an Azure DNS Private Resolver reference Azure PowerShell and the Azure portal, but do not mention Azure CLI or provide Linux-oriented examples. There are no explicit Linux or cross-platform command-line instructions, and the documentation does not reference Linux-native tools or patterns for DNS configuration or management. The examples and guidance are platform-neutral in the architecture sections, but the actionable setup guidance leans toward Windows-centric tools.
Recommendations
  • Include instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux.
  • Add references or links to documentation for configuring DNS resolver settings on Linux VMs (e.g., /etc/resolv.conf, systemd-resolved).
  • Provide parity in setup guides by offering both PowerShell and CLI/bash examples for all key configuration steps.
  • Explicitly mention that the Azure DNS Private Resolver can be managed from Linux, macOS, and Windows environments, and provide guidance for each.
  • Where possible, include troubleshooting or verification steps using Linux tools (e.g., dig, nslookup) alongside any Windows-specific tools.
GitHub Create Pull Request
DNS Resolve Azure and on-premises domains. .../blob/main/articles/dns/private-resolver-hybrid-dns.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 in several ways: examples for configuring on-premises DNS conditional forwarders exclusively use Windows DNS Server, with no mention of Linux-based DNS solutions (such as BIND or dnsmasq). The procedures and screenshots focus on Windows tools and interfaces, and there are no Linux-specific instructions or parity in examples. Additionally, PowerShell is referenced before CLI in some quickstart links, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent instructions and screenshots for configuring conditional forwarders using popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
  • Include Linux CLI examples (such as using dig, nsupdate, or relevant configuration files) alongside PowerShell and portal instructions.
  • Explicitly mention that the procedures apply to both Windows and Linux DNS servers, and provide guidance for each.
  • Reorder quickstart links to present CLI and cross-platform options before or alongside PowerShell.
  • Where screenshots are used, provide both Windows and Linux examples, or use generic representations.
  • Add troubleshooting and validation steps using Linux tools (e.g., dig, host) in the demonstration sections.
GitHub Create Pull Request
DNS Azure DNS Private Resolver endpoints and rulesets ...in/articles/dns/private-resolver-endpoints-rulesets.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 exhibits Windows bias primarily in the 'Next steps' section, where only Azure PowerShell and Azure Portal are mentioned as ways to create an Azure DNS Private Resolver, with no reference to Linux-friendly tools such as Azure CLI or ARM templates. There are no examples or instructions using Linux shell commands, and Windows-centric tools (PowerShell) are referenced before any cross-platform alternatives. No Linux-specific guidance or parity is provided throughout the page.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all provisioning and configuration tasks.
  • Reference ARM/Bicep templates for infrastructure-as-code scenarios, which are platform-neutral.
  • Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide links to relevant documentation.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments; include examples from Linux terminals where appropriate.
  • Review all example commands and ensure both Windows and Linux users are supported with clear, parallel instructions.
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
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 by exclusively providing a Windows command-line example (nslookup in PowerShell syntax) for testing DNS resolution, without mentioning or showing equivalent Linux commands. The command prompt format (C:\>) and PowerShell code block further reinforce the Windows-centric approach. No Linux tools (e.g., dig, nslookup on Linux) or shell examples are provided, and Windows terminology appears first and exclusively in the testing section.
Recommendations
  • Include Linux command-line examples for DNS resolution, such as 'nslookup 10.1.2.5' or 'dig -x 10.1.2.5', with sample output.
  • Show both Windows and Linux command prompt formats (e.g., C:\> and $) to clarify cross-platform usage.
  • Explicitly mention that the DNS resolution steps can be performed on both Windows and Linux VMs, and provide guidance for each.
  • Avoid using only PowerShell code blocks; use generic code blocks or label them appropriately for each OS.
  • Add a note about tool availability and installation on Linux (e.g., 'nslookup' is part of the 'dnsutils' package on Ubuntu).
GitHub Create Pull Request
DNS Tutorial - Set up DNS failover using private resolvers ...articles/dns/tutorial-dns-private-resolver-failover.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 in several ways: configuration examples for DNS forwarding are provided exclusively for Windows Server using PowerShell and the DNS console, with no mention of Linux-based DNS servers (such as BIND or dnsmasq). Windows terminology and tools are used throughout, and the only command-line examples (nslookup) are shown in Windows command prompt syntax. There are no Linux equivalents or instructions for configuring DNS failover on non-Windows platforms.
Recommendations
  • Add equivalent instructions and examples for configuring DNS forwarding and conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
  • Provide Linux command-line examples for DNS queries (e.g., using dig or nslookup in a Linux shell).
  • Include screenshots or configuration file snippets for Linux DNS server setups.
  • Explicitly mention that the procedure applies to both Windows and Linux environments, and clarify any platform-specific steps.
  • Reorder sections or provide parallel instructions so that Linux and Windows users are equally supported.
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-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 demonstrates a Windows bias by providing only Azure PowerShell and Windows command prompt examples for deploying and validating the ARM template. Linux equivalents (such as Bash/CLI) are not shown, and Windows tools (PowerShell, cmd) are referenced exclusively or before mentioning alternatives. The validation step uses Windows command prompt syntax, and there are no Linux shell or Azure CLI examples for deployment, validation, or cleanup.
Recommendations
  • Add Azure CLI examples for deploying and cleaning up resources, using Bash syntax.
  • Include Linux shell commands for validation (e.g., using 'dig' or 'nslookup' in Bash).
  • Present cross-platform instructions side-by-side or clearly indicate both Windows and Linux approaches.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for each.
  • Avoid using only Windows command prompt syntax; show how to run equivalent commands on Linux/macOS.
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-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 Azure PowerShell and classic PowerShell examples, referencing Windows-centric tools and patterns, and omitting explicit Linux shell (bash) or cross-platform scripting examples. Although Azure CLI is included, which is cross-platform, there are no native Linux shell commands (e.g., curl, dig, nslookup) or guidance for Linux users. The Cloud Services section is exclusively PowerShell-based, with no CLI or Linux alternatives.
Recommendations
  • Add Linux shell examples (e.g., using az CLI in bash, or using dig/nslookup to verify PTR records).
  • Include explicit instructions or notes for Linux/macOS users, especially for verification steps.
  • Present Azure CLI examples before PowerShell to emphasize cross-platform parity.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each.
  • For Cloud Services, clarify if PowerShell is required or provide any available CLI or REST API alternatives.
  • Where PowerShell object manipulation is shown, offer equivalent az CLI or REST API workflows.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-security-policy.md ...ure-docs/blob/main/articles/dns/dns-security-policy.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 mentions Azure PowerShell and the Azure portal as configuration methods for DNS security policy, but does not mention or provide examples for Linux-oriented tools (such as Azure CLI, Bash, or REST API). There are no Linux-specific instructions or parity in examples, and the only command-line tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add instructions and examples for configuring DNS security policy using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include Bash script examples for common tasks, such as creating policies, domain lists, and traffic rules.
  • Reference REST API documentation for users who prefer direct API calls, which are platform-agnostic.
  • Explicitly state that all configuration steps can be performed from Linux, macOS, and Windows, and clarify tool availability.
  • Ensure that any screenshots or UI references are complemented by equivalent command-line instructions for both PowerShell and Azure CLI.
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-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 examples are provided for every step, and the testing instructions use nslookup in a Windows/PowerShell context. The CLI and Portal instructions are present, but PowerShell is emphasized, and Windows tools (nslookup) are used for validation, with no mention of Linux alternatives. The order of examples sometimes places PowerShell before CLI, and the testing section uses Windows command-line prompts.
Recommendations
  • Include Linux-specific testing instructions, such as using dig or host commands, alongside nslookup.
  • Provide example outputs for Linux shells (bash/zsh) in addition to PowerShell.
  • Balance the order of examples so that Azure CLI (cross-platform) is presented before or alongside PowerShell.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows, and provide any necessary platform-specific notes.
  • Add a note or section for troubleshooting using Linux tools, or reference common Linux DNS utilities.
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-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 through its 'Next steps' section, which links specifically to a PowerShell-based guide for creating a Private DNS zone, without mentioning or providing parity for Linux or cross-platform CLI examples. Throughout the scenarios, there is no mention of Linux tools, commands, or workflows, and the examples and terminology are generic but implicitly favor Windows environments by omission.
Recommendations
  • Include links to Azure CLI and/or Bash-based guides for creating and managing Private DNS zones, alongside PowerShell examples.
  • Explicitly mention that Azure DNS management can be performed from Linux, macOS, and Windows, and provide examples for each platform where relevant.
  • Add sample commands for common tasks (e.g., DNS queries, zone creation) using cross-platform tools such as dig, nslookup, and Azure CLI.
  • Ensure that documentation references to PowerShell are balanced with equivalent instructions for Linux users.
  • Review scenario descriptions to avoid implicit Windows-centric language and ensure examples are platform-neutral.
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-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 demonstrates a Windows bias by referencing Windows DNS file locations before mentioning BIND (Linux/Unix), providing only Windows Command Prompt examples for DNS queries (nslookup), and omitting Linux/macOS equivalents (e.g., dig, Linux nslookup). No PowerShell examples are present, but Windows tools and patterns are prioritized or exclusively shown.
Recommendations
  • Include Linux/macOS equivalents for DNS verification, such as examples using 'dig' and 'nslookup' on Linux.
  • Mention BIND (Linux/Unix) zone file locations before or alongside Windows DNS locations to avoid Windows-first ordering.
  • Add explicit instructions or examples for obtaining zone files from Linux-based DNS servers.
  • Where command-line examples are given (e.g., nslookup), provide both Windows and Linux/macOS syntax and expected output.
  • Clarify that Azure CLI commands work identically across platforms and highlight any platform-specific considerations if they exist.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-custom-domain.md ...azure-docs/blob/main/articles/dns/dns-custom-domain.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 Windows bias primarily through its exclusive use of Windows tools (specifically 'nslookup') for DNS validation, with screenshots and instructions referencing the Windows command prompt. There are no examples or instructions for performing equivalent DNS validation on Linux or macOS systems, nor are alternative tools (such as 'dig') mentioned. The ordering and presentation of examples implicitly assume a Windows environment, with no mention of cross-platform considerations.
Recommendations
  • Include Linux/macOS equivalents for DNS validation, such as using the 'dig' command, alongside 'nslookup'.
  • Provide screenshots or terminal output examples from Linux shells (e.g., Bash) in addition to Windows CMD.
  • Explicitly state that DNS validation can be performed on any OS and mention the relevant commands for each platform.
  • Add a section or note on cross-platform compatibility for all steps involving command-line tools.
  • Ensure that instructions do not implicitly assume the user is on Windows, and use neutral language where possible.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-import-export-portal.md ...ocs/blob/main/articles/dns/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 displays a Windows bias by mentioning Windows DNS and its default zone file location before Linux/BIND equivalents. Windows tools and folder paths are referenced explicitly, while Linux/BIND is only briefly mentioned without example commands or file paths. No Linux-specific instructions or examples (such as how to obtain a zone file from a Linux server or using Linux utilities) are provided, and the examples do not demonstrate parity for Linux users.
Recommendations
  • Provide explicit instructions and examples for obtaining zone files from Linux/BIND servers, including typical file paths (e.g., /etc/bind/zones/) and commands (such as 'cp', 'cat', or 'named-checkzone').
  • Mention Linux/BIND before or alongside Windows DNS when discussing sources of zone files to avoid Windows-first ordering.
  • Include screenshots or walkthroughs for Linux environments where relevant, such as exporting or preparing zone files.
  • Reference Linux tools/utilities (e.g., dig, named-checkzone, scp) for zone file management and transfer.
  • Ensure that all example commands and file paths are provided for both Windows and Linux environments to achieve parity.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-private-records.md ...ure-docs/blob/main/articles/dns/dns-private-records.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 Windows bias primarily through its references to PowerShell and the Azure portal as primary interfaces for managing DNS records. In the TXT records section, PowerShell and portal are mentioned before CLI, and PowerShell is specifically referenced in the Etags section as the default tool for concurrency control. There is no mention of Linux-specific tools or examples, and the ordering of interfaces favors Windows-centric tools.
Recommendations
  • Provide explicit Linux CLI examples (e.g., Azure CLI commands) alongside PowerShell and portal instructions.
  • Mention cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Include references to Linux-native DNS management tools (e.g., dig, nsupdate) where relevant.
  • Clarify that Azure CLI is available on both Windows and Linux, and provide parity in example usage.
  • Avoid assuming PowerShell as the default interface; present alternatives equally.
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-09 00:34
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 presenting Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and in some cases, only providing PowerShell instructions (e.g., record set level resource locks). There are no Linux-specific examples, nor any mention of Linux shell patterns or tools. The documentation assumes familiarity with PowerShell and does not address parity for Linux users, who may prefer Bash or other shells.
Recommendations
  • Ensure all operations demonstrated with Azure PowerShell are also shown with Azure CLI, especially where CLI support exists or is planned.
  • Explicitly note platform limitations (e.g., when a feature is only available in PowerShell) and provide guidance or workarounds for Linux users.
  • Where possible, provide Bash script examples alongside PowerShell, especially for common administrative tasks.
  • Clarify in each section whether the instructions are platform-agnostic or platform-specific, and link to relevant cross-platform documentation.
  • Advocate for feature parity between Azure PowerShell and Azure CLI, especially for resource lock management at the record set level.
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-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 by consistently referencing Azure PowerShell and the Azure portal as the primary methods for setup and management, without mentioning or providing examples for Linux-friendly tools such as Azure CLI or Bash scripting. Quickstart and next steps sections prioritize PowerShell, and there are no explicit Linux or cross-platform command-line examples. This may disadvantage users who administer Azure from Linux or macOS environments.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all setup and management tasks.
  • Reference Bash or shell scripting where appropriate, especially for automation scenarios.
  • Ensure quickstart and next steps sections include links to both PowerShell and CLI guides.
  • Explicitly state cross-platform options for managing Azure DNS Private Resolver.
  • Consider adding a table comparing PowerShell, CLI, and portal workflows for parity.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is consistently presented as the primary scripting interface, with examples and instructions given for PowerShell before Azure CLI. Record set level resource locks are only supported via Azure PowerShell, with no Azure CLI or Linux-native alternatives. There are no explicit Linux shell (bash) examples, and the use of PowerShell-centric terminology and patterns may disadvantage Linux users.
Recommendations
  • Provide bash/Linux shell equivalents for all Azure CLI examples, including explicit instructions for Linux environments.
  • Clarify platform support for each tool (e.g., note that Azure PowerShell is available cross-platform, but is most familiar to Windows admins).
  • Where functionality is only available in PowerShell (e.g., record set level resource locks), explicitly state the limitation and suggest workarounds or alternatives for Linux users.
  • Add a section summarizing cross-platform tool availability and best practices for both Windows and Linux administrators.
  • Ensure that examples alternate or equally represent both PowerShell and bash/CLI usage, and avoid presenting Windows-centric tools first unless there is a technical reason.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-reverse-dns-hosting.md ...docs/blob/main/articles/dns/dns-reverse-dns-hosting.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 First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and by providing PowerShell-specific commands throughout. The use of PowerShell as a primary example and the ordering of examples (PowerShell first, then CLI) suggest a preference for Windows tooling and workflows. There are no Linux-specific shell examples (e.g., bash, zsh), nor are Linux-native DNS tools (like dig, nsupdate, or bind utilities) mentioned. The Azure CLI is cross-platform, but its examples are always secondary to PowerShell, reinforcing the Windows-first approach.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Include Linux-native DNS management examples (e.g., using dig, nsupdate, or editing BIND zone files) for context.
  • Explicitly note that Azure CLI works on Linux, macOS, and Windows, and provide installation links for Linux users.
  • Add bash/zsh shell script examples for common tasks, especially for record creation and viewing.
  • Balance the documentation by alternating the order of PowerShell and CLI examples, or grouping them together without preference.
  • Mention and link to Linux-specific DNS documentation or community guides for further reading.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-zones-records.md ...azure-docs/blob/main/articles/dns/dns-zones-records.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 Missing Linux Example
Summary
The documentation page references Azure DNS management via PowerShell and REST API, but does not mention or provide examples for Linux-native tools (such as Azure CLI, Bash, or shell scripting). PowerShell is highlighted as the default interface for certain features (e.g., Etags), and there is no parity in examples or tool recommendations for Linux users. This creates a bias towards Windows-centric management patterns and tools.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all management tasks, especially for Etags and record management.
  • Explicitly mention that Azure CLI and Bash scripting can be used on Linux and macOS, and provide equivalent command-line examples.
  • Where PowerShell is referenced as the default, clarify that Azure CLI is equally supported and provide usage patterns.
  • Add a section or note about cross-platform tooling, listing both Windows and Linux options for DNS management in Azure.
  • Ensure that all tool references and examples are presented in a platform-neutral order, or alternate which platform is presented first.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for unsigning an Azure Public DNS zone using the Azure portal, Azure CLI, and PowerShell. PowerShell examples are given equal prominence as Azure CLI, and the CLI example is labeled 'azurepowershell-interactive', which may suggest a Windows-centric approach. There is no mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users. The documentation implicitly assumes familiarity with Windows tools and patterns, such as PowerShell and the Azure portal, which are more commonly used on Windows systems.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, showing usage in a Linux terminal.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide instructions for installing and using Azure CLI on Linux.
  • Avoid labeling CLI examples as 'azurepowershell-interactive' when they are standard Azure CLI commands, to reduce confusion and Windows bias.
  • Include notes or links for Linux users on how to authenticate (e.g., az login) and manage subscriptions in a Linux environment.
  • Consider adding troubleshooting steps or screenshots from Linux environments where relevant.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-fallback.md ...re-docs/blob/main/articles/dns/private-dns-fallback.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 Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by consistently presenting command-line examples using Windows tools (cmd.exe, nslookup, dig) with Windows-style prompts (C:\>), and referencing command prompts on Azure virtual machines without mentioning Linux equivalents or shell environments. Screenshots and instructions are tailored to Windows users, with no explicit guidance for Linux users, despite the cross-platform nature of Azure VMs and DNS tools.
Recommendations
  • Provide Linux shell equivalents for all command-line examples (e.g., show dig/nslookup usage in bash/zsh with $ prompt).
  • Include instructions for running DNS queries from Linux-based Azure VMs, specifying any differences in tool installation or usage.
  • Add screenshots or terminal output examples from Linux environments to balance visual representation.
  • Explicitly mention that the steps apply to both Windows and Linux VMs, and clarify any platform-specific nuances.
  • Where Azure CLI is used, note that it is cross-platform and show example usage in both Windows and Linux shells.
GitHub Create Pull Request
← Previous Page 3 of 13 Next →