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 51-75 of 130 flagged pages
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing Azure Front Door resources. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and screenshots exclusively show PowerShell output. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or workflows. The documentation assumes familiarity with PowerShell and does not clarify cross-platform usage for CLI or PowerShell. This may unintentionally prioritize Windows users and workflows.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI commands, clarifying that Azure CLI works natively on Linux/macOS.
  • Include screenshots of CLI output in addition to PowerShell output, or use CLI output as the primary example.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, while PowerShell is primarily Windows-focused (though available cross-platform).
  • Instruct users on how to install and use Azure CLI on Linux/macOS, and provide links to relevant installation guides.
  • Avoid using PowerShell output as the sole visual example; balance with CLI or portal screenshots.
  • Consider a 'Platform considerations' section to highlight any differences or additional steps for Linux/macOS users.
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-08 00:53
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 referencing Azure PowerShell migration instructions in the 'Related content' section, while omitting equivalent Linux/CLI examples. The PowerShell migration guide is specifically called out, but there is no mention of Azure CLI or Bash-based migration steps, which are more common on Linux and macOS platforms. This prioritizes Windows tooling and patterns, and may leave Linux users without clear guidance.
Recommendations
  • Add links to Azure CLI-based migration guides alongside PowerShell instructions.
  • Explicitly mention cross-platform tools and provide examples for both Windows (PowerShell) and Linux/macOS (Bash, Azure CLI).
  • Ensure that all procedural steps (e.g., DNS changes, DevOps pipeline updates) include platform-agnostic instructions or note any platform-specific differences.
  • Review related content to ensure parity between Windows and Linux documentation references.
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-08 00:53
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, despite PowerShell being primarily a Windows tool. There are no Linux-specific shell examples (such as Bash scripts), and no mention of platform differences or considerations for Linux users. The documentation does not clarify that Azure CLI is cross-platform, nor does it provide parity for Linux-first users.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux and macOS users.
  • Provide Bash or shell script examples alongside Azure CLI commands to demonstrate usage in Linux environments.
  • Add a note clarifying that Azure PowerShell is primarily for Windows, and suggest Azure CLI for Linux/macOS users.
  • Ensure that CLI examples are presented before PowerShell examples to avoid implicit Windows-first bias.
  • Consider including links or references to installing and using Azure CLI on Linux.
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-08 00:53
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 environments by primarily referencing Azure PowerShell for command-line migration instructions and linking to PowerShell-specific guides. There are no explicit examples or instructions for Linux users (e.g., Azure CLI or Bash), and PowerShell is mentioned before or instead of cross-platform alternatives. This may make it more difficult for Linux users to follow migration steps or feel equally supported.
Recommendations
  • Include Azure CLI examples and documentation links alongside PowerShell for all command-line operations, especially migration steps.
  • When referencing command-line tools, mention cross-platform options (e.g., Azure CLI) before or alongside PowerShell.
  • Ensure that all linked guides (such as those for certificate management or migration) provide both PowerShell and CLI/Bash instructions.
  • Review all references to tools and ensure Linux users are explicitly supported and addressed in the documentation.
  • Add a section or callout clarifying that all major operations can be performed on both Windows and Linux, with links to relevant guides for each platform.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page lists 'PowerShell' as a management option for Azure Front Door and CDN services, but does not mention Linux-specific tools (such as Azure CLI or Bash scripting) or provide parity for Linux users. The ordering of management options puts PowerShell before alternatives, and there are no Linux-focused examples or references to Linux-native workflows.
Recommendations
  • Explicitly mention Azure CLI and Bash as management options alongside PowerShell.
  • Provide example commands for both PowerShell and Azure CLI/Bash for common management tasks.
  • Ensure that documentation references cross-platform tools first, or at least equally, rather than prioritizing Windows/PowerShell.
  • Add a section or note clarifying cross-platform support and linking to Linux-specific guidance where relevant.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for template deployment and resource cleanup, with no equivalent Azure CLI (bash/Linux) commands. The deployment walkthrough and screenshots focus on PowerShell and Windows-centric workflows, mentioning other methods only in passing and without examples. This may disadvantage Linux users or those preferring cross-platform CLI tools.
Recommendations
  • Add Azure CLI (bash) examples alongside PowerShell for all deployment and cleanup steps.
  • Include screenshots or output examples from Azure CLI to match PowerShell visuals.
  • Explicitly mention Linux/macOS compatibility in prerequisites and instructions.
  • Reorder or parallelize instructions so that CLI and PowerShell examples are presented together, not PowerShell first.
  • Provide links to both PowerShell and CLI reference documentation where relevant.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell instructions and terminology, referencing Azure PowerShell and Cloud Shell (which defaults to PowerShell), and omitting explicit Linux shell examples or guidance. The CLI tab is present, but the overall narrative and instructions are written with a Windows/PowerShell-first perspective, and there are no examples or notes about running commands in native Linux environments or using bash/zsh. There is also no mention of Linux-specific tools, patterns, or troubleshooting.
Recommendations
  • Add explicit bash/zsh examples for Linux users, including instructions for running Azure CLI commands in native Linux terminals.
  • Clarify that Azure CLI can be used cross-platform and provide guidance for installing and using it on Linux systems.
  • Include troubleshooting notes or tips relevant to Linux environments (e.g., permissions, environment variables, certificate file formats).
  • Balance the order of presentation so that CLI and PowerShell instructions are given equal prominence, or alternate which is presented first.
  • Reference Linux tools (such as openssl, curl, dig) where appropriate for certificate management and DNS validation.
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-08 00:53
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 listing Windows tools and patterns before their Linux equivalents, providing PowerShell-specific instructions, and referencing Windows file paths and utilities first. For example, 'Invoke-WebRequest on Windows using PowerShell' is mentioned alongside 'Wget on Linux', but PowerShell is listed first. The hosts file location is described for Windows before Linux, and the use of Windows-specific tools and terminology is prevalent throughout the guide.
Recommendations
  • Alternate the order of mentioning Windows and Linux tools (e.g., list Linux first in some cases).
  • Provide Bash or shell script examples alongside PowerShell commands, especially for common tasks like HTTP requests.
  • Reference Linux file paths and utilities equally or before Windows equivalents where appropriate.
  • Include screenshots or instructions for both Windows and Linux environments when describing steps involving the OS (e.g., editing the hosts file).
  • Explicitly state that all steps can be performed on both Windows and Linux, and provide parity in examples and tool recommendations.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation mentions PowerShell as a primary command line tool for DevOps integration, listing it before other cross-platform options like Azure CLI. There are no Linux-specific examples, tools, or patterns provided, and Windows-oriented tools (PowerShell) are referenced without equal mention of Linux alternatives. This may make Linux users feel less prioritized or supported.
Recommendations
  • Explicitly mention Azure CLI and Bash as first-class options alongside PowerShell when discussing command line tools.
  • Provide example workflows or commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
  • Add references to Linux-compatible automation and scripting tools in relevant sections.
  • Ensure that any instructions or examples are platform-neutral or offer parallel guidance for both Windows and Linux users.
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-08 00:53
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, and references to Windows installation paths) before or alongside cross-platform alternatives. PowerShell is given its own dedicated section, with prerequisites and examples, while Linux-specific tools or shell examples (e.g., Bash) are not mentioned. ARM template export instructions include Azure PowerShell and Azure CLI, but PowerShell is listed as a primary method and links to Windows-specific installation guides. There are no Linux shell script examples or references to Linux-specific workflows.
Recommendations
  • Add explicit Linux/Bash examples for scripting tasks alongside PowerShell, especially for deployment and resource management.
  • Reference cross-platform installation guides for Azure CLI and PowerShell, not just Windows-specific ones.
  • Include instructions for exporting ARM templates and managing resources using Bash or other Linux-native tools.
  • Balance the order of tool presentation (e.g., CLI before PowerShell, or present both together) to avoid Windows-first impression.
  • Highlight platform-neutral approaches where possible, and clarify which steps or tools work identically on Linux and macOS.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools (Fiddler, IIS), omitting Linux/Unix equivalents for checking compression or configuring origin servers. All server-side troubleshooting steps are described for IIS, with no mention of Apache, Nginx, or other common Linux web servers. The guidance and examples assume a Windows environment, which may disadvantage users on Linux platforms.
Recommendations
  • Include Linux/Unix command-line examples for checking HTTP headers, such as using curl or wget to inspect the Content-Encoding header.
  • Mention cross-platform or Linux-specific tools (e.g., tcpdump, Wireshark, or command-line browser tools) alongside Fiddler and browser developer tools.
  • Provide instructions for configuring compression on popular Linux web servers, such as Apache (mod_deflate) and Nginx (gzip module), especially regarding proxy headers like Via.
  • Ensure that troubleshooting steps and examples are presented for both Windows and Linux environments, or at least reference documentation for both.
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-08 00:53
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-specific troubleshooting tools (Fiddler, browser developer tools) and omitting Linux alternatives. The order of tool recommendations and examples prioritizes Windows approaches, and there are no explicit Linux command-line or tool examples (e.g., curl, tcpdump, Wireshark) for troubleshooting. The only command-line example provided is for OpenSSL, which is cross-platform, but no Linux-specific context or instructions are given.
Recommendations
  • Include Linux-specific troubleshooting tools and examples, such as using curl, wget, tcpdump, or Wireshark for network diagnostics.
  • When recommending tools like Fiddler, also mention Linux alternatives (e.g., mitmproxy, Wireshark, curl) and provide usage examples for both platforms.
  • Ensure that command-line examples (such as OpenSSL) include notes on installation and usage for both Windows and Linux environments.
  • Provide parity in screenshots and instructions for both Windows and Linux users, especially for steps involving client-side troubleshooting.
  • Explicitly state that browser developer tools are available on all major platforms, and clarify any platform-specific steps if necessary.
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-08 00:53
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 as primary automation tools for migration, listing PowerShell before CLI, API, and Terraform, and providing a dedicated link for PowerShell-based migration. There are no explicit Linux shell or Bash examples, nor is there mention of Linux-specific tooling or parity in migration instructions.
Recommendations
  • Add explicit Bash and Linux shell examples for migration steps, especially where PowerShell is referenced.
  • Provide parity in documentation links, e.g., add a 'migrate-tier-cli.md' for Azure CLI and reference it alongside PowerShell.
  • List cross-platform tools (CLI, Terraform, API) before or alongside PowerShell to avoid Windows-first ordering.
  • Include notes or sections for Linux/macOS users, clarifying any platform-specific considerations.
  • Ensure all automation and scripting guidance is available for both Windows and Linux environments.
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: 2025-07-13 21:37
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 (PowerShell) and Linux (wget) are both mentioned, but Windows/PowerShell is listed second. However, in the hosts file editing section, the Windows path is listed before the Linux path, and the instructions for testing endpoints reference Windows-specific tools and locations first. There is also an assumption of familiarity with Windows tools and patterns (such as 'Invoke-WebRequest' and the Windows hosts file path), and PowerShell is mentioned as the Windows method for HTTP requests, with no mention of curl, which is available on both platforms.
Recommendations
  • When listing tools or commands, present cross-platform options side-by-side (e.g., 'Use wget or curl on Linux/macOS, or Invoke-WebRequest or curl on Windows').
  • Alternate the order in which Windows and Linux instructions are presented, or provide both together where possible.
  • In hosts file editing instructions, mention both Windows and Linux paths together, or start with Linux to balance representation.
  • Include curl as a cross-platform HTTP request tool, since it is available on both Windows and Linux.
  • Where possible, provide explicit Linux/macOS shell command examples alongside Windows/PowerShell examples.
  • Avoid assuming the user is more familiar with Windows tools or patterns.
GitHub Create Pull Request
Frontdoor https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/standard-premium/tls-policy.md ...main/articles/frontdoor/standard-premium/tls-policy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically referencing Windows operating systems (Windows 10, 8.1, 8, 7) and their compatibility with cipher suites, while omitting any mention of Linux or macOS client compatibility. There are no examples or notes for Linux users, and the only client-side guidance is Windows-specific. No Linux tools, distributions, or configuration patterns are mentioned.
Recommendations
  • Add equivalent compatibility notes for common Linux distributions (e.g., Ubuntu, CentOS) and macOS, specifying which cipher suites are supported by default in OpenSSL or GnuTLS.
  • Include example commands or configuration snippets for verifying TLS/cipher support on Linux (e.g., using openssl s_client).
  • Mention how to update or configure cipher suites on Linux systems, or link to relevant documentation.
  • Ensure that client compatibility guidance is cross-platform, not Windows-only, and appears in a platform-neutral order or with equal prominence.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line deployment instructions and examples are provided exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The workflow assumes use of PowerShell and references Windows-specific cmdlets and output. While there is a brief mention that Azure CLI and REST API are also available, no examples or guidance are given for Linux/macOS users or for cross-platform command-line tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for all deployment and cleanup steps, ideally in Bash syntax.
  • Present both PowerShell and CLI/Bash examples side by side, or allow the user to toggle between them.
  • Avoid using only PowerShell-specific cmdlets and terminology; reference cross-platform tools equally or first.
  • Include screenshots or output examples from both PowerShell and CLI where relevant.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
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-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and CLI for migration tasks, mentioning PowerShell before CLI, and providing a 'Next steps' link specifically for PowerShell-based migration. There are no Linux-specific examples, nor are there instructions or examples for Bash or Linux-native tooling. The documentation assumes familiarity with PowerShell and Windows-centric workflows, with no parity for Linux users.
Recommendations
  • Add explicit Linux/Bash/terminal examples for migration tasks, especially where PowerShell is referenced.
  • In 'Next steps', provide parallel guides for Linux users (e.g., 'How to migrate using Azure CLI on Linux').
  • When listing tools or automation options, mention Azure CLI and Terraform before or alongside PowerShell, and clarify that all tools are cross-platform.
  • Include sample CLI commands (az front-door ...) for common migration actions, not just PowerShell scripts.
  • Review all references to scripting and automation to ensure Linux users are equally supported and not implicitly deprioritized.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly referencing Azure PowerShell as a primary migration method and providing a dedicated link for it, while not mentioning or linking to equivalent Linux-friendly tools such as Azure CLI or Bash scripts. There are no examples or instructions for Linux users, and the ordering of tools consistently places Windows-centric solutions first or exclusively.
Recommendations
  • Add migration instructions and dedicated documentation links for Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Wherever Azure PowerShell is mentioned, provide equivalent Azure CLI commands or scripts, and link to relevant documentation.
  • Ensure that references to command-line tools do not assume a Windows environment; mention Bash, shell, or cross-platform options alongside PowerShell.
  • In the 'Next steps' and migration sections, list both Azure portal, Azure CLI, and Azure PowerShell options, ideally with CLI first or in parallel.
  • If Terraform is supported for migration, provide explicit examples or links for both Windows and Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
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 file compression. There are no Linux or cross-platform server examples, and the only origin server configuration guidance is for Microsoft IIS, with no mention of Apache, Nginx, or other common Linux-based servers. The troubleshooting steps and tool recommendations are Windows-centric, and Linux alternatives are not provided.
Recommendations
  • Include examples and instructions for popular Linux-based web servers such as Apache and Nginx, detailing how to configure compression and handle proxy headers.
  • Suggest cross-platform tools for inspecting HTTP headers, such as curl, wget, or httpie, alongside Fiddler and browser developer tools.
  • Provide parity in troubleshooting steps for both Windows and Linux environments, ensuring that users on any platform can follow the guidance.
  • Mention Linux-specific considerations for compression and proxy headers, such as relevant Apache or Nginx directives.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring endpoint domain reuse, but does not include explicit Linux shell (bash) examples or clarify that the Azure CLI example is cross-platform. PowerShell is a Windows-centric tool, and its example is given equal prominence to the CLI, which may suggest a Windows bias. There is no mention of Linux-specific tools or workflows, nor is it clarified that the CLI example works on Linux/macOS.
Recommendations
  • Clarify that the Azure CLI example is cross-platform and works on Linux, macOS, and Windows.
  • Consider providing a bash shell example or explicitly labeling the CLI example as suitable for Linux/macOS.
  • If including PowerShell, consider also including a Linux shell (bash/zsh) example for parity.
  • Avoid giving the impression that PowerShell is required or preferred by placing CLI (cross-platform) examples first.
  • Add a note or section on how to perform the same operation using the Azure portal, which is platform-agnostic.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently presenting PowerShell (a Windows-centric tool) instructions before Azure CLI (which is more cross-platform), and by providing detailed guidance on using Azure PowerShell and Cloud Shell. There is no explicit mention of Linux or macOS environments, and the instructions for local installation and usage focus on PowerShell and Azure CLI without clarifying parity or differences for Linux users. The use of PowerShell as the first/default example and the lack of explicit Linux-specific guidance or troubleshooting may make the documentation less approachable for Linux users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI tabs, or present Azure CLI first, as it is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation links for all platforms.
  • Include Linux/macOS-specific notes or troubleshooting tips where relevant (e.g., file paths, shell differences, permissions).
  • Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash equivalents for common tasks.
  • Ensure that all examples and instructions are validated on Linux and macOS, and note any platform-specific caveats.
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: 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 page demonstrates a Windows bias by referencing Azure PowerShell explicitly as a migration method, both in the FAQ and the Next Steps section, without mentioning or providing equivalent examples for Azure CLI (which is cross-platform and commonly used on Linux/macOS). There are no Linux-specific tools or examples, and the ordering of migration instructions puts PowerShell (a Windows-centric tool) on equal or higher footing than more platform-neutral options. No Linux or bash command line examples are provided.
Recommendations
  • Add Azure CLI examples and documentation links alongside Azure PowerShell for all migration instructions.
  • Explicitly mention that both Azure CLI and Azure PowerShell can be used for management and migration, and provide parity in documentation.
  • Wherever PowerShell is referenced, ensure a corresponding CLI/bash example is present, or at least mention the CLI alternative.
  • Consider including a table or section comparing management options (Portal, PowerShell, CLI, Terraform) with notes on cross-platform compatibility.
  • Review for any other Windows-centric language or tool references and ensure Linux/macOS parity.
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: 2025-07-08 04:23
Reviewed by: Unknown
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 all deployment, validation, and cleanup steps. However, PowerShell (a Windows-centric tool) is always presented as the alternative to CLI, and screenshots explicitly show PowerShell output. There are no Linux shell-specific examples (e.g., bash scripting), and no mention of Linux-native tools or environments. The CLI examples are cross-platform, but the documentation implicitly centers Windows by pairing CLI with PowerShell and by using PowerShell output in visuals.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and consider mentioning bash or zsh as common shells.
  • Include example terminal output from a Linux shell (e.g., bash) in addition to or instead of PowerShell screenshots.
  • Clarify that PowerShell Core is cross-platform, but also note that many Linux users will use bash or other shells.
  • If scripting is discussed, provide bash script snippets alongside PowerShell scripts.
  • Avoid language or visuals that suggest PowerShell is the default or primary way to interact with Azure, especially for cross-platform documentation.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for deploying the ARM template, referencing PowerShell-specific cmdlets, and showing PowerShell output screenshots. While it briefly mentions that Azure CLI and REST API are alternative options, it does not provide any Linux-friendly (Bash/Azure CLI) examples or instructions, nor does it mention or show Linux terminal usage. The step-by-step deployment and cleanup instructions are exclusively tailored to Windows/PowerShell users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all deployment and cleanup steps, using Bash syntax.
  • Include screenshots or output examples from Azure CLI/Bash terminals alongside PowerShell examples.
  • Present both PowerShell and CLI examples in parallel, or provide a tabbed interface for users to select their preferred environment.
  • Explicitly mention that the steps work on both Windows and Linux, and provide clear guidance for Linux/macOS users.
  • Avoid using only PowerShell-specific cmdlets and terminology; ensure parity in instructions and explanations 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: 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 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, despite PowerShell being primarily associated with Windows. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The ordering of examples (CLI first, then PowerShell, then Bicep) is reasonable, but the lack of explicit Linux/bash scripting guidance or examples may disadvantage Linux users.
Recommendations
  • Add explicit bash shell scripting examples for Linux users, especially for automation scenarios.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample invocations in bash/zsh.
  • Consider de-emphasizing PowerShell unless there are Windows-specific steps, or move PowerShell examples after CLI/bash examples.
  • Where possible, mention that Bicep and ARM templates are platform-agnostic.
  • Add a note or section on cross-platform usage, highlighting any differences or considerations for Linux users.
GitHub Create Pull Request
← Previous Page 3 of 6 Next →