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 101-125 of 130 flagged pages
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/origin-security.md
...e-docs/blob/main/articles/frontdoor/origin-security.md
Medium Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-terraform.md
...main/articles/frontdoor/create-front-door-terraform.md
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/standard-premium/how-to-enable-private-link-apim.md
...or/standard-premium/how-to-enable-private-link-apim.md
Medium Priority
View Details →
Detected Bias Types
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').
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-portal.md
...ob/main/articles/frontdoor/create-front-door-portal.md
Medium Priority
View Details →
Detected Bias Types
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).
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/create-front-door-terraform.md
...main/articles/frontdoor/create-front-door-terraform.md
Medium Priority
View Details →
Detected Bias Types
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.
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
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/how-to-enable-private-link-application-gateway.md
...door/how-to-enable-private-link-application-gateway.md
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/integrate-storage-account.md
...b/main/articles/frontdoor/integrate-storage-account.md
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/managed-identity.md
...-docs/blob/main/articles/frontdoor/managed-identity.md
Medium Priority
View Details →
Detected Bias Types
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).
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/origin-authentication-with-managed-identities.md
...tdoor/origin-authentication-with-managed-identities.md
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/origin-security.md
...e-docs/blob/main/articles/frontdoor/origin-security.md
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/refstring.md
...s/azure-docs/blob/main/articles/frontdoor/refstring.md
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/frontdoor/troubleshoot-issues.md
...cs/blob/main/articles/frontdoor/troubleshoot-issues.md
Medium Priority
View Details →
Detected Bias Types
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.
Frontdoor
Quickstart: Create an Azure Front Door using Bicep
...lob/main/articles/frontdoor/create-front-door-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and validation steps. However, PowerShell (a Windows-centric tool) is given equal prominence to CLI, and screenshots are exclusively from PowerShell output. There is a subtle Windows-first bias in the imagery and tool selection, but Linux/macOS users can complete all tasks using Azure CLI. No Linux-specific shell examples or screenshots are provided.
Recommendations
- Include screenshots of Azure CLI output alongside PowerShell output to represent Linux/macOS workflows.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows.
- Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform.
- Add notes or links for installing Azure CLI on Linux/macOS.
- If possible, add bash/zsh shell snippets for common tasks (e.g., file creation, navigation) relevant to Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Bicep, but the PowerShell example is given equal prominence to the CLI example, and no Linux/macOS-specific shell examples (such as Bash or shell scripting) are provided. The CLI example is cross-platform, but the presence of PowerShell (which is traditionally Windows-centric) and the lack of explicit Linux/macOS guidance or troubleshooting tips may create minor friction for non-Windows users.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Consider adding Bash or shell script examples for endpoint creation, especially if there are nuances for Linux/macOS users.
- If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide links to installation instructions for non-Windows systems.
- Ensure that troubleshooting or configuration steps do not assume a Windows environment.
Frontdoor
Configure HTTPS on Front Door (classic) custom domain
...n/articles/frontdoor/front-door-custom-domain-https.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias: PowerShell is presented as the first option for command-line automation, and PowerShell-specific instructions are given equal prominence to Azure CLI, which is cross-platform. There are no explicit Linux/macOS examples, nor are Linux-specific tools or shell patterns mentioned. However, Azure CLI is documented, and all instructions are compatible with Linux/macOS via Azure CLI and Cloud Shell, so Linux users are not blocked from completing the task.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI and Cloud Shell work on Linux/macOS, and provide example commands for bash/zsh where relevant.
- Add a note clarifying that PowerShell is available on Linux/macOS, but Azure CLI may be more familiar to non-Windows users.
- Where local installation is discussed, include installation links for Linux/macOS (e.g., apt, yum, Homebrew) for Azure CLI and PowerShell.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation mentions integration with DevOps-friendly command line tools, specifically listing PowerShell alongside CLI, SDKs, Bicep, and ARM templates. PowerShell is a Windows-centric tool, and its explicit mention without equal emphasis on Bash or Linux-native tools may suggest a Windows bias. There are no platform-specific examples, but the only shell mentioned by name is PowerShell, and there is no reference to Linux/macOS equivalents or usage patterns.
Recommendations
- Explicitly mention Bash or Linux shell support alongside PowerShell when discussing command line tools.
- Provide examples or links for both Azure CLI and PowerShell, clarifying cross-platform compatibility.
- Add a note or section highlighting how Linux/macOS users can interact with Azure Front Door using their native tools.
- Ensure parity in documentation by including Linux/macOS-specific guidance or troubleshooting where relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by mentioning Windows-specific troubleshooting tools (Fiddler) and listing them before cross-platform or Linux-native alternatives. The only explicit command-line example is for OpenSSL, which is cross-platform, but browser developer tools and Fiddler are referenced for debugging without mention of Linux/macOS equivalents. No PowerShell or Windows-only configuration steps are present, and most instructions are GUI-based and platform-neutral.
Recommendations
- When suggesting troubleshooting tools, mention cross-platform alternatives alongside Windows tools (e.g., suggest curl, tcpdump, Wireshark, or browser developer tools for Linux/macOS users).
- If referencing Fiddler, clarify its platform limitations and suggest alternatives for non-Windows users.
- Provide example commands for Linux/macOS where relevant, especially for tasks like inspecting HTTP headers.
- Ensure screenshots and instructions for Azure portal actions are clearly platform-neutral.
- Consider listing cross-platform tools first or equally with Windows tools.
Frontdoor
Migrate Azure CDN from Edgio to Azure Front Door
...b/main/articles/frontdoor/migrate-cdn-to-front-door.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates mild Windows bias by listing Windows/PowerShell tools before Linux equivalents (e.g., 'Invoke-WebRequest on Windows using PowerShell' before 'Wget on Linux'), and referencing Windows file paths before Linux ones. Some examples and tool recommendations are Windows-centric, with Linux alternatives mentioned but not equally emphasized. There are no Linux-specific command examples, and PowerShell is referenced as the default for Windows users.
Recommendations
- Present Linux and Windows tools/examples in parallel, rather than listing Windows first.
- Provide explicit Linux/macOS command examples (e.g., show both wget and curl usage, not just mention them).
- When referencing file paths (e.g., hosts file), list Linux/macOS and Windows locations together, or alternate the order.
- Include shell commands for Linux/macOS users where PowerShell is shown for Windows.
- Mention cross-platform tools (e.g., curl) that work on both Windows and Linux.
- Ensure monitoring tool recommendations include open-source/Linux-friendly options.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation mentions integration with DevOps-friendly command line tools, specifically listing PowerShell alongside CLI, Bicep, ARM templates, and SDKs. PowerShell is a Windows-centric tool, and its mention without explicit reference to Linux/macOS alternatives (such as Bash or shell scripting) or parity in examples suggests a subtle Windows bias. No Linux/macOS-specific tools or examples are provided, and PowerShell is listed as a primary automation method.
Recommendations
- Explicitly mention that Azure CLI and PowerShell are cross-platform, and provide links or notes on how to use these tools on Linux/macOS.
- Include Linux/macOS-specific examples or references, such as Bash scripts or usage in native terminals.
- Clarify that all automation and management tasks can be performed on Linux/macOS, not just Windows.
- Consider listing CLI before PowerShell to avoid Windows-first impression.
- Add a section or note highlighting platform parity for DevOps and automation tools.
Frontdoor
Settings mapping between Azure Front Door (classic) and Standard/Premium tier
...zure-docs/blob/main/articles/frontdoor/tier-mapping.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by listing Azure PowerShell as the only command-line migration example in the 'Next steps' section, without mentioning Linux/macOS-friendly alternatives such as Azure CLI or REST API. Additionally, PowerShell is referenced before the Azure portal, which is cross-platform.
Recommendations
- Add Azure CLI migration instructions or links alongside PowerShell to ensure Linux/macOS parity.
- Mention REST API or ARM template options for automation, which are platform-neutral.
- List cross-platform tools (Azure portal, CLI) before platform-specific ones (PowerShell) in 'Next steps'.
Frontdoor
Quickstart: Create an Azure Front Door using Bicep
...lob/main/articles/frontdoor/create-front-door-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup. However, PowerShell examples and screenshots are included and highlighted, which are primarily relevant to Windows users. The screenshot of deployment output is specifically from PowerShell, and PowerShell commands are presented alongside CLI commands throughout. There is no mention of Linux/macOS-specific considerations, and PowerShell is a Windows-centric tool, though it is available cross-platform. The CLI examples (which are cross-platform) are present, but PowerShell is given equal prominence, and the only screenshot is Windows/PowerShell-specific.
Recommendations
- Include screenshots of Azure CLI output, which is more universally applicable across platforms.
- Clarify that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, but CLI is more commonly used on Linux/macOS.
- Consider listing CLI examples before PowerShell examples to reduce implicit Windows-first bias.
- Add notes or links for installing Azure CLI and PowerShell on Linux/macOS, if relevant.
- Explicitly state that all steps can be completed on Linux/macOS using Azure CLI.
Frontdoor
Configure HTTPS on Front Door (classic) custom domain
...n/articles/frontdoor/front-door-custom-domain-https.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by presenting PowerShell instructions and references before Azure CLI equivalents in several sections. The PowerShell tab is listed first in prerequisites and service principal registration, and instructions for running commands locally reference PowerShell before CLI. However, Azure CLI examples are provided for most steps, and the use of Azure Cloud Shell mitigates platform-specific issues. There are no Windows-only tools or missing Linux/macOS examples, but the ordering and emphasis may create minor friction for non-Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI tabs, or present CLI first to avoid implicit prioritization of Windows tools.
- Explicitly mention that both PowerShell and CLI are cross-platform and supported on Linux/macOS.
- Add a brief note clarifying that Azure Cloud Shell supports both PowerShell and CLI regardless of the user's OS.
- Ensure all examples and instructions are equally detailed for both PowerShell and CLI.
- Consider adding explicit Linux/macOS installation instructions for Azure CLI and PowerShell, or link to relevant documentation.
Low Priority
View Details →
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. PowerShell is a Windows-centric tool, and no Linux/macOS-specific shell examples (such as Bash or direct REST API usage) are provided. The CLI example is cross-platform, but the presence of PowerShell and lack of explicit Linux/macOS guidance may create friction for non-Windows users.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider omitting or de-emphasizing PowerShell examples unless there is unique functionality.
- Add explicit Bash or shell script examples for Linux/macOS users, if applicable.
- Provide guidance for using REST API or ARM templates directly from Linux/macOS environments.
- Ensure example ordering starts with the most cross-platform tool (Azure CLI) and clarifies platform compatibility.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions configuring wildcard domains using Azure Resource Manager API, Bicep, PowerShell, and Azure CLI, but lists PowerShell before Azure CLI and does not provide any explicit Linux/macOS-specific instructions or examples. There is a subtle bias toward Windows tooling (PowerShell) and no parity examples for Linux/macOS users, such as bash or shell commands, nor clarification that Azure CLI is cross-platform.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
- Provide example commands for both PowerShell (Windows) and bash/shell (Linux/macOS) when mentioning configuration via CLI.
- Explicitly mention Linux/macOS compatibility in sections discussing tooling, especially where PowerShell is referenced.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform support.