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 101-125 of 323 flagged pages
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary interfaces for managing DNS records, especially in the TXT records section and Etag handling. PowerShell is mentioned explicitly as the default tool for Etag management, and examples or instructions for Linux-native tools (such as Azure CLI or Bash scripting) are missing or mentioned after Windows tools. There are no Linux-specific examples or parity in tool recommendations.
Recommendations
  • Provide equivalent examples and instructions for Azure CLI and Bash scripting alongside PowerShell and portal references.
  • Mention Linux-native tools and workflows (e.g., Azure CLI, REST API via curl) before or alongside Windows tools.
  • Ensure that all management scenarios (e.g., TXT record creation, Etag handling) include explicit CLI commands and REST API examples, not just PowerShell.
  • Add a section or callout for Linux/macOS users, highlighting cross-platform management options.
  • Review and update documentation to avoid assuming PowerShell or Windows as the default environment.
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-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 page demonstrates a Windows bias in several ways: PowerShell (Resolve-DnsName) is used as the primary example for querying DNSSEC records, and Windows-specific tools and patterns (such as Group Policy and NRPT) are discussed in detail. The dig command is shown, but only in a Windows command prompt context (C:\>dig), and there are no explicit Linux or macOS shell examples. Linux-native tools and usage patterns are not mentioned or prioritized, and there is a lack of parity in guidance for non-Windows environments.
Recommendations
  • Provide Linux and macOS shell examples for DNSSEC queries, e.g., show dig usage in a bash/zsh shell (e.g., $ dig ...), and clarify that dig is a standard tool on Unix-like systems.
  • Mention Linux-native tools (such as drill, kdig, or host) where appropriate, and provide equivalent command examples.
  • When discussing DNSSEC validation enforcement, include information about how to configure DNSSEC validation on popular Linux DNS resolvers (e.g., Unbound, BIND) and mention relevant configuration files.
  • Avoid presenting Windows tools or patterns (e.g., PowerShell, NRPT, Group Policy) before or to the exclusion of their Linux equivalents; instead, present both in parallel or provide platform-specific sections.
  • Clarify that Resolve-DnsName is a Windows-only tool, and suggest alternatives for other platforms.
  • Explicitly state that dig is available on both Windows (if installed) and Unix-like systems by default, and provide installation instructions if needed.
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-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 a Windows bias in several areas. When describing how to obtain an existing DNS zone file, Windows DNS is mentioned before BIND (the most common Linux DNS server), and the Windows file path is given in detail while the BIND example is less specific. There are no concrete examples or screenshots for Linux/BIND workflows, and no mention of Linux tools or commands for zone file access. The page does not provide parity in guidance for Linux users, focusing more on Windows environments.
Recommendations
  • Present Linux/BIND examples and instructions before or alongside Windows examples when describing how to obtain zone files.
  • Provide specific Linux/BIND file paths (e.g., /etc/bind/zones/) and configuration details, similar to the Windows example.
  • Include screenshots or step-by-step instructions for accessing zone files on Linux/BIND systems.
  • Mention common Linux tools (e.g., scp, rsync, cat, nano) for copying and editing zone files.
  • Add troubleshooting notes relevant to Linux/BIND environments.
  • Ensure that all examples and guidance are platform-neutral or include both Windows and Linux variants.
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-08 00:53
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 examples before Azure CLI, referencing PowerShell-specific tooling, and using PowerShell syntax throughout. The Azure classic CLI is included, but there are no explicit Linux shell (bash/zsh) or cross-platform scripting examples, nor is there mention of Linux-native DNS tools (e.g., dig, nsupdate) for validation or management. The repeated use of PowerShell and its placement before CLI examples suggests a prioritization of Windows workflows.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to reflect cross-platform parity.
  • Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, and provide bash/zsh shell examples where appropriate.
  • Include examples using common Linux DNS utilities (e.g., dig, nsupdate) to validate or query DNS records after creation.
  • Add notes or sections for Linux users, such as installation instructions for Azure CLI on Linux and integration with Linux automation tools.
  • Avoid using only PowerShell-specific syntax in explanations; provide generic or cross-platform command-line patterns where possible.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a subtle Windows bias by referencing a 'get started' guide that uses PowerShell for creating a Private DNS zone, without mentioning or linking to Linux/CLI alternatives. No Linux-specific tools or examples are provided, and PowerShell (a Windows-centric tool) is implicitly presented as the default method.
Recommendations
  • Include links to equivalent Azure CLI or Bash-based guides for Linux users in the 'Next steps' section.
  • Explicitly mention that Azure DNS management can be performed using multiple platforms and tools, such as Azure CLI, REST API, and Portal, not just PowerShell.
  • Provide example commands for both PowerShell and Azure CLI when referencing operational tasks.
  • Ensure that documentation titles and links do not imply PowerShell is the only or primary method for managing Azure DNS zones.
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-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 primarily in the 'Next steps' section, where only Azure PowerShell and Azure Portal are mentioned as methods for creating an Azure DNS Private Resolver. There are no references to Linux-specific tools (such as Azure CLI or Bash scripting), nor are there examples or instructions for Linux users. The documentation also lists PowerShell before the Portal, reinforcing a Windows-first approach. Throughout the page, there is an absence of cross-platform command-line examples, and no mention of Linux or non-Windows environments.
Recommendations
  • Add instructions and examples for creating and managing Azure DNS Private Resolver resources using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include Bash scripting examples alongside PowerShell to demonstrate parity for Linux users.
  • Explicitly mention that Azure DNS Private Resolver can be managed from Linux, macOS, and Windows environments, and provide links to relevant cross-platform documentation.
  • In the 'Next steps' section, list Azure CLI and other cross-platform tools before or alongside PowerShell to avoid Windows-first ordering.
  • Review screenshots and UI references to ensure they are not exclusively Windows-centric, and add notes or images relevant to Linux environments where appropriate.
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-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 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 present, but there is no explicit mention of Linux shell equivalents, nor are Linux-specific instructions or examples provided. The use of dig.exe (Windows binary) is referenced before mentioning generic 'dig', and jq is used without clarifying Linux usage. There are no bash or Linux shell examples for obtaining DS records or interacting with Azure DNS.
Recommendations
  • Add Linux shell (bash) examples for all CLI operations, including az commands and parsing output (e.g., using grep, awk, or jq in Linux context).
  • Clarify that 'dig' is available on Linux and show usage with Linux command-line syntax (e.g., dig adatum.com DS +dnssec).
  • Provide explicit instructions for Linux users, including installation notes for required tools (az CLI, dig, jq) on Linux.
  • Ensure that references to command-line tools are platform-neutral or include both Windows and Linux variants.
  • Consider adding a 'Linux' tab alongside PowerShell and CLI, or at least ensure parity in examples and screenshots for Linux users.
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-08 00:53
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 strong Windows bias. All virtual machine creation examples use Windows images, and all testing instructions (firewall configuration, ping commands, and sample outputs) are exclusively shown using Windows PowerShell and Windows tools. There are no Linux VM creation examples, nor any instructions for configuring Linux firewalls or testing DNS resolution from Linux VMs. The use of Windows-specific commands and outputs may hinder Linux users from following the quickstart effectively.
Recommendations
  • Include examples for creating Linux VMs (e.g., using --image UbuntuLTS) alongside Windows VM creation.
  • Provide instructions for configuring firewalls on Linux VMs (e.g., using ufw or iptables to allow ICMP).
  • Show how to test DNS resolution and connectivity from Linux VMs (e.g., using ping and dig/host commands in a Bash shell).
  • Present both Windows and Linux command outputs for ping and DNS resolution to illustrate parity.
  • Explicitly mention that the Azure CLI commands work cross-platform and highlight any OS-specific steps.
  • Avoid assuming the user is on Windows or using PowerShell; offer Bash and Linux terminal alternatives wherever possible.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Cmd Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting command-line examples using Windows Command Prompt (cmd) syntax and referencing Windows tools (nslookup, dig) with Windows-style prompts (C:\>). All DNS query examples are shown from a Windows VM perspective, with no explicit Linux shell examples or instructions. The screenshots and step-by-step instructions assume use of the Azure Portal, which is platform-neutral, but the command-line context is Windows-centric. There are no Linux shell equivalents (e.g., Bash, sh) or Linux-specific instructions for running DNS queries from a Linux VM.
Recommendations
  • Provide equivalent Linux shell examples for DNS queries, using Bash prompt ($) and Linux tools (nslookup, dig) as run on Linux VMs.
  • Include instructions or screenshots showing how to run DNS queries from a Linux VM in Azure, highlighting any differences in output or command usage.
  • Add a note clarifying that the steps and commands apply to both Windows and Linux VMs, and specify any platform-specific considerations.
  • Where possible, alternate examples between Windows and Linux, or present both side-by-side for parity.
  • Ensure that prerequisite sections mention both Windows and Linux VM options for running DNS queries.
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-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 Windows bias by explicitly mentioning Azure PowerShell as a configuration method for DNS security policy, without referencing Azure CLI or Linux-native tools. There are no examples or instructions for Linux users, and the only automation tooling referenced is PowerShell, which is primarily associated with Windows environments. This may disadvantage users who prefer or require Linux-based workflows.
Recommendations
  • Include Azure CLI instructions and examples alongside PowerShell for all configuration steps.
  • Explicitly mention that DNS security policy can be configured from Linux, macOS, and Windows environments using cross-platform tools.
  • Add sample commands for both PowerShell and Azure CLI in relevant sections.
  • Where screenshots or UI references are made, clarify that the portal is accessible from any OS.
  • Consider referencing automation options such as ARM templates, Bicep, or Terraform, which are platform-agnostic.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias primarily through the explicit mention and prioritization of PowerShell as a management tool for Azure DNS, including specific behavioral notes about PowerShell usage (e.g., Etags). There is no mention of Linux-specific tools or examples, and PowerShell is referenced before other cross-platform options like the Azure CLI or REST API. This may make Linux users feel less supported or require them to infer parity from Windows-centric instructions.
Recommendations
  • Provide explicit Linux-oriented examples, such as using Azure CLI or shell scripts, alongside or before PowerShell examples.
  • Clarify that Azure CLI and REST API are fully cross-platform and provide equivalent functionality, with usage notes for Linux environments.
  • Avoid language that implies PowerShell is the default or primary tool; instead, present management options in a neutral, platform-agnostic order.
  • Include references to Linux DNS utilities (e.g., dig, nsupdate) where relevant, especially in sections discussing DNS record management.
  • Add a section or callouts for Linux users, highlighting best practices and tool recommendations for managing Azure DNS from Linux systems.
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-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 by exclusively providing a Windows command-line (PowerShell) example for testing DNS resolution (nslookup), without mentioning or showing equivalent Linux commands (such as dig or nslookup on Linux). The command prompt syntax and screenshot are Windows-specific, and there are no references to Linux tools or workflows throughout the article.
Recommendations
  • Include Linux command-line examples for DNS resolution, such as 'dig -x 10.1.2.5' and 'nslookup 10.1.2.5' run from a Linux shell.
  • Show screenshots or output examples from a Linux terminal in addition to Windows.
  • Explicitly mention that the steps for testing DNS resolution apply to both Windows and Linux VMs, and provide instructions for both platforms.
  • Avoid using Windows-specific prompt syntax (e.g., 'C:\>') without also showing Linux equivalents ('$').
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-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 primarily in the 'Next steps' section, where guidance is provided for creating an Azure DNS Private Resolver using Azure PowerShell (a Windows-centric tool) and the Azure portal, with no mention of Linux-native tools (such as Azure CLI or ARM templates). There are no examples or references to Linux command-line usage, and the documentation does not provide parity for Linux users in terms of setup or management instructions.
Recommendations
  • Include instructions and examples for creating and managing Azure DNS Private Resolver using Azure CLI, which is cross-platform and widely used on Linux.
  • Add references or links to ARM/Bicep template deployment guides for infrastructure-as-code scenarios, which are platform-agnostic.
  • Ensure that any PowerShell examples are paired with equivalent Azure CLI examples, and present both options together or in parallel sections.
  • Explicitly mention that Azure CLI and ARM templates can be used from Linux, macOS, and Windows, to reinforce cross-platform support.
  • Audit other referenced documentation (such as 'Get started' guides) to ensure Linux parity in examples and instructions.
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-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 listing Azure PowerShell before Azure CLI in the 'Next steps' section, and by referencing PowerShell as a primary tool for getting started. There are no explicit Linux-specific examples or mentions of Linux tools, and the documentation does not provide parity in guidance for Linux administrators. The 'Familiar tools' section lists Azure PowerShell before Azure CLI, reinforcing the Windows-first approach.
Recommendations
  • List Azure CLI before Azure PowerShell in example links and tool references to reflect cross-platform parity.
  • Explicitly mention that Azure CLI is available and supported on Linux and macOS, and provide example commands for those platforms.
  • Include Linux-specific guidance or examples, such as using Azure CLI from a Linux shell, or integrating with Linux-native DNS tools.
  • Add notes or sections highlighting cross-platform support and considerations for both Windows and Linux administrators.
  • Ensure that documentation for getting started and common scenarios includes both PowerShell and CLI examples side-by-side.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates Windows bias by exclusively using Windows Server as the example OS for the test VM, providing only Windows-centric instructions (such as RDP and PowerShell), and omitting any Linux VM creation or Linux command-line examples for DNS testing. The 'Test the private zone' section uses PowerShell and Windows-style ping output, with no mention of Linux alternatives.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide Linux command-line examples for DNS testing, such as using 'ping', 'nslookup', or 'dig' from a Linux shell.
  • Mention SSH as an alternative to RDP for connecting to Linux VMs.
  • Show how to use the Azure portal's Run Command feature with Bash scripts for Linux VMs.
  • Ensure screenshots and command outputs include both Windows and Linux variants where applicable.
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-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 strong Windows bias by relying almost exclusively on PowerShell scripts and commands for the migration process. All automation and migration steps are described using PowerShell, with instructions to use elevated PowerShell windows and references to Windows-specific tools (PowerShell Gallery, install-script, etc.). There are no Bash or Linux shell script equivalents, and no instructions for running the migration from Linux or macOS environments. The prerequisites and installation steps assume a Windows environment, and Linux users are not provided with alternative guidance.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for the migration process, including installation and execution steps.
  • Include instructions for running the migration from Linux and macOS environments, such as using Azure CLI or cross-platform scripting languages.
  • Mention cross-platform compatibility for the migration script, or explicitly state any limitations.
  • List Linux prerequisites (e.g., required CLI tools, Python, etc.) alongside Windows prerequisites.
  • Ensure that examples and screenshots include both Windows and Linux terminal environments.
  • Clarify whether the migration script can be run in environments other than Windows, and offer alternatives if not.
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-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 page demonstrates a Windows bias by providing only Windows Server and PowerShell examples for configuring DNS forwarding. The instructions and screenshots focus exclusively on Windows tools (PowerShell, DNS console), with no mention of Linux equivalents (such as BIND, dnsmasq, or resolv.conf). The Windows procedure is presented as the default, and there are no Linux-specific steps or commands for configuring DNS forwarders.
Recommendations
  • Add equivalent Linux instructions for configuring DNS forwarding, such as examples for BIND (named.conf), dnsmasq, or systemd-resolved.
  • Include Linux command-line examples (e.g., using dig or host) alongside nslookup.
  • Provide screenshots or configuration file snippets for common Linux DNS server setups.
  • Explicitly state that the procedure applies to both Windows and Linux environments, and offer guidance for each.
  • List both Windows and Linux options when mentioning DNS server types, rather than assuming Windows Server as the default.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-alias-tm.md ...azure-docs/blob/main/articles/dns/tutorial-alias-tm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial exclusively uses Windows Server virtual machines and IIS for the web server examples, with step-by-step instructions and screenshots tailored to Windows environments. There are no Linux VM or Apache/Nginx examples, nor any mention of Linux alternatives for the web server setup. All configuration and testing steps assume a Windows-based deployment, leading to a clear Windows bias.
Recommendations
  • Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
  • Include screenshots and commands for Linux-based web server setup and configuration.
  • Mention Linux as an alternative in the prerequisites and throughout the tutorial, making it clear that either OS is supported.
  • Provide CLI commands (e.g., SSH, apt, systemctl) for Linux VM configuration alongside the Windows RDP and IIS steps.
  • Ensure testing steps include Linux-based verification (e.g., using curl or browser on Linux).
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias in the testing and validation steps. While the Azure CLI commands are cross-platform, all VM creation examples use Windows images, and all instructions for testing DNS resolution are written for Windows (PowerShell commands, Windows firewall configuration, and Windows command prompt outputs). There are no Linux VM creation examples, nor are there instructions for configuring or testing from a Linux environment.
Recommendations
  • Add parallel Linux VM creation examples using a common Linux image (e.g., Ubuntu) alongside the Windows examples.
  • Provide instructions for configuring the firewall on Linux VMs to allow ICMP (e.g., using ufw or firewalld).
  • Include Linux command-line examples for testing DNS resolution (e.g., using ping, dig, or nslookup from a bash shell).
  • Show sample output from Linux terminals in addition to Windows PowerShell.
  • Explicitly state that the Azure CLI commands work on all supported platforms, and ensure parity in validation steps for both Windows and Linux users.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Azure PowerShell cmdlets, with no mention of Azure CLI or Bash equivalents, which are more commonly used on Linux and macOS. The DNS testing example uses nslookup in a Windows PowerShell prompt, and there are no examples using dig or host, which are standard on Linux. The documentation refers to Windows tools and patterns exclusively and does not provide Linux-specific guidance or parity.
Recommendations
  • Provide Azure CLI (az) command examples alongside or in place of PowerShell for all DNS record creation and web app configuration steps.
  • Include DNS query examples using dig and/or host, which are standard on Linux, in addition to or instead of nslookup.
  • Avoid showing only PowerShell prompts (e.g., 'PS C:\>') and instead use generic shell prompts or show both Windows and Linux terminal examples.
  • Explicitly mention that the steps can be performed from any OS, and provide links or notes for installing required tools on Linux/macOS.
  • Consider restructuring the documentation to present cross-platform examples side-by-side, or default to Azure CLI, which is cross-platform.
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: 2025-07-13 21:37
Reviewed by: Unknown
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 example VM OS, referencing RDP for remote access, and using PowerShell scripts for testing DNS resolution. There are no examples or instructions for creating or managing Linux VMs, nor for testing DNS resolution using Linux tools or shells. The documentation does not mention or show parity for Linux users in key steps.
Recommendations
  • Provide parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows Server example.
  • Include examples for connecting to a Linux VM (e.g., using SSH) and testing DNS resolution with Linux-native tools (e.g., ping, dig, or nslookup from a Bash shell).
  • When referencing the 'Run command' feature, show both RunPowerShellScript (for Windows) and RunShellScript (for Linux) options.
  • Avoid assuming the use of RDP or Windows-specific ports; mention SSH and Linux authentication methods as alternatives.
  • Explicitly state that the process is OS-agnostic where possible, and highlight any differences for Linux users.
  • Add links to Linux-specific quickstarts or documentation where available.
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: 2025-07-13 21:37
Reviewed by: Unknown
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 Linux/CLI alternatives. There are no command-line examples or instructions for Linux users, and the 'Next steps' section prioritizes PowerShell, which is most commonly associated with Windows environments.
Recommendations
  • Include links to Azure CLI and/or Azure Portal guides for creating and managing Private DNS zones, in addition to the PowerShell guide.
  • Add example commands for both Windows (PowerShell) and Linux/macOS (Azure CLI) users where relevant.
  • Ensure that references to tooling and instructions are platform-neutral or provide parity between Windows and Linux environments.
  • In the 'Next steps' section, either generalize the link (e.g., 'create a Private DNS zone using PowerShell, Azure CLI, or Portal') or provide separate links for each platform.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a moderate Windows bias. When discussing how to obtain an existing DNS zone file, the Windows DNS file location is described in detail before mentioning BIND (the most common Linux DNS server). In the verification section, only the Windows Command Prompt syntax for nslookup is shown, with no Linux/macOS equivalent. There are no explicit Linux shell or macOS Terminal examples for common DNS tools, and the only OS-specific tool usage is for Windows.
Recommendations
  • When describing how to obtain a DNS zone file, provide equal detail for both Windows DNS and BIND (Linux), including example file paths and commands for both.
  • In the verification section, add examples for running nslookup (or dig) from Linux/macOS Terminal, showing the equivalent command and expected output.
  • Where Windows-specific tools or paths are mentioned, also mention the Linux/macOS equivalents (e.g., /etc/bind for BIND zone files).
  • Consider including a table or section summarizing OS-specific steps for common tasks (obtaining zone files, running DNS queries) to ensure parity.
  • Review all examples to ensure that, where OS-specific instructions are needed, both Windows and Linux/macOS users are equally supported.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by linking only to a PowerShell-based getting started guide for creating a Private DNS zone, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash). There are no Linux or cross-platform examples or references, and the PowerShell path is presented as the default.
Recommendations
  • Add links to Linux-friendly guides, such as how to create a Private DNS zone using Azure CLI or Bash.
  • Wherever PowerShell examples are provided, also include Azure CLI or REST API examples to ensure cross-platform parity.
  • In the 'Next steps' section, avoid referencing only PowerShell documentation; instead, offer parallel links for both PowerShell and CLI.
  • Explicitly mention that Azure DNS management can be performed from any platform, and provide examples for both Windows and Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and patterns. PowerShell (Resolve-DnsName) is presented first and in more detail, with multiple examples, while Linux/Unix-native tools (dig) are mentioned but not explained as thoroughly. The documentation references Windows-specific features (such as Group Policy and NRPT) without mentioning Linux equivalents or validation methods. There are no explicit Linux command-line examples (e.g., bash shell usage), and the guidance assumes familiarity with Windows environments.
Recommendations
  • Provide Linux/Unix command-line examples (e.g., using dig in bash or sh, with sample output).
  • Present dig (the cross-platform tool) examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Mention Linux/Unix DNSSEC validation methods and tools (e.g., unbound, bind, systemd-resolved) where Windows Group Policy and NRPT are discussed.
  • Clarify that dig is available by default on most Linux distributions, and provide installation instructions for both Windows and Linux if needed.
  • Balance the number and detail of examples between Windows and Linux environments.
  • Reference Linux documentation or man pages for DNSSEC validation and troubleshooting.
GitHub Create Pull Request
← Previous Page 5 of 13 Next →