Frontdoor

208
Total Pages
192
Linux-Friendly Pages
16
Pages with Bias
7.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

41 issues found
Showing 1-25 of 41 flagged pages
Frontdoor Azure Front Door ...cs/blob/main/articles/frontdoor/front-door-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions integration with 'DevOps friendly command line tools across SDKs of different languages, Bicep, ARM templates, CLI, and PowerShell.' PowerShell is called out specifically, which is traditionally a Windows-centric tool, and there is no mention of Linux/macOS equivalents or shell environments (e.g., Bash). No examples or instructions are provided for Linux/macOS users, and Windows tools are referenced without parity for other platforms.
Recommendations
  • Explicitly mention support for Bash, Azure CLI, and scripting on Linux/macOS alongside PowerShell.
  • Provide example commands for both PowerShell and Bash/Azure CLI where relevant.
  • Clarify cross-platform compatibility for DevOps tools and automation scripts.
  • Add a section or note highlighting how Linux/macOS users can perform the same tasks.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page repeatedly references Azure PowerShell as the primary command-line tool for migration and management tasks, with no mention of Linux/macOS equivalents such as Azure CLI or Bash scripting. Where command-line instructions are referenced, only PowerShell is mentioned, and links use 'tabs=powershell'. This creates friction for Linux/macOS users who may prefer or require non-Windows tooling.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all command-line instructions.
  • When linking to guides, use tabs or sections for both PowerShell and Azure CLI/Bash, not just PowerShell.
  • Explicitly mention that migration and management tasks can be performed on Linux/macOS using Azure CLI.
  • Ensure that references to command-line tools do not assume a Windows environment by default.
GitHub Create Pull Request
Frontdoor Endpoints in Azure Front Door ...cs/azure-docs/blob/main/articles/frontdoor/endpoint.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring endpoint domain reuse, but the PowerShell example is given equal prominence to the CLI example, and no explicit Linux/macOS shell example (e.g., Bash) is provided. The CLI example is cross-platform, but the presence of a PowerShell example (which is traditionally Windows-centric) without a corresponding Bash or Linux shell script may create friction for Linux/macOS users. There is no mention of platform-specific differences or guidance for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples or note that the Azure CLI example works on Linux/macOS.
  • If PowerShell is shown, consider also showing Bash or other Linux-native scripting examples for parity.
  • Add a note about platform compatibility for each example.
GitHub Create Pull Request
Frontdoor Migration FAQ ...ure-docs/blob/main/articles/frontdoor/migration-faq.md
Medium Priority View Details →
Scanned: 2026-01-12 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 for migration tasks and lists it as a primary method, but does not mention cross-platform alternatives such as Azure CLI or provide Linux/macOS-specific guidance. The related content links prioritize PowerShell and portal-based instructions, which may create friction for Linux/macOS users who prefer or require CLI-based workflows.
Recommendations
  • Add migration instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly state that Azure PowerShell is available on Linux/macOS, or provide installation guidance for non-Windows platforms.
  • Ensure that examples and guidance are not Windows-centric; include bash and CLI examples alongside PowerShell.
  • In related content, link to Azure CLI migration documentation if available, or create such documentation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for deploying and cleaning up resources, with no equivalent Azure CLI or Bash examples. The step-by-step instructions and screenshots are PowerShell-centric, and Linux/macOS users are not shown how to perform these tasks in their native environments. Although a brief mention is made that other methods exist, no actionable guidance or examples are provided for those platforms.
Recommendations
  • Add equivalent Azure CLI (az) examples for deployment and cleanup, with Bash syntax.
  • Include instructions and screenshots for using Azure Cloud Shell in Bash mode.
  • Present both PowerShell and CLI examples side-by-side or indicate which is suitable for Windows, Linux, and macOS.
  • Explicitly mention platform compatibility for each method.
  • Consider showing CLI examples first or equally to avoid Windows-first bias.
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-12 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. The IIS example is Windows-specific and uses IIS configuration files, while Linux equivalents (such as Apache or NGINX outside AKS) are not mentioned. The IIS example appears before the AKS NGINX controller example, suggesting a Windows-first ordering. There are no examples for popular Linux web servers like Apache or generic NGINX outside Kubernetes, which may leave Linux users without direct guidance.
Recommendations
  • Add configuration examples for Apache (httpd) and standalone NGINX (outside AKS) to show how to filter the X-Azure-FDID header.
  • Consider reordering examples so that Linux-origin examples (NGINX, Apache) are presented before or alongside IIS.
  • Explicitly mention Linux and macOS options/tools where relevant, and provide parity in instructions for configuring network security and header filtering.
  • Include a note that the IIS example is for Windows and provide links or guidance for equivalent Linux setups.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the prominence and detail of PowerShell instructions and references to Windows-specific installation guides. PowerShell is given its own dedicated section, while Linux/macOS equivalents (such as Bash scripting) are not mentioned. Installation links for PowerShell and CLI tools often point to Windows-specific pages first. ARM template export instructions list Azure PowerShell before Azure CLI, and the PowerShell section is more detailed than the CLI section.
Recommendations
  • Add explicit examples and guidance for Linux/macOS users, such as Bash or shell scripting alternatives to PowerShell.
  • Ensure installation instructions for CLI tools (Terraform, Azure CLI, Bicep) include Linux/macOS steps and links, not just Windows.
  • Balance the prominence of PowerShell and CLI sections, providing equal detail and examples for both.
  • In ARM template export instructions, list Azure CLI before PowerShell or present both equally.
  • Where possible, use cross-platform commands (Azure CLI, Terraform) as primary examples, with PowerShell as an alternative.
GitHub Create Pull Request
Frontdoor Troubleshoot File Compression ...frontdoor/standard-premium/troubleshoot-compression.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exclusively mentioning Windows-specific tools (Fiddler, IIS), providing configuration steps only for Microsoft IIS (Windows web server), and omitting Linux equivalents (such as Apache or Nginx). No Linux/macOS command-line or server configuration examples are given, and Windows tools are referenced before generic browser tools.
Recommendations
  • Include Linux server examples, such as how to configure compression for Apache (mod_deflate) and Nginx.
  • Mention cross-platform tools like curl or wget for checking HTTP headers, with example commands.
  • Reference Linux/macOS browser developer tools equivalently, and avoid listing Windows tools first.
  • Provide troubleshooting steps for common Linux web servers when discussing proxy/compression issues.
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-12 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/macOS equivalents (such as Azure CLI or Bash scripting). The ordering places PowerShell before any cross-platform tooling, and no explicit Linux/macOS instructions or examples are provided.
Recommendations
  • Add Azure CLI migration instructions and links alongside PowerShell, as Azure CLI is cross-platform.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or clarify platform requirements.
  • Ensure examples and migration guides are available for both Windows (PowerShell) and Linux/macOS (CLI/Bash).
  • Consider listing cross-platform tools (Azure CLI) before or alongside Windows-specific tools.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for deploying and cleaning up resources, with no equivalent Azure CLI or Bash examples. The deployment instructions and screenshots are PowerShell-centric, and Linux/macOS users are not given direct guidance or code samples for their platforms. While alternative methods are mentioned, they are not demonstrated, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for deployment and cleanup steps.
  • Show both PowerShell and Bash/CLI code blocks, or provide tabs for users to select their preferred environment.
  • Include screenshots or output examples from CLI/Bash in addition to PowerShell.
  • Explicitly mention and link to Linux/macOS setup guides for Azure CLI.
  • Reorder or parallelize instructions so Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Frontdoor Migration FAQ ...ure-docs/blob/main/articles/frontdoor/migration-faq.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell for migration steps and links to a PowerShell-specific guide, but does not mention or provide equivalent examples for Azure CLI or Bash, which are preferred on Linux/macOS. The portal-based instructions are platform-neutral, but scripting guidance is Windows-centric.
Recommendations
  • Add migration instructions using Azure CLI or Bash scripts alongside PowerShell examples.
  • Explicitly mention cross-platform tools (Azure CLI) in the 'Related content' section.
  • Ensure scripting examples are provided for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
  • Clarify that portal-based steps are platform-agnostic.
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-11 06:20
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 a primary migration method and links to PowerShell-specific instructions, with no mention of Azure CLI, Bash, or Linux/macOS-specific examples. The migration steps and certificate management guidance are Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples and links alongside PowerShell instructions for migration and certificate management.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, Terraform) where relevant.
  • Ensure that all command-line instructions are available for both Windows and Linux/macOS environments.
  • Provide parity in documentation structure, listing Linux/macOS options before or alongside Windows options.
GitHub Create Pull Request
Frontdoor Azure Front Door ...cs/blob/main/articles/frontdoor/front-door-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell as a primary command line tool for DevOps integration before listing other options, and does not explicitly reference Linux/macOS equivalents (such as Bash or Azure CLI) in the same context. Examples and tooling references are Windows-centric, with PowerShell highlighted and no Linux/macOS-specific instructions or examples provided.
Recommendations
  • Explicitly mention Azure CLI and Bash as supported and recommended tools for Linux/macOS users alongside PowerShell.
  • Provide example commands for both PowerShell and Azure CLI/Bash where command line usage is discussed.
  • Add a note clarifying cross-platform support and linking to platform-specific setup guides.
  • Ensure that future documentation sections include Linux/macOS examples and tool references in parallel with Windows/PowerShell.
GitHub Create Pull Request
Frontdoor Support for wildcard domains .../main/articles/frontdoor/front-door-wildcard-domain.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation references Azure Resource Manager API, Bicep, PowerShell, and Azure CLI as tools for configuring wildcard domains, but does not provide any examples or guidance for Linux/macOS users. PowerShell is mentioned as a primary tool, which is traditionally Windows-centric, and there is no mention of Bash, shell scripts, or Linux-specific usage patterns. No explicit Linux/macOS examples or parity guidance are present.
Recommendations
  • Provide explicit examples using Azure CLI commands in Bash or shell environments, which are cross-platform and preferred on Linux/macOS.
  • Clarify that PowerShell Core is available cross-platform, or provide equivalent Bash/shell scripts for common tasks.
  • Add a note or section outlining Linux/macOS setup steps, including any prerequisites or differences in workflow.
  • Ensure that all tooling references (e.g., PowerShell, Azure CLI) are presented in a platform-neutral order, or with equal prominence.
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-11 06:20
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 Windows-specific and uses IIS configuration files, while there is no equivalent example for popular Linux web servers such as Apache or Nginx (outside of AKS NGINX controller, which is Kubernetes-focused). The IIS example is presented before the AKS NGINX controller example, indicating a mild 'Windows first' bias. There are no PowerShell-heavy sections, and most instructions are platform-neutral or Azure-focused, but the lack of direct Linux web server examples is a gap.
Recommendations
  • Add configuration examples for common Linux web servers such as Apache (httpd) and standalone Nginx (outside of AKS), showing how to filter requests based on the X-Azure-FDID header.
  • Ensure that Linux-origin examples are presented alongside Windows-origin examples, ideally in parallel tabs or sections.
  • Reference Linux tools and configuration patterns where appropriate, not just Windows/IIS.
  • Consider the order of examples to avoid implicit prioritization of Windows tools.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides guidance for updating DevOps pipelines after migrating Azure Front Door/CDN resources. While it covers multiple tools (Terraform, ARM templates, Bicep, PowerShell, Azure CLI), there is a notable emphasis on PowerShell, including a dedicated section and prerequisite links that point to Windows-specific installation guides. PowerShell examples and references are more detailed than those for Azure CLI, and PowerShell is mentioned before CLI in the ARM template export options. The PowerShell section links only to Windows installation instructions, and there is no mention of Linux/macOS compatibility or alternatives for scripting tasks. This creates friction for Linux/macOS users, especially those who do not use PowerShell.
Recommendations
  • Add explicit instructions and links for installing and using Azure PowerShell on Linux/macOS.
  • Ensure all PowerShell examples are accompanied by equivalent Azure CLI examples, especially for resource management and deployment tasks.
  • When listing export options (e.g., for ARM templates), present Azure CLI before or alongside PowerShell, and clarify cross-platform support.
  • Include notes or sections highlighting Linux/macOS compatibility for all tools, and avoid linking only to Windows-specific installation guides.
  • Consider adding Bash script examples for pipeline automation where relevant.
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-11 06:20
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 CLI or Bash/Linux alternatives. The ordering also lists PowerShell after the portal, reinforcing a Windows-centric approach. No Linux/macOS-specific tools or examples are provided.
Recommendations
  • Add instructions or links for migrating using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention Bash or shell scripting options where relevant.
  • Ensure that examples and tooling references are not limited to PowerShell; provide parity for Linux/macOS users.
  • Consider listing cross-platform methods (CLI) before or alongside PowerShell in 'Next steps'.
GitHub Create Pull Request
Frontdoor Troubleshoot File Compression ...frontdoor/standard-premium/troubleshoot-compression.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively mentioning Windows tools (Fiddler, IIS) for troubleshooting and configuration, and by providing configuration instructions only for Microsoft IIS servers. There are no equivalent Linux or cross-platform examples or references (e.g., Apache, Nginx, curl, command-line tools), which may hinder Linux/macOS users attempting similar troubleshooting.
Recommendations
  • Include Linux/macOS-friendly tools for inspecting HTTP headers, such as curl, wget, or httpie, with example commands.
  • Mention cross-platform alternatives to Fiddler, such as Wireshark or browser developer tools available on all platforms.
  • Provide troubleshooting steps for popular Linux web servers (e.g., Apache, Nginx), including how to configure compression and handle proxy headers.
  • Clarify that browser developer tools are available on all platforms, not just Windows.
  • Add links to relevant documentation for Linux server configuration regarding compression and proxy headers.
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-11 06:20
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, CLI, API, and Terraform for migration, but only provides a direct link to a PowerShell-specific migration guide. The 'Related content' section lists the PowerShell migration guide explicitly, while Linux/macOS-friendly tools (Azure CLI, Terraform) are mentioned only in passing and lack dedicated example links. This ordering and emphasis suggest a Windows-first and PowerShell-heavy bias, with missing parity for Linux/macOS users who may prefer CLI or Terraform.
Recommendations
  • Add direct links to migration guides using Azure CLI and Terraform in the 'Related content' section, alongside the PowerShell guide.
  • Provide explicit examples and step-by-step instructions for migration using Azure CLI and Terraform, ensuring Linux/macOS users have clear guidance.
  • When mentioning scripting or automation, list CLI and Terraform options before or alongside PowerShell, not after.
  • Review the documentation for other sections where Windows-specific tools or patterns are prioritized and ensure Linux/macOS parity.
GitHub Create Pull Request
Frontdoor Troubleshoot common issues ...cs/blob/main/articles/frontdoor/troubleshoot-issues.md
Medium 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 references Windows-specific tools (Fiddler) and browser developer tools for troubleshooting, with no mention of Linux/macOS alternatives. The only explicit command-line example given is for OpenSSL, which is cross-platform, but troubleshooting steps and tool recommendations are otherwise Windows-centric. Linux/macOS users may need to infer or substitute their own tools, creating friction.
Recommendations
  • Include Linux/macOS equivalents for troubleshooting tools (e.g., suggest curl, wget, tcpdump, Wireshark, or browser dev tools available on all platforms).
  • When mentioning Fiddler, also mention cross-platform alternatives such as mitmproxy or Wireshark.
  • Provide example commands for both Windows (PowerShell, Fiddler) and Linux/macOS (curl, openssl, etc.) where relevant.
  • Clarify that browser developer tools are available on all major platforms.
  • Add troubleshooting steps using Linux-native tools for HTTP header inspection and SSL verification.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides example configurations for multiple origin types, including App Service, Application Gateway, AKS NGINX, and IIS. However, IIS (a Windows-only web server) is given a dedicated example, while there is no equivalent example for popular Linux web servers such as Apache or Nginx (outside of AKS NGINX, which is Kubernetes-specific). The IIS example is presented before the AKS NGINX example, indicating a slight Windows-first ordering. There are no PowerShell-heavy or Windows-only instructions, but the lack of parity for standalone Linux web servers (Apache, Nginx) constitutes a notable bias.
Recommendations
  • Add example configurations for popular Linux web servers such as Apache HTTP Server and standalone Nginx (outside of Kubernetes), showing how to filter requests based on the X-Azure-FDID header.
  • Ensure ordering of examples alternates or starts with platform-neutral or Linux examples to avoid implicit prioritization of Windows tools.
  • Explicitly mention that the IIS example is for Windows and provide guidance for equivalent Linux scenarios.
GitHub Create Pull Request
Frontdoor Migration FAQ ...ure-docs/blob/main/articles/frontdoor/migration-faq.md
Medium 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 references Azure PowerShell for migration tasks and lists it before any mention of Linux-friendly alternatives (such as Azure CLI or Bash scripting). There are no explicit Linux/macOS examples or instructions, and the only command-line migration guide linked is PowerShell-based, which is Windows-centric. This creates friction for Linux/macOS users who may prefer or require Azure CLI or other cross-platform tools.
Recommendations
  • Add migration instructions using Azure CLI and Bash for Linux/macOS users.
  • Provide parity in example scripts and links for both PowerShell and CLI.
  • Explicitly mention cross-platform options and clarify tool compatibility.
  • Reorder related content to present platform-neutral or Linux-friendly options before Windows/PowerShell-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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive coverage of PowerShell (a Windows-centric tool) with a dedicated section, detailed prerequisites, and command mappings, while Linux/macOS alternatives (such as Bash or shell scripting) are not mentioned. PowerShell examples and references are given before CLI examples, and installation links for PowerShell point to Windows-specific instructions. There is no mention of cross-platform scripting approaches or parity for Linux/macOS users in the PowerShell section.
Recommendations
  • Add explicit Bash/shell script examples for deployment tasks alongside PowerShell examples.
  • Clarify that Azure CLI and Terraform are cross-platform and provide installation instructions for Linux/macOS as well as Windows.
  • In the PowerShell section, mention that PowerShell Core is available on Linux/macOS, and link to installation instructions for those platforms.
  • Reorder sections so that cross-platform tools (CLI, Terraform, Bicep) are presented before Windows-centric tools like PowerShell.
  • Where possible, provide parity in examples and troubleshooting steps for Linux/macOS users.
GitHub Create Pull Request
Frontdoor Troubleshoot File Compression ...frontdoor/standard-premium/troubleshoot-compression.md
Medium 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 shows a Windows bias by recommending Windows-specific tools (Fiddler, IIS) for troubleshooting and configuration. It provides detailed IIS instructions for compression settings but omits equivalent guidance for Linux-based web servers (e.g., Apache, Nginx). No Linux/macOS command-line or tool examples are given, and Windows tools are mentioned before cross-platform alternatives.
Recommendations
  • Include examples for checking compression using Linux/macOS command-line tools (e.g., curl, wget).
  • Mention and provide instructions for configuring compression on popular Linux web servers such as Apache (mod_deflate) and Nginx (gzip module).
  • List cross-platform tools (e.g., Wireshark, curl) alongside Fiddler for inspecting HTTP headers.
  • Ensure troubleshooting steps are not IIS-specific and cover common Linux server scenarios.
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 mentions Azure PowerShell as a migration method in the 'Next steps' section, but does not mention CLI or Bash/Linux alternatives. This prioritizes Windows tooling and may create friction for Linux/macOS users who typically use Azure CLI or shell scripts.
Recommendations
  • Include Azure CLI migration instructions and link to relevant documentation alongside PowerShell.
  • Mention Bash or shell scripting options if available.
  • Present cross-platform tools (CLI, REST API) before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →