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 76-100 of 130 flagged pages
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the prerequisites, Windows tooling (Invoke-WebRequest in PowerShell) is mentioned alongside Linux (wget), but Windows is listed second. However, in the hosts file editing instructions, the Windows path is given before the Linux path, and the instructions are more detailed for Windows. The documentation references Windows-specific tools (PowerShell, Windows hosts file path) and patterns, and provides more explicit guidance for Windows users. There are no Linux-specific command examples beyond mentioning wget and the Linux hosts file path. No Bash or Linux-native command-line examples are provided for other steps.
Recommendations
  • When mentioning command-line tools, provide both Windows (PowerShell/CMD) and Linux (Bash) examples side by side, and in equal detail.
  • List Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
  • For hosts file editing, provide explicit editing instructions for both Linux and Windows, including example commands (e.g., using sudo nano /etc/hosts for Linux).
  • Include Linux-native command examples for steps such as DNS lookups (e.g., dig, host, nslookup) and file editing.
  • When referencing tools, mention cross-platform or Linux alternatives where possible, and avoid assuming the user is on Windows.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references Azure PowerShell and CLI for migration but does not provide any explicit Linux or cross-platform examples. The 'Next steps' section specifically links to a PowerShell-based migration guide, and throughout the document, PowerShell is mentioned before CLI, API, and Terraform. There are no Linux shell or Bash examples, nor is there mention of Linux-specific tools or workflows. This may create a perception that Windows/PowerShell is the primary or preferred platform for managing Azure Front Door migrations.
Recommendations
  • Provide explicit Bash/Azure CLI examples for migration steps, especially in the 'Next steps' section.
  • Ensure that CLI commands are given equal prominence to PowerShell, and consider mentioning CLI before PowerShell to avoid 'windows_first' ordering.
  • Include links to Linux/macOS-compatible migration guides or scripts.
  • Add a note clarifying that Azure CLI and Terraform are fully cross-platform and suitable for Linux/macOS users.
  • Where scripts or automation are discussed, provide both PowerShell and Bash/CLI equivalents.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/troubleshoot-performance-issues.md .../articles/frontdoor/troubleshoot-performance-issues.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing and providing examples for Windows-native network troubleshooting tools (tracert, pathping) and omitting Linux/macOS equivalents (such as traceroute, mtr). The instructions and command-line examples for network path analysis are tailored to Windows users, with no parallel guidance for users on Linux or macOS platforms.
Recommendations
  • Include Linux/macOS equivalents for all Windows-specific tools mentioned (e.g., mention 'traceroute' and 'mtr' alongside 'tracert' and 'pathping').
  • Provide example commands for Linux/macOS users wherever Windows command-line examples are given.
  • When referencing tools, use platform-neutral language (e.g., 'use a network path analysis tool such as tracert (Windows), traceroute (Linux/macOS), or mtr').
  • Consider providing a table or section summarizing equivalent commands for common platforms.
  • Ensure that troubleshooting steps are inclusive and actionable for users on all major operating systems.
GitHub Create Pull Request
Frontdoor Azure Front Door (classic) retirement FAQ ...blob/main/articles/frontdoor/classic-retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page frequently references Azure PowerShell as the primary or sole command-line migration method, with no mention of Linux/macOS alternatives such as Azure CLI or Bash scripts. In several places, PowerShell is listed before or instead of cross-platform tools, and migration instructions link only to PowerShell-based guides. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add Azure CLI examples and migration guides alongside PowerShell instructions.
  • Explicitly mention that Azure CLI and Bash scripts can be used for migration and management tasks.
  • Ensure links to migration documentation include both PowerShell and CLI/Bash options.
  • Present cross-platform tools (Azure CLI, Terraform) before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Frontdoor Quickstart: Create an Azure Front Door using an ARM template .../main/articles/frontdoor/create-front-door-template.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily provides Azure PowerShell examples for deploying and cleaning up resources, with step-by-step instructions tailored to PowerShell and Cloud Shell. There are no equivalent Azure CLI or Bash examples, and PowerShell is presented as the main method, which may disadvantage Linux/macOS users who typically use Bash or Azure CLI.
Recommendations
  • Add Azure CLI (az) examples for all deployment and cleanup steps alongside PowerShell.
  • Present both PowerShell and CLI examples in parallel, or allow users to select their preferred shell.
  • Explicitly mention that Cloud Shell supports Bash and provide instructions for both Bash and PowerShell.
  • Ensure screenshots and output samples are not PowerShell-specific, or provide CLI equivalents.
GitHub Create Pull Request
Frontdoor Secure traffic to origins ...e-docs/blob/main/articles/frontdoor/origin-security.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides platform-specific configuration examples for several origin types. While most examples are platform-neutral (App Service, Application Gateway, AKS NGINX), the IIS example is Windows-specific and uses IIS configuration syntax. The IIS example is presented before the AKS NGINX example, and there is no equivalent example for common Linux web servers such as Apache or Nginx outside AKS. This creates a mild Windows bias, especially for users running Linux-based web servers outside Kubernetes.
Recommendations
  • Add example configurations for popular Linux web servers (e.g., Apache, Nginx) showing how to filter requests based on the X-Azure-FDID header.
  • Ensure that Linux-origin examples (outside AKS) are presented alongside or before Windows/IIS examples to avoid Windows-first ordering.
  • Explicitly mention that the IIS example is for Windows and suggest Linux alternatives.
  • Consider including PowerShell or Windows command-line examples only when Linux equivalents are also provided.
GitHub Create Pull Request
Frontdoor Post Migration Dev-Ops Experience ...rticles/frontdoor/post-migration-dev-ops-experience.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides guidance for updating DevOps pipelines post-migration to Azure Front Door Standard/Premium. While most sections are cross-platform (Terraform, ARM, Bicep, CLI), there is a notable emphasis on Windows-centric tools, especially PowerShell. PowerShell is given its own dedicated section with detailed instructions, while Linux/macOS equivalents (such as Bash scripting or cross-platform automation) are not mentioned. Additionally, links for installing Azure PowerShell specifically reference Windows, and PowerShell is listed before CLI in some contexts, suggesting a Windows-first approach.
Recommendations
  • Add explicit examples and guidance for Linux/macOS users, such as Bash scripts or shell automation for deployment tasks.
  • Ensure installation links for Azure PowerShell and CLI reference cross-platform instructions, not just Windows.
  • Balance the prominence of PowerShell and CLI sections, possibly merging them or presenting CLI first to reflect its cross-platform nature.
  • Include notes or examples for using Azure DevOps or GitHub Actions runners on Linux/macOS.
  • Where PowerShell is referenced, clarify that Azure CLI is fully supported and provide parallel examples.
GitHub Create Pull Request
Frontdoor Troubleshoot File Compression ...frontdoor/standard-premium/troubleshoot-compression.md
Medium Priority View Details →
Scanned: 2026-01-14 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-only tools (Fiddler, IIS), providing configuration instructions exclusively for Microsoft IIS (a Windows server), and omitting Linux equivalents or examples. Troubleshooting steps and server configuration guidance are focused on Windows environments, with no mention of how to check or configure compression on common Linux web servers (e.g., Apache, Nginx).
Recommendations
  • Include Linux-based troubleshooting examples, such as using curl or wget to inspect HTTP headers.
  • Mention cross-platform tools (e.g., Wireshark, curl) alongside or before Windows-specific tools like Fiddler.
  • Provide guidance for configuring compression on popular Linux web servers (Apache, Nginx), including how to handle proxy headers.
  • Add notes or links for macOS users where relevant.
GitHub Create Pull Request
Frontdoor Azure Front Door (Classic) To Standard/Premium Tier Migration ...re-docs/blob/main/articles/frontdoor/tier-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell, CLI, API, and Terraform as migration tools, but only provides a direct link to a PowerShell-based migration guide. The 'Related content' section lists the PowerShell migration guide explicitly, while CLI and Terraform are mentioned only in passing, with no dedicated migration instructions or examples. There are no Linux/macOS-specific instructions or examples, and Windows tools (PowerShell) are prioritized in guidance and links.
Recommendations
  • Add explicit migration guides and examples for Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include Terraform-based migration instructions or link to relevant resources.
  • Ensure that all command-line examples are provided for both PowerShell and CLI, with CLI examples shown first or side-by-side.
  • Clarify that migration can be performed from any OS and highlight platform-agnostic tools.
  • Avoid listing PowerShell migration as the only example in 'Related content'; add parity for CLI and Terraform.
GitHub Create Pull Request
Frontdoor Settings mapping between Azure Front Door (classic) and Standard/Premium tier ...zure-docs/blob/main/articles/frontdoor/tier-mapping.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page mentions Azure PowerShell as a migration method in the 'Next steps' section, but does not mention Azure CLI or Bash/Linux alternatives. This prioritizes Windows tooling and may create friction for Linux/macOS users who prefer or require cross-platform tools.
Recommendations
  • Add references to Azure CLI migration guides alongside Azure PowerShell.
  • Explicitly mention that migration can be performed using Bash or on Linux/macOS platforms.
  • Ensure that examples and links for both PowerShell and CLI are provided in parallel, with equal prominence.
GitHub Create Pull Request
Frontdoor Azure Front Door (classic) retirement FAQ ...blob/main/articles/frontdoor/classic-retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell as a primary migration method and links to PowerShell-specific instructions, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash scripts). Windows-centric tools and terminology are presented before cross-platform options, and Linux/macOS users are not given parity in migration guidance.
Recommendations
  • Include Azure CLI examples and migration guides alongside PowerShell instructions.
  • Explicitly mention that migration can be performed from Linux/macOS using Azure CLI or REST API.
  • Provide links to cross-platform documentation and scripts.
  • Ensure that all tooling references (e.g., for certificate management) include Linux/macOS-compatible options.
GitHub Create Pull Request
Frontdoor Quickstart: Create an Azure Front Door using an ARM template .../main/articles/frontdoor/create-front-door-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only Azure PowerShell examples for deploying and cleaning up resources, with no equivalent Azure CLI or Bash examples. The deployment walkthrough is written entirely around PowerShell, which is most familiar to Windows users, and the screenshots and instructions reference PowerShell output. While the page mentions that other methods (CLI, portal, REST API) exist, it does not provide concrete examples or guidance for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all deployment and cleanup steps.
  • Include Bash shell instructions and sample commands for Linux/macOS users.
  • Alternate the order of examples, or present CLI and PowerShell side-by-side.
  • Provide screenshots or output examples from CLI/Bash in addition to PowerShell.
  • Explicitly mention platform parity and link to cross-platform instructions.
GitHub Create Pull Request
Frontdoor Migration FAQ ...ure-docs/blob/main/articles/frontdoor/migration-faq.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell specifically for migration tasks and lists the PowerShell method before any mention of Linux/macOS-friendly alternatives (such as Azure CLI or Bash). There are no examples or guidance for Linux/macOS users, and PowerShell is a Windows-centric tool, though it is available cross-platform. The absence of explicit Linux/macOS instructions or CLI examples creates friction for non-Windows users.
Recommendations
  • Add Azure CLI and/or Bash examples for migration tasks alongside PowerShell instructions.
  • Explicitly mention that PowerShell is available cross-platform, but also provide parity for Linux/macOS users.
  • Ensure that links to migration guides include both PowerShell and CLI/Bash options, and present them with equal prominence.
  • Consider listing platform-agnostic methods (Azure portal, CLI) before platform-specific ones.
GitHub Create Pull Request
Frontdoor Post Migration Dev-Ops Experience ...rticles/frontdoor/post-migration-dev-ops-experience.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples and guidance for both Windows (PowerShell) and cross-platform (Azure CLI, Terraform, Bicep) tools. However, there is a noticeable emphasis on PowerShell, including a dedicated section, prerequisite links that point to Windows-specific installation guides, and references to PowerShell modules. In several places, PowerShell is mentioned before CLI alternatives, and the PowerShell section is more detailed than the CLI section. Some links (e.g., 'Install Azure PowerShell') default to Windows instructions, and there are no explicit Linux/macOS PowerShell installation notes or examples.
Recommendations
  • Add explicit Linux/macOS installation instructions and links for Azure PowerShell.
  • Ensure parity in example depth and detail between PowerShell and Azure CLI sections.
  • Where PowerShell is mentioned, also mention cross-platform alternatives (e.g., Azure CLI) and clarify OS compatibility.
  • Avoid defaulting to Windows-centric links; use cross-platform documentation pages where possible.
  • Consider listing CLI examples before PowerShell, or side-by-side, to avoid implicit prioritization.
GitHub Create Pull Request
Frontdoor Secure traffic to origins ...e-docs/blob/main/articles/frontdoor/origin-security.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides platform-specific configuration examples for several origin types. Notably, the IIS example is detailed and uses Windows-centric tooling (IIS configuration XML), while there is no equivalent example for common Linux web servers such as Apache or Nginx (outside of AKS NGINX controller, which is Kubernetes-specific). The IIS example appears before the AKS NGINX controller example, suggesting a slight ordering bias. There are no PowerShell-only instructions, but the lack of direct Linux web server examples (e.g., Apache, standalone Nginx) may create friction for Linux users hosting origins outside Kubernetes.
Recommendations
  • Add configuration examples for popular Linux web servers such as Apache (httpd) and standalone Nginx (outside AKS), showing how to filter requests based on the X-Azure-FDID header.
  • Ensure ordering of examples alternates or groups by platform, or explicitly states parity between Windows and Linux approaches.
  • Reference Linux-native tools (e.g., iptables, firewalld) for IP filtering alongside network security group rules.
  • Clarify that the IIS example is for Windows and provide links or guidance for equivalent Linux scenarios.
GitHub Create Pull Request
Frontdoor Troubleshoot File Compression ...frontdoor/standard-premium/troubleshoot-compression.md
Medium Priority View Details →
Scanned: 2026-01-13 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-centric tools (Fiddler, IIS), providing configuration steps only for Microsoft IIS servers, and omitting Linux or cross-platform equivalents for origin server compression troubleshooting. No Linux/Apache/Nginx examples or references are given, and Windows tools are mentioned first and exclusively.
Recommendations
  • Include troubleshooting steps for popular Linux web servers such as Apache (mod_deflate) and Nginx (gzip module), detailing how to handle proxy headers and compression settings.
  • Suggest cross-platform tools for inspecting HTTP headers, such as curl, httpie, or command-line utilities, alongside Fiddler.
  • Add examples or links for configuring compression on Linux-based origins and how they handle the Via header.
  • Present browser developer tools and cross-platform command-line tools before or alongside Windows-specific tools.
GitHub Create Pull Request
Frontdoor Azure Front Door (Classic) To Standard/Premium Tier Migration ...re-docs/blob/main/articles/frontdoor/tier-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell and CLI for migration, but the 'Related content' section only provides a migration guide for Azure PowerShell, omitting Linux/macOS-friendly tools and examples (such as Azure CLI or Terraform). Windows-centric tools (PowerShell) are mentioned before CLI and API in the DevOps section, and no explicit Linux/macOS instructions or parity are provided.
Recommendations
  • Add explicit migration instructions and examples using Azure CLI, which is cross-platform and preferred by many Linux/macOS users.
  • Include Terraform migration guidance, as Terraform is widely used for infrastructure automation across platforms.
  • Ensure that all referenced guides (in 'Related content') include both PowerShell and CLI/Terraform options, or link to equivalent Linux/macOS-friendly documentation.
  • When listing tools or scripting options (e.g., in DevOps), mention CLI and API before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Frontdoor Azure Front Door (classic) overview ...-docs/blob/main/articles/frontdoor/classic-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page references certificate management migration and links to a 'Bring Your Own Certificate (BYOC)' guide that is explicitly tagged with 'tabs=powershell', suggesting a Windows/Powershell-centric approach. There are no explicit Linux or cross-platform CLI examples or references, and no mention of Linux tools or patterns for certificate management or other operational tasks. This may create a perception that Windows is the preferred or only supported platform for certain administrative actions.
Recommendations
  • Ensure that all linked guides (such as BYOC for Front Door) provide both Powershell and Azure CLI (cross-platform) instructions, and reference Bash/Linux usage where relevant.
  • Add explicit examples or notes for Linux users, such as using Azure CLI in Bash, or certificate management with OpenSSL.
  • Avoid using only 'tabs=powershell' in documentation links; use 'tabs=azure-cli,powershell' or provide platform-neutral instructions.
  • Where administrative tasks are described, mention both Windows and Linux workflows/tools to ensure parity.
GitHub Create Pull Request
Frontdoor Azure Front Door (classic) overview ...-docs/blob/main/articles/frontdoor/classic-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, notably in its use of links that default to PowerShell examples (e.g., certificate management tabs), and a lack of explicit Linux or cross-platform command-line examples. The referenced migration and certificate management guides prioritize PowerShell, which is predominantly a Windows tool, and do not mention Linux alternatives or parity.
Recommendations
  • Ensure that all command-line instructions and code samples are provided for both PowerShell (Windows) and Bash/CLI (Linux/macOS) environments.
  • Where links reference tabs or pivots (e.g., 'tabs=powershell'), also provide direct links or notes for Linux/CLI equivalents.
  • Explicitly mention cross-platform support and tools in migration and certificate management sections, including Azure CLI and REST API usage.
  • Review all referenced articles for similar bias and update them to include Linux and macOS instructions where applicable.
GitHub Create Pull Request
Frontdoor Migrate Azure CDN from Edgio to Azure Front Door ...b/main/articles/frontdoor/migrate-cdn-to-front-door.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows tools (Invoke-WebRequest via PowerShell) before Linux equivalents (Wget), and referencing Windows file paths before Linux paths in the hosts file modification section. The only command-line example given for HTTP header retrieval is 'wget' (Linux) or 'Invoke-WebRequest' (Windows PowerShell), but no Linux shell or cross-platform examples are shown for other steps. The instructions for editing the hosts file mention Windows first, then Linux, and provide explicit Windows paths. No Linux shell or cross-platform automation examples are provided for Azure resource creation or DNS testing, and Azure CLI or Bash examples are absent.
Recommendations
  • Present Linux and Windows tools in parallel, or list Linux tools first to balance representation.
  • Provide Azure CLI and Bash examples for resource creation and DNS testing, alongside PowerShell and portal instructions.
  • Include Linux shell commands (e.g., curl, dig, nslookup) in all relevant steps, not just Windows equivalents.
  • Reference Linux file paths before or alongside Windows paths when discussing hosts file modifications.
  • Add explicit Linux examples for HTTP header retrieval (e.g., 'curl -I'), and for modifying the hosts file (e.g., using 'sudo nano /etc/hosts').
  • Where possible, use cross-platform tools and commands, or note platform-specific differences clearly.
GitHub Create Pull Request
Frontdoor Settings mapping between Azure Front Door (classic) and Standard/Premium tier ...zure-docs/blob/main/articles/frontdoor/tier-mapping.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page references Azure PowerShell as a migration method in the 'Next steps' section, without mentioning Linux-friendly alternatives such as Azure CLI or REST API. This suggests a Windows-first and PowerShell-heavy bias, as PowerShell is primarily associated with Windows environments, even though it is available cross-platform. No Linux-specific tools or examples are provided, and PowerShell is listed before any other automation or scripting options.
Recommendations
  • Include Azure CLI instructions and links alongside PowerShell for migration tasks.
  • Mention REST API or ARM template options for automation, which are platform-agnostic.
  • Ensure that scripting and automation examples are provided for both Windows and Linux users.
  • Avoid listing Windows-centric tools (like PowerShell) before cross-platform alternatives unless justified by usage data.
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
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 exhibits subtle Windows bias by referencing certificate management migration with a link that specifically points to a Powershell tab ("tabs=powershell") for Bring Your Own Certificate (BYOC). No Linux or cross-platform CLI examples are mentioned or linked, and there is no indication of parity for Linux users in certificate management or automation. The documentation does not provide examples or guidance for Linux tools or workflows, and the only explicit tooling reference is Windows-centric.
Recommendations
  • Ensure that all linked guides (such as BYOC) include both Powershell and Azure CLI/Bash examples, and link to a neutral tab or provide clear navigation for Linux users.
  • Explicitly mention cross-platform tooling (e.g., Azure CLI, Bash scripts) alongside Powershell in migration and management scenarios.
  • Add examples or references for certificate management and automation using Linux-native tools and workflows.
  • Review all documentation links for platform-specific bias and update them to ensure equal visibility and support for Linux users.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/end-to-end-tls.md ...re-docs/blob/main/articles/frontdoor/end-to-end-tls.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 subtle Windows bias, most notably in the section discussing supported cipher suites. Recommendations for cipher suite selection are given specifically for Windows operating systems (Windows 10, 8.1, 8, 7), with no mention of Linux or other platforms. No Linux-specific examples, tools, or compatibility notes are provided throughout the page, and Windows is the only OS referenced in client compatibility guidance.
Recommendations
  • Add compatibility notes for common Linux distributions (e.g., Ubuntu, CentOS) and their default TLS/cipher suite support.
  • Include Linux-specific recommendations for cipher suite selection and configuration, referencing popular web servers (e.g., Apache, Nginx) and how to enable/verify supported ciphers.
  • Provide example commands for checking TLS/cipher suite support on Linux (e.g., using openssl or nmap).
  • Mention macOS and other platforms where relevant, to ensure broader cross-platform parity.
  • When giving OS-specific recommendations, present Windows and Linux guidance together, or in parallel, rather than Windows-only or Windows-first.
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
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 mentions Azure PowerShell as a method for approving private endpoint connections alongside Azure CLI and Azure Portal, but does not provide any explicit examples or guidance for Linux users. There are no command-line examples shown, but the order of mention (Azure CLI, Azure PowerShell) and lack of Linux-specific instructions or parity in tooling may suggest a subtle Windows-first bias. No Linux tools, shell commands, or platform-specific considerations are discussed.
Recommendations
  • Provide explicit command-line examples for both Azure CLI and Azure PowerShell, and clarify platform compatibility (e.g., show CLI commands that work on Linux/macOS).
  • When listing tools, mention Azure CLI first and clarify that it is cross-platform, while Azure PowerShell is available on Windows, Linux, and macOS.
  • Add notes or sections for Linux users, such as how to install Azure CLI or PowerShell on Linux, and any platform-specific caveats.
  • Ensure that any referenced scripts or automation steps include both Bash (Linux/macOS) and PowerShell (Windows) examples where relevant.
  • Review related content and linked articles to ensure Linux parity in examples and troubleshooting steps.
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
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 configuration examples for multiple origin types, but the IIS (Windows) example appears before the AKS NGINX (Linux) example, and includes detailed configuration using Windows-specific tooling (IIS rewrite rules). There is no equivalent example for Apache or other common Linux web servers. The Application Gateway and AKS examples are platform-neutral or cloud-native, but the only explicit OS-specific example is for Windows (IIS), with no parity for Linux web servers.
Recommendations
  • Add example configurations for popular Linux web servers, such as Apache (httpd) and NGINX (standalone, not just AKS ingress), showing how to filter the X-Azure-FDID header.
  • Present OS-specific examples (Windows/IIS and Linux/Apache/NGINX) in parallel tabs or sections, rather than listing Windows first.
  • Ensure that Linux tools and patterns are mentioned with equal prominence and detail as Windows tools.
  • Consider including shell or configuration snippets for Linux environments (e.g., iptables, firewalld, or UFW for IP filtering) alongside network security group examples.
GitHub Create Pull Request
← Previous Page 4 of 6 Next →