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 1-25 of 130 flagged pages
Frontdoor
Quickstart: Create an Azure Front Door using an ARM template
.../main/articles/frontdoor/create-front-door-template.md
High Priority
View Details →
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 template deployment and resource cleanup, referencing PowerShell output screenshots, and guiding users through Windows-centric workflows. Although it briefly mentions that Azure CLI and REST API are alternative methods, no examples or guidance for Linux-friendly tools (such as Azure CLI/bash) are provided, making the instructions less accessible for Linux users.
Recommendations
- Add equivalent Azure CLI (bash) examples for template deployment and resource cleanup alongside PowerShell scripts.
- Include screenshots or output examples from Azure CLI to complement PowerShell visuals.
- Present both Windows and Linux instructions in parallel, or alternate which platform is shown first.
- Explicitly mention platform compatibility for each method and link to cross-platform documentation.
- Ensure that references to tools (e.g., Cloud Shell) clarify that both bash and PowerShell environments are available.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates Windows bias by listing Windows-centric tools (PowerShell) before or alongside cross-platform options (Azure CLI, Bicep, ARM API) when describing how to configure wildcard domains with Azure DNS. There are no explicit Linux shell or bash examples, and no mention of Linux-specific tooling or workflows. The order of tool presentation (PowerShell before CLI) and lack of Linux command-line examples suggest a preference for Windows environments.
Recommendations
- Provide explicit bash or Linux shell examples for all configuration steps, especially for Azure CLI and ARM API usage.
- List cross-platform tools (Azure CLI, Bicep, ARM API) before Windows-specific tools (PowerShell) when enumerating options.
- Clarify that all listed tools (CLI, Bicep, ARM API, PowerShell) are available on Linux, macOS, and Windows, and provide links to installation guides for each platform.
- Add a section or note highlighting Linux/macOS parity and best practices for users on those platforms.
- Avoid using PowerShell as the default or first example unless it is the only supported method.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly referencing Azure PowerShell migration instructions and omitting equivalent guidance for Linux users (e.g., Azure CLI or Bash). The 'Related content' section lists PowerShell migration before mentioning any cross-platform alternatives, and there are no examples or instructions for Linux-native tools or workflows.
Recommendations
- Add migration instructions using Azure CLI or Bash scripts, which are cross-platform and commonly used on Linux.
- Ensure that references to platform-specific tools (e.g., PowerShell) are accompanied by alternatives for Linux/macOS users.
- Present cross-platform or Linux-native options (such as Azure CLI) before or alongside Windows-specific tools in the documentation.
- Include explicit examples for updating DNS records using Linux tools (e.g., dig, nsupdate) where relevant.
- Review and update the 'Related content' section to feature cross-platform migration guides with equal prominence.
Frontdoor
Quickstart: Create an Azure Front Door using Bicep
...lob/main/articles/frontdoor/create-front-door-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing Azure Front Door resources, but it gives equal prominence to PowerShell (a Windows-centric tool) alongside CLI. Screenshots and output examples are exclusively from PowerShell, and there is no mention of Linux-specific shell environments (e.g., Bash) or guidance for Linux users. The documentation does not acknowledge platform differences or provide Linux-specific context, which may make it less approachable for non-Windows users.
Recommendations
- Include explicit Bash examples and instructions for Linux/macOS users, especially for saving files and running CLI commands.
- Provide screenshots or output examples from Azure CLI in a Bash shell, not just PowerShell.
- Add a note clarifying that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Avoid using only PowerShell output/screenshots; alternate or supplement with CLI/Bash examples.
- Mention installation instructions or prerequisites for Azure CLI and PowerShell on both Windows and Linux platforms.
Frontdoor
Azure Front Door (classic) retirement FAQ
...blob/main/articles/frontdoor/classic-retirement-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by consistently referencing Azure PowerShell as the primary command-line tool for migration and management tasks, without mentioning or providing examples for cross-platform alternatives such as Azure CLI or Bash. The migration instructions and certificate management guidance link only to PowerShell-based documentation, and there are no Linux-specific or platform-neutral examples. This may disadvantage users on Linux or macOS systems, or those who prefer Azure CLI.
Recommendations
- Add Azure CLI examples and links alongside PowerShell instructions for all management and migration tasks.
- Explicitly mention that both Azure PowerShell and Azure CLI are supported, and clarify any platform-specific requirements.
- Provide Bash or shell script examples for common operations, especially for certificate management and migration.
- Review linked documentation (e.g., BYOC, migration guides) to ensure Linux parity and cross-platform guidance.
- Include a section or table comparing available tools (Azure portal, PowerShell, CLI, Terraform) with notes on platform compatibility.
Frontdoor
Comparison between Azure Front Door and Azure CDN services
...b/main/articles/frontdoor/front-door-cdn-comparison.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page mentions management via REST API, .NET, de.js, or PowerShell, but does not mention Linux-native tools or CLI options such as Azure CLI or Bash scripting. PowerShell, a Windows-centric tool, is listed explicitly as a management option, and is mentioned before any Linux equivalents. There are no examples or references to Linux-specific tools, shell commands, or cross-platform management patterns. This suggests a bias towards Windows and PowerShell usage patterns.
Recommendations
- Explicitly mention Azure CLI as a cross-platform management tool alongside PowerShell.
- Provide example commands for both PowerShell and Azure CLI/Bash where management actions are discussed.
- Include references to Linux-native tools and workflows, such as Bash scripting, when describing integration and automation.
- Reorder tool mentions to avoid listing Windows-centric tools first; consider grouping cross-platform tools together.
- Add a note clarifying that all management actions can be performed from Linux, macOS, and Windows environments.
High 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, despite PowerShell being primarily a Windows tool. There are no Linux shell-specific examples (such as Bash or shell scripting), and PowerShell is mentioned before Bicep, which is platform-neutral. The documentation does not mention Linux-specific tools or patterns, nor does it clarify cross-platform usage for CLI commands.
Recommendations
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux users.
- Add explicit Bash or shell script examples for Linux users, especially for endpoint creation.
- De-emphasize PowerShell as a primary example, or move it after CLI/Bicep examples.
- Include notes on how to run Azure CLI commands in Linux environments.
- Mention that Bicep and ARM templates are platform-neutral and suitable for both Windows and Linux users.
Frontdoor
Configure HTTPS on Front Door (classic) custom domain
...n/articles/frontdoor/front-door-custom-domain-https.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions and references before Azure CLI equivalents, emphasizing PowerShell and Azure Cloud Shell (which defaults to PowerShell), and referencing Windows-centric tools and patterns. There is a lack of explicit Linux-specific guidance, and the documentation assumes familiarity with Windows/PowerShell workflows. Azure CLI is mentioned, but PowerShell is consistently given prominence and detail first.
Recommendations
- Alternate the order of PowerShell and Azure CLI instructions, or present Azure CLI first to avoid implicit Windows-first bias.
- Explicitly mention Linux/macOS compatibility and provide guidance for running Azure CLI and PowerShell on those platforms.
- Include examples of using Azure CLI in native Linux/macOS terminals, not just Azure Cloud Shell.
- Add troubleshooting or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, using bash/zsh).
- Clarify that both PowerShell and Azure CLI are cross-platform, and provide links to relevant installation guides for Linux/macOS.
- Where possible, provide bash script equivalents for common operations, especially for certificate management and DNS validation.
High 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 equivalents (such as Bash or Linux shell scripting) or clarification that PowerShell Core is cross-platform may imply a Windows bias. There are no explicit examples or instructions for Linux users, nor are Linux-specific tools or patterns mentioned.
Recommendations
- Clarify that PowerShell Core is available cross-platform, or explicitly mention Bash and Linux shell scripting as supported options.
- Provide example commands for both Azure CLI and Bash, in addition to PowerShell, to ensure parity for Linux users.
- Include references to Linux-native tools and workflows where relevant, and avoid listing Windows-centric tools first unless justified by usage statistics.
- Add a note or section highlighting cross-platform support and best practices for both Windows and Linux environments.
Frontdoor
Migrate Azure CDN from Edgio to Azure Front Door
...b/main/articles/frontdoor/migrate-cdn-to-front-door.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools and patterns are mentioned before their Linux equivalents (e.g., 'Invoke-WebRequest on Windows using PowerShell' is listed alongside 'Wget on Linux', but PowerShell is referenced first and more prominently throughout), Windows file paths and instructions are given before Linux ones (e.g., hosts file location), and PowerShell/Windows-centric terminology is used. There is a lack of parity in example commands and troubleshooting steps for Linux users, and some steps (such as modifying the hosts file) provide more detail for Windows than Linux.
Recommendations
- Present Linux and Windows tools/examples side-by-side, or alternate which is mentioned first.
- Provide equivalent example commands for both platforms (e.g., show both 'wget' and 'Invoke-WebRequest' syntax).
- When referencing file paths (such as the hosts file), list Linux and Windows locations together and with equal detail.
- Include troubleshooting steps and screenshots for both Linux and Windows environments.
- Avoid Windows-centric terminology when describing generic steps (e.g., use 'command line' instead of 'PowerShell' unless specifically required).
- Explicitly mention cross-platform alternatives for monitoring and DNS tools (e.g., curl, dig, nslookup) and provide usage examples for both OSes.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric technologies like IIS are given dedicated configuration examples, and the IIS example is presented before the Linux equivalent (NGINX on AKS). There is no example for configuring Apache or NGINX outside of AKS, nor for Linux VMs running common web servers. The IIS example uses Windows-specific configuration formats (XML/web.config), while Linux equivalents (e.g., Apache .htaccess, NGINX config) are missing. There are no PowerShell command examples, but the overall pattern is to provide more explicit guidance for Windows tools and environments.
Recommendations
- Add explicit configuration examples for popular Linux web servers such as Apache (using .htaccess or httpd.conf) and NGINX (outside AKS), showing how to filter requests by the X-Azure-FDID header.
- Present Linux and Windows examples side-by-side or in parallel tabs, rather than listing IIS first.
- Include guidance for configuring firewall rules on Linux VMs (e.g., using iptables, ufw, or firewalld) to restrict access by IP/service tag.
- Reference Linux-native tools and patterns (e.g., systemd, SELinux, auditd) where relevant for securing origins.
- Ensure parity in depth and clarity between Windows and Linux examples, avoiding implicit prioritization of Windows environments.
Frontdoor
Post Migration Dev-Ops Experience
...rticles/frontdoor/post-migration-dev-ops-experience.md
High Priority
View Details →
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 Azure PowerShell, and references to Windows installation paths) before or alongside cross-platform alternatives. PowerShell is given a dedicated section with detailed instructions, while Linux-specific considerations (such as Bash, shell scripting, or Linux package managers) are absent. Installation links and examples often default to Windows or do not clarify Linux parity, and there are no explicit Linux or macOS examples or troubleshooting notes.
Recommendations
- Add explicit Linux/macOS installation instructions and links for all tools (Terraform, Azure CLI, Bicep, PowerShell).
- Provide Bash or shell script examples alongside PowerShell, especially for pipeline automation.
- Clarify that Azure CLI and Terraform are cross-platform, and include Linux-specific usage notes (e.g., package manager commands, file paths).
- Include troubleshooting or environment setup notes for Linux/macOS users (e.g., permissions, path differences).
- Balance the order of examples so that cross-platform or Linux-native tools (Azure CLI, Bash) are not listed after Windows-centric tools.
- Add references to Linux package managers (apt, yum, Homebrew) for installing CLI tools.
Frontdoor
Secure your Origin with Private Link in Azure Front Door Premium
...zure-docs/blob/main/articles/frontdoor/private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions Azure PowerShell and Azure portal as primary tools for approving private endpoint connections, with Azure CLI listed but not emphasized. There are no explicit Linux or cross-platform command examples, and the workflow descriptions tend to mention Windows-centric tools (PowerShell, portal) before CLI. No Linux-specific guidance or parity is provided for managing endpoints or troubleshooting.
Recommendations
- Provide explicit Azure CLI examples alongside PowerShell for all management tasks, especially for approving private endpoint connections.
- Clearly indicate that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add troubleshooting steps and workflow examples using Linux tools and shell environments.
- Ensure that references to management tools do not prioritize Windows-centric options; list CLI and portal first or equally.
- Include notes or links to Linux-specific documentation where relevant.
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools (Fiddler, IIS), providing configuration instructions only for Microsoft IIS (Windows web server), and omitting Linux/Unix equivalents (such as curl, wget, Apache, Nginx). Troubleshooting steps and examples are tailored to Windows environments, with no mention of how to perform similar checks or configurations on Linux systems.
Recommendations
- Include Linux/Unix command-line examples for checking HTTP headers (e.g., using curl or wget).
- Mention and provide guidance for configuring compression on popular Linux web servers such as Apache (mod_deflate) and Nginx (gzip module).
- List cross-platform tools for inspecting HTTP responses, such as curl, httpie, or browser developer tools on Linux.
- Present troubleshooting steps for both Windows and Linux origins, ensuring parity in guidance and examples.
- Avoid assuming IIS is the only possible origin server; acknowledge other server types and provide relevant instructions.
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning Windows-centric troubleshooting tools (Fiddler, browser developer tools) and omitting Linux equivalents. The order of tool recommendations places Windows tools first, and there are no examples or instructions for Linux users (e.g., using curl, tcpdump, or Wireshark for troubleshooting). This may hinder Linux users from efficiently following the troubleshooting steps.
Recommendations
- Include Linux troubleshooting tool examples (e.g., curl, tcpdump, Wireshark, wget) alongside or before Windows tools.
- Provide command-line examples for both Windows (PowerShell, CMD) and Linux (bash, shell) when suggesting diagnostics.
- Mention cross-platform tools (such as browser developer tools) as universally available, but clarify usage on both Windows and Linux.
- When referencing tools like Fiddler, also suggest Linux alternatives (e.g., mitmproxy, Charles Proxy).
- Ensure screenshots and UI instructions are not Windows-specific, or provide Linux equivalents where applicable.
Frontdoor
Connect Front Door Premium to an Azure API Management origin with Private Link
...or/standard-premium/how-to-enable-private-link-apim.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides three pivots: Azure Portal, Azure PowerShell, and Azure CLI. The PowerShell pivot is detailed and uses Windows-centric tooling (PowerShell), which is most commonly associated with Windows environments. The PowerShell section appears before the CLI section, and the CLI section is not as detailed in terms of explanations. There is a strong emphasis on Azure PowerShell and Cloud Shell, which may be less familiar or less native to Linux users compared to Bash or native CLI usage. There are no explicit Linux shell/Bash examples, nor any mention of Linux-specific considerations or parity.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, demonstrating usage in native Linux environments.
- Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide installation instructions for Linux.
- Consider moving the CLI pivot before the PowerShell pivot, or presenting both equally, to avoid Windows-first ordering.
- Mention that Cloud Shell supports Bash and PowerShell, and highlight Bash as a first-class option for Linux users.
- Where PowerShell is referenced, note that it is available cross-platform, but CLI/Bash is more common on Linux.
- Add troubleshooting or environment notes for Linux users, such as file path conventions, authentication, or permissions.
Frontdoor
Azure Front Door (Classic) To Standard/Premium Tier Migration
...re-docs/blob/main/articles/frontdoor/tier-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and CLI tools for migration, mentioning PowerShell before CLI, and providing a dedicated migration guide for PowerShell but not for Linux shell environments. There are no explicit Linux or bash examples, and the DevOps section lists PowerShell first when discussing script changes. The related content links include a PowerShell-specific migration guide, but lack parity for bash/CLI or Terraform workflows.
Recommendations
- Add explicit Linux/bash examples for migration steps, including Azure CLI commands.
- Provide a migration guide for Linux users, similar to the PowerShell guide (e.g., 'migrate-tier-cli.md').
- Mention Azure CLI and Terraform equally or before PowerShell when listing automation options.
- Ensure all examples and instructions are cross-platform, with clear notes on OS-specific differences.
- Include references to Linux tools and scripting patterns in the DevOps section.
Frontdoor
Azure Front Door (classic) retirement FAQ
...blob/main/articles/frontdoor/classic-retirement-faq.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Azure PowerShell as the primary or sole command-line migration tool, with no mention of Linux-native tools (such as Azure CLI or Bash examples). The migration instructions and certificate management links default to PowerShell tabs, and there are no Linux-specific or cross-platform command-line examples provided. This may make the documentation less accessible to Linux users or those preferring non-Windows environments.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line instructions, especially for migration and certificate management.
- Explicitly mention that Azure CLI and Bash scripts can be used on Linux/macOS for managing Azure Front Door resources.
- Ensure that documentation links and tabs default to a cross-platform tool (e.g., Azure CLI) or provide both PowerShell and CLI options equally.
- Include references to Terraform and other cross-platform automation tools where relevant, and provide sample usage.
- Review all command-line tool instructions to ensure parity between Windows and Linux environments.
Frontdoor
Quickstart: Create an Azure Front Door using Bicep
...lob/main/articles/frontdoor/create-front-door-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
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 and output examples are shown only for PowerShell. There is no mention of Linux-specific shell environments, nor are there examples for Bash scripting or other Linux-native tools. The documentation does not clarify that Azure CLI is cross-platform, nor does it prioritize CLI (which is more universal) over PowerShell. This may unintentionally signal a bias toward Windows users and workflows.
Recommendations
- Prioritize Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Add explicit notes that Azure CLI works on Windows, Linux, and macOS, and provide Bash-specific usage tips where relevant.
- Include screenshots or output examples for Azure CLI, not just PowerShell.
- Mention that PowerShell Core is available on Linux/macOS if PowerShell must be included, or clarify its cross-platform nature.
- Consider adding a 'Linux/macOS' tab or section for shell-specific instructions if there are any differences.
- Avoid using Windows-centric terminology (e.g., 'local computer') without clarifying cross-platform support.
Frontdoor
Quickstart: Create an Azure Front Door using an ARM template
.../main/articles/frontdoor/create-front-door-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for template deployment and resource cleanup, referencing PowerShell output screenshots, and omitting equivalent Azure CLI (cross-platform) or Bash examples. Windows tools and patterns (PowerShell, right-click/paste instructions) are mentioned exclusively and before any Linux alternatives, despite Azure CLI being available and commonly used on Linux/macOS. The page does mention that other methods exist, but does not provide direct examples or parity for Linux users.
Recommendations
- Add Azure CLI (az) examples for template deployment and resource cleanup alongside PowerShell scripts.
- Include Bash shell instructions and screenshots where appropriate.
- Present both PowerShell and CLI examples in parallel, or default to CLI for cross-platform compatibility.
- Clarify instructions for copying/pasting in non-Windows terminals.
- Ensure screenshots and step-by-step instructions reflect both Windows and Linux user experiences.
- Explicitly mention that Azure CLI is available on all platforms and link to installation guides.
Frontdoor
Comparison between Azure Front Door and Azure CDN services
...b/main/articles/frontdoor/front-door-cdn-comparison.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page mentions management via REST API, .NET, de.js, or PowerShell, but does not mention Linux-native tools or CLI options such as Azure CLI or Bash scripting. PowerShell, a Windows-centric tool, is listed explicitly, and is mentioned before any Linux-friendly alternatives. There are no Linux-specific examples, nor is there mention of Linux command-line usage for service management.
Recommendations
- Add explicit references to Azure CLI and Bash scripting for service management alongside PowerShell.
- Provide example commands for both PowerShell and Azure CLI to demonstrate parity.
- Mention cross-platform management tools (e.g., Terraform, Ansible) where relevant.
- Ensure that Linux-friendly options are listed before or alongside Windows tools.
- Clarify that all management operations are available on Linux, macOS, and Windows platforms.
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation mentions configuration via Azure Resource Manager API, Bicep, PowerShell, and Azure CLI, but lists PowerShell (a Windows-centric tool) before Azure CLI and does not provide any Linux-specific examples or guidance. There are no explicit Linux shell or bash examples, nor is there mention of Linux-native tools or workflows. The ordering and tool selection suggest a Windows-first perspective.
Recommendations
- List Azure CLI before PowerShell when mentioning cross-platform tools, as CLI is natively supported on Linux and macOS.
- Provide explicit bash/Linux shell examples for domain and certificate management tasks.
- Clarify that Azure CLI and Bicep are cross-platform, and include links or notes for Linux/macOS installation and usage.
- Avoid implying PowerShell is the primary or default method for configuration; present CLI and API options equally.
- Add a section or note on managing wildcard domains from Linux environments, including troubleshooting tips specific to non-Windows platforms.
High 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 omits explicit Linux shell (bash) examples and does not mention cross-platform usage patterns. Azure PowerShell is Windows-centric and is listed before Bicep, which is platform-neutral. There is no mention of Linux-specific tools or considerations, and the CLI example does not clarify its cross-platform nature.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide bash-specific examples if there are differences.
- Add Linux shell (bash) examples or clarify that the Azure CLI example is suitable for Linux/macOS users.
- Consider listing platform-neutral tools (Azure CLI, Bicep) before Windows-centric tools (Azure PowerShell).
- Include a note about Azure PowerShell availability on Linux and macOS, or link to installation instructions for non-Windows platforms.
- Review documentation for any assumptions about the user's operating system and ensure parity in instructions for both Windows and Linux users.
Frontdoor
Configure HTTPS on Front Door (classic) custom domain
...n/articles/frontdoor/front-door-custom-domain-https.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell instructions and references before Azure CLI equivalents, and by emphasizing Windows-centric tools and workflows (such as PowerShell and Azure Cloud Shell with PowerShell). There is no mention of Linux-specific shell environments, nor are Linux command-line patterns or troubleshooting steps provided. The examples and instructions are platform-neutral in terms of Azure CLI, but the ordering and emphasis favor Windows/PowerShell users.
Recommendations
- Alternate the order of PowerShell and Azure CLI instructions, or present Azure CLI first to avoid implicit prioritization of Windows tools.
- Explicitly mention that Azure CLI commands can be run natively on Linux/macOS terminals, not just in Azure Cloud Shell.
- Add troubleshooting notes or examples for Linux/macOS users, such as certificate file formats, permissions, or common shell issues.
- Include references to Bash scripts or Linux-native tools where relevant, especially for certificate management and DNS configuration.
- Clarify that all steps can be performed on any OS with Azure CLI installed, and link to installation guides for Linux/macOS.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation mentions integration with 'DevOps friendly command line tools across SDKs of different languages, Bicep, ARM templates, CLI, and PowerShell.' PowerShell is explicitly called out, which is a Windows-centric tool, and it is listed alongside CLI without specifying cross-platform parity or providing Linux-specific examples. There are no Linux-specific tools or patterns mentioned, nor are there examples for Linux users. The documentation does not provide guidance or examples for Linux shell environments (e.g., Bash), nor does it mention Linux-native tools or workflows.
Recommendations
- Explicitly mention cross-platform compatibility of Azure CLI and provide examples for both Windows (PowerShell) and Linux (Bash).
- Include Linux-native tools or workflows where relevant, such as Bash scripts or integration with Linux package managers.
- Ensure that PowerShell is not listed before CLI or Bash unless there is a specific reason; consider listing CLI/Bash first to reflect cross-platform usage.
- Add a section or note clarifying that all command-line tools are available and supported on Linux, macOS, and Windows.
- Provide example commands for both PowerShell and Bash where automation or scripting is discussed.