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 126-150 of 323 flagged pages
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-get-started-template.md
...ocs/blob/main/articles/dns/dns-get-started-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line deployment instructions use Azure PowerShell, and the validation step uses Windows Command Prompt syntax (cmd). There are no examples or instructions for using Azure CLI (which is cross-platform and preferred on Linux/macOS), nor are there any Linux shell or terminal examples for validation (e.g., using dig or nslookup in a bash shell). The workflow and screenshots are tailored to Windows users, with no mention of Linux or macOS alternatives.
Recommendations
- Provide equivalent Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Include Linux/macOS shell instructions for validation, such as using nslookup or dig from a bash terminal.
- When referencing command-line tools, avoid using only Windows Command Prompt syntax; show both Windows and Linux/macOS alternatives side by side.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
- Add screenshots or output examples from Linux/macOS terminals where appropriate.
- Rephrase steps to be OS-agnostic where possible, or clearly indicate when a step is specific to Windows.
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 →
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, prerequisites, and automation are described exclusively using PowerShell scripts and modules, with explicit instructions to use an 'elevated PowerShell window.' There are no equivalent instructions or scripts for Linux or cross-platform environments, nor are alternative methods (such as Bash, Azure CLI, or Python scripts) provided. The documentation assumes the user is on Windows and does not address Linux or macOS users, except for a brief mention of Azure CLI in the discovery step.
Recommendations
- Provide equivalent migration instructions using Azure CLI and/or Bash scripts that can be run on Linux and macOS.
- Offer a cross-platform version of the migration script (e.g., in Python or as an Azure CLI extension) and document its usage.
- Explicitly state platform compatibility for the provided scripts and offer guidance for non-Windows users.
- Include Linux/macOS-specific prerequisites and installation steps (e.g., how to install Azure CLI or PowerShell Core on Linux).
- Ensure that all screenshots and command prompts are not Windows-specific, or provide alternatives for other platforms.
- Reorder examples or provide parallel instructions so that Linux and cross-platform options are presented alongside or before Windows-specific ones.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only a Windows/Powershell example (nslookup with C:\> prompt) for testing DNS resolution, with no mention of Linux or cross-platform alternatives. The command-line example and screenshot style are Windows-centric, and there is no guidance for users on Linux or macOS systems.
Recommendations
- Include equivalent Linux/macOS command-line examples for DNS resolution, such as using nslookup or dig from a bash shell (e.g., $ nslookup 10.1.2.5 or $ dig -x 10.1.2.5).
- Present both Windows and Linux/macOS examples side-by-side or indicate that the instructions apply to multiple platforms.
- Use neutral language when referring to command-line operations (e.g., 'Open a terminal or command prompt') rather than assuming a Windows environment.
- Add screenshots or output samples from Linux/macOS terminals where appropriate to ensure parity.
- Explicitly mention that the Azure portal steps are platform-agnostic, but that command-line verification can be performed from any OS.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-sdk.md
...osoftDocs/azure-docs/blob/main/articles/dns/dns-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by referencing Visual Studio and NuGet Package Manager (GUI) as the primary development environment and package management approach, with no mention of Linux-compatible tools or workflows. The service principal creation step links to a PowerShell-based guide, and there are no examples or instructions for Linux users (e.g., using .NET CLI, VS Code, or Bash).
Recommendations
- Add instructions for creating a service principal using Azure CLI (az), which is cross-platform, alongside or instead of PowerShell.
- Include steps for installing NuGet packages using the .NET CLI (dotnet add package ...) for users on Linux or macOS.
- Reference cross-platform editors such as Visual Studio Code, and clarify that the .NET SDK and libraries work on Linux and macOS as well as Windows.
- Provide links to Linux/macOS setup guides for .NET development.
- Ensure that all tooling and workflow steps are presented in a platform-neutral way, or provide parallel instructions for both Windows and Linux users.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Windows Server and PowerShell-based instructions for configuring DNS conditional forwarders. No Linux or cross-platform DNS server configuration examples are given. Windows terminology and tools (PowerShell, Windows DNS Server role, DNS console) are used exclusively, and the only command-line example for configuring forwarders is in PowerShell. The documentation does not mention or provide steps for common Linux DNS servers (such as BIND or dnsmasq), nor does it acknowledge their usage in on-premises environments.
Recommendations
- Add equivalent instructions for configuring DNS conditional forwarders on popular Linux DNS servers, such as BIND (named.conf options) and dnsmasq.
- Include Linux command-line examples (e.g., editing /etc/named.conf or using rndc for BIND) alongside PowerShell examples.
- Explicitly state that the procedure applies to both Windows and Linux DNS servers, and provide links or references to relevant Linux documentation.
- Where possible, use neutral terminology (e.g., 'on-premises DNS server') and avoid assuming the use of Windows Server.
- Present Windows and Linux examples in parallel or alternate the order to avoid 'windows_first' bias.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All command-line automation and scripting examples are provided exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. The only non-portal automation path is via PowerShell, and all command-line DNS query examples use Windows paths (e.g., C:\>) and Windows-native tools (Resolve-DnsName). There are no Linux shell or Azure CLI examples for creating or managing DNS security policies, nor are there instructions for running equivalent DNS queries from Linux environments.
Recommendations
- Add Azure CLI examples for all resource creation, configuration, and management steps, alongside or in place of PowerShell.
- Provide Bash shell command examples for DNS queries (e.g., using dig or host) from a Linux VM, including sample output.
- When showing command-line DNS queries, use generic prompts (e.g., $ or #) or show both Windows (C:\>) and Linux ($) examples.
- Document how to install and use the Azure CLI on Linux for DNS resolver and policy management.
- Explicitly mention Linux support and provide parity in instructions, screenshots, and troubleshooting steps.
- If certain features are only available via PowerShell, clearly state this and provide a roadmap or alternatives for Linux users.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows DNS and its default zone file location before mentioning BIND (the most common Linux DNS server), and by providing explicit Windows file paths (e.g., %systemroot%\system32\dns) without equivalent Linux examples. There are no Linux command-line or file path examples, and the process for obtaining zone files from Linux/BIND is less detailed than for Windows. No Linux-specific tools or workflows are mentioned, and screenshots and instructions are entirely platform-agnostic or Windows-oriented.
Recommendations
- Provide explicit Linux/BIND examples for obtaining zone files, including common file paths (e.g., /etc/bind/).
- Include sample commands for exporting zone files from BIND (e.g., using 'cp', 'cat', or 'named-checkzone').
- Mention Linux tools and workflows alongside Windows ones, not after.
- Ensure parity in detail between Windows and Linux/BIND instructions.
- Consider adding a table or section comparing default zone file locations and export methods for both Windows DNS and BIND/Linux.
- Where Windows paths are given, provide Linux equivalents in parallel.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references Azure PowerShell as a primary interface for managing DNS records (e.g., for TXT records and Etag handling), without mentioning or providing parity for Linux-native tools or CLI usage. There are no explicit Linux or cross-platform command-line examples, and the only tooling called out by name is PowerShell, which is most closely associated with Windows environments.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- When referencing management interfaces, mention both PowerShell and CLI equally, and provide links or examples for both.
- Avoid implying PowerShell is the default or only scripting interface; clarify that both PowerShell and CLI are supported.
- If discussing tooling-specific behaviors (such as Etag handling), describe how these work in both PowerShell and CLI contexts.
- Add explicit Linux/Bash shell examples where relevant, especially for common DNS management tasks.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. While the Azure CLI is correctly described as cross-platform and most command-line examples are OS-agnostic, the documentation repeatedly references Windows-specific tools, paths, and usage patterns before or instead of Linux equivalents. For example, the location of DNS zone files is given for Windows DNS with explicit paths and UI instructions, while the BIND/Linux equivalent is mentioned only briefly. The only explicit example for verifying DNS records uses the Windows Command Prompt and nslookup, with no mention of Linux/macOS alternatives (e.g., dig or nslookup on Unix shells). There are no shell-specific examples for Linux/macOS users.
Recommendations
- When mentioning the location of DNS zone files, provide equal detail for both Windows DNS and BIND/Linux (e.g., typical BIND zone file locations such as /etc/bind/).
- When giving verification steps, include both Windows (cmd) and Linux/macOS (bash) examples, e.g., show how to use nslookup and dig from a Unix shell.
- Avoid phrases like 'Use Windows Command Prompt...' unless also providing the equivalent for other platforms.
- Where file paths are referenced, show both Windows and Unix-style path examples.
- Consider adding a short section or callout noting that all Azure CLI commands work identically on Windows, Linux, and macOS, and provide shell-appropriate syntax where relevant.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-get-started-template.md
...ocs/blob/main/articles/dns/dns-get-started-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line deployment instructions are provided exclusively using Azure PowerShell, with no Azure CLI (bash) or Linux shell examples. The validation step uses Windows command prompt syntax (cmd) for nslookup, and there are no Linux or macOS equivalents. The instructions and screenshots reference Windows tools and workflows first or exclusively, making it less accessible for Linux or cross-platform users.
Recommendations
- Add Azure CLI (az) examples alongside or before the Azure PowerShell examples for deploying ARM templates.
- Provide Linux/macOS shell equivalents for validation steps (e.g., using nslookup or dig in bash/zsh).
- Include screenshots or terminal output from Linux/macOS environments where appropriate.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
- Avoid using only Windows command prompt syntax; show cross-platform alternatives.
- Ensure all steps and code blocks have parity between Windows and Linux/macOS environments.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-private-resolver-overview.md
...lob/main/articles/dns/dns-private-resolver-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell and the Azure portal for quickstarts and next steps, without mentioning or linking to Linux-native tools or CLI examples (such as Azure CLI or Bash). There are no Linux-specific instructions or examples, and PowerShell is presented as the primary automation/scripting interface, which may disadvantage Linux users.
Recommendations
- Add equivalent quickstart and how-to links for Azure CLI (az) and Bash scripting, ensuring Linux users have first-class guidance.
- In the 'Next steps' and 'For more information' sections, list Azure CLI and Linux/Bash options alongside or before PowerShell to provide parity.
- Include explicit examples or references for configuring on-premises DNS forwarders using Linux-based DNS servers (e.g., BIND, dnsmasq), not just generic 'conditional forwarder' instructions.
- Review and update all automation and scripting recommendations to include cross-platform options, not just PowerShell.
- Where possible, use neutral language (e.g., 'using Azure CLI or PowerShell') instead of defaulting to Windows-centric tools.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-protect-private-zones-recordsets.md
...n/articles/dns/dns-protect-private-zones-recordsets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples, and in some cases (such as record set level resource locks), only PowerShell commands are provided, with explicit notes that the functionality is not available in the Azure CLI or portal. There are no references to Linux-specific tools, shell environments, or considerations, and the use of PowerShell as the primary scripting example may implicitly favor Windows users. No Linux shell or cross-platform scripting guidance is provided.
Recommendations
- Wherever possible, provide Azure CLI examples first or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI and Azure PowerShell are both cross-platform, and clarify any platform-specific limitations.
- For scenarios where only PowerShell is supported, offer guidance for Linux users on how to install and use Azure PowerShell on Linux, or provide alternative approaches if available.
- Include examples using Bash or other common Linux shells when demonstrating CLI usage, especially for scripting or automation.
- Add a section or note addressing Linux/macOS users, highlighting any differences or additional steps required.
- Where features are not available in the CLI or portal, consider linking to feedback channels or roadmaps for feature parity.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-protect-zones-recordsets.md
...blob/main/articles/dns/dns-protect-zones-recordsets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for most operations, which supports cross-platform usage. However, there is a notable bias in the 'Protecting individual records' section, where record set level resource locks can only be configured using Azure PowerShell, with no Azure CLI or Linux-native alternative. This effectively prioritizes Windows tooling and excludes Linux-only users from performing this operation. Additionally, the documentation does not mention or provide any Linux-native shell scripting or automation examples outside of Azure CLI, and does not clarify platform requirements for PowerShell usage.
Recommendations
- Work with the Azure product team to enable record set level resource lock management via Azure CLI, ensuring Linux parity.
- Where PowerShell is required, clarify that Azure PowerShell is cross-platform and provide installation/use instructions for Linux users.
- Explicitly state platform requirements or limitations for each tool (Azure PowerShell, Azure CLI, Portal) at the start of the documentation.
- Where possible, provide bash/shell scripting examples for Linux users, especially for automation scenarios.
- Add a note or workaround for Linux users when a feature is only available via Azure PowerShell, such as using Azure Cloud Shell (which supports PowerShell on Linux) or requesting the feature in Azure CLI.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-reverse-dns-for-azure-services.md
...ain/articles/dns/dns-reverse-dns-for-azure-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell (and classic PowerShell) examples before CLI equivalents, providing only PowerShell-based instructions for Cloud Services, and omitting Linux/Unix-native command examples (such as Bash, dig, or nslookup). The use of PowerShell-specific cmdlets and the absence of Linux shell or cross-platform DNS validation tools further reinforce this bias.
Recommendations
- Provide Linux-native command examples (e.g., Bash, dig, nslookup) for verifying reverse DNS records alongside PowerShell examples.
- Include instructions and examples for configuring reverse DNS using cross-platform tools and scripts, not just PowerShell.
- When listing command-line examples, present Azure CLI (which is cross-platform) before or alongside PowerShell, rather than always leading with PowerShell.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample shell environments where appropriate.
- For Cloud Services, clarify if there are any cross-platform or REST API alternatives to PowerShell, and provide those if available.
- Add a section or callout for Linux users, summarizing the parity and any limitations or differences in the process.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by only mentioning Azure PowerShell as a configuration method and omitting any references to cross-platform or Linux-native tools (such as Azure CLI, Bash, or REST API). No Linux or cross-platform command-line examples are provided, and the only automation tool referenced is PowerShell, which is most commonly associated with Windows environments.
Recommendations
- Include Azure CLI examples alongside PowerShell for all configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that DNS security policy can be configured using Azure CLI, REST API, or ARM templates, and provide links or examples for each.
- Avoid referencing only Windows-centric tools (like PowerShell) as the primary or sole automation method.
- Where screenshots or UI steps are shown, clarify that the Azure portal is platform-agnostic.
- Add a section or note highlighting cross-platform support and parity for Linux users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently using Windows command prompt syntax (e.g., 'C:\>') for DNS query examples, referencing 'command prompt' and 'cmd', and showing nslookup and dig commands prefixed with Windows-style prompts. There are no explicit Linux or macOS shell examples, nor is there mention of running these commands from a Bash shell or Linux VM. The instructions for running DNS queries assume a Windows environment, and there is no guidance for Linux users, despite the cross-platform nature of Azure VMs.
Recommendations
- Provide parallel Linux/macOS shell examples for DNS queries (e.g., show '$ dig ...' and '$ nslookup ...' in Bash).
- Explicitly mention that the DNS query steps can be performed from either Windows or Linux VMs, and clarify any OS-specific differences.
- Include screenshots or terminal output from Linux environments where appropriate.
- Avoid using only Windows command prompt syntax (e.g., 'C:\>')—use a neutral prompt ('$') or show both.
- In the prerequisites, clarify that the virtual machine used for DNS queries can be Windows or Linux, and provide instructions for both.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the example VM OS, referencing RDP and PowerShell for management and testing, and omitting any Linux-based examples or instructions. All command-line and remote management examples use Windows tools (PowerShell, RDP), and there is no mention of Linux VMs, SSH, or Bash/CLI alternatives. This may make the documentation less accessible or relevant for users who primarily work with Linux environments.
Recommendations
- Include parallel instructions and screenshots for creating a Linux virtual machine (e.g., Ubuntu) alongside the Windows VM example.
- Provide examples for connecting to the VM using SSH (for Linux) in addition to RDP (for Windows).
- Show how to test DNS resolution from a Linux VM using Bash commands (e.g., ping, dig, nslookup) as well as from Windows/PowerShell.
- Mention both PowerShell and Bash/CLI options for running remote commands, or reference the Azure CLI/Cloud Shell where appropriate.
- Balance the order of presentation so that Linux and Windows options are given equal prominence, or clearly indicate that both are supported.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-sdk.md
...osoftDocs/azure-docs/blob/main/articles/dns/dns-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows, such as Visual Studio and NuGet Package Manager, without mentioning or providing alternatives for Linux users. The instructions for creating a service principal link to a PowerShell-based guide, and there are no examples or guidance for performing these steps using Linux-friendly tools (e.g., .NET CLI, VS Code, or Azure CLI). There is also no mention of cross-platform development environments or package management approaches outside of Visual Studio.
Recommendations
- Include instructions for installing required NuGet packages using the .NET CLI (e.g., 'dotnet add package') for Linux and macOS users.
- Reference cross-platform editors such as Visual Studio Code, and provide guidance for users not on Windows.
- Provide links and examples for creating service principals and resource groups using the Azure CLI, which is available on all platforms.
- Avoid assuming the use of Visual Studio or Windows-specific tools; offer alternative steps for common Linux development environments.
- Explicitly state that the .NET SDK and Azure DNS Management libraries are cross-platform, and clarify any platform-specific requirements if they exist.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all DNS record creation and management examples, and demonstrates DNS record validation using nslookup in a Windows PowerShell context. There are no CLI, Bash, or Linux-native examples provided, nor are cross-platform tools or commands mentioned. The workflow assumes a Windows environment and does not address Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI (az) commands for all DNS record operations alongside PowerShell examples.
- Include Linux/macOS-friendly instructions for DNS validation, such as using dig or host commands, in addition to nslookup.
- Explicitly mention that the steps can be performed on any OS, and clarify which tools are cross-platform.
- Consider reordering or parallelizing examples so that Linux/macOS and Windows users see relevant instructions at the same level of prominence.
- Add a section or callout for using Azure Cloud Shell, which supports both Bash and PowerShell, to emphasize cross-platform accessibility.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary tool for managing Azure DNS (e.g., Etags section), without mentioning or providing parity for Linux-native tools or CLI usage. There are no examples or guidance for Linux users, and the only command-line tool referenced is PowerShell, which is most commonly associated with Windows environments.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, if PowerShell examples are retained, and provide installation guidance for non-Windows users.
- Include bash or shell script examples where relevant, especially for common DNS management tasks.
- Ensure that all tool references (e.g., for Etags or record management) include both PowerShell and Azure CLI approaches, with equal prominence.
- Add a section or callout for Linux/macOS users, highlighting any differences or special considerations.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All automation and scripting examples are provided exclusively in PowerShell, with no equivalent Azure CLI, Bash, or Linux-native instructions. The PowerShell tab is the only programmatic method shown, and all command-line examples (including DNS query tests) use Windows paths and tools. There are no Linux-specific instructions, nor are Linux tools or workflows mentioned. The documentation assumes a Windows environment for scripting and management, leaving Linux users without clear guidance.
Recommendations
- Add Azure CLI and/or Bash examples for all resource creation, configuration, and management steps, ensuring parity with PowerShell instructions.
- Include Linux-native command-line examples (e.g., using dig or nslookup from a Bash shell) for DNS query and testing sections.
- When referencing file paths or environment variables, provide both Windows and Linux equivalents (e.g., C:\bin\PSRepo vs. ~/bin/PSRepo).
- Explicitly mention that the instructions apply to both Windows and Linux environments, and provide guidance for each where workflows differ.
- Consider adding a 'Linux' or 'Azure CLI' tab alongside the existing 'PowerShell' and 'Portal' tabs for all relevant sections.
- Reference cross-platform tools and patterns (such as Azure Cloud Shell, which supports both Bash and PowerShell) earlier and more prominently.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is given a dedicated section, and the Azure CLI examples use 'dig.exe' (the Windows version of dig) rather than simply 'dig', which is more common on Linux/macOS. There are no explicit Linux or macOS command-line examples, nor is there mention of Linux-native tools or shell environments. The documentation assumes a Windows environment for command-line operations and does not provide parity for Linux users.
Recommendations
- Add explicit Linux/macOS examples for command-line operations, including Azure CLI usage in bash/zsh.
- Replace 'dig.exe' with 'dig', and clarify that 'dig' is available on Linux/macOS by default, while Windows users may need to install it.
- Provide sample commands for installing required tools (e.g., dig) on Linux distributions.
- Include screenshots or instructions for Linux/macOS terminal environments where relevant.
- Ensure that all PowerShell examples have equivalent bash (or generic shell) examples for cross-platform parity.
- Review terminology and tool references to avoid Windows-specific language unless necessary.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md
...ocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides detailed instructions for the Azure Portal, Azure CLI, and PowerShell. While the Azure CLI is cross-platform, the explicit inclusion of PowerShell (which is traditionally associated with Windows environments) and the use of PowerShell-specific cmdlets indicate a bias towards Windows users. Additionally, the PowerShell section is given equal prominence to the CLI, and there are no explicit Linux shell (bash) examples or references to Linux-native tools or workflows. The CLI examples use the Azure CLI, which is available on Linux, but there is no mention of running these commands in a Linux environment or using bash scripting, and the CLI section is labeled with 'azurepowershell-interactive', which may be confusing.
Recommendations
- Add explicit bash shell examples for the Azure CLI section, showing usage in a Linux/macOS terminal.
- Clarify that the Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for bash).
- If PowerShell is included, also include bash equivalents for parity.
- Avoid labeling CLI code blocks as 'azurepowershell-interactive' when they are standard Azure CLI commands.
- Mention that PowerShell Core is cross-platform if you intend to support Linux, or clarify that the PowerShell examples are for Windows users.
- Consider the order of sections: present the Azure CLI (cross-platform) before PowerShell to avoid a 'windows_first' impression.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias primarily in its examples and tool recommendations. PowerShell (Resolve-DnsName) is presented first and in more detail than Linux/Unix equivalents. Windows-specific tools and concepts (such as Group Policy, NRPT, and explicit references to Windows 10/11 clients) are mentioned without Linux parallels. The dig command is shown, but only as a secondary example, and there is no mention of Linux-native environments or tools like host or unbound. There are no Linux shell prompt examples, and the guidance assumes a Windows-centric audience.
Recommendations
- Provide Linux/Unix shell examples (e.g., bash prompt, dig, host) alongside or before Windows/PowerShell examples.
- Mention Linux/Unix DNSSEC validation tools (e.g., unbound, bind, dnssec-trigger) and how to configure them.
- Balance references to Windows-specific features (like Group Policy and NRPT) with Linux equivalents (such as systemd-resolved, resolvconf, or dnssec-trigger).
- Clarify that dig is a cross-platform tool and provide installation instructions for both Windows and Linux.
- Include guidance or links for DNSSEC validation and troubleshooting on Linux systems.
- Use neutral language when describing client operating systems (e.g., 'Windows, Linux, and macOS clients...') where appropriate.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a strong Windows bias in the testing and validation sections. All VM creation examples use Windows images, and all instructions for configuring and testing DNS resolution are written exclusively for Windows (PowerShell commands, Windows firewall, and output). There are no Linux VM creation examples, nor are there any Linux shell or firewall commands provided. The documentation assumes the user is operating in a Windows environment for all post-deployment steps.
Recommendations
- Provide parallel Linux examples for VM creation (e.g., using --image UbuntuLTS) and show both Windows and Linux VM creation commands.
- Include instructions for configuring the firewall to allow ICMP on Linux VMs (e.g., using ufw or firewalld).
- Show how to test DNS resolution from a Linux shell (e.g., using ping, dig, or nslookup in bash).
- Present both Windows and Linux command outputs for DNS resolution tests.
- Explicitly mention that the steps apply to both Windows and Linux, and clarify any OS-specific differences.
- Consider alternating the order of Windows and Linux examples, or presenting them side-by-side to avoid 'windows_first' bias.