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 251-275 of 323 flagged pages
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: 2026-01-09 00:34
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 (commonly used on Windows) before Azure CLI (cross-platform) in the 'Next steps' section. No Linux-specific tools or examples are provided, and the screenshot appears to be from the Azure Portal, which is platform-neutral. There are no explicit Windows-only tools or patterns, but the ordering and emphasis on PowerShell may subtly favor Windows users.
Recommendations
  • List Azure CLI before Azure PowerShell in example links and instructions, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that both Azure CLI and PowerShell are available on Linux, macOS, and Windows.
  • Provide example commands for both Azure CLI and PowerShell when demonstrating how to enable autoregistration.
  • Include a note or section on how Linux users can accomplish the same tasks, possibly with screenshots from Linux environments or terminal.
  • Avoid implying that PowerShell is the primary or preferred method unless there is a technical reason.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-import-export.md ...cs/blob/main/articles/dns/private-dns-import-export.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides information for both Windows and Linux users, but there is evidence of Windows bias. In the section 'Obtain your existing DNS zone file', the location for Windows DNS zone files is described first and in more detail, including the default folder and a reference to the DNS console. The Linux/BIND equivalent is mentioned second, with less detail. The only tool mentioned for verifying DNS records is 'nslookup', which is available on both platforms but is more commonly associated with Windows. No Linux-specific tools (e.g., 'dig') are mentioned for verification. There are no PowerShell examples, and the Azure CLI is correctly presented as cross-platform, but the ordering and tool references show a slight Windows preference.
Recommendations
  • Present Linux/BIND information before or alongside Windows DNS details to avoid Windows-first ordering.
  • Include Linux-specific verification tools such as 'dig' in the 'Verify the zone' section, with example commands.
  • Clarify that 'nslookup' is available on both Windows and Linux, and provide examples for both platforms.
  • Expand the BIND section to include more details about typical zone file locations and retrieval steps on Linux.
  • Consider mentioning other cross-platform DNS tools where relevant.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples using 'nslookup' and references a generic 'command prompt' without specifying platform. However, the context and terminology (e.g., 'command prompt', 'nslookup') are more familiar to Windows users, and there are no explicit Linux or macOS instructions or examples (such as using 'dig' or referencing a Linux terminal). The documentation does not mention PowerShell or Windows-specific tools directly, but it implicitly favors Windows by omitting Linux-specific guidance.
Recommendations
  • Include Linux/macOS equivalents for command-line examples, such as using 'dig' or specifying how to run 'nslookup' from a Linux terminal.
  • Clarify that 'nslookup' is available on multiple platforms and provide installation instructions for Linux if needed.
  • Use neutral terminology like 'terminal' instead of 'command prompt', or specify both ('command prompt or terminal').
  • Add screenshots or step-by-step instructions for Linux/macOS environments where applicable.
  • Explicitly mention that the Azure portal steps are platform-agnostic, but command-line verification can be performed on any OS.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server for the virtual machine example and provides instructions only for installing IIS on Windows. There are no Linux VM examples, nor guidance for deploying a Linux-based web server (such as Apache or Nginx). All screenshots and steps are tailored to Windows environments, with no mention of Linux alternatives.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) and installing a web server (Apache or Nginx).
  • Include Linux-specific steps for connecting to the VM (using SSH) and verifying the web server.
  • Provide screenshots and command-line examples for Linux environments.
  • Mention both Windows and Linux options in the prerequisites and throughout the tutorial to ensure cross-platform parity.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-alias-tm.md ...azure-docs/blob/main/articles/dns/tutorial-alias-tm.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server virtual machines and IIS for the web server setup, with no mention or examples of Linux-based alternatives (e.g., Ubuntu, Apache, Nginx). All instructions for VM creation, web server installation, and testing are tailored to Windows, demonstrating a clear Windows-first bias and omitting Linux parity.
Recommendations
  • Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) in Azure.
  • Include steps for installing and configuring a web server on Linux (e.g., Apache or Nginx).
  • Provide Linux-specific commands and screenshots for web server setup and testing.
  • Mention both Windows and Linux options in prerequisites and throughout the tutorial.
  • Ensure that DNS label and Traffic Manager steps are shown with Linux VM examples as well.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-public-dns-zones-child.md ...b/main/articles/dns/tutorial-public-dns-zones-child.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all steps and does not provide any command-line examples. While it avoids explicit Windows tools like PowerShell, the lack of CLI instructions (such as Azure CLI or Bash) means users on Linux or macOS do not see platform-neutral or Linux-friendly workflows. The tutorial implicitly assumes a graphical, Windows-like environment by focusing solely on the portal and omitting Linux command-line alternatives.
Recommendations
  • Add equivalent instructions using Azure CLI commands for creating and managing child DNS zones, including resource creation, delegation, and cleanup.
  • Provide examples of DNS record verification using cross-platform tools (e.g., dig, nslookup) from a Linux shell.
  • Include a section comparing portal-based and CLI-based workflows, highlighting platform neutrality.
  • Ensure screenshots and UI references are supplemented with text-based steps for users who prefer or require command-line access.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page mentions Azure PowerShell before Azure CLI when describing next steps for creating a private DNS zone, which suggests a Windows-first bias. PowerShell is primarily associated with Windows, while Azure CLI is cross-platform. No Linux-specific tools or examples are provided, and there is no mention of Linux shell usage or parity.
Recommendations
  • List Azure CLI before Azure PowerShell in examples and next steps, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, to reinforce cross-platform parity.
  • Provide example commands for both Azure CLI (bash/zsh) and PowerShell when demonstrating how to enable features or manage DNS zones.
  • Include notes or links to documentation on using these tools from Linux environments.
  • Avoid language or ordering that implies Windows is the default or preferred platform.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on creating Windows virtual machines as part of the Terraform workflow, with no mention of Linux VM creation or examples. The checklist and sample code only reference Windows VMs, and the customer intent is specifically tied to Windows. There are no Linux-specific instructions, examples, or parity in VM creation guidance.
Recommendations
  • Add parallel instructions and sample code for creating Linux virtual machines alongside Windows VMs.
  • Update the checklist and customer intent to be inclusive of both Windows and Linux VM scenarios.
  • Provide example Terraform code for Linux VM creation and configuration.
  • Include verification steps relevant to Linux VMs (e.g., SSH access, Linux-specific Azure CLI commands).
  • Ensure troubleshooting and cleanup sections mention considerations for both Windows and Linux resources.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides only Windows-centric instructions for testing DNS records, specifically referencing 'nslookup' from a command prompt, which is most commonly associated with Windows environments. There are no examples or mentions of equivalent Linux tools (such as 'dig') or Linux-specific command-line usage. The tutorial implicitly assumes a Windows environment for verification steps, which may disadvantage Linux users.
Recommendations
  • Include Linux-specific instructions and examples for testing DNS records, such as using the 'dig' command.
  • Explicitly mention that 'nslookup' is available on both Windows and Linux, and provide command-line examples for both platforms.
  • Add screenshots or terminal output examples from a Linux shell to demonstrate parity.
  • Consider referencing cross-platform tools or providing guidance for macOS users as well.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-delegate-domain-azure-dns.md ...lob/main/articles/dns/dns-delegate-domain-azure-dns.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides only Windows-centric instructions for verifying DNS delegation, specifically using the nslookup command from a 'command prompt' without mentioning Linux or cross-platform alternatives. There are no Linux-specific examples, nor is there mention of using Linux tools or terminal environments. The documentation implicitly assumes a Windows environment for command-line operations.
Recommendations
  • Include Linux-specific instructions for verifying DNS delegation, such as using nslookup or dig from a Linux terminal.
  • Explicitly mention that nslookup is available on both Windows and Linux, and provide example commands for both platforms.
  • Add a note or section on cross-platform DNS verification tools, such as dig, and show example usage.
  • Avoid referring only to 'command prompt'; instead, use 'command prompt or terminal' to be inclusive of Linux and macOS users.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-get-started-bicep.md ...e-docs/blob/main/articles/dns/dns-get-started-bicep.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 operations (deploy, validate, clean up), but PowerShell is featured equally alongside CLI, which can introduce a Windows bias since PowerShell is primarily a Windows tool. The documentation does not mention Linux-specific shell environments (e.g., Bash) or note that Azure CLI is cross-platform, nor does it provide any Linux-specific context or troubleshooting tips.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (with cross-platform support, but less common on Linux).
  • Add a note or tab for Bash shell usage on Linux, or clarify that the CLI commands are suitable for Bash/zsh/fish shells.
  • Provide troubleshooting or installation instructions for Azure CLI on Linux.
  • Consider listing CLI examples before PowerShell, as CLI is more universal.
  • Add links to documentation for using Azure CLI on Linux and macOS.
GitHub Create Pull Request
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 Linux equivalents (such as 'dig' or Linux terminal usage). No Linux-specific tools or instructions are provided, and the example assumes a Windows environment for DNS testing.
Recommendations
  • Include Linux command-line instructions for DNS testing, such as using 'dig' or 'nslookup' from a Linux terminal.
  • Mention that the Azure portal and Azure PowerShell are cross-platform, and provide links or notes about using Azure CLI on Linux.
  • Add screenshots or examples showing the process from a Linux environment where relevant.
  • Explicitly state that the steps can be performed from any OS, and provide parity in examples for both Windows and Linux users.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 PowerShell is presented as a primary tab alongside CLI, and there are no explicit Linux shell (bash) examples or references. The CLI example is generic, but the PowerShell example is specific to Windows environments. No Linux-specific tools or instructions are mentioned, and the validation steps focus on the Azure portal UI, which is cross-platform but does not address Linux command-line validation.
Recommendations
  • Add explicit bash shell examples for Linux users, using the Azure CLI in a Linux context (e.g., with export instead of read, and $() syntax).
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide platform-specific notes where relevant.
  • Consider including a section or tab for deploying via bash on Linux, or referencing Linux-specific tools (such as curl, jq) for template validation.
  • Ensure parity in troubleshooting and validation steps by mentioning command-line validation options available on Linux.
  • Review the order of tabs/examples to avoid implicit prioritization of Windows/PowerShell over Linux/bash.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-centric tooling and patterns, specifically referencing 'nslookup' for DNS validation and showing screenshots of Windows interfaces (e.g., cmd). There are no examples or instructions for Linux or cross-platform alternatives, such as using 'dig' or Linux shell commands. This may hinder Linux users or those working in non-Windows environments from following the guidance seamlessly.
Recommendations
  • Include Linux-specific examples for DNS validation, such as using 'dig' or 'host' commands, alongside 'nslookup'.
  • Add notes or screenshots demonstrating equivalent steps in Linux environments (e.g., Azure CLI usage in bash, terminal output).
  • Explicitly state that the steps are platform-agnostic where possible, or provide parallel instructions for both Windows and Linux users.
  • Avoid assuming the use of Windows command prompt; mention alternative shells and tools.
  • Where screenshots are used, consider adding at least one example from a Linux terminal or a cross-platform tool.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-import-export.md ...cs/blob/main/articles/dns/private-dns-import-export.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux context for DNS zone file locations, but mentions Windows DNS and its default folder before BIND/Linux equivalents. It also references Windows-specific paths (e.g., %systemroot%\system32\dns) and the DNS console, which are Windows-centric tools. However, the Azure CLI commands themselves are cross-platform and examples do not show Windows-only syntax or PowerShell usage. There is no explicit Linux example for obtaining a zone file, and the Windows method is described in more detail.
Recommendations
  • Present Linux/BIND instructions before or alongside Windows instructions when describing how to obtain zone files.
  • Provide explicit Linux command-line examples (e.g., using 'cat', 'cp', or 'ls' to locate and copy zone files from BIND directories).
  • Avoid referencing Windows GUI tools (like the DNS console) without offering equivalent Linux/BIND methods.
  • Clarify that Azure CLI commands work identically on Linux, Mac, and Windows, and show example CLI usage on Linux (e.g., using bash).
  • Consider including troubleshooting tips or file permission notes relevant to Linux environments.
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: 2026-01-08 00:53
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 consistently lists Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). However, the PowerShell examples are included as a primary tab, which can suggest a slight Windows bias, especially since no explicit Linux shell (bash) or macOS-specific guidance is given. There are no explicit Windows-only tools or commands, but the presence of PowerShell and lack of explicit Linux/macOS shell examples may disadvantage non-Windows users.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users, especially for common verification and scripting steps.
  • Clarify in the prerequisites or verification sections that Azure CLI commands are cross-platform and provide sample terminal prompts for Linux/macOS.
  • Consider including a 'Bash' or 'Linux/macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' to demonstrate parity and inclusivity.
  • If PowerShell is included, note that it is available cross-platform, or provide guidance for installing PowerShell on Linux/macOS if relevant.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-import-export-portal.md .../main/articles/dns/private-dns-import-export-portal.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 path is given explicitly, while the BIND location is described less directly. No Linux-specific tools or commands are referenced, and the only example of obtaining a zone file is for Windows DNS. The documentation does not provide Linux command-line examples (e.g., using 'cat', 'scp', or BIND file paths), nor does it mention Linux file system conventions. The focus is slightly skewed toward Windows environments.
Recommendations
  • Provide explicit examples for obtaining zone files from BIND on Linux, including common file paths (e.g., /etc/bind/zones/) and commands to copy or view files.
  • Mention Linux/Unix tools (such as 'scp', 'cat', or 'ls') for handling zone files.
  • Present BIND/Linux information before or alongside Windows DNS details to avoid 'windows_first' ordering.
  • Include screenshots or walkthroughs that show Linux file systems or terminal commands where relevant.
  • Clarify that the process is platform-agnostic and provide parity in instructions for both Windows and Linux administrators.
GitHub Create Pull Request
DNS https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-public-dns-zones-child.md ...b/main/articles/dns/tutorial-public-dns-zones-child.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all steps and does not provide any command-line examples. While it avoids explicit Windows tools or PowerShell commands, the tutorial implicitly favors Windows by referencing the Azure portal, which is most commonly accessed via Windows environments. There are no CLI (az), PowerShell, or Bash examples, and no mention of Linux-specific workflows or tools. This lack of parity may disadvantage users who prefer or require command-line or Linux-native approaches.
Recommendations
  • Add equivalent instructions for creating and managing child DNS zones using the Azure CLI (az) with example commands.
  • Include Bash shell examples for Linux users, especially for verification steps (e.g., using dig or nslookup).
  • Explicitly mention that the Azure portal is cross-platform, but provide links or sections for command-line alternatives.
  • Ensure that resource cleanup steps include CLI commands for deleting zones and records, not just portal navigation.
  • Consider a 'Platform parity' section that lists all supported methods (Portal, CLI, PowerShell) with links to relevant documentation.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which subtly prioritizes Windows-centric tooling. There are no explicit Linux examples, and PowerShell is referenced as a primary method for resource creation, which may imply a preference for Windows environments.
Recommendations
  • List Azure CLI before Azure PowerShell in example links to reflect platform neutrality, as CLI is cross-platform.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to avoid implying PowerShell is Windows-only.
  • Provide example commands for both Azure CLI and PowerShell in the main body, not just in linked articles, to ensure parity.
  • Add a note clarifying that all operations can be performed equally on Linux and macOS, not just Windows.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server for the web server VM, with all instructions and screenshots focused on Windows and IIS. There are no examples or guidance for deploying a Linux VM or using a Linux-based web server, nor are alternative Linux tools or commands mentioned. This creates a Windows-first bias and omits Linux parity.
Recommendations
  • Add a parallel section for creating a Linux VM (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
  • Include screenshots and step-by-step instructions for connecting to a Linux VM (using SSH) and installing/configuring the web server.
  • Provide Linux-specific testing instructions (e.g., using curl or a browser to access the site).
  • Explicitly mention that the alias record steps apply to both Windows and Linux VMs.
  • Consider using more generic terminology (e.g., 'web server VM') and offer both Windows and Linux options throughout the tutorial.
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-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows as the default operating system in examples (App Service plans and web apps), with no mention of Linux or cross-platform options. There are no Linux-specific instructions or parity in the walkthrough, and the runtime stack is limited to .NET Core, which is cross-platform, but the hosting environment is Windows-only in all examples.
Recommendations
  • Include examples for both Windows and Linux App Service plans in the configuration tables.
  • Explicitly mention that App Service plans and web apps can be created on Linux, and provide step-by-step instructions or notes for Linux users.
  • Show at least one example using a Linux runtime stack (e.g., Node.js, Python, or .NET Core on Linux) to demonstrate cross-platform support.
  • Clarify in the prerequisites or relevant sections that the process is applicable to both Windows and Linux environments.
  • Where UI steps are given, note any differences for Linux-based App Services if applicable.
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-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses 'nslookup' as the sole example for DNS validation, with screenshots and references that appear to be from Windows Command Prompt. There are no examples or mentions of equivalent Linux/macOS tools (such as 'dig' or 'host'), nor are there instructions or screenshots for validating DNS from non-Windows environments. This presents a subtle Windows-first bias and omits guidance for Linux users.
Recommendations
  • Include equivalent DNS validation commands for Linux/macOS, such as 'dig <domain>' and 'host <domain>', alongside 'nslookup'.
  • Add screenshots or terminal output examples from Linux/macOS environments to demonstrate parity.
  • Explicitly mention that DNS validation can be performed from any OS, and provide cross-platform instructions.
  • Where possible, use neutral language (e.g., 'run a DNS query using your preferred tool, such as nslookup, dig, or host') rather than referencing only Windows tools.
  • Consider a table or note summarizing common DNS query tools across platforms.
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-13 21:37
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 example, which can be seen as a Windows bias since PowerShell is primarily a Windows tool (despite cross-platform support). There are no Linux-specific shell examples (such as Bash), and the validation steps focus on the Azure Portal UI, which is platform-agnostic but often associated with Windows workflows. The order of examples (CLI first, then PowerShell) is good, but the lack of explicit Linux/Bash guidance may disadvantage Linux users.
Recommendations
  • Add explicit Bash shell examples for Linux users, highlighting any differences in environment variable syntax or command usage.
  • Clarify that Azure CLI commands work identically on Windows, macOS, and Linux, and provide notes on installing the CLI on Linux.
  • If PowerShell is included, mention that it is available cross-platform, but also provide Bash alternatives to ensure Linux parity.
  • Consider including a table or section summarizing deployment options for different operating systems.
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-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on creating Windows virtual machines, with no mention or example of Linux VMs. All VM-related steps and outputs are Windows-specific, and there are no Linux alternatives or parity in the walkthrough. While both Azure CLI and PowerShell are provided for verification, the core scenario is Windows-centric.
Recommendations
  • Include parallel instructions and Terraform code samples for creating Linux virtual machines alongside Windows VMs.
  • Update the checklist and scenario description to mention both Windows and Linux VM creation, or provide a choice.
  • Add outputs and verification steps relevant to Linux VMs (such as SSH credentials, Linux admin username, etc.).
  • Ensure that the sample code repository referenced contains both Windows and Linux VM examples.
  • Consider providing a toggle or tabbed interface for users to choose between Windows and Linux scenarios throughout the guide.
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-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates creating and configuring a Windows Server virtual machine, including detailed steps for installing IIS via the Windows GUI and using RDP. There are no examples or instructions for deploying a Linux-based web server or using Linux-native tools. The documentation assumes a Windows environment throughout, omitting Linux alternatives.
Recommendations
  • Add parallel instructions for creating a Linux virtual machine (e.g., Ubuntu or CentOS) and installing a web server such as Apache or Nginx.
  • Include Linux command-line examples for connecting to the VM (e.g., using SSH) and installing web server packages.
  • Provide screenshots or terminal output relevant to Linux environments.
  • Explicitly mention that either Windows or Linux VMs can be used, and link to relevant Azure documentation for both platforms.
  • Consider alternating or balancing the order of Windows and Linux examples to avoid implicit prioritization.
GitHub Create Pull Request
← Previous Page 11 of 13 Next →