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 276-300 of 323 flagged pages
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/delegate-subdomain.md ...zure-docs/blob/main/articles/dns/delegate-subdomain.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing command-line testing instructions only for Windows (using 'command prompt' and 'nslookup'), without mentioning or illustrating equivalent steps for Linux or macOS users. There are no Linux shell or cross-platform examples, and the only non-portal automation reference is to Azure PowerShell, with no mention of Azure CLI or other cross-platform tools.
Recommendations
  • Include Linux/macOS instructions for testing DNS delegation, such as using 'dig' or 'nslookup' from a Unix shell.
  • When referencing command-line tools, specify both Windows (Command Prompt/PowerShell) and Linux/macOS equivalents.
  • Mention and provide examples using Azure CLI for subdomain delegation, as it is cross-platform.
  • Avoid phrases like 'Open a command prompt' without also mentioning 'Open a terminal' for Linux/macOS users.
  • Add screenshots or code snippets that reflect both Windows and Linux environments where applicable.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-alias-appservice.md ...re-docs/blob/main/articles/dns/dns-alias-appservice.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively using Windows as the operating system in all examples for App Service plans and web apps. There are no examples or guidance for Linux-based App Service plans or web apps, nor is there any mention of Linux runtimes or deployment patterns. This may lead Linux users to believe that the process is Windows-specific or that Linux is not supported.
Recommendations
  • Provide parallel examples using Linux as the operating system in the App Service plan and web app creation steps.
  • Include at least one Linux runtime (such as Node.js, Python, or .NET Core on Linux) in the web app configuration tables.
  • Add a note clarifying that both Windows and Linux App Service plans are supported, and link to relevant documentation for Linux deployments.
  • Ensure that instructions and screenshots (if any) are not Windows-specific and are applicable to both platforms.
  • Explicitly mention any differences or considerations when using Linux-based App Service plans with Traffic Manager and Azure DNS.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-custom-domain.md ...azure-docs/blob/main/articles/dns/dns-custom-domain.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses the nslookup tool for DNS validation, with screenshots and references that appear to be from Windows Command Prompt. There are no examples or screenshots for Linux or macOS users, nor are alternative tools (like dig) mentioned. This presents a subtle Windows-first and Windows-only bias, as it assumes the reader is using a Windows environment for DNS troubleshooting.
Recommendations
  • Include Linux/macOS equivalents for DNS validation, such as using the dig command (e.g., dig <domain>) alongside nslookup.
  • Provide screenshots or terminal output examples from Linux/macOS environments in addition to Windows Command Prompt.
  • Explicitly mention that nslookup is available on multiple platforms, but also suggest dig as a common alternative on Unix-like systems.
  • Wherever command-line validation is shown, provide both Windows and Linux/macOS command syntax and expected output.
  • Consider a short section or callout box summarizing DNS troubleshooting commands for different operating systems.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-private-resolver-get-started-template.md ...icles/dns/dns-private-resolver-get-started-template.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but the PowerShell example is given equal prominence as the CLI, and no explicit Linux/bash-specific instructions or examples are provided. The CLI example is cross-platform, but the inclusion of PowerShell (which is traditionally associated with Windows) without a corresponding bash or Linux shell example may suggest a slight Windows bias. There are no references to Windows-only tools, but the documentation does not explicitly address Linux users or provide Linux-specific guidance.
Recommendations
  • Clarify that the Azure CLI example works on Linux, macOS, and Windows, and consider labeling it as 'Bash/CLI' or 'Linux/macOS/Windows CLI' to highlight cross-platform compatibility.
  • If possible, provide a bash-specific example or note that the CLI commands can be run in a Linux shell.
  • Consider adding a note for Linux users about installing and using the Azure CLI, or linking to relevant documentation.
  • If PowerShell is included, consider also including bash or shell script examples to ensure parity for Linux users.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-private-zone-terraform.md ...s/blob/main/articles/dns/dns-private-zone-terraform.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on creating and managing Windows virtual machines, with no mention of Linux VM options or examples. All VM-related steps and outputs are Windows-specific, and there is no guidance for users who may want to deploy Linux VMs. While both Azure CLI and PowerShell are provided for verification, the overall workflow and resource creation are Windows-centric.
Recommendations
  • Include parallel instructions and Terraform code samples for deploying Linux virtual machines alongside Windows VMs.
  • Update the checklist and summary to mention both Windows and Linux VM creation, or provide an explicit choice.
  • Add example outputs and troubleshooting notes relevant to Linux VMs.
  • Ensure that any referenced scripts, variables, or admin credential outputs are equally applicable to Linux (e.g., SSH keys instead of only passwords).
  • Consider providing a toggle or tabs for Windows and Linux VM scenarios throughout the guide.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-private-resolver-get-started-terraform.md ...cles/dns/dns-private-resolver-get-started-terraform.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell section is included immediately after the CLI section, and both use Windows-centric scripting syntax. There are no explicit Linux shell (bash) examples, and the PowerShell tab is presented as an alternative rather than providing parity with Linux-native tools or workflows. The use of PowerShell and CLI together may implicitly favor Windows users, as PowerShell is primarily a Windows tool, though now cross-platform.
Recommendations
  • Add explicit Bash/Linux shell examples for all verification steps, especially for users running Terraform and Azure CLI on Linux or macOS.
  • Clarify that Azure CLI commands can be run on any platform, and provide example shell commands for Linux/macOS (e.g., using export instead of $var=).
  • If PowerShell is included, ensure that Bash examples are given equal prominence and are presented before or alongside PowerShell examples.
  • Mention that PowerShell Core is cross-platform, but provide clear guidance for Linux/macOS users who may not use PowerShell.
  • Consider adding a table or tabbed interface that includes Bash, PowerShell, and Azure CLI examples for each step.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-reverse-dns-hosting.md ...docs/blob/main/articles/dns/dns-reverse-dns-hosting.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples, and all PowerShell code is shown using Windows PowerShell syntax. There are no explicit Linux shell or Bash examples, and the PowerShell approach is highlighted as a primary method throughout. This ordering and emphasis may give the impression that Windows or PowerShell is the preferred or default environment for managing Azure DNS, which can be unwelcoming or confusing for Linux users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell context where appropriate.
  • Add example command lines using Bash or other common Linux shells, especially for tasks like scripting or automation.
  • Clarify that PowerShell is available cross-platform, but provide guidance for Linux users who may not have PowerShell installed by default.
  • Review screenshots and UI instructions to ensure they are not Windows-specific where possible.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-autoregistration.md ...blob/main/articles/dns/private-dns-autoregistration.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which subtly prioritizes Windows-centric tooling. There are no Linux-specific examples or explicit mention of Linux tools, and the only command-line examples referenced are PowerShell and CLI, with PowerShell listed first.
Recommendations
  • Present Azure CLI before Azure PowerShell in example links and instructions, as CLI is cross-platform and more familiar to Linux users.
  • Include explicit Linux usage examples or screenshots where relevant, such as showing CLI commands being run in a Bash shell.
  • Mention that both Azure CLI and PowerShell are available on multiple platforms, and provide parity in documentation for both.
  • If possible, add a section or note for Linux administrators, highlighting any differences or tips for using the autoregistration feature from Linux environments.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-overview.md ...re-docs/blob/main/articles/dns/private-dns-overview.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing PowerShell as a primary tool. While the main content is platform-neutral and does mention Azure CLI, there are no Linux- or Bash-specific examples or explicit parity in tool recommendations. The documentation avoids exclusive mention of Windows tools, but the ordering and emphasis subtly prioritize Windows/PowerShell users.
Recommendations
  • Ensure that Azure CLI (which is cross-platform) is mentioned before or alongside Azure PowerShell in all tool lists and 'Next steps' sections.
  • Explicitly state that Azure CLI commands can be run on Linux, macOS, and Windows to reinforce cross-platform support.
  • Where possible, provide example commands for both Azure PowerShell and Azure CLI (or Bash scripts) to demonstrate parity.
  • Include references or links to Linux-specific guidance or troubleshooting if relevant.
  • Review all documentation for consistent ordering and equal emphasis of cross-platform tools.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-virtual-network-links.md ...main/articles/dns/private-dns-virtual-network-links.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references Azure PowerShell before Azure CLI in the 'Next steps' section, which may suggest a Windows-first or PowerShell-heavy approach. While both PowerShell and CLI are mentioned, the ordering may subtly prioritize Windows tooling. There are no explicit Linux or cross-platform examples, and no mention of Linux-specific tools or workflows.
Recommendations
  • Present Azure CLI before or alongside Azure PowerShell in all lists and examples, as CLI is cross-platform and more familiar to Linux users.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to reinforce cross-platform parity.
  • Add Linux-specific or cross-platform command examples where appropriate, or clarify that the instructions apply equally to Linux environments.
  • Avoid ordering that consistently places Windows/PowerShell tools before Linux/CLI equivalents.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-resolver-endpoints-rulesets.md ...in/articles/dns/private-resolver-endpoints-rulesets.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page does not provide any OS-specific command-line examples, but in the 'Next steps' section, it only references Azure PowerShell and the Azure portal for creating a DNS Private Resolver. There is no mention of Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there any Linux-specific tools or workflows discussed. This subtly prioritizes Windows-centric tools and patterns, and omits Linux parity in guidance.
Recommendations
  • Add Azure CLI instructions and links alongside Azure PowerShell and portal guidance, as Azure CLI is cross-platform and widely used on Linux.
  • Wherever command-line examples are referenced, ensure both PowerShell and CLI (bash) examples are provided, or at least link to both.
  • Explicitly mention that the Azure DNS Private Resolver can be managed from Linux, macOS, and Windows environments, and provide links to relevant documentation for each.
  • If referencing scripts or automation, include bash/shell script examples in addition to PowerShell.
  • Review screenshots and UI guidance to ensure they are not Windows-specific, or provide equivalent Linux/macOS context where relevant.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-alias-pip.md ...zure-docs/blob/main/articles/dns/tutorial-alias-pip.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server for the virtual machine example, including instructions for installing IIS via the Windows GUI and connecting via RDP. There are no examples or instructions for creating or configuring a Linux-based VM, nor for installing a web server (such as Apache or Nginx) on Linux. All screenshots and step-by-step instructions assume a Windows environment, and no Linux alternatives are mentioned.
Recommendations
  • Add parallel instructions for creating a Linux virtual machine (e.g., Ubuntu or CentOS) in Azure.
  • Provide steps for installing a web server (such as Apache or Nginx) on the Linux VM, including relevant command-line examples.
  • Include screenshots or terminal output relevant to Linux environments.
  • Mention both RDP (for Windows) and SSH (for Linux) as connection methods, with instructions for each.
  • Where possible, use neutral language (e.g., 'web server VM') and clarify that either Windows or Linux can be used.
  • Consider providing a table or toggle for users to select their preferred OS (Windows or Linux) for the tutorial steps.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-alias-rr.md ...azure-docs/blob/main/articles/dns/tutorial-alias-rr.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by only providing instructions and examples using the Azure Portal (a web UI) and the nslookup command from a generic 'command prompt' without specifying or illustrating Linux or cross-platform alternatives. The testing step assumes the use of nslookup from a Windows command prompt, with no mention of Linux shells, tools like dig, or cross-platform command syntax. There are no CLI (az cli, PowerShell, or bash) examples, and no explicit Linux guidance is provided.
Recommendations
  • Include explicit instructions for verifying DNS records from Linux/macOS terminals, such as using dig (e.g., `dig test.contoso.com`) in addition to nslookup.
  • Clarify that nslookup is available on both Windows and Linux, or provide installation instructions for Linux users if needed.
  • Where 'command prompt' is mentioned, specify that these steps can be performed from Windows Command Prompt, PowerShell, or Linux/macOS terminal.
  • Consider adding Azure CLI (az cli) examples for creating and managing DNS records, which are cross-platform.
  • Add a note or section for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Bicep ...e-docs/blob/main/articles/dns/dns-get-started-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all commands, but PowerShell is given equal prominence and is shown immediately alongside CLI, rather than being clearly secondary. There is no explicit mention of Linux/macOS environments, nor any guidance for users who may not have PowerShell available. The CLI examples are cross-platform, but the inclusion and prominence of PowerShell may suggest a slight Windows bias.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add a note indicating that PowerShell examples are primarily for Windows users, and may require installation on other platforms.
  • Consider listing CLI examples first, as they are more universally applicable.
  • Explicitly mention Linux/macOS compatibility in the prerequisites or introduction.
  • If relevant, provide shell script examples for bash/zsh users.
GitHub Create Pull Request
DNS What is a virtual network link subresource of Azure DNS private zones ...main/articles/dns/private-dns-virtual-network-links.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation lists Azure PowerShell (commonly associated with Windows) before Azure CLI (cross-platform) in the 'Next steps' section, which subtly prioritizes Windows tooling. However, both Windows and Linux-compatible tools are mentioned, and no examples or instructions are given that are exclusive to Windows.
Recommendations
  • List Azure CLI before Azure PowerShell to reflect cross-platform parity.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
  • Where possible, provide parallel examples for both CLI and PowerShell in future documentation updates.
GitHub Create Pull Request
DNS Import and export a domain zone file for Azure private DNS - Azure CLI ...cs/blob/main/articles/dns/private-dns-import-export.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Windows DNS and its default zone file location before mentioning BIND (Linux), and provides specific instructions for Windows DNS tools and paths. However, the core Azure CLI commands are cross-platform and examples are not Windows-specific. No PowerShell examples or Windows-only command syntax is present.
Recommendations
  • Present Linux/BIND zone file location before or alongside Windows DNS location to avoid Windows-first ordering.
  • Provide explicit examples or notes for obtaining zone files from BIND/Linux systems, such as common file paths and commands.
  • Clarify that Azure CLI commands are identical across platforms, and mention any platform-specific considerations (e.g., file path formats).
  • Add a brief example of using Linux commands (e.g., `cat`, `cp`) to locate or copy zone files, for parity.
GitHub Create Pull Request
DNS Import and export a private DNS zone file - Azure portal .../main/articles/dns/private-dns-import-export-portal.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation mentions Windows DNS as a source for zone files before mentioning BIND (the most common DNS server on Linux/Unix). It provides the Windows DNS folder path and GUI instructions, while the BIND section is brief and lacks detail. There are no Linux-specific examples or screenshots, and the only file path shown is for Windows. The overall workflow is platform-neutral (using the Azure portal), but Windows is prioritized in explanatory sections.
Recommendations
  • Provide equal detail for BIND/Linux: Include example BIND zone file locations (e.g., /etc/bind/zones/) and instructions for exporting zone files from BIND.
  • Add Linux/macOS file path examples and screenshots where relevant.
  • Mention Linux tools (e.g., dig, named-checkzone) for verifying or exporting zone files.
  • Present Windows and Linux/Unix instructions in parallel, or mention Linux first in sections where both are relevant.
  • Clarify that the Azure portal workflow is OS-agnostic, and users can upload zone files from any platform.
GitHub Create Pull Request
DNS Integrate Azure DNS with your Azure resources - Azure DNS ...azure-docs/blob/main/articles/dns/dns-custom-domain.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by showing DNS validation steps using 'nslookup' screenshots from Windows Command Prompt, with no mention of Linux/macOS equivalents or CLI syntax. All validation examples are visually Windows-centric, and there are no explicit instructions or screenshots for Linux or macOS users.
Recommendations
  • Include Linux/macOS command-line examples for DNS validation, such as showing 'nslookup', 'dig', or 'host' usage on those platforms.
  • Add screenshots or terminal output from Linux/macOS environments alongside Windows examples.
  • Explicitly state that DNS validation steps can be performed on any OS and provide the relevant commands for each.
  • Avoid showing only Windows Command Prompt in screenshots; consider using generic terminal windows or multiple OS examples.
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure portal ...ocs/blob/main/articles/dns/dns-import-export-portal.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation mentions Windows DNS and its default zone file location before mentioning BIND (the most common DNS server on Linux/Unix). The Windows DNS file path is given explicitly, while the BIND section is less detailed. No Linux/macOS-specific examples or screenshots are provided, and the only file path example is Windows-specific. However, the core import/export workflow is platform-neutral, focusing on the Azure portal UI.
Recommendations
  • List BIND (Linux/Unix) before or alongside Windows DNS when describing how to obtain zone files.
  • Provide explicit example file paths for BIND (e.g., /etc/bind/zones/) and mention common Linux/Unix DNS server locations.
  • Include a brief note or screenshot showing how to locate zone files on Linux/BIND systems.
  • Add a section or link for Linux/macOS users on exporting zone files from BIND or other common DNS servers.
  • Ensure parity in detail and clarity between Windows and Linux instructions.
GitHub Create Pull Request
DNS Private DNS records overview - Azure Private DNS ...ure-docs/blob/main/articles/dns/dns-private-records.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias, primarily through references to PowerShell and the Azure portal as primary interfaces for managing DNS records. The section on TXT records explicitly mentions PowerShell before CLI, and the Etags section describes PowerShell behavior in detail while only briefly mentioning REST API and HTTP headers. There are no Linux/macOS-specific examples or explicit parity guidance for non-Windows users.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell, especially for common tasks like managing TXT records and Etags.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users, and link to relevant CLI documentation.
  • Reorder examples so that CLI and REST API usage are described before or alongside PowerShell and portal instructions.
  • Add notes or sections highlighting Linux/macOS workflows, including any differences or caveats.
  • Avoid language that implies PowerShell is the default or preferred tool unless truly necessary.
GitHub Create Pull Request
DNS Import and export a domain zone file - Azure CLI ...azure-docs/blob/main/articles/dns/dns-import-export.md
Low Priority View Details →
Scanned: 2026-01-14 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 mild Windows bias. Windows DNS is mentioned before BIND when discussing zone file locations, and the example for verifying DNS records uses Windows Command Prompt syntax for nslookup, without showing Linux/macOS alternatives. There is no explicit Linux/macOS example for obtaining zone files or verifying DNS records, and Windows-specific paths and terminology are used first.
Recommendations
  • Present BIND/Linux zone file locations before or alongside Windows DNS locations.
  • Include Linux/macOS command-line examples (e.g., nslookup or dig usage) for verifying DNS records.
  • Show file path examples using Linux/macOS conventions (e.g., /etc/bind/ for BIND zone files).
  • Clarify that Azure CLI commands work identically on all platforms, and provide sample commands in both Windows and Linux/macOS shells where relevant.
GitHub Create Pull Request
DNS Azure DNS Private Resolver Overview ...lob/main/articles/dns/dns-private-resolver-overview.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by listing Azure PowerShell (a Windows-centric tool) as the first and only command-line example for creating a DNS Private Resolver. There are no explicit Linux/macOS CLI examples (such as Azure CLI or Bash), and PowerShell is referenced before any cross-platform alternatives. However, the page does mention the Azure portal, which is platform-agnostic.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all setup and management tasks.
  • Explicitly mention that Azure CLI is available on Linux/macOS and provide links to relevant CLI documentation.
  • Ensure that any command-line instructions are presented in both PowerShell and Bash/CLI formats, with equal prominence.
  • Consider listing cross-platform tools (Azure CLI, Terraform) before Windows-specific tools in 'Next steps' and quickstart sections.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver using Terraform ...cles/dns/dns-private-resolver-get-started-terraform.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell examples are given equal prominence and detail. PowerShell is a Windows-centric tool, and its inclusion alongside CLI may suggest a slight Windows bias, especially since no Linux/macOS-specific shell examples (e.g., Bash, zsh) or instructions are provided. However, the Azure CLI examples are cross-platform and shown first, mitigating the severity of the bias.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add example shell commands for Linux/macOS users (e.g., Bash/zsh), especially for variable assignment and command usage.
  • Clarify that PowerShell examples are primarily for Windows users, and recommend Azure CLI for cross-platform scenarios.
  • Consider adding a table or note summarizing which commands/tools are best for each OS.
GitHub Create Pull Request
DNS DNS Zones and Records Overview ...azure-docs/blob/main/articles/dns/dns-zones-records.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page shows mild Windows bias. PowerShell is mentioned explicitly as a primary interface for managing DNS records, and Windows tools (PowerShell) are referenced before alternatives. There are no explicit Linux/macOS CLI examples or mentions of cross-platform tools, and PowerShell is not identified as cross-platform. However, REST API and Azure portal interfaces are referenced, which are platform-neutral.
Recommendations
  • Add explicit Azure CLI examples alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify that PowerShell is available on Linux/macOS, or provide Bash examples where relevant.
  • Ensure that all tool references (PowerShell, CLI, portal, REST API) are presented together or in a neutral order, rather than prioritizing Windows-centric tools.
  • Include links or guidance for Linux/macOS users on installing and using Azure CLI and PowerShell.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. PowerShell examples are provided alongside Azure CLI and portal instructions, but PowerShell (a Windows-centric tool) is featured prominently. The only explicit DNS query example uses Windows' nslookup syntax and prompt, with no mention of Linux/macOS alternatives. The order of examples sometimes places PowerShell before CLI, and the testing section assumes a Windows shell environment.
Recommendations
  • Include Linux/macOS equivalents for DNS queries, such as dig or host, in the 'Test the new records' section.
  • Add notes or examples for running Azure CLI on Linux/macOS, clarifying any differences in usage or prerequisites.
  • When showing command-line examples, alternate the order or present CLI and PowerShell side-by-side to avoid implicit prioritization.
  • Instruct users on how to install and use Azure CLI and PowerShell on non-Windows platforms, or link to relevant cross-platform guides.
  • Use generic prompts (e.g., '$' for shell) or show both Windows and Linux/macOS shell prompts in examples.
GitHub Create Pull Request
← Previous Page 12 of 13 Next →