Frontdoor

102
Total Pages
81
Linux-Friendly Pages
21
Pages with Bias
20.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (30)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/migrate-cdn-to-front-door.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/origin-security.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation provides configuration examples for multiple origin types, including App Service, Application Gateway, Application Gateway for Containers, IIS, and AKS NGINX controller. However, it includes a dedicated example for Microsoft IIS (a Windows-specific web server) and omits equivalent examples for common Linux web servers such as Apache HTTP Server or NGINX (outside of Kubernetes). The IIS example is the only origin-specific example that is platform-specific, and it appears before the AKS NGINX controller example, which is more Linux-centric. There are no PowerShell-specific commands or explicit Windows command-line instructions, but the inclusion of IIS and omission of standalone Linux web server examples indicates a subtle Windows 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 the X-Azure-FDID header.
  • Ensure that Linux-origin examples appear alongside or before Windows-specific examples like IIS to provide parity and avoid the perception of Windows-first ordering.
  • If possible, provide shell command snippets (e.g., iptables, firewalld) for configuring IP address filtering on Linux servers, in addition to network security group rules.
  • Review the documentation for other subtle Windows-centric language or assumptions and ensure cross-platform inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/standard-premium/tls-policy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-terraform.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a bias toward Windows by exclusively using the azurerm_windows_web_app resource for the App Service example, without mentioning or providing examples for Linux-based App Service resources. There are no explicit PowerShell or Windows command-line instructions, but the resource selection implicitly favors Windows environments. No Linux equivalents or guidance are offered.
Recommendations:
  • Include an example using azurerm_linux_web_app alongside azurerm_windows_web_app to provide parity for Linux users.
  • Add a note or section explaining how to adapt the Terraform configuration for Linux-based App Service deployments.
  • Ensure that any referenced sample code or GitHub repositories contain both Windows and Linux App Service examples.
  • Review the documentation for other implicit Windows-first patterns, such as screenshots or troubleshooting steps, and provide Linux alternatives where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/standard-premium/how-to-enable-private-link-apim.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation provides three pivots: Portal, PowerShell, and CLI. The PowerShell section is detailed and appears before the CLI section, which may indicate a slight Windows-first and PowerShell-heavy bias. However, the CLI section is present and complete, supporting Linux and macOS users. There are no missing Linux examples, but the ordering and emphasis on PowerShell could be improved for parity.
Recommendations:
  • Consider listing the CLI pivot before the PowerShell pivot to give equal or greater prominence to cross-platform tooling.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, provide Bash script examples or notes for Linux users in the CLI section.
  • Ensure that all features and steps described in PowerShell are also available and equally detailed in the CLI section.
  • Add a short note in the prerequisites for each pivot clarifying the OS compatibility (e.g., 'Azure CLI runs on Windows, Linux, and macOS').
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/end-to-end-tls.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation contains a subtle Windows bias in the section discussing supported cipher suites. It specifically references Windows operating systems (Windows 10, 8.1, 8, and 7) when recommending cipher suite compatibility, without mentioning Linux or macOS equivalents. There are no command-line examples or tool references, but the only OS-specific advice is Windows-centric.
Recommendations:
  • Include information about cipher suite compatibility for popular Linux distributions and macOS, not just Windows.
  • Provide guidance or references for how to check or configure TLS cipher suites on Linux (e.g., using OpenSSL or system configuration files).
  • If mentioning OS compatibility, ensure parity by listing both Windows and Linux/macOS considerations, or link to relevant documentation for those platforms.
  • Consider adding example commands or configuration snippets for both Windows (e.g., PowerShell) and Linux (e.g., OpenSSL, update-alternatives, or systemd-tls settings) where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/tier-migration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/classic-retirement-faq.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/standard-premium/troubleshoot-compression.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/endpoint.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/front-door-custom-domain-https.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/classic-retirement-faq.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-bicep.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/end-to-end-tls.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation page exhibits a mild 'windows_first' bias. In the section discussing supported cipher suites, recommendations are made specifically for Windows 10 and later, with additional compatibility notes for Windows 8.1, 8, and 7. There are no equivalent recommendations or compatibility notes for Linux or macOS clients. No PowerShell commands or Windows-specific tools are mentioned, but the only OS-specific guidance is for Windows.
Recommendations:
  • Add equivalent recommendations or compatibility notes for Linux distributions (e.g., minimum OpenSSL versions or cipher suite support in common Linux browsers/clients).
  • Include a note about how to check or configure supported cipher suites on Linux systems.
  • If mentioning Windows compatibility, also mention macOS and Linux client compatibility to ensure parity.
  • Consider providing a table or matrix showing cipher suite support across major operating systems (Windows, Linux, macOS) and browsers.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by only providing examples for deploying App Services using the Windows operating system. The 'Operating System' field is set to 'Windows' by default, and there are no instructions or examples for deploying on Linux, which is a common and supported scenario for Azure App Services. No Linux-specific guidance, screenshots, or parity notes are included.
Recommendations:
  • Add parallel instructions and screenshots for deploying App Services on Linux (e.g., by selecting 'Linux' in the 'Operating System' field and choosing a Linux-compatible runtime stack).
  • Include a note or section explaining that both Windows and Linux are supported for App Services, and highlight any differences in configuration or available features.
  • Provide example configurations for both Windows and Linux, possibly using tabs or side-by-side comparisons.
  • Ensure that terminology and steps are inclusive of both platforms (e.g., refer to 'App Service plan' rather than 'Windows Plan' when possible, or clarify the difference).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-terraform.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation provides a quickstart for creating an Azure Front Door using Terraform, but it only demonstrates the creation of an App Service app using the azurerm_windows_web_app resource. There are no examples or mentions of Linux-based App Service equivalents (such as azurerm_linux_web_app), nor are there instructions or notes for users deploying on Linux. This omission may lead users to assume that only Windows-based web apps are supported or recommended.
Recommendations:
  • Include parallel examples or instructions for creating an App Service app using azurerm_linux_web_app, or at least mention that Linux is supported and link to relevant documentation.
  • Add a note clarifying that both Windows and Linux App Service plans are supported, with guidance on how to choose between them.
  • Where possible, provide code samples or references for both Windows and Linux scenarios to ensure parity.
  • Review any referenced sample code to ensure Linux examples are present and easy to find.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/endpoint.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/front-door-custom-domain-https.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both PowerShell and Azure CLI instructions, but PowerShell (a Windows-centric tool) is consistently presented first in all code tabs and explanations. The narrative and guidance around using PowerShell (including Cloud Shell and local installation) is more detailed and prominent than for Azure CLI. There are no explicit Linux-only examples or references to Linux-native tools, and the documentation assumes familiarity with PowerShell patterns.
Recommendations:
  • Alternate the order of PowerShell and Azure CLI tabs, or present Azure CLI first to avoid implicit prioritization of Windows tooling.
  • Ensure that explanations and guidance for Azure CLI are as detailed as those for PowerShell, including instructions for both Windows and Linux environments.
  • Explicitly mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Where possible, provide bash shell examples or reference Linux-native workflows for common tasks (e.g., DNS configuration, certificate management).
  • Add a note or section highlighting that all steps can be performed from Linux or macOS using Azure CLI, and provide troubleshooting tips for those environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/how-to-enable-private-link-application-gateway.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation presents a clear Windows-first bias by listing the Azure Portal (GUI) and PowerShell methods before the Azure CLI approach. The PowerShell section is detailed and assumes the use of PowerShell or Azure Cloud Shell, which is more familiar to Windows users. While a CLI section is present (which is cross-platform), it is placed after the PowerShell section, and there are no explicit Linux- or Bash-specific examples or troubleshooting notes. No Linux-specific tools or workflows are highlighted.
Recommendations:
  • Reorder the technical pivots so that Azure CLI (which is cross-platform and preferred by many Linux users) appears before PowerShell, or at least give them equal prominence.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific notes or troubleshooting tips where relevant.
  • Where PowerShell is referenced, also mention that Azure Cloud Shell supports Bash, and provide equivalent Bash/CLI snippets for any PowerShell-specific logic.
  • In the prerequisites and tool installation sections, include instructions for installing Azure CLI and PowerShell on Linux, and clarify that both are supported.
  • Add a note in the introduction or prerequisites highlighting that all workflows can be completed from Linux, macOS, or Windows, and link to platform-specific setup guides.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/integrate-storage-account.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples for either Windows (PowerShell, Command Prompt) or Linux (Bash, CLI). However, the absence of CLI examples (such as Azure CLI commands) means Linux users do not see parity or explicit guidance for non-Windows environments. Additionally, the documentation refers to the Azure Portal, which is platform-agnostic but often associated with Windows-centric workflows in Azure documentation. There are no explicit Windows-only tools or commands, but the lack of Linux/CLI examples is a notable omission.
Recommendations:
  • Add Azure CLI examples for all major steps (creating storage accounts, configuring Front Door, purging cache, etc.), as Azure CLI is cross-platform and widely used on Linux.
  • Where possible, provide both portal and CLI instructions side-by-side, or link to CLI documentation for each step.
  • Explicitly mention that all steps can be performed from any OS via the Azure Portal, but highlight CLI alternatives for automation and scripting.
  • If PowerShell examples are ever added, ensure Bash/Azure CLI equivalents are also provided.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/managed-identity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation page exclusively describes configuration steps using the Azure Portal GUI and does not provide any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI or Azure PowerShell), nor are there any Linux-specific instructions or examples. The absence of CLI examples implicitly favors Windows users, as the Azure Portal experience is often more closely associated with Windows environments, and omits parity for Linux or automation-focused users.
Recommendations:
  • Add Azure CLI examples for all configuration steps, including enabling managed identity and assigning Key Vault permissions. Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Where relevant, provide Azure PowerShell examples as well, but ensure Azure CLI is presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that all steps can be performed using CLI tools on any platform, and link to relevant CLI documentation.
  • Include a section or callout for automation and scripting, highlighting how these tasks can be performed non-interactively (e.g., in CI/CD pipelines or on Linux servers).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/migrate-cdn-to-front-door.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/origin-authentication-with-managed-identities.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page provides only portal-based (GUI) instructions and screenshots, with no command-line examples for either Windows (PowerShell) or Linux (CLI). However, there is an implicit Windows bias because Azure documentation often defaults to PowerShell or Windows-centric tools when command-line examples are provided, and this page does not make any effort to include or mention Linux CLI (Azure CLI) equivalents. Additionally, the terminology and workflow are oriented around the Azure Portal, which is more familiar to Windows users, and there is no mention of how to perform these tasks using cross-platform tools.
Recommendations:
  • Add Azure CLI (az) command-line examples for all major steps, such as enabling managed identities, assigning roles, and associating identities with origin groups.
  • Explicitly mention that all steps can be performed using Azure CLI on Linux, macOS, or Windows, and provide links to relevant CLI documentation.
  • If PowerShell examples are added in the future, ensure that Azure CLI equivalents are provided alongside them.
  • Include a section or callout for users who prefer automation or scripting, referencing both PowerShell and Azure CLI.
  • Review terminology and instructions to ensure they are platform-neutral and do not assume use of the Azure Portal or a Windows environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/origin-security.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation provides configuration examples for multiple origin types, but the IIS (Windows) example is presented before the AKS NGINX (Linux) example. Additionally, the IIS example is detailed and uses Windows-specific configuration (web.config), while there is no equivalent example for generic Linux web servers (e.g., Apache, NGINX outside AKS). This ordering and tool selection may suggest a slight Windows bias.
Recommendations:
  • Reorder the example sections so that Linux-based origins (e.g., AKS NGINX, generic NGINX, Apache) are presented before or alongside Windows/IIS examples.
  • Add configuration examples for common Linux web servers such as Apache and standalone NGINX (not just AKS ingress), showing how to filter the X-Azure-FDID header.
  • Ensure that for every Windows-specific example, there is a Linux equivalent, and that both are equally detailed.
  • Explicitly mention cross-platform applicability and provide links or references to Linux documentation where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/refstring.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation provides detailed instructions and screenshots for capturing the Reference String using the Microsoft Edge browser and its developer tools, which are primarily associated with Windows environments. There are no examples or instructions for capturing the Reference String using tools or browsers commonly used on Linux (such as curl, wget, Firefox, or Chrome on Linux), nor are there command-line examples that would be cross-platform. The only method described is Windows-centric, and it is presented as the default/primary approach.
Recommendations:
  • Add instructions and examples for capturing the Reference String using cross-platform command-line tools such as curl or wget, which are available on both Linux and Windows.
  • Include a browser-agnostic section or provide examples for other browsers (e.g., Firefox, Chrome) and clarify that the process is similar across platforms.
  • Explicitly mention that the Reference String can be obtained on any OS and provide at least one Linux-specific example (e.g., using curl in a Linux terminal to view response headers).
  • Consider reordering the examples or providing a tabbed interface for different operating systems (Windows, Linux, macOS) to ensure parity and avoid the perception of Windows-first bias.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/tier-migration.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/troubleshoot-issues.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation references Windows-specific tools (Fiddler) and does not provide Linux-equivalent examples or mention Linux tools for troubleshooting. While one example uses OpenSSL (a cross-platform tool), there is a lack of parity in suggesting or demonstrating Linux-native approaches or alternatives where relevant.
Recommendations:
  • When suggesting Fiddler, also mention Linux-compatible alternatives such as mitmproxy, curl, or tcpdump, and provide example commands.
  • Where browser developer tools are mentioned, clarify that these are available on all major platforms.
  • For all troubleshooting steps involving command-line tools, provide both Windows (PowerShell/CMD) and Linux (bash) example commands where applicable.
  • Explicitly state that OpenSSL commands work on both Windows and Linux, and provide installation guidance if needed.
  • Review the documentation for any other implicit Windows-first assumptions and ensure Linux users are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/troubleshoot-performance-issues.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.