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 26-50 of 323 flagged pages
DNS
Quickstart - Create an Azure private DNS zone using the Azure portal
...lob/main/articles/dns/private-dns-getstarted-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the test VM, referencing RDP for access, and providing only PowerShell-based examples for command execution (e.g., RunPowerShellScript). There are no examples or instructions for creating or testing with a Linux VM, nor are Linux shell commands (such as bash or SSH) mentioned. The 'ping' test is shown only via Windows command prompt and PowerShell, with no Linux equivalent.
Recommendations
- Include parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
- Provide examples for connecting to a Linux VM using SSH, and demonstrate DNS resolution tests using Linux shell commands (e.g., 'ping', 'nslookup', 'dig').
- Show how to use the Azure portal's Run Command feature with Linux VMs (e.g., using 'RunShellScript').
- Mention Linux-specific access methods (SSH, SCP) and ports (e.g., 22 for SSH) when discussing inbound connectivity.
- Ensure that CLI and PowerShell links in prerequisites are equally emphasized, and clarify that all steps can be performed on either platform.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the link to creating a Private DNS zone points specifically to a PowerShell-based guide, which is most commonly used on Windows. There is no mention of Linux tools, CLI, or cross-platform alternatives, and no Linux-specific examples are provided. The documentation implicitly prioritizes Windows tooling and patterns.
Recommendations
- Include links to equivalent Linux or cross-platform guides, such as using Azure CLI or REST API for creating Private DNS zones.
- Explicitly mention that Azure DNS management can be performed from Linux, macOS, and Windows, and provide examples for each.
- Balance example coverage by providing both PowerShell and Azure CLI (or Bash) commands when demonstrating tasks.
- Add a note clarifying the cross-platform nature of Azure DNS management tools.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing a 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 or cross-platform command examples, and the only explicit 'how-to' link is Windows-centric. This may make it harder for Linux users to follow along or feel equally supported.
Recommendations
- Include links to Linux/CLI/Bash-based guides for creating and managing Private DNS zones alongside the PowerShell guide.
- Add cross-platform command examples (e.g., Azure CLI) within the scenarios to demonstrate how to perform key actions on both Windows and Linux.
- Ensure that references to tools or scripts are presented in a platform-neutral way, or that both Windows and Linux options are given equal prominence.
- Review the 'Next steps' section to ensure parity between Windows and Linux documentation links.
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing examples and procedures for Windows DNS servers when configuring on-premises DNS conditional forwarders. There are no examples or guidance for configuring equivalent DNS forwarding on Linux-based DNS servers (such as BIND or dnsmasq), nor are Linux tools or commands mentioned. The quickstarts and procedural steps prioritize PowerShell and portal interfaces, with CLI mentioned but not emphasized. This may leave Linux administrators without clear instructions for hybrid DNS setups.
Recommendations
- Add explicit examples and step-by-step instructions for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
- Include screenshots or configuration file snippets for Linux DNS server setups, similar to those provided for Windows DNS.
- Mention Linux CLI tools and commands (e.g., dig, nsupdate) when demonstrating DNS queries and troubleshooting.
- Ensure that quickstart links and procedural steps include Linux CLI and configuration options with parity to PowerShell/portal examples.
- Add a section discussing differences and considerations for hybrid DNS resolution in mixed Windows/Linux environments.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only a Windows command-line example (nslookup in a PowerShell prompt) for testing DNS resolution, with no mention of Linux equivalents or Linux tools. The command prompt shown is explicitly Windows (C:\>), and there is no guidance for Linux users on how to perform similar tasks. The documentation implicitly assumes the user is on Windows, both in screenshots and instructions.
Recommendations
- Include Linux command-line examples for DNS resolution, such as using 'nslookup', 'dig', or 'host' from a Linux shell.
- Show both Windows and Linux command prompts in examples (e.g., 'C:\>' and '$').
- Add a note clarifying that the steps for testing DNS resolution apply to both Windows and Linux VMs, and provide explicit instructions for each.
- Where screenshots or instructions reference Windows-specific tools or UI, provide Linux equivalents or clarify cross-platform applicability.
DNS
Tutorial - Set up DNS failover using private resolvers
...articles/dns/tutorial-dns-private-resolver-failover.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias in the DNS forwarding configuration section. Only Windows Server and PowerShell examples are provided for setting up conditional forwarders, with no mention of Linux-based DNS servers (such as BIND or dnsmasq) or their configuration steps. Windows terminology and tools (PowerShell, DNS console) are used exclusively, and Windows is presented as the default/primary platform for on-premises DNS management.
Recommendations
- Add equivalent configuration instructions for popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound), including sample configuration file snippets for conditional forwarding.
- Include Linux command-line examples (e.g., editing named.conf, using dig/nslookup from Linux shells) alongside Windows/PowerShell examples.
- Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and provide links to relevant Linux documentation.
- Reorder or parallelize examples so that Windows and Linux instructions are presented together, rather than Windows first.
- Clarify any platform-specific limitations or considerations for Azure DNS Private Resolver integration.
DNS
How to unsign your Azure Public DNS zone
...ocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
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. While the Azure CLI is cross-platform, the explicit inclusion of PowerShell examples and the use of Azure CLI commands in a 'azurepowershell-interactive' code block may suggest a Windows-centric approach. There are no Linux-specific shell examples (e.g., bash), nor any mention of Linux tools or patterns. The ordering places PowerShell instructions on equal footing with CLI, and no effort is made to clarify cross-platform usage or provide Linux-specific guidance.
Recommendations
- Add explicit bash shell examples for the Azure CLI section, demonstrating usage on Linux/macOS.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide platform-specific notes if needed.
- Remove or replace 'azurepowershell-interactive' code block labeling with a more neutral 'bash' or 'sh' where appropriate.
- Consider including troubleshooting or verification steps using Linux-native tools (e.g., dig, nslookup) to check DNSSEC status.
- Ensure that PowerShell is presented as an option, not the default or primary method, and balance with Linux-native alternatives.
DNS
Secure and view DNS traffic - Azure DNS
...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive PowerShell-based instructions and examples, referencing Windows-specific tools and filesystem paths (e.g., C:\bin\PSRepo), and using Windows command-line conventions. There are no equivalent Linux/bash CLI examples for scripting or automation, and the PowerShell tab is the only non-portal automation method described. The only Linux-relevant content is the use of 'dig', but even this is shown in a Windows command prompt context (C:\>dig ...), and there are no bash/Azure CLI instructions for Linux users.
Recommendations
- Add equivalent Azure CLI/bash examples for all PowerShell automation steps, including resource creation, policy management, and diagnostics.
- Provide Linux-specific instructions for setting up local repositories and installing required modules/packages.
- Include Linux shell examples for DNS queries and troubleshooting, using native Linux tools and conventions.
- Ensure that command-line examples are shown in both Windows and Linux contexts, with appropriate prompts and paths.
- Reference cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
- Explicitly mention Linux support and parity in prerequisites and throughout the documentation.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell and Windows command prompt (cmd) examples for deploying and validating the ARM template. There are no Linux shell or Azure CLI examples, and the instructions reference Windows tools and patterns (e.g., right-click to paste, cmd prompt) without mentioning Linux equivalents. The validation step uses 'nslookup' in a Windows command prompt, omitting Linux shell alternatives.
Recommendations
- Add Azure CLI examples for deploying the ARM template, suitable for both Linux and macOS users.
- Include instructions and screenshots for using Bash or other Linux shells in Azure Cloud Shell.
- Provide Linux/macOS equivalents for validation steps, such as using 'dig' or 'nslookup' in a Bash terminal.
- Clarify that Azure Cloud Shell supports both PowerShell and Bash, and show how to select the shell.
- Avoid Windows-specific instructions like 'right-click to paste' and instead use cross-platform guidance.
- Ensure screenshots and command blocks reflect both Windows and Linux environments where appropriate.
DNS
Integrate Azure DNS with your Azure resources - Azure DNS
...azure-docs/blob/main/articles/dns/dns-custom-domain.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently references the Windows-centric 'nslookup' tool for DNS validation, and all screenshots and instructions appear to be based on the Azure Portal GUI, which is platform-neutral but lacks any command-line examples. There are no Linux-specific validation commands (such as 'dig') or mentions of Linux tools. The only DNS validation example shown is 'nslookup', which is most commonly associated with Windows and is demonstrated in a Windows command prompt. No PowerShell-specific commands are present, but the omission of Linux CLI examples and the use of Windows tools indicate a Windows-first bias.
Recommendations
- Include Linux-specific DNS validation examples using 'dig' alongside 'nslookup'.
- Explicitly mention that 'nslookup' is available on both Windows and Linux, and provide sample commands for each platform.
- Add CLI-based instructions for DNS record management using Azure CLI or cross-platform tools, not just portal screenshots.
- Where screenshots show command prompts, clarify the platform and provide equivalent Linux terminal screenshots if possible.
- Ensure terminology and instructions are inclusive of both Windows and Linux users, especially in validation and troubleshooting steps.
DNS
Import and export a domain zone file - Azure portal
...ocs/blob/main/articles/dns/dns-import-export-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows DNS and its zone file location before Linux/BIND equivalents, and by providing explicit details for Windows tools (e.g., DNS console, %systemroot% path) while only briefly referencing BIND for Linux. There are no concrete Linux/BIND file path examples or screenshots, and no Linux-specific workflow or troubleshooting guidance. The import/export instructions and examples are platform-neutral, but the initial guidance for obtaining zone files is Windows-centric.
Recommendations
- Present Linux/BIND instructions and examples alongside or before Windows equivalents, including typical file paths (e.g., /etc/bind/) and configuration file references.
- Include screenshots or step-by-step instructions for obtaining zone files from BIND/Linux environments, similar to those provided for Windows DNS.
- Add troubleshooting notes for common Linux/BIND scenarios (e.g., permissions, file formats, named.conf location).
- Explicitly state that the process applies equally to zone files from both Windows and Linux/BIND, and provide parity in example details.
- Consider a table or section comparing Windows and Linux/BIND zone file locations and extraction methods.
DNS
Import and export a domain zone file - Azure CLI
...azure-docs/blob/main/articles/dns/dns-import-export.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. 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. In the verification section, the only explicit example for querying DNS records uses the Windows Command Prompt and nslookup, without mentioning Linux equivalents (e.g., dig or nslookup on Linux). No Linux-specific examples or file paths are provided, and no cross-platform shell commands are shown for verification.
Recommendations
- Mention BIND (Linux) before or alongside Windows DNS when discussing zone file locations, and provide example Linux file paths (e.g., /etc/bind/).
- Include Linux shell command examples (e.g., using dig or nslookup in bash) for DNS verification, not just Windows Command Prompt.
- Clarify that nslookup and dig are available on Linux/macOS, and show equivalent commands for those platforms.
- Where file paths are referenced, provide both Windows and Linux examples.
- Explicitly state that Azure CLI commands work identically on Windows, Linux, and macOS, and show sample CLI usage in a Linux shell (bash/zsh) as well as Windows.
DNS
Private DNS records overview - Azure Private DNS
...ure-docs/blob/main/articles/dns/dns-private-records.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias primarily through its references to PowerShell as the default example interface for managing Azure DNS resources. PowerShell is mentioned explicitly as the tool for handling Etags and for managing TXT records, with no equivalent mention of Linux-native tools or cross-platform alternatives. The ordering and phrasing suggest that Windows/PowerShell is the primary or preferred method, while Linux or cross-platform CLI options are not given equal visibility.
Recommendations
- Include explicit examples using Azure CLI (az) for all operations currently described with PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Mention and demonstrate REST API usage where appropriate, as it is platform-agnostic.
- When referencing tools or interfaces, present Azure CLI and PowerShell together, or list Azure CLI first to avoid implicit Windows-first bias.
- Add notes or links for Linux users, clarifying how to perform the same tasks on Linux or macOS.
- Avoid language that implies PowerShell is the default or only option; instead, use neutral phrasing such as 'using Azure CLI or PowerShell'.
DNS
Protecting DNS Zones and Records - Azure DNS
...blob/main/articles/dns/dns-protect-zones-recordsets.md
High Priority
View Details →
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 automation example, often before Azure CLI. Several advanced operations (e.g., record set-level resource locks) are only documented with PowerShell, with explicit notes that Azure CLI or portal do not support these actions. There are no Linux-specific command-line examples, nor any mention of Linux tools or shell patterns (e.g., bash, scripting, environment variables). The documentation assumes familiarity with PowerShell syntax and workflows, which are most common on Windows systems.
Recommendations
- Ensure all automation examples are provided for both Azure PowerShell and Azure CLI, with equal prominence and ordering.
- Where PowerShell is the only supported method, clarify whether this is due to Azure platform limitations or documentation gaps, and provide guidance for Linux users (e.g., running PowerShell Core on Linux, or alternative approaches).
- Include Linux shell (bash/zsh) usage notes, such as environment variable handling, file paths, and scripting patterns.
- Add explicit statements about cross-platform compatibility for Azure CLI and PowerShell, including installation links for Linux and macOS.
- If certain features are unavailable in CLI or portal, suggest workarounds or provide links to feature requests/community discussions for parity.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for Azure DNS Private Resolver demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal as the primary methods for setup, with no mention of Linux-native tools (such as Azure CLI or Bash scripting) or examples. PowerShell is a Windows-centric tool, and its use is highlighted before any Linux-compatible alternatives. There are no explicit Linux or cross-platform setup instructions or examples, and the documentation does not mention or link to Azure CLI-based quickstarts or tutorials.
Recommendations
- Add Azure CLI-based quickstart and setup instructions, and link them alongside PowerShell and portal options.
- Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide example commands for common tasks.
- Ensure that cross-platform tools (e.g., Terraform, ARM templates, Bicep) are referenced with parity to Windows-specific tools.
- Where PowerShell is mentioned, also provide equivalent Bash or Azure CLI examples.
- Review all setup and configuration sections to ensure Linux administrators can follow along without needing to use Windows tools.
DNS
Reverse DNS for Azure services - Azure DNS
...ain/articles/dns/dns-reverse-dns-for-azure-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing extensive examples using Azure PowerShell and classic PowerShell cmdlets, which are primarily Windows-centric. The Cloud Services section is exclusively documented with PowerShell commands, with no Azure CLI or Linux-native instructions. While Azure CLI examples are present for Public IP resources, there are no bash, shell, or Linux-native DNS tool examples (e.g., dig, nslookup) for validation or verification. PowerShell is consistently presented first in example sections, reinforcing a Windows-first approach.
Recommendations
- Add Linux-native command examples (e.g., bash, dig, nslookup) for viewing and validating reverse DNS records.
- Provide parity for Cloud Services management by including Azure CLI or REST API instructions, if supported, or clarify platform limitations.
- Alternate the order of examples to avoid always presenting PowerShell first; consider starting with Azure CLI or presenting both side-by-side.
- Explicitly mention cross-platform compatibility for Azure CLI and highlight usage on Linux/macOS.
- Where PowerShell is required, note the availability of PowerShell Core on Linux/macOS and provide installation guidance.
High Priority
View Details →
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, Bash, or Linux-native tools. No Linux or cross-platform command-line examples are provided, and PowerShell is listed before the Azure portal, suggesting a Windows-first approach. There are no examples or guidance for configuring DNS security policy from Linux environments.
Recommendations
- Add Azure CLI examples for configuring DNS security policy, ensuring parity with PowerShell instructions.
- Explicitly mention cross-platform tools (e.g., Azure CLI, Bash) alongside PowerShell in configuration sections.
- Provide sample commands and workflows for Linux/macOS users, including screenshots or terminal output where appropriate.
- Review related how-to guides to ensure Linux and cross-platform instructions are present and equally prominent.
- Avoid listing Windows-specific tools (PowerShell) before cross-platform alternatives unless justified by feature availability.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits Windows bias primarily through its emphasis on PowerShell as the default management tool for Azure DNS, with explicit references to PowerShell usage and options (such as the '-Overwrite' switch) before mentioning other interfaces. There is no mention of Linux-specific tools or command-line examples (e.g., Bash, Azure CLI on Linux), nor are cross-platform alternatives highlighted. The documentation implicitly assumes users are familiar with Windows-centric tooling and patterns.
Recommendations
- Add Azure CLI examples for DNS management tasks alongside PowerShell examples, ensuring parity for Linux and macOS users.
- Explicitly mention that Azure CLI and REST API can be used from any platform, including Linux and macOS, and provide links or examples.
- When discussing features like Etags, include CLI and REST API usage patterns, not just PowerShell.
- Avoid presenting PowerShell as the default or only option; instead, introduce management interfaces in a platform-neutral order (e.g., REST API, CLI, PowerShell, Portal).
- Include references to Linux tools (e.g., dig, nsupdate) where relevant, especially in sections discussing DNS records and troubleshooting.
DNS
Protecting private DNS Zones and Records - Azure DNS
...n/articles/dns/dns-protect-private-zones-recordsets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell (commonly used on Windows) is consistently presented before Azure CLI in all code examples, and some advanced operations (such as record set level resource locks) are only documented for PowerShell, with no Linux-native or cross-platform alternatives. There are no explicit Linux shell (bash) examples, and no mention of Linux-specific tooling or workflows. The page assumes familiarity with PowerShell and does not provide parity for users who prefer or require Linux environments.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell, especially for common tasks.
- Where PowerShell is the only option, explicitly state platform limitations and provide guidance for Linux users (e.g., using PowerShell Core on Linux, or alternatives if available).
- Add bash shell examples for Azure CLI commands to demonstrate usage in Linux environments.
- Highlight cross-platform compatibility of Azure CLI and PowerShell Core, and clarify any Windows-only requirements.
- Where features are unavailable in CLI or portal, note this clearly and suggest workarounds for non-Windows users.
DNS
Host reverse DNS lookup zones in Azure DNS
...docs/blob/main/articles/dns/dns-reverse-dns-hosting.md
High Priority
View Details →
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 examples, and by including PowerShell-specific instructions throughout. The use of PowerShell is emphasized, which is primarily a Windows tool, and no Linux-specific shell examples (such as Bash) are provided. The Azure classic CLI is mentioned, but it is deprecated and not platform-specific. There are no references to Linux-native tools or workflows, and the documentation does not address Linux user experience or parity.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
- Add explicit Bash shell examples for Azure CLI commands, showing usage in a Linux terminal.
- Include notes or sections on how to install and use Azure CLI on Linux systems.
- Avoid using PowerShell-specific syntax or instructions as the primary example; treat PowerShell and CLI equally.
- Mention Linux-native DNS tools (e.g., dig, nsupdate) for verification or troubleshooting steps.
- Clarify that all CLI commands work on Linux, macOS, and Windows, and provide platform-specific guidance where relevant.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured prominently and often before Azure CLI, both in prerequisites and step-by-step instructions. Windows-specific tools and patterns, such as nslookup with Windows-style prompts (PS C:\>), are used for DNS validation. There is no mention of Linux-specific tools (e.g., dig) or shell environments, and examples assume a Windows context for command-line usage and output formatting.
Recommendations
- Include Linux-specific validation examples, such as using 'dig' or 'host' commands, alongside or instead of 'nslookup'.
- Show Azure CLI usage in both Windows (cmd/powershell) and Linux/macOS (bash/zsh) contexts, clarifying shell differences where relevant.
- Balance PowerShell and CLI examples by presenting CLI instructions first or equally, as CLI is cross-platform.
- Avoid Windows-centric prompts and output formats (e.g., 'PS C:\>'), or provide equivalent Linux/macOS examples.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation or usage notes for those platforms.
- Add notes or links for Linux users on how to access Azure Cloud Shell from non-Windows environments.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias by prioritizing Windows tools and patterns. Examples for viewing DNSSEC records are given first in PowerShell (Resolve-DnsName), with Windows command prompt (dig.exe) shown as a secondary method. There is explicit mention of Windows 10/11 client behavior and Group Policy, with no discussion of Linux client or server equivalents. Linux-native tools (e.g., dig, drill, host) are not highlighted, and there are no Linux shell examples. The guidance on DNSSEC validation and enforcement is Windows-centric, omitting Linux system configuration approaches.
Recommendations
- Provide Linux shell examples using dig, drill, or host, and show equivalent commands for viewing DNSSEC records.
- Mention Linux DNS resolver behavior (e.g., systemd-resolved, Unbound, BIND) and how DNSSEC validation/enforcement is configured on Linux systems.
- Reorder examples to present cross-platform tools (e.g., dig) before or alongside Windows-specific tools.
- Include notes on how to perform DNSSEC validation and policy enforcement on Linux, referencing relevant configuration files (e.g., /etc/unbound/unbound.conf, /etc/bind/named.conf.options).
- Clarify that dig is available on both Windows and Linux, and provide installation instructions for both platforms if needed.
- Avoid exclusive references to Windows Group Policy and NRPT; mention Linux equivalents or alternatives for DNSSEC policy management.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and references to Windows command-line tools (e.g., dig.exe) before or in preference to Linux equivalents. The CLI and PowerShell tabs are presented, but there are no explicit Linux shell/bash examples, and the use of 'dig.exe' suggests a Windows-centric approach. There is no mention of Linux-specific commands, nor are Linux installation or usage notes provided for tools like dig or jq.
Recommendations
- Add explicit bash/Linux shell examples for each step, including commands for querying DS records (e.g., using 'dig' or 'host' on Linux).
- Replace references to 'dig.exe' with platform-neutral 'dig', and clarify installation instructions for both Windows and Linux.
- Include notes or examples for installing required tools (e.g., dig, jq) on Linux distributions.
- Ensure parity in CLI instructions by showing both Windows and Linux command syntax and output where differences exist.
- Add a Linux tab or section alongside PowerShell and Azure CLI to demonstrate cross-platform support.
DNS
Quickstart - Create an Azure private DNS zone using the Azure portal
...lob/main/articles/dns/private-dns-getstarted-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the example OS for the test VM, providing only Windows-centric instructions (such as RDP access and PowerShell-based commands), and omitting any Linux VM creation or Linux command-line examples for DNS resolution. The 'Test the private zone' section uses Windows 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 resolution, such as using 'ping', 'nslookup', or 'dig' from a Linux shell.
- Show how to use the Azure portal's 'Run command' feature with Bash scripts for Linux VMs.
- When referencing remote access, mention SSH for Linux VMs in addition to RDP for Windows.
- Balance screenshots and command outputs to show both Windows and Linux environments.
- Explicitly state that the steps apply to both Windows and Linux VMs, and highlight any OS-specific differences.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All migration instructions, prerequisites, and automation steps are exclusively described using PowerShell scripts and modules, with no mention of Linux shell equivalents or cross-platform alternatives. The guide assumes use of an 'elevated PowerShell window', references Windows-specific administrative modes, and omits Bash or Azure CLI scripting for Linux/macOS users. The only non-PowerShell command is a single Azure CLI query, but the actual migration process is entirely PowerShell-based.
Recommendations
- Provide equivalent migration instructions using Azure CLI and Bash scripts for Linux/macOS users.
- Include prerequisites and installation steps for Azure CLI and relevant modules on Linux/macOS.
- Offer downloadable migration scripts in Bash or Python, or clarify if the PowerShell script works cross-platform (e.g., with PowerShell Core on Linux/macOS).
- Rephrase instructions to avoid Windows-specific terminology (e.g., 'elevated PowerShell window') and include guidance for Linux/macOS environments.
- Add screenshots or examples showing the migration process on Linux/macOS terminals.
- Explicitly state platform compatibility for the migration script and provide troubleshooting steps for non-Windows users.