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 151-175 of 323 flagged pages
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by mentioning Windows DNS and its file locations before Linux/BIND equivalents, and by providing specific details for Windows tools (e.g., %systemroot%\system32\dns) while only briefly referencing BIND and its configuration. No explicit Linux command-line examples or file paths are given, and the only concrete example of obtaining a zone file is for Windows DNS. There are no Linux-specific instructions or troubleshooting tips, despite BIND being called out as a common Linux DNS server.
Recommendations
- Provide explicit Linux/BIND examples, such as sample named.conf entries and typical zone file paths (e.g., /etc/bind/zones/db.example.com).
- List Linux/BIND instructions before or alongside Windows instructions, especially since BIND is the most common DNS server.
- Include example commands for exporting a zone file from BIND (e.g., using cp or cat to copy the file), and clarify permissions or file locations.
- Add troubleshooting tips or notes relevant to Linux users, such as file permissions or SELinux considerations.
- Ensure parity in detail and clarity between Windows and Linux instructions throughout the documentation.
Create Pull Request
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-resiliency.md
...-docs/blob/main/articles/dns/private-dns-resiliency.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Next steps' section, where the link to 'create a Private DNS zone' points specifically to a PowerShell-based guide, which is Windows-centric. There are no examples or references to Linux tools, CLI, or cross-platform approaches for managing Azure Private DNS zones. The absence of Linux or Azure CLI examples and the exclusive mention of PowerShell suggest a bias towards Windows users.
Recommendations
- Include links to equivalent Linux/Azure CLI documentation for creating and managing Private DNS zones.
- Provide examples using Azure CLI and/or REST API alongside PowerShell to ensure cross-platform accessibility.
- Avoid referencing only Windows-specific tools (like PowerShell) in primary navigation or 'Next steps'; instead, offer parallel options for Linux and macOS users.
- Explicitly mention that Azure DNS management can be performed from any platform, and provide guidance for non-Windows environments.
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 no mention of Linux, Bash, or cross-platform alternatives. The instructions assume the use of an 'elevated PowerShell window' and reference Windows-specific tools and installation methods. There are no examples or guidance for users on Linux or macOS, nor are there alternative scripts or CLI-based migration paths provided.
Recommendations
- Provide equivalent migration instructions using Azure CLI and Bash scripts that can be run on Linux and macOS.
- Include Linux/macOS prerequisites, such as ensuring Azure CLI is installed and up-to-date, and provide installation instructions for non-Windows environments.
- Offer a cross-platform migration script (e.g., Python or Bash) or document how to perform the migration manually using Azure CLI commands.
- Clearly indicate which steps are Windows-specific and provide alternative steps for Linux/macOS users.
- Add screenshots or terminal output examples from Linux/macOS environments to improve inclusivity.
- Mention that PowerShell Core is available cross-platform and provide instructions for installing and running the script on Linux/macOS if no alternative is available.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-scenarios.md
...e-docs/blob/main/articles/dns/private-dns-scenarios.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only the PowerShell-based getting started guide for creating a Private DNS zone, without mentioning or linking to equivalent Linux/CLI/Bash instructions. No Linux tools, commands, or examples are provided, and the 'get started' link specifically points to a PowerShell tutorial, which is typically associated with Windows environments. There are no examples or guidance for Linux users or those preferring cross-platform Azure CLI.
Recommendations
- Include links to both PowerShell and Azure CLI (Bash/Linux) guides for creating and managing Private DNS zones.
- Add example commands using Azure CLI alongside PowerShell, ensuring parity in instructions for both platforms.
- Explicitly mention that Azure DNS management can be performed from Windows, Linux, and macOS, and provide platform-agnostic examples where possible.
- Where only PowerShell is referenced, add a note or section for Linux/macOS users, directing them to appropriate CLI documentation.
- Review all 'Next steps' and instructional links to ensure they are not Windows-centric and provide equal visibility to cross-platform tooling.
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-based example for testing DNS resolution (using nslookup with a C:\> prompt), with no Linux or cross-platform command-line examples. The command-line prompt and syntax are Windows-specific, and there is no mention of how to perform the same operation on Linux or macOS. This may lead Linux users to feel unsupported or unclear about how to verify reverse DNS functionality.
Recommendations
- Include Linux and macOS examples for testing DNS resolution, such as showing the nslookup or dig command with a $ prompt.
- Present both Windows and Linux/macOS command-line examples side by side, or use a neutral prompt (e.g., 'nslookup 10.1.2.5') without platform-specific context.
- Explicitly mention that the steps for verifying DNS resolution can be performed on any OS, and provide sample outputs for both Windows and Linux.
- If using screenshots or code blocks, alternate between Windows and Linux environments, or provide both to ensure parity.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-resolver-hybrid-dns.md
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows and PowerShell in procedural examples, omitting Linux/BIND equivalents, and focusing on Windows DNS server tools for on-premises configuration. Linux-based DNS servers and command-line tools are not mentioned or demonstrated, leaving a gap for cross-platform administrators.
Recommendations
- Add parallel instructions and screenshots for configuring conditional forwarders on common Linux DNS servers (e.g., BIND/named.conf).
- Include CLI examples using Azure CLI and bash, not just PowerShell, for Azure resource creation and management.
- When referencing on-premises DNS, explicitly mention and provide steps for both Windows DNS and Linux/BIND (and optionally other popular DNS servers).
- Ensure that Linux examples are presented alongside or before Windows examples to avoid 'windows_first' bias.
- Provide sample dig/nslookup commands from both Windows and Linux environments to demonstrate DNS resolution.
- In the 'Next steps' section, link to Linux/BIND documentation or community guides for hybrid DNS scenarios.
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The tutorial exclusively uses Windows Server virtual machines for the web server setup, with detailed steps for installing IIS via the Windows GUI and RDP. There are no examples or instructions for deploying Linux-based VMs or using common Linux web servers (e.g., Apache, Nginx). All configuration and testing steps assume a Windows environment, and no Linux alternatives are mentioned.
Recommendations
- Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
- Provide CLI-based steps for web server setup (using Azure CLI, SSH, and Linux package managers) alongside the Windows/RDP/IIS instructions.
- Include Linux-based examples for editing the web root (e.g., using nano or vim to edit /var/www/html/index.html).
- Demonstrate testing the setup from a Linux client (e.g., using curl or a browser on a Linux desktop).
- Clearly indicate that both Windows and Linux are supported, and offer a choice at the start of the tutorial.
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 demonstrates a clear Windows bias in the section on configuring on-premises DNS forwarding. Only Windows Server and PowerShell-based instructions are provided, with no mention of Linux-based DNS servers (such as BIND or dnsmasq) or their configuration. All command-line examples and screenshots are Windows-centric, and the documentation does not acknowledge or provide parity for Linux environments, which are common in enterprise and hybrid cloud scenarios.
Recommendations
- Add equivalent instructions and examples for configuring DNS forwarding on popular Linux DNS servers, such as BIND and dnsmasq.
- Include Linux command-line examples (e.g., editing named.conf.options for BIND) alongside PowerShell examples.
- Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and provide links or references to official documentation for Linux DNS server configuration.
- Reorganize the documentation to present both Windows and Linux options in parallel, or at least acknowledge Linux as a supported and common scenario.
- Where screenshots are used, consider including Linux-based management interfaces or configuration file snippets as well.
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions and screenshots for configuring hybrid DNS using Azure DNS Private Resolver, but only demonstrates on-premises DNS configuration using a Windows DNS server. There are no examples or guidance for configuring conditional forwarders on Linux-based DNS servers (such as BIND), nor are Linux/macOS command-line examples shown for DNS testing. Windows/PowerShell quickstarts are mentioned before CLI alternatives.
Recommendations
- Add a section or example showing how to configure conditional forwarders on a Linux DNS server (e.g., BIND), including sample configuration files.
- Include Linux/macOS command-line examples (e.g., using dig or nslookup) for DNS query testing, alongside or instead of Windows screenshots.
- When listing quickstarts, mention CLI and Linux-compatible options before or alongside PowerShell/Windows-specific ones.
- Clarify that the procedures are applicable to both Windows and Linux environments, and provide parity in troubleshooting steps.
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides detailed steps and screenshots for configuring DNS conditional forwarders using a Windows DNS server, but does not include equivalent instructions or examples for Linux-based DNS servers (e.g., BIND). Windows DNS is presented first and exclusively in the on-premises configuration section, which may create friction for users operating Linux-based DNS infrastructure.
Recommendations
- Add a section or example showing how to configure conditional forwarders on a popular Linux DNS server such as BIND.
- Include CLI commands or configuration file snippets for Linux DNS server setups.
- Clarify in the procedures that the steps for on-premises DNS configuration can be adapted for non-Windows DNS servers, and provide links to relevant external documentation for Linux/BIND.
- Present both Windows and Linux examples in parallel where possible, or at least mention Linux alternatives.
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides detailed steps and screenshots for configuring on-premises DNS conditional forwarders using a Windows DNS server, but does not mention or provide examples for Linux-based DNS servers (such as BIND or dnsmasq). Windows DNS is presented as the default/primary example for on-premises integration, and there are no instructions or references for Linux equivalents.
Recommendations
- Add a section or example for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
- Include screenshots or configuration file snippets for Linux DNS server setups.
- Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and link to relevant external documentation for Linux DNS configuration if full instructions are out of scope.
- Where possible, present both Windows and Linux examples side-by-side, or clarify when steps are OS-specific.
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions and screenshots for configuring DNS conditional forwarders using a Windows DNS server, but does not offer equivalent examples or guidance for Linux-based DNS servers (such as BIND or dnsmasq). PowerShell and portal quickstarts are listed before CLI options, and the only on-premises DNS configuration example is for Windows, potentially creating friction for Linux users.
Recommendations
- Add explicit instructions and examples for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
- Include screenshots or configuration file snippets for Linux DNS server setups.
- List CLI-based quickstarts before or alongside PowerShell/portal options to avoid Windows-first ordering.
- Clarify that the procedures are applicable to both Windows and Linux DNS servers, and provide links to external resources for Linux DNS configuration if full instructions are out of scope.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a configuration method for DNS security policy, but does not mention Azure CLI, Bash, or provide Linux/macOS-specific instructions or examples. All example references are either generic or portal-based, with no explicit parity for Linux users. This creates a subtle bias by implying PowerShell is the primary or only scripting interface, which is more common on Windows.
Recommendations
- Explicitly mention Azure CLI as a supported configuration method alongside Azure PowerShell.
- Provide example commands for both Azure PowerShell and Azure CLI (or Bash) for key tasks such as creating policies, managing domain lists, and linking VNets.
- Add a note clarifying that all operations can be performed from Linux/macOS using Azure CLI.
- Where scripting is referenced, show both PowerShell and CLI examples, or link to platform-specific guides.
DNS
How to sign your Azure Public DNS zone with DNSSEC
...ocs/azure-docs/blob/main/articles/dns/dnssec-how-to.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given a dedicated section. The CLI section references 'dig.exe', which is a Windows-specific binary name, and the CLI output examples use jq, which is more common on Linux/macOS but not explained for Windows. The PowerShell section is detailed and assumes user familiarity with Windows tooling. There is a slight ordering bias: PowerShell is given equal prominence to CLI, and 'dig.exe' is mentioned before the generic 'dig' command, which may confuse Linux/macOS users.
Recommendations
- Clarify that 'dig' is available on Linux/macOS and provide installation instructions for those platforms.
- Provide explicit Linux/macOS command-line examples (e.g., bash, zsh) for querying DS records, rather than referencing 'dig.exe'.
- Add notes or examples for using Azure CLI and jq on Windows, since jq is not natively available.
- Balance PowerShell and CLI coverage by including shell script examples for Linux/macOS users where appropriate.
- Reorder examples so that cross-platform tools (CLI, dig) are presented before Windows-specific tools (PowerShell).
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows DNS servers are used as the sole example for on-premises DNS configuration, and PowerShell is referenced before CLI for Azure resource creation. No Linux/BIND or macOS DNS server configuration examples are provided, nor are Linux tools (e.g., dig, nslookup) mentioned for DNS query demonstration. This may create friction for administrators using Linux-based DNS servers or clients.
Recommendations
- Include examples for configuring conditional forwarders on Linux-based DNS servers (e.g., BIND/named.conf).
- Provide Azure DNS Private Resolver creation steps using Azure CLI and reference them equally with PowerShell.
- Demonstrate DNS queries using cross-platform tools like dig or nslookup, not just Windows screenshots.
- Explicitly mention that the procedures apply to non-Windows environments and link to relevant Linux/macOS documentation.
- Add a section or note on how to adapt the steps for Linux/macOS DNS servers and clients.
DNS
Tutorial: Create an alias record to refer to a resource record in a zone
...azure-docs/blob/main/articles/dns/tutorial-alias-rr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line testing instructions using 'nslookup' and refers to a 'command prompt' without specifying platform, implicitly assuming Windows. No Linux/macOS-specific instructions or alternative tools (like 'dig') are mentioned. The Azure Portal UI steps are platform-neutral, but the only CLI example is Windows-centric.
Recommendations
- Explicitly mention that 'nslookup' is available on Windows, Linux, and macOS, or provide platform-specific instructions.
- Include Linux/macOS terminal instructions, e.g., using 'dig' as an alternative to 'nslookup'.
- Replace 'command prompt' with 'terminal or command prompt' to be inclusive of all platforms.
- Add a note or table showing equivalent commands for Windows, Linux, and macOS.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions for delegating a subdomain in Azure DNS primarily using the Azure portal, with a mention of Azure PowerShell as an alternative. The only command-line example given for testing delegation uses 'nslookup' from a 'command prompt', which implicitly refers to Windows. There are no Linux/macOS-specific instructions, nor are cross-platform CLI tools (like dig) mentioned. The documentation does not provide parity for Linux/macOS users in terms of examples or tool references.
Recommendations
- Include Linux/macOS equivalents for command-line instructions, such as using 'dig' or 'nslookup' from a terminal.
- Clarify that 'nslookup' is available on multiple platforms, and provide example commands for Linux/macOS.
- Add Azure CLI examples for delegation tasks, as Azure CLI is cross-platform.
- Avoid referring to 'command prompt' without also mentioning 'terminal' for Linux/macOS users.
DNS
Quickstart: Create an Azure DNS zone and record - Azure Resource Manager template (ARM template)
...ocs/blob/main/articles/dns/dns-get-started-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell and Windows command prompt (cmd) examples for deploying and validating the DNS zone. There are no Linux/macOS equivalents (e.g., Bash/CLI examples), and Windows tools and patterns are referenced exclusively and/or first. This may create friction for Linux/macOS users who prefer Azure CLI or Bash.
Recommendations
- Add Azure CLI (bash) examples alongside PowerShell for template deployment and resource group deletion.
- Show how to run the nslookup command in a Linux/macOS terminal, not just Windows cmd.
- Explicitly mention cross-platform alternatives (Azure CLI, REST API) in deployment and clean-up sections, with code samples.
- Consider presenting CLI/Bash examples before or alongside PowerShell to avoid Windows-first ordering.
DNS
Quickstart: Use Terraform to configure private DNS zones in Azure
...s/blob/main/articles/dns/dns-private-zone-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on creating Windows virtual machines, with no mention or examples for Linux VMs. The checklist and customer intent are Windows-centric, and the sample Terraform code is implied to be for Windows VMs only. While Azure CLI and PowerShell verification steps are provided, there are no Linux-specific VM creation or management examples, which may hinder Linux users seeking parity.
Recommendations
- Add instructions and sample Terraform code for creating Linux virtual machines alongside Windows VMs.
- Update the checklist and customer intent to mention both Windows and Linux VM scenarios.
- Provide verification examples for Linux VMs, such as SSH access or Linux-specific resource outputs.
- Clarify that the process is applicable to both Windows and Linux VMs, or link to Linux VM quickstarts.
DNS
Protecting private DNS Zones and Records - Azure DNS
...n/articles/dns/dns-protect-private-zones-recordsets.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI, and in some cases (record set level resource locks), only PowerShell is supported and documented, with no Linux/macOS alternatives. The use of PowerShell-centric instructions and terminology may create friction for Linux/macOS users, especially where CLI or portal options are unavailable.
Recommendations
- Clearly indicate platform requirements for PowerShell-only operations, and provide guidance for Linux/macOS users (e.g., using PowerShell Core on Linux, or alternatives if available).
- Where only PowerShell is supported, add explicit notes about lack of CLI/portal support and suggest workarounds or roadmap for parity.
- Present CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Expand documentation to include Linux/macOS-specific instructions or troubleshooting tips for cross-platform users.
- Consider adding a table summarizing which operations are available via Portal, PowerShell, CLI, and on which platforms.
DNS
Reverse DNS for Azure services - Azure DNS
...ain/articles/dns/dns-reverse-dns-for-azure-services.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is consistently presented first in all example sections, and Cloud Services configuration is only documented via PowerShell (which is Windows-centric). There are no Linux/macOS-specific shell examples (e.g., bash, zsh), nor are there explicit instructions for Linux users regarding PowerShell Core or cross-platform CLI usage. The Azure CLI examples are present, but PowerShell is prioritized and Cloud Services tasks cannot be completed without Windows tools.
Recommendations
- Add explicit instructions or notes for Linux/macOS users regarding PowerShell Core compatibility, or alternatives for Cloud Services reverse DNS configuration.
- Reorder examples to present Azure CLI first, as it is cross-platform, and clarify that PowerShell is Windows-centric unless using PowerShell Core.
- Provide bash/zsh shell script equivalents for common tasks, especially for viewing and validating DNS records.
- For Cloud Services, document if there is any REST API or ARM template support for reverse DNS, or clarify that Windows is required.
- Add a table summarizing tool/platform compatibility for each scenario.
DNS
Protecting DNS Zones and Records - Azure DNS
...blob/main/articles/dns/dns-protect-zones-recordsets.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for most tasks, but PowerShell is consistently presented first and in more detail. Some advanced operations, such as record set level resource locks, are only possible via PowerShell, with no Linux/macOS equivalent. There is a notable reliance on PowerShell, which is a Windows-centric tool, and some features are unavailable to CLI users, impacting Linux/macOS parity.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Clearly indicate which features are unavailable in the Azure CLI and provide alternative guidance or workarounds for Linux/macOS users.
- Advocate for parity in Azure CLI functionality, especially for resource lock operations at the record set level.
- Add explicit notes or sections for Linux/macOS users, including installation and usage tips for Azure CLI.
- Where PowerShell is required for advanced features, suggest using Azure Cloud Shell (which supports Bash and PowerShell) as a cross-platform workaround.
DNS
Host reverse DNS lookup zones in Azure DNS
...docs/blob/main/articles/dns/dns-reverse-dns-hosting.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently provides Azure PowerShell examples alongside Azure CLI, with PowerShell examples always listed first. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. There are no Linux-specific shell examples (e.g., Bash), and no mention of platform-specific considerations for running CLI commands. The use of 'Azure classic CLI' is also legacy and Windows-oriented.
Recommendations
- List Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS.
- Explicitly note that Azure CLI works on Windows, Linux, and macOS, and provide installation links.
- Remove or de-emphasize Azure classic CLI examples, as it is deprecated and less relevant for modern cross-platform workflows.
- Add Bash script examples for common tasks, or clarify that Azure CLI commands can be run in any shell.
- Where PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or link to installation instructions for non-Windows users.
DNS
Secure and view DNS traffic - Azure DNS
...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides extensive PowerShell-based instructions and examples, which are specific to Windows environments. The only CLI automation shown is via PowerShell, with no equivalent Bash, Azure CLI, or Linux/macOS shell examples. The setup steps reference Windows file paths (e.g., C:\bin\PSRepo) and use Windows-specific tools (PowerShell, Register-PSRepository, etc.). The portal instructions are platform-neutral, but the scripting/automation section is Windows-centric. There are no Linux/macOS automation examples, nor is Azure CLI or REST API usage covered.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell automation steps, including resource creation, policy management, and diagnostics.
- Include Bash shell examples for Linux/macOS users, especially for DNS query testing (e.g., using dig or nslookup from Linux/macOS terminals).
- Reference cross-platform tools and avoid Windows-specific file paths in generic instructions.
- Explicitly mention platform compatibility and provide guidance for Linux/macOS users where PowerShell modules are referenced.
- Consider adding REST API examples for advanced users who may prefer direct API calls.
DNS
How to unsign your Azure Public DNS zone
...ocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides three methods for unsigning an Azure Public DNS zone: Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, the PowerShell example is Windows-centric, and PowerShell is presented as a separate, prominent tab. The CLI example uses the 'azurepowershell-interactive' code block type, which may confuse Linux users. There are no explicit Linux/macOS shell (bash) examples, and PowerShell is highlighted as a primary automation tool, which is more common on Windows.
Recommendations
- Add explicit bash examples for Linux/macOS users using Azure CLI.
- Clarify that Azure CLI commands work on all platforms (Windows, Linux, macOS).
- Use a generic 'bash' or 'shell' code block for CLI examples instead of 'azurepowershell-interactive'.
- Mention cross-platform compatibility in the CLI section.
- Consider providing guidance for installing Azure CLI on Linux/macOS.