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 1-25 of 323 flagged pages
DNS Migrating legacy Azure DNS private zones to the new resource model .../blob/main/articles/dns/private-dns-migration-guide.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All migration steps rely on a PowerShell script, with instructions to use an elevated PowerShell window and references to PowerShell modules and tools. There are no equivalent Bash, Azure CLI, or Linux/macOS instructions for running the migration, nor any mention of how non-Windows users can perform the migration. The only CLI example is for identifying zones, not for migration itself. The documentation assumes the user has access to Windows and PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Provide a Bash or Azure CLI equivalent script for the migration process, or document how Linux/macOS users can perform the migration without PowerShell.
  • Include instructions for installing and running the migration on Linux/macOS, such as using Azure CLI or cross-platform scripting languages.
  • Mention cross-platform alternatives to PowerShell, such as running scripts in Docker containers or using cloud shell (if possible).
  • Ensure examples and instructions are provided for both Windows and Linux/macOS environments, or clearly state platform requirements up front.
GitHub Create Pull Request
DNS Tutorial: Create an alias record to support apex domain name with Traffic Manager ...azure-docs/blob/main/articles/dns/tutorial-alias-tm.md
High Priority View Details →
Scanned: 2026-01-14 00:00
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 Windows-specific tooling (IIS, RDP, Server Manager) for the web server setup. There are no instructions or examples for deploying Linux-based VMs, using Linux web servers (e.g., Apache, Nginx), or connecting via SSH. All configuration and testing steps assume a Windows environment, which may exclude or create friction for Linux/macOS users.
Recommendations
  • Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
  • Include SSH-based connection steps for Linux VMs, alongside RDP for Windows.
  • Show how to edit the default web page on Linux (e.g., /var/www/html/index.html) and verify with curl or a browser.
  • Explicitly mention that either Windows or Linux VMs can be used, and provide both sets of steps in the tutorial.
  • Ensure screenshots and examples are balanced between Windows and Linux environments.
GitHub Create Pull Request
DNS Migrating legacy Azure DNS private zones to the new resource model .../blob/main/articles/dns/private-dns-migration-guide.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. The migration process is described exclusively using PowerShell scripts, with all installation and execution steps requiring PowerShell and Windows-specific instructions (elevated PowerShell window, install-script, etc.). There are no Bash, Linux shell, or cross-platform alternatives provided for the migration script. The prerequisites and automation update sections mention PowerShell first and in detail, while CLI and SDK links are listed but not used in migration steps. Linux/macOS users are left without clear guidance or supported tooling for the migration process.
Recommendations
  • Provide a Bash or Azure CLI equivalent script for the migration process, or clarify if the PowerShell script can run on PowerShell Core on Linux/macOS.
  • Add explicit instructions for running the migration on Linux/macOS, including prerequisites and installation steps.
  • List Azure CLI and cross-platform options before or alongside PowerShell instructions.
  • Clarify whether the migration script is supported in non-Windows environments and, if not, provide alternatives or workarounds.
  • Include screenshots or terminal examples from Linux/macOS environments.
GitHub Create Pull Request
DNS DNS Zones and Records Overview ...azure-docs/blob/main/articles/dns/dns-zones-records.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily through its emphasis on PowerShell as the default tool for managing Azure DNS resources, mentioning PowerShell before other interfaces (such as CLI or REST API) and describing behaviors and options specific to PowerShell (e.g., the use of Etags and the -Overwrite switch). There is little to no mention of Linux-native tools or workflows, and examples or instructions for Linux users are missing.
Recommendations
  • Provide equivalent Azure CLI examples and instructions alongside PowerShell references, ensuring Linux users have clear guidance.
  • Explicitly mention cross-platform compatibility for management tasks, including REST API usage and CLI commands.
  • Add references to Linux-native DNS management tools (e.g., dig, nsupdate) where relevant, and clarify how Azure DNS can be managed from Linux environments.
  • Reorder sections to present cross-platform or OS-neutral tools first, or present PowerShell and CLI options together.
  • Include notes or links for Linux users on installing and using Azure CLI and other relevant tools.
GitHub Create Pull Request
DNS Overview of DNSSEC - Azure Public DNS ...rosoftDocs/azure-docs/blob/main/articles/dns/dnssec.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Windows tools and terminology (PowerShell, Resolve-DnsName, nslookup.exe, Group Policy, NRPT) are mentioned first and in detail, with command-line examples provided primarily for Windows (PowerShell and Windows CMD). Linux equivalents (such as dig) are mentioned but not explained or prioritized. There is no explicit example for Linux shell usage, and the guidance assumes familiarity with Windows environments and tools.
Recommendations
  • Provide Linux shell examples (e.g., using dig from bash) alongside or before Windows examples.
  • Mention Linux-native tools (e.g., drill, kdig, host) and their usage for DNSSEC queries.
  • Clarify that dig is available on both Windows and Linux, and show installation instructions for both platforms.
  • Balance references to Windows-specific features (Group Policy, NRPT) with Linux equivalents (e.g., systemd-resolved, Unbound, BIND configuration).
  • Avoid using Windows paths (C:\>) exclusively; show Linux shell prompts ($) in examples.
  • Add a section on DNSSEC validation and management for common Linux DNS servers (BIND, Unbound, Knot).
  • Explicitly state cross-platform support and provide parity in troubleshooting and validation steps.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Azure Resource Manager template (ARM template) ...ocs/blob/main/articles/dns/dns-get-started-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell and Windows command prompt (cmd) examples for template deployment and DNS validation. There are no Linux shell (bash) or Azure CLI examples, and the instructions and screenshots focus on Windows tools and workflows. Linux users are not given equivalent guidance for deploying or validating DNS zones.
Recommendations
  • Add Azure CLI (az) examples for deploying the ARM template, alongside PowerShell.
  • Provide bash shell instructions for running nslookup, including Linux/Mac terminal screenshots.
  • Mention and demonstrate deployment from Linux/macOS environments, not just Windows/PowerShell.
  • Present deployment and validation steps for both Windows and Linux users, ideally side-by-side.
  • Clarify that Azure Cloud Shell supports both PowerShell and Bash, and show how to select each.
GitHub Create Pull Request
DNS Reverse DNS for Azure services - Azure DNS ...ain/articles/dns/dns-reverse-dns-for-azure-services.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell and Windows PowerShell examples, especially for Cloud Services, where only PowerShell is supported and shown. There are no Linux shell (bash) or cross-platform scripting examples, and the use of PowerShell cmdlets and terminology is prevalent throughout. The Azure CLI is included, but Windows-centric tools and patterns (PowerShell, Classic CLI) are presented first or exclusively in some sections.
Recommendations
  • Add explicit bash/shell examples for Linux users, especially for viewing and validating DNS records (e.g., using dig, nslookup, or host commands).
  • Clarify which tools are cross-platform (e.g., Azure CLI) and recommend them for Linux/Mac users.
  • Where PowerShell is required (e.g., for Cloud Services), note the lack of Linux support and suggest alternatives or workarounds if possible.
  • Present Azure CLI examples before PowerShell to avoid Windows-first ordering.
  • Include guidance for configuring and verifying reverse DNS using native Linux tools alongside Azure CLI.
GitHub Create Pull Request
DNS Host reverse DNS lookup zones in Azure DNS ...docs/blob/main/articles/dns/dns-reverse-dns-hosting.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page consistently presents Azure PowerShell examples before Azure CLI examples, and includes PowerShell as a primary automation tool throughout. This ordering and tool selection favors Windows users, as PowerShell is traditionally a Windows-centric technology. There are no Linux shell (bash) or platform-agnostic examples, and no mention of Linux-specific patterns or tools. The Azure CLI is cross-platform, but its examples are always secondary to PowerShell, reinforcing a Windows-first approach.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash shell usage examples where appropriate.
  • Include notes or examples for Linux users, such as using bash scripts or integrating with Linux automation tools.
  • Reduce reliance on PowerShell as the primary scripting example, or provide parity by including equivalent bash or shell script snippets.
  • Clarify that Azure PowerShell is available on Linux and macOS, if retaining PowerShell examples, to reduce perception of Windows exclusivity.
GitHub Create Pull Request
DNS How to unsign your Azure Public DNS zone ...ocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides step-by-step instructions for unsigning an Azure Public DNS zone using the Azure Portal, Azure CLI, and PowerShell. The CLI examples use the 'azurepowershell-interactive' code block, and PowerShell is given its own dedicated section. There are no explicit Linux shell (bash) examples, and the CLI instructions do not clarify Linux usage or mention platform differences. The ordering places PowerShell examples after CLI, but CLI examples are not explicitly Linux-friendly, and PowerShell is a Windows-centric tool.
Recommendations
  • Add explicit bash/Linux shell examples for Azure CLI usage, clarifying that 'az' commands work cross-platform.
  • Use generic 'cli' code blocks or provide both Windows (PowerShell) and Linux (bash) code blocks for CLI instructions.
  • Clarify in the CLI section that the commands are platform-agnostic and can be run in bash, zsh, or other shells on Linux/Mac.
  • Avoid using 'azurepowershell-interactive' for CLI examples; use 'bash' for CLI commands and reserve 'PowerShell' for actual PowerShell scripts.
  • Consider reordering or equally presenting PowerShell and bash examples to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
DNS Integrate Azure DNS with your Azure resources - Azure DNS ...azure-docs/blob/main/articles/dns/dns-custom-domain.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently uses Windows-centric tools and patterns, such as referencing 'nslookup' with screenshots from Windows Command Prompt, and does not provide Linux or cross-platform alternatives for DNS validation. There are no examples or instructions for performing equivalent steps on Linux or macOS, nor are Linux-native tools (like dig) mentioned. This may make the documentation less accessible or immediately useful for users on non-Windows platforms.
Recommendations
  • Include Linux/macOS equivalents for DNS validation, such as using 'dig' or 'host' commands, alongside 'nslookup'.
  • Add screenshots or terminal output examples from Linux shells (e.g., bash) to complement Windows Command Prompt images.
  • Explicitly state that the steps can be performed on any OS, and provide guidance for cross-platform command-line usage.
  • Where GUI navigation is described, clarify that the Azure Portal is OS-agnostic, but CLI steps (if any) should be shown for both Windows (PowerShell/CMD) and Linux (bash/CLI).
  • Add a section or note on troubleshooting DNS issues from Linux/macOS environments.
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure portal ...ocs/blob/main/articles/dns/dns-import-export-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 mentioning Windows DNS and its default zone file location before Linux/BIND equivalents, and by providing explicit instructions for Windows users (e.g., referencing %systemroot%\system32\dns and the DNS console). There is no example or guidance for obtaining zone files from Linux-based DNS servers (such as BIND), nor are Linux tools or file paths shown in detail. The documentation lacks parity in examples and instructions for Linux users.
Recommendations
  • Provide explicit instructions and examples for obtaining zone files from BIND or other Linux-based DNS servers, including typical file paths (e.g., /etc/bind/ or /var/named/).
  • Mention Linux tools and commands (such as cat, cp, scp, or named-checkzone) for handling zone files.
  • Ensure that references to Windows and Linux/BIND are presented with equal prominence and detail, ideally listing both together or alternating order.
  • Add screenshots or CLI snippets showing Linux file system navigation and zone file access.
  • Clarify that the Azure portal and CLI are cross-platform, and provide guidance for both Windows and Linux environments where relevant.
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure CLI ...azure-docs/blob/main/articles/dns/dns-import-export.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 only Windows Command Prompt nslookup examples, and omitting explicit Linux/macOS equivalents for verification steps. The use of Windows-specific paths and tools is prioritized, and Linux shell commands or usage patterns are not illustrated.
Recommendations
  • Include Linux/macOS examples alongside Windows, such as showing how to use nslookup or dig from a Bash shell.
  • Mention BIND (Linux) zone file locations before or alongside Windows DNS locations.
  • Provide sample commands for verifying DNS records using Linux/macOS tools (e.g., dig, nslookup in Bash).
  • Clarify that Azure CLI commands are cross-platform and show example usage in both Windows Command Prompt and Linux/macOS terminal environments.
  • Avoid referencing Windows-specific paths or tools without also providing the Linux/macOS equivalents.
GitHub Create Pull Request
DNS Protecting private DNS Zones and Records - Azure DNS ...n/articles/dns/dns-protect-private-zones-recordsets.md
High Priority View Details →
Scanned: 2026-01-11 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 moderate Windows bias. Azure PowerShell is consistently presented as the first and primary automation example for all tasks, with Azure CLI shown second. There are no Linux-specific examples, nor any mention of Linux-native tools or shell environments. Some advanced operations (e.g., record set level resource locks) are only available via Azure PowerShell, with no CLI or Linux alternative. The documentation does not address usage from Bash or Linux environments, nor does it clarify cross-platform support for PowerShell.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and can be used from Linux, macOS, and Windows.
  • Where PowerShell is required for functionality, clarify whether PowerShell Core (pwsh) on Linux/macOS is supported, and provide example commands for those platforms.
  • Add Bash shell examples for Azure CLI usage, including environment variable usage and scripting patterns common on Linux.
  • Where features are only available in PowerShell, note the limitation and suggest workarounds or alternatives for Linux users.
  • Consider including a parity matrix/table showing feature availability across Azure Portal, Azure CLI, and Azure PowerShell, with platform notes.
  • Avoid always listing PowerShell examples first; alternate ordering or group by tool rather than platform.
GitHub Create Pull Request
DNS Private DNS records overview - Azure Private DNS ...ure-docs/blob/main/articles/dns/dns-private-records.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias primarily through its references to PowerShell and the Azure portal as primary interfaces for managing DNS records, with CLI mentioned only in passing and no explicit Linux-specific examples or tools. The explanation of Etags specifically calls out Azure DNS PowerShell behavior before mentioning REST API headers, and the TXT records section lists PowerShell and portal before CLI. There are no Linux command-line examples (e.g., using dig, nsupdate, or Azure CLI on Linux), and Windows-centric tools and patterns are mentioned first or exclusively.
Recommendations
  • Add explicit Azure CLI examples for all operations, and clarify that CLI works cross-platform (Windows, Linux, macOS).
  • Include Linux-native DNS management tools (e.g., dig, nsupdate) in examples where appropriate.
  • When listing interfaces (portal, PowerShell, CLI), avoid always listing PowerShell first; rotate or clarify parity.
  • Add a section or note highlighting cross-platform support and usage patterns for Linux users.
  • Ensure that REST API examples are not overshadowed by PowerShell-specific instructions.
GitHub Create Pull Request
DNS Protecting DNS Zones and Records - Azure DNS ...blob/main/articles/dns/dns-protect-zones-recordsets.md
High Priority View Details →
Scanned: 2026-01-11 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 moderate Windows bias. PowerShell is consistently featured as the primary scripting example, with Azure CLI provided as a secondary option. Several operations (notably record set level resource locks) are only documented for PowerShell, with explicit notes that Azure CLI and portal do not support these actions. There are no Linux-specific shell examples (e.g., bash), nor are cross-platform scripting patterns discussed. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not address Linux-native tools or workflows.
Recommendations
  • Where PowerShell is used, provide equivalent bash or shell script examples for Linux users, especially for Azure CLI commands.
  • Clarify platform support for each tool (e.g., note that Azure CLI is cross-platform, while PowerShell may require installation on Linux).
  • For operations only available in PowerShell, suggest workarounds or alternatives for Linux users, or provide links to relevant GitHub issues/feature requests.
  • Include explicit instructions for installing and using Azure PowerShell on Linux, or recommend using Azure CLI where possible.
  • Add a section summarizing cross-platform considerations and best practices for Linux administrators managing Azure DNS.
GitHub Create Pull Request
DNS Azure DNS Private Resolver Overview ...lob/main/articles/dns/dns-private-resolver-overview.md
High Priority View Details →
Scanned: 2026-01-11 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 by prioritizing Azure PowerShell (a Windows-centric tool) in both quickstart and next steps links, without mentioning or providing equivalent Linux-friendly CLI examples (such as Azure CLI or Bash). There are no references to Linux tools or workflows, and PowerShell is presented before or instead of cross-platform alternatives.
Recommendations
  • Add quickstart and setup instructions using Azure CLI (az), which is cross-platform and widely used on Linux.
  • Include examples and references for Bash scripting and Linux DNS tools (e.g., dig, resolvectl) where relevant.
  • Ensure that PowerShell is not presented as the only or primary automation option; mention Terraform, ARM templates, and Bicep equally.
  • Where DNS configuration is discussed, provide guidance for both Windows (PowerShell, GUI) and Linux (CLI, config files) environments.
  • Review all code samples and walkthroughs to ensure Linux parity and cross-platform accessibility.
GitHub Create Pull Request
DNS Secure and view DNS traffic - Azure DNS ...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing extensive PowerShell-based instructions and examples for configuring Azure DNS security policies, with no equivalent CLI or scripting examples for Linux/macOS users. Windows-specific tools and patterns (e.g., PowerShell modules, C:\ paths, Resolve-DnsName) are used exclusively or mentioned first. Linux alternatives (such as Azure CLI, Bash, or cross-platform scripting) are missing, and there is no guidance for users who do not use Windows or PowerShell.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell instructions, including resource creation, policy configuration, and testing.
  • Provide Linux/macOS-specific setup instructions, such as using the Azure CLI or REST API, and avoid Windows-only file paths (e.g., use ~/bin/PSRepo or /tmp/PSRepo for Linux).
  • Include cross-platform DNS query examples (e.g., using dig or nslookup from Linux/macOS terminals) alongside PowerShell's Resolve-DnsName.
  • Clearly indicate parity between Windows and Linux workflows, and ensure that all major steps have examples for both environments.
  • Consider restructuring sections so that cross-platform or Linux examples are presented alongside or before Windows/PowerShell examples, to avoid implicit prioritization.
GitHub Create Pull Request
DNS Overview of DNS security policy ...ure-docs/blob/main/articles/dns/dns-security-policy.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by only mentioning Azure PowerShell and the Azure portal as configuration methods, with no references to Linux-native tools, Azure CLI, or cross-platform scripting. There are no examples or instructions for Linux users, and Windows-centric tools are presented as the default or only options.
Recommendations
  • Add instructions and examples for configuring DNS security policy using Azure CLI, which is cross-platform and widely used on Linux.
  • Explicitly mention Linux and macOS compatibility where relevant, and provide guidance for users on those platforms.
  • Include sample scripts or commands for both PowerShell and Azure CLI, and present them side-by-side or in parallel sections.
  • Avoid presenting Windows tools or patterns as the default; instead, introduce cross-platform options first or equally.
  • Reference documentation or guides for Linux users, such as installing and using Azure CLI on Linux.
GitHub Create Pull Request
DNS How to sign your Azure Public DNS zone with DNSSEC ...ocs/azure-docs/blob/main/articles/dns/dnssec-how-to.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by providing PowerShell examples and referencing Windows-specific tools (e.g., dig.exe) without explicitly offering Linux shell or cross-platform alternatives. The ordering of examples places PowerShell after Azure CLI, but the CLI examples use 'azurepowershell-interactive' syntax blocks, which may confuse Linux users. The use of 'dig.exe' suggests a Windows environment, and there is no mention of Linux-specific command syntax or tools (e.g., bash, dig on Linux, or shell scripting). There are no explicit Linux examples or guidance for Linux users.
Recommendations
  • Add explicit Linux shell examples (bash) for all CLI commands, using standard Linux tools and syntax.
  • Clarify that 'dig' is available on Linux and provide a Linux command-line example (e.g., 'dig adatum.com DS +dnssec' in bash).
  • Use neutral code block syntax (e.g., 'bash', 'sh', or 'console') for CLI commands instead of 'azurepowershell-interactive', unless PowerShell is required.
  • Include guidance for installing and using Azure CLI and dig on Linux systems.
  • Ensure parity in instructions for both Windows and Linux environments, possibly with tabs or sections for each OS.
GitHub Create Pull Request
DNS Tutorial: Create Custom Azure DNS Records For a Web App .../blob/main/articles/dns/dns-web-sites-custom-domain.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 in detail and are referenced before Azure CLI examples throughout the page. The testing section uses nslookup with Windows-style prompts (PS C:\>), and does not mention Linux alternatives or shell environments. The prerequisites and instructions reference Azure PowerShell and Cloud Shell prominently, with less emphasis on CLI or Linux-native tools. There is no mention of Linux-specific DNS utilities (e.g., dig), nor are Linux shell examples or command-line environments discussed.
Recommendations
  • Provide Linux shell examples alongside PowerShell, especially for DNS testing (e.g., show dig usage in addition to nslookup).
  • Avoid Windows-centric prompts (e.g., PS C:\>) in generic command examples; use neutral or Linux shell prompts (e.g., $) where possible.
  • Mention that Azure CLI is cross-platform and can be used in Linux/macOS environments, and provide instructions for installing/running CLI on those platforms.
  • Include references to Linux-native tools and environments in prerequisites and testing sections.
  • Balance the order of examples: alternate between PowerShell and CLI, or present CLI first in some sections to avoid 'windows_first' bias.
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-11 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, which subtly prioritizes Windows tooling. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific patterns or tools. The 'Familiar tools' section groups PowerShell and CLI together, but PowerShell is listed first, and no Linux-specific guidance or screenshots are provided.
Recommendations
  • Alternate the order of PowerShell and CLI references, or list CLI first to better reflect cross-platform usage.
  • Explicitly mention that Azure CLI is cross-platform and provide examples or links for Linux users.
  • Include Linux/Bash-specific usage examples or screenshots where relevant.
  • Add a note clarifying that both PowerShell and CLI are supported on Windows, Linux, and macOS.
  • Ensure parity in troubleshooting and advanced scenarios by including Linux-centric instructions and considerations.
GitHub Create Pull Request
DNS Private resolver architecture ...lob/main/articles/dns/private-resolver-architecture.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where Azure PowerShell is listed as the only CLI-based method for creating a DNS Private Resolver, with no mention of Azure CLI (cross-platform) or Linux-specific tools. Throughout the page, there are no examples or references to Linux DNS tools (e.g., dig, resolv.conf), nor are Linux configuration patterns discussed. The documentation assumes the use of Azure-provided DNS and custom DNS settings, but does not address how these would be configured or verified on Linux VMs or with Linux-native tooling.
Recommendations
  • Add Azure CLI instructions alongside Azure PowerShell for creating and managing DNS Private Resolvers.
  • Include Linux-specific DNS configuration examples (e.g., editing /etc/resolv.conf, using dig/nslookup on Linux).
  • Reference Linux tools and patterns for DNS troubleshooting and verification.
  • Ensure that cross-platform parity is maintained in all example commands and configuration steps.
  • Explicitly mention that the guidance applies to both Windows and Linux VMs, and provide links to OS-specific DNS configuration documentation.
GitHub Create Pull Request
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-11 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 demonstrates a Windows bias in several ways: all VM creation examples use Windows images, all testing instructions and output are based on Windows PowerShell, and only Windows firewall configuration is shown. There are no Linux VM creation examples, nor instructions for configuring Linux firewalls or testing DNS resolution from Linux VMs. Windows tools and patterns (PowerShell, Windows firewall, Windows-centric output) are used exclusively for post-deployment steps.
Recommendations
  • Include Linux VM creation examples using a popular image (e.g., Ubuntu) alongside Windows examples.
  • Provide instructions for configuring Linux firewalls to allow ICMP (e.g., using ufw or iptables).
  • Show how to test DNS resolution from a Linux VM (e.g., using ping, nslookup, or dig) and provide sample output.
  • Present both Windows and Linux steps in parallel, or clearly indicate which instructions apply to which OS.
  • Avoid assuming users are only deploying Windows workloads; mention cross-platform applicability in the introduction.
GitHub Create Pull Request
DNS Migrating legacy Azure DNS private zones to the new resource model .../blob/main/articles/dns/private-dns-migration-guide.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All migration steps rely on PowerShell scripts, with explicit instructions to use elevated PowerShell windows and references to PowerShell modules and tools. There are no Bash or Linux shell script equivalents, nor is there guidance for running the migration from Linux or macOS environments. The documentation assumes the user is on Windows, and Linux alternatives are not mentioned or prioritized.
Recommendations
  • Provide equivalent migration scripts or instructions using Azure CLI and Bash for Linux/macOS users.
  • Include installation and usage steps for Azure CLI and relevant modules on Linux and macOS.
  • Clarify whether the migration can be performed from Azure Cloud Shell (Bash) or provide alternatives if not.
  • Ensure screenshots and examples reflect both Windows and Linux environments.
  • Mention cross-platform compatibility of scripts and tools, or provide platform-specific guidance where necessary.
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-11 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 through its 'Next steps' section, which lists Azure PowerShell (a Windows-centric tool) as the only command-line example for creating a DNS Private Resolver, with no mention of Azure CLI or Linux shell equivalents. The page also references screenshots and configuration patterns that are platform-neutral but omits explicit Linux or cross-platform tooling guidance. There are no examples or instructions for Linux users or those using non-Windows environments.
Recommendations
  • Add Azure CLI examples for creating and managing DNS Private Resolver resources, ensuring parity with PowerShell instructions.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant Linux/macOS documentation.
  • Include screenshots or terminal output from Linux environments where applicable.
  • Clarify that all configuration steps can be performed from Linux, macOS, or Windows, and provide guidance for each where differences exist.
  • Review all referenced tutorials and ensure Linux/CLI instructions are present alongside PowerShell and portal steps.
GitHub Create Pull Request
← Previous Page 1 of 13 Next →