Frontdoor

105
Total Pages
76
Linux-Friendly Pages
29
Pages with Bias
27.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

130 issues found
Showing 26-50 of 130 flagged pages
Frontdoor Migration FAQ ...ure-docs/blob/main/articles/frontdoor/migration-faq.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell migration instructions in the 'Related content' section, without mentioning or linking to equivalent Linux-friendly tools or CLI instructions (e.g., Azure CLI, Bash). The PowerShell example is listed before any Linux alternatives, and there are no explicit examples or guidance for Linux users or those using cross-platform tools.
Recommendations
  • Add migration instructions using Azure CLI (az) and Bash scripts, and link to them alongside PowerShell instructions.
  • Ensure that Linux/macOS tools and workflows are mentioned and documented with equal prominence as Windows/PowerShell options.
  • In 'Related content', provide links for both PowerShell and Azure CLI migration guides, and clarify which platforms each is suitable for.
  • Include examples or notes for updating DNS records using Linux-native tools (e.g., dig, nsupdate) in addition to Windows-based approaches.
GitHub Create Pull Request
Frontdoor Post Migration Dev-Ops Experience ...rticles/frontdoor/post-migration-dev-ops-experience.md
High Priority View Details →
Scanned: 2026-01-10 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 by consistently listing Windows-centric tools (PowerShell, ARM templates via Azure portal) before Linux-friendly equivalents, and by providing detailed PowerShell guidance and prerequisites. PowerShell is given its own dedicated section, while Linux-native scripting (e.g., Bash) is not mentioned. Installation links for PowerShell reference Windows-specific instructions, and there is no mention of Linux-specific nuances or examples for CLI or scripting.
Recommendations
  • Add explicit Linux/Bash examples for CLI and scripting workflows, especially in sections currently focused on PowerShell.
  • Include installation and usage instructions for Azure PowerShell and CLI on Linux and macOS, not just Windows.
  • When listing export options (e.g., for ARM templates), mention CLI before PowerShell and Azure portal, or present all options together without ordering bias.
  • Clarify cross-platform compatibility for all tools and scripts, and provide troubleshooting notes for Linux environments where relevant.
  • Consider adding a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Frontdoor Azure Front Door (Classic) To Standard/Premium Tier Migration ...re-docs/blob/main/articles/frontdoor/tier-migration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and CLI tools for migration, mentioning PowerShell before CLI, API, and Terraform. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific tooling or workflows. The migration instructions and related content prioritize Windows-centric tools, and the related links highlight PowerShell migration guides but do not provide parity for Bash/CLI or Linux workflows.
Recommendations
  • Add explicit Bash/Azure CLI examples for migration steps alongside PowerShell instructions.
  • Include references and links to Linux-compatible migration guides (e.g., using Azure CLI or Terraform on Linux).
  • Ensure that CLI and API instructions are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Mention cross-platform compatibility of migration tools and clarify any OS-specific requirements.
  • Provide troubleshooting steps or notes for Linux users where differences may exist.
GitHub Create Pull Request
Frontdoor Secure traffic to origins ...e-docs/blob/main/articles/frontdoor/origin-security.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by providing IIS (Windows-only) configuration examples and mentioning Windows-centric tools and patterns (IIS, XML config). The IIS example appears before the AKS NGINX controller (Linux) example, and there is no Apache or general Linux web server example. The page lacks parity in Linux-specific guidance, such as for Apache, NGINX (outside AKS), or other common Linux-origin scenarios.
Recommendations
  • Add configuration examples for popular Linux web servers such as Apache and standalone NGINX (outside AKS), showing how to filter the X-Azure-FDID header.
  • Ensure that Linux-origin examples (Apache, NGINX) are presented alongside or before Windows/IIS examples to avoid ordering bias.
  • Include shell-based (bash) or Linux-native configuration steps where appropriate, not just Windows-centric tools or XML configs.
  • Reference Linux firewall tools (e.g., iptables, firewalld) for IP filtering, not just Azure NSG rules.
  • Review and expand documentation to cover a broader set of Linux-origin scenarios, ensuring parity in depth and clarity.
GitHub Create Pull Request
Frontdoor Secure your Origin with Private Link in Azure Front Door Premium ...zure-docs/blob/main/articles/frontdoor/private-link.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a method for approving private endpoint connections, listing it alongside Azure CLI and the Azure portal. However, PowerShell is mentioned before CLI, and there are no explicit examples or references to Linux-specific tools or workflows. The documentation does not provide command-line examples, but the ordering and tool references suggest a slight Windows bias. There are no references to Linux shells, nor are there instructions tailored for Linux users.
Recommendations
  • When listing management tools, mention Azure CLI before Azure PowerShell to avoid implicit Windows-first bias.
  • Explicitly state that Azure CLI is cross-platform and provide example commands for both Azure CLI and Azure PowerShell.
  • Include references or links to Linux-specific documentation or workflows where relevant.
  • If providing code samples or walkthroughs in future updates, ensure parity between PowerShell and Bash/CLI examples.
GitHub Create Pull Request
Frontdoor Connect Front Door Premium to an Azure API Management origin with Private Link ...or/standard-premium/how-to-enable-private-link-apim.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides three pivots: Portal, PowerShell, and Azure CLI. The PowerShell pivot is detailed and uses Windows-centric tooling, with explicit instructions for Azure PowerShell and references to running PowerShell locally. The CLI pivot is present and covers Azure CLI commands, which are cross-platform, but the PowerShell instructions and references to Azure Cloud Shell are more prominent and detailed. There is a slight Windows-first bias in the ordering and depth of examples, and no explicit mention of Linux-specific considerations or shell environments (e.g., Bash, zsh).
Recommendations
  • Add explicit instructions or notes for running Azure CLI commands in Linux/macOS environments, including shell syntax differences if any.
  • Mention that Azure CLI is cross-platform and provide parity in example depth and troubleshooting steps for CLI users.
  • Include references to Bash scripts or Linux-native tools where appropriate, especially for users not using Cloud Shell.
  • Balance the detail level between PowerShell and CLI sections to ensure Linux users have equal guidance.
  • Consider adding a troubleshooting section for common Linux-specific issues (e.g., permissions, path differences) when using Azure CLI.
GitHub Create Pull Request
Frontdoor Troubleshoot File Compression ...frontdoor/standard-premium/troubleshoot-compression.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Windows tools (Fiddler, IIS) and Windows-centric configuration steps for troubleshooting file compression. There are no Linux or cross-platform equivalents provided for inspecting HTTP headers or configuring compression on non-Windows origin servers. The guidance assumes IIS as the origin server and omits common Linux web servers like Apache or Nginx.
Recommendations
  • Include Linux and cross-platform tools for inspecting HTTP headers, such as curl, wget, or httpie, alongside Fiddler and browser developer tools.
  • Provide troubleshooting steps for popular Linux web servers (e.g., Apache, Nginx), including how to configure compression and handle proxy headers.
  • When discussing server configuration, mention both IIS and Linux server equivalents, and provide links to relevant documentation for each.
  • Present examples for both Windows and Linux environments, or use platform-neutral language where possible.
GitHub Create Pull Request
Frontdoor Troubleshoot common issues ...cs/blob/main/articles/frontdoor/troubleshoot-issues.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific troubleshooting tools (Fiddler, browser developer tools) without mentioning Linux alternatives, and by listing these tools before mentioning any cross-platform or Linux-native options. The only command-line example given is for OpenSSL, which is cross-platform, but there are no Linux-specific troubleshooting steps or tool recommendations (e.g., curl, tcpdump, Wireshark, wget). No PowerShell commands are present, but the overall troubleshooting guidance assumes a Windows environment and omits Linux workflows.
Recommendations
  • Include Linux-native troubleshooting tools such as curl, wget, tcpdump, and Wireshark alongside or before Windows tools like Fiddler.
  • Provide example commands for both Windows (PowerShell, CMD) and Linux (bash) when discussing troubleshooting steps.
  • Mention cross-platform browser developer tools explicitly, and clarify their availability on Linux.
  • Add troubleshooting steps or screenshots from Linux environments where relevant.
  • Ensure parity in tool recommendations and workflows for both Windows and Linux users.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/front-door-custom-domain-https.md ...n/articles/frontdoor/front-door-custom-domain-https.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions and references before Azure CLI, emphasizing Azure PowerShell and Cloud Shell (which defaults to PowerShell on Windows), and using terminology and patterns familiar to Windows users. There is a lack of explicit Linux-specific guidance, and Windows tools (PowerShell) are mentioned more prominently than their cross-platform equivalents.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is more platform-neutral and widely used on Linux.
  • Explicitly mention that Azure CLI and Cloud Shell are available and fully supported on Linux/macOS, and provide installation/usage instructions for those platforms.
  • Include guidance for running commands in native Linux/macOS terminals, not just Cloud Shell or PowerShell.
  • Avoid language that assumes PowerShell is the default or preferred tool; clarify that both PowerShell and CLI are supported equally.
  • Add troubleshooting or notes for common Linux-specific issues (e.g., certificate formats, file permissions) where relevant.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-bicep.md ...lob/main/articles/frontdoor/create-front-door-bicep.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but PowerShell is featured equally alongside CLI, and screenshots show PowerShell output. PowerShell is a Windows-centric tool, and its inclusion (with screenshots) may suggest a Windows-first approach. There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific considerations or tools. The documentation does not address Linux users directly, nor does it provide parity for Linux-native workflows beyond Azure CLI.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI and PowerShell, especially for file operations (e.g., saving the Bicep file).
  • Include screenshots of CLI output, not just PowerShell, to avoid visual Windows bias.
  • Clarify that Azure CLI works cross-platform and highlight Linux usage where relevant.
  • Mention that PowerShell Core is available on Linux, or provide links for Linux users to install/use PowerShell if examples are kept.
  • Consider ordering examples with CLI (cross-platform) first, and PowerShell second, to reinforce platform neutrality.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/classic-overview.md ...-docs/blob/main/articles/frontdoor/classic-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily through its linking practices and example references. For instance, the migration guidance for certificates links to a 'Bring Your Own Certificate (BYOC)' page with a 'tabs=powershell' parameter, indicating that PowerShell (a Windows-centric tool) is the default or only example provided. There are no explicit Linux or cross-platform command-line examples, nor references to Linux-native tools (such as Bash, CLI, or shell scripts). The documentation does not mention or prioritize Linux workflows, and Windows tools/patterns are referenced before any Linux equivalents (if any exist).
Recommendations
  • Ensure that all example links (such as those for BYOC) provide parity between PowerShell and Azure CLI/Bash examples, ideally defaulting to a cross-platform CLI tab.
  • Explicitly mention and provide Linux-compatible instructions and tools where relevant, such as Azure CLI or Bash scripts.
  • Review all linked documentation to confirm that Linux users are not disadvantaged or forced to adapt Windows-centric instructions.
  • Add a section or note clarifying cross-platform support and pointing to resources for both Windows and Linux users.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/endpoint.md ...cs/azure-docs/blob/main/articles/frontdoor/endpoint.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Bicep, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux shell scripting or Bash alternatives. The use of Azure PowerShell (which is Windows-centric) and the absence of Linux-specific command-line patterns or examples (such as Bash or shell scripting) indicate a mild Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users alongside Azure CLI examples.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide OS-specific notes if needed.
  • Consider reordering examples to present cross-platform tools (Azure CLI, Bicep) before Windows-centric tools (PowerShell).
  • Include a note or section on how to perform these operations in a Linux environment, possibly with screenshots or terminal output.
  • If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, or provide Bash equivalents.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/front-door-overview.md ...cs/blob/main/articles/frontdoor/front-door-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation mentions integration with DevOps-friendly command line tools, specifically listing PowerShell alongside CLI, ARM templates, and Bicep. PowerShell is a Windows-centric tool, and its mention before Linux-native tools (such as Bash or shell scripting) suggests a Windows-first bias. There are no explicit Linux examples or references to Linux-specific tools, patterns, or workflows. The documentation does not provide parity for Linux users in terms of examples or tool recommendations.
Recommendations
  • Explicitly mention Linux-native tools (e.g., Bash, shell scripting) alongside PowerShell when discussing command line integration.
  • Provide examples for both Windows (PowerShell) and Linux (Bash/CLI) when demonstrating command line operations.
  • Clarify that Azure CLI is cross-platform and provide usage examples on both Windows and Linux.
  • Avoid listing PowerShell before CLI or Linux-native tools unless contextually relevant; strive for equal representation.
  • Add a section or note highlighting support for Linux environments and workflows.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/classic-retirement-faq.md ...blob/main/articles/frontdoor/classic-retirement-faq.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell for command-line migration instructions, mentioning PowerShell before any other automation or CLI tool, and not providing equivalent Linux/Unix shell or Azure CLI examples. There are no explicit Linux-specific instructions or parity in tooling guidance.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all command-line instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • When referencing automation or scripting, mention both PowerShell and Bash/Azure CLI options, or provide links to both sets of documentation.
  • Avoid listing PowerShell or Windows-centric tools first; instead, present cross-platform tools (like Azure CLI) before or alongside PowerShell.
  • Explicitly state that migration and management can be performed from Linux, macOS, and Windows, and provide relevant instructions for each.
  • Review all linked documentation (such as migration guides) to ensure Linux parity and add missing Linux/Bash examples where necessary.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-template.md .../main/articles/frontdoor/create-front-door-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing only Azure PowerShell examples for deploying and cleaning up resources, with no equivalent Azure CLI (cross-platform) or Bash examples. The deployment instructions and screenshots focus on PowerShell, which is more commonly used on Windows, and there is no mention of Linux-specific tools or patterns. Although the text briefly mentions that Azure CLI and REST API can be used, no examples or guidance are provided for those methods.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all deployment and cleanup steps.
  • Include Bash shell instructions for Linux/macOS users.
  • Present CLI and PowerShell examples side-by-side or in tabs, rather than only PowerShell.
  • Update screenshots and walkthroughs to include CLI output as well as PowerShell.
  • Explicitly mention platform parity and provide links to Linux/macOS setup guides for Azure CLI.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/front-door-cdn-comparison.md ...b/main/articles/frontdoor/front-door-cdn-comparison.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page mentions management via REST API, .NET, de.js, or PowerShell, but does not mention Linux-native tools (such as Azure CLI or Bash scripting) for service management. PowerShell is listed as a primary management method, which is more closely associated with Windows environments. There are no explicit Linux or cross-platform command examples, and Windows-oriented tooling is mentioned before any Linux equivalents (if any).
Recommendations
  • Add explicit references and examples for Azure CLI and Bash scripting for service management, alongside PowerShell.
  • Clarify that management can be performed from Linux, macOS, and Windows platforms, and provide parity in example commands.
  • List cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Include links to documentation for Linux/macOS usage and installation of management tools.
  • Ensure that all management scenarios (migration, configuration, monitoring) have both PowerShell and Azure CLI/Bash examples.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/migration-faq.md ...ure-docs/blob/main/articles/frontdoor/migration-faq.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell migration instructions in the 'Related content' section, while omitting equivalent examples or guidance for Linux users (e.g., Azure CLI or Bash). The ordering also places PowerShell before any mention of cross-platform tools, and there are no explicit Linux or cross-platform command-line examples provided.
Recommendations
  • Add migration instructions using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Ensure that references to command-line tools are not Windows-centric; mention Azure CLI and Bash scripts alongside PowerShell.
  • In 'Related content', provide links to both PowerShell and Azure CLI migration guides, and avoid listing PowerShell before CLI unless both are given equal prominence.
  • Explicitly state that migration steps can be performed from any OS and provide examples for both Windows and Linux environments.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/post-migration-dev-ops-experience.md ...rticles/frontdoor/post-migration-dev-ops-experience.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently listing Windows-centric tools (PowerShell, ARM templates via PowerShell, references to Windows installation paths) before or alongside cross-platform alternatives. PowerShell is given its own dedicated section, and links for installing Azure PowerShell specifically reference Windows. There is little mention of Linux-specific patterns, and examples or instructions for Linux environments (such as Bash scripting, Linux package managers, or WSL) are absent.
Recommendations
  • Add explicit Linux and macOS installation instructions for Azure CLI, Terraform, Bicep, and PowerShell (including references to package managers like apt, yum, brew, etc.).
  • Include Bash shell script examples alongside PowerShell examples for deployment automation.
  • Clarify that Azure CLI and Terraform are cross-platform and provide sample commands for Linux/macOS terminals.
  • Reference WSL for Windows users who may prefer a Linux-like environment.
  • Ensure that links to installation guides are not Windows-specific and mention platform parity.
  • Consider adding troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variables).
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/standard-premium/how-to-enable-private-link-apim.md ...or/standard-premium/how-to-enable-private-link-apim.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides three pivots: Azure Portal, PowerShell, and Azure CLI. The PowerShell section is extensive and detailed, with step-by-step instructions and code samples, reflecting a bias toward Windows-centric tooling. The PowerShell pivot is presented before the CLI pivot, and there is significant emphasis on Azure PowerShell and Cloud Shell, which are most commonly used on Windows. There is no mention of Linux-specific shell environments, nor are there any bash or shell script examples. The CLI instructions are present but less emphasized, and the documentation does not discuss Linux-specific considerations or parity.
Recommendations
  • Add explicit bash or shell script examples for Linux users, especially for Azure CLI commands.
  • Mention that Azure CLI can be installed and run natively on Linux and macOS, and provide links or instructions for those platforms.
  • Ensure that CLI instructions are as detailed and prominent as PowerShell instructions.
  • Include notes about using Azure Cloud Shell from Linux/macOS terminals, not just from the Azure Portal.
  • Consider reordering pivots or providing a neutral order (e.g., Portal, CLI, PowerShell) to avoid Windows-first impression.
  • Add troubleshooting or environment setup notes for Linux users where relevant.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/migrate-cdn-to-front-door.md ...b/main/articles/frontdoor/migrate-cdn-to-front-door.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. In the prerequisites, Windows tools (Invoke-WebRequest in PowerShell) are mentioned alongside Linux tools (wget), but Windows is listed second. However, throughout the guide, command-line examples and file paths (such as the hosts file location) are provided for both Windows and Linux. There is a slight emphasis on Windows-specific tools and patterns, such as referencing PowerShell and the Windows hosts file path, but Linux equivalents are generally included. No Linux-specific command-line examples (e.g., curl, dig usage) are shown, and monitoring tool recommendations are platform-neutral.
Recommendations
  • Provide explicit Linux command-line examples (e.g., show both wget and curl commands, and dig usage) alongside Windows examples.
  • When mentioning tools, list Linux and Windows options in parallel, rather than defaulting to Windows-first or Windows-only patterns.
  • Include Linux-specific troubleshooting steps or notes where relevant, such as permissions for editing /etc/hosts.
  • Ensure parity in example commands and screenshots for both platforms, especially for steps involving command-line or file system operations.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/origin-security.md ...e-docs/blob/main/articles/frontdoor/origin-security.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides configuration examples for several origin types, but the IIS example is Windows-specific and uses IIS configuration (XML), with no equivalent example for popular Linux web servers such as Apache or Nginx. The IIS example appears before the AKS NGINX controller example, and there is no mention of Linux tools or patterns for non-containerized Linux workloads. There are no shell or configuration examples for Linux-based VMs or web servers outside Kubernetes/NGINX. This demonstrates a Windows-first approach and a lack of Linux parity.
Recommendations
  • Add configuration examples for common Linux web servers such as Apache (httpd) and Nginx (standalone, not just AKS ingress), showing how to filter requests based on the X-Azure-FDID header.
  • Provide shell (bash) or configuration snippets for Linux VMs, such as using iptables or firewalld for IP filtering.
  • Ensure Linux examples appear alongside or before Windows/IIS examples to avoid Windows-first ordering.
  • Mention Linux-native tools and approaches (e.g., mod_security for Apache, Nginx configuration blocks) for header validation and access control.
  • Clarify that the guidance applies to both Windows and Linux origins, and link to platform-specific documentation where appropriate.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/private-link.md ...zure-docs/blob/main/articles/frontdoor/private-link.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell and Azure portal as primary management tools for approving private endpoint connections, with Azure CLI mentioned but not emphasized. There are no explicit Linux-specific examples or instructions, and no mention of Linux-native tools or patterns. The order of tools listed (portal, CLI, PowerShell) slightly favors Windows-centric approaches, and the lack of Linux command-line examples or troubleshooting steps further indicates a Windows bias.
Recommendations
  • Include explicit Linux-based examples using Azure CLI, especially for private endpoint approval and management.
  • Ensure parity in troubleshooting steps and error messages for both Windows and Linux environments.
  • List Azure CLI before PowerShell when mentioning management options, or clarify that CLI is cross-platform.
  • Add notes or links for Linux users regarding installation and usage of Azure CLI.
  • Where relevant, mention Linux-native networking tools or patterns for verifying connectivity.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/standard-premium/troubleshoot-compression.md ...frontdoor/standard-premium/troubleshoot-compression.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (Fiddler, IIS) and configuration steps for troubleshooting compression issues. There are no Linux or cross-platform command-line examples, and only Windows server (IIS) configuration is discussed for origin-side troubleshooting.
Recommendations
  • Include examples using cross-platform tools such as curl or wget to check HTTP headers for compression.
  • Mention Linux/Unix server equivalents (e.g., Apache, Nginx) and provide guidance or links for enabling and troubleshooting compression on those platforms.
  • When suggesting tools, list cross-platform or Linux tools (e.g., tcpdump, Wireshark, curl) alongside or before Windows-specific tools.
  • Provide configuration steps or references for common Linux web servers in the 'Check the request at the origin server' section.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/troubleshoot-issues.md ...cs/blob/main/articles/frontdoor/troubleshoot-issues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific troubleshooting tools (Fiddler, browser developer tools) without mentioning Linux alternatives, and by listing these tools before any cross-platform or Linux-native options. The only explicit command-line example provided is for OpenSSL, which is cross-platform, but there are no Linux-specific troubleshooting workflows or tool recommendations. No PowerShell-heavy bias is present, but the lack of Linux parity in examples and tool mentions is evident.
Recommendations
  • Include Linux-native troubleshooting tools such as curl, wget, tcpdump, or Wireshark alongside Fiddler and browser developer tools.
  • Provide example commands for inspecting HTTP headers and SSL certificates using Linux CLI tools (e.g., curl -I, openssl, wget).
  • Explicitly mention that browser developer tools are available on Linux browsers (e.g., Firefox, Chrome) and provide guidance for their use.
  • Add troubleshooting steps using Linux terminal commands for common scenarios (e.g., checking response headers, simulating requests).
  • When listing tools, present cross-platform or Linux options first or in parallel with Windows tools.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/tier-migration.md ...re-docs/blob/main/articles/frontdoor/tier-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell and CLI before other automation tools, and by providing a dedicated migration guide for PowerShell but not for Linux-specific tools or shell environments. There is no explicit example or guidance for Linux users (e.g., Bash, shell scripts), and the DevOps section prioritizes PowerShell and CLI commands, which are more commonly associated with Windows environments.
Recommendations
  • Add explicit migration instructions and examples for Linux users, such as Bash scripts or Azure CLI usage in a Linux shell.
  • Provide parity in 'Related content' by including links to migration guides using Azure CLI and Terraform, not just PowerShell.
  • When listing automation tools (PowerShell, CLI, API, Terraform), avoid listing PowerShell first or exclusively; ensure equal coverage and ordering.
  • Include notes or examples for both Windows and Linux environments where command-line operations are discussed.
  • Clarify that Azure CLI is cross-platform and provide examples for both Windows (CMD/PowerShell) and Linux (Bash/zsh) usage.
GitHub Create Pull Request
← Previous Page 2 of 6 Next →