Frontdoor

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

Bias Trend Over Time

Pages with Bias Issues

41 issues found
Showing 26-41 of 41 flagged pages
Frontdoor Troubleshoot common issues ...cs/blob/main/articles/frontdoor/troubleshoot-issues.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by recommending Fiddler (a Windows-centric tool) and referencing browser developer tools for troubleshooting, without mentioning Linux/macOS alternatives. The only explicit command-line example is for OpenSSL, which is cross-platform. No PowerShell or Windows-only command syntax is present, but the first troubleshooting tool listed is Fiddler, which may create friction for Linux/macOS users.
Recommendations
  • When suggesting troubleshooting tools, include cross-platform or Linux/macOS-native options such as curl, wget, or tcpdump alongside Fiddler.
  • Explicitly mention that OpenSSL commands work on Linux/macOS, and provide example usage for those platforms if needed.
  • When listing tools, avoid putting Windows-centric tools first, or provide parity by listing alternatives for all platforms.
  • Consider adding troubleshooting steps or screenshots from Linux/macOS environments where relevant.
GitHub Create Pull Request
Frontdoor Quickstart: Create an Azure Front Door using Bicep ...lob/main/articles/frontdoor/create-front-door-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and validation steps. However, PowerShell (a Windows-centric tool) is given equal prominence to CLI, and screenshots show PowerShell output specifically. There is a subtle Windows-first bias: PowerShell is featured as a primary method, and output screenshots are from PowerShell, which may be less familiar or accessible to Linux/macOS users. No Linux-specific shell examples (e.g., Bash) or notes about cross-platform usage are provided.
Recommendations
  • Feature Azure CLI examples first, as CLI is cross-platform and native to Linux/macOS.
  • Include screenshots of CLI output in addition to or instead of PowerShell output.
  • Add notes clarifying that Azure CLI works on all platforms, and PowerShell is optional.
  • Consider mentioning Bash or shell scripting for Linux users where relevant.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI.
GitHub Create Pull Request
Frontdoor Configure HTTPS on Front Door (classic) custom domain ...n/articles/frontdoor/front-door-custom-domain-https.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by presenting PowerShell instructions and references before Azure CLI equivalents, and by using PowerShell as the primary example in several sections. While Azure CLI instructions are provided, PowerShell (a Windows-centric tool) is given prominence, which may create minor friction for Linux/macOS users who typically prefer CLI or Bash-based workflows.
Recommendations
  • Present Azure CLI and PowerShell instructions side-by-side or in parallel tabs, ensuring equal visibility.
  • Where possible, use Azure CLI as the default or first example, as it is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that both Azure CLI and PowerShell are supported on all platforms, and link to installation guides for Linux/macOS.
  • Add Bash script examples for common tasks, especially for certificate management and DNS updates, to further improve parity.
  • Review language to avoid implying PowerShell is the default or preferred tool.
GitHub Create Pull Request
Frontdoor Migrate Azure CDN from Edgio to Azure Front Door ...b/main/articles/frontdoor/migrate-cdn-to-front-door.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation 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 in hosts file instructions. There are no Linux-specific command examples, and PowerShell is mentioned explicitly, but Linux alternatives are only briefly referenced. No Linux/macOS-specific troubleshooting or parity guidance is provided.
Recommendations
  • Present Linux and Windows tools/examples side-by-side, or alternate which is listed first.
  • Provide explicit Linux/macOS command examples (e.g., show 'wget' and 'curl' commands, not just mention them).
  • Include Linux/macOS-specific troubleshooting tips where relevant.
  • Reference Linux file paths before or alongside Windows paths in instructions.
  • Clarify that all steps are applicable to Linux/macOS unless otherwise noted.
GitHub Create Pull Request
Frontdoor Secure your Origin with Private Link in Azure Front Door Premium ...zure-docs/blob/main/articles/frontdoor/private-link.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as a method for approving private endpoint connections alongside Azure CLI and portal, but lists PowerShell before CLI. No explicit Linux/macOS examples or tools are highlighted, and no Linux-specific guidance is provided. However, the Azure CLI is cross-platform and is mentioned, so Linux users are not blocked from completing the task.
Recommendations
  • List Azure CLI before Azure PowerShell when describing approval methods, as CLI is cross-platform.
  • Explicitly state that Azure CLI works on Linux/macOS and provide example commands for both CLI and PowerShell.
  • Add a note or section confirming parity of functionality for Linux/macOS users.
  • Where possible, provide example commands for common Linux shell environments (e.g., bash) alongside PowerShell.
GitHub Create Pull Request
Frontdoor Azure Front Door (Classic) To Standard/Premium Tier Migration ...re-docs/blob/main/articles/frontdoor/tier-migration.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by referencing Azure PowerShell and CLI for migration, but only provides a direct link to a PowerShell-based migration guide. There is no explicit mention of Linux/macOS-specific tools, nor are there examples or links for Bash, shell scripting, or Linux-native workflows. The DevOps section lists PowerShell before CLI, API, and Terraform, and the related content prioritizes PowerShell migration guidance over CLI or cross-platform alternatives.
Recommendations
  • Add explicit instructions and examples for Azure CLI and Terraform-based migration, including links to relevant guides.
  • Ensure that migration steps and automation scripts are shown for both PowerShell and Bash/shell environments.
  • In the 'Related content' section, provide parity by including links to CLI and Terraform migration guides alongside PowerShell.
  • When listing tools or scripting options, alternate or balance the order (e.g., CLI before PowerShell, or mention both together) to avoid Windows-first perception.
GitHub Create Pull Request
Frontdoor Quickstart: Create an Azure Front Door using Bicep ...lob/main/articles/frontdoor/create-front-door-bicep.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and validation steps. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and screenshots are exclusively from PowerShell output. There is a subtle Windows bias in the ordering and visual emphasis, as well as in the choice of tools highlighted.
Recommendations
  • Include screenshots of Azure CLI output alongside PowerShell output to provide parity for Linux/macOS users.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell, or clarify that both are equally supported.
  • Add notes about installing and using Azure CLI on Linux/macOS.
  • Avoid exclusive use of PowerShell screenshots in critical steps.
GitHub Create Pull Request
Frontdoor Configure HTTPS on Front Door (classic) custom domain ...n/articles/frontdoor/front-door-custom-domain-https.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by presenting PowerShell instructions and references before Azure CLI equivalents in several sections. PowerShell is a Windows-centric tool, and its precedence may subtly favor Windows users. However, Azure CLI instructions are also provided, and most steps are performed via the Azure portal or Cloud Shell, which are cross-platform. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks described.
Recommendations
  • Alternate the order of PowerShell and Azure CLI instructions, or present Azure CLI first to better reflect cross-platform usage.
  • Explicitly mention that both PowerShell and Azure CLI are available in Cloud Shell, which works on any OS.
  • Add a note clarifying that all steps can be performed on Linux/macOS using Azure CLI or the portal.
  • Consider providing bash script examples where appropriate for Linux users.
GitHub Create Pull Request
Frontdoor Migrate Azure CDN from Edgio to Azure Front Door ...b/main/articles/frontdoor/migrate-cdn-to-front-door.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits 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-specific file paths (hosts file location) prior to Linux. While Linux tools are mentioned, examples and instructions tend to favor Windows first, and there are no explicit Linux command examples beyond mentioning 'wget'.
Recommendations
  • Present Linux and Windows tools/examples in parallel, or alternate which is listed first.
  • Provide explicit Linux command examples (e.g., show full wget usage, dig, hosts file editing) alongside Windows/PowerShell equivalents.
  • Include macOS instructions where relevant (e.g., hosts file location, command-line tools).
  • Clarify that all steps are cross-platform unless otherwise noted, and highlight any platform-specific caveats.
GitHub Create Pull Request
Frontdoor Secure your Origin with Private Link in Azure Front Door Premium ...zure-docs/blob/main/articles/frontdoor/private-link.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as a method for approving private endpoint connections alongside Azure CLI and Azure Portal, listing PowerShell before CLI. There are no explicit code examples in this page, but the reference to PowerShell as a primary tool and its placement before CLI may subtly prioritize Windows tooling. No Linux/macOS-specific instructions or examples are provided, but CLI is mentioned, which is cross-platform.
Recommendations
  • List Azure CLI before Azure PowerShell when describing approval methods, as CLI is cross-platform.
  • Explicitly state that Azure CLI works on Linux/macOS and provide example commands for both CLI and PowerShell in referenced documentation.
  • Add a note clarifying parity of features and tooling across Windows, Linux, and macOS.
  • Where possible, link to documentation pages that show both CLI and PowerShell examples, or ensure referenced pages do so.
GitHub Create Pull Request
Frontdoor Endpoints in Azure Front Door ...cs/azure-docs/blob/main/articles/frontdoor/endpoint.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation 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 primarily a Windows 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 inclusion and emphasis on PowerShell may suggest a slight Windows bias.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash or shell script examples for Linux/macOS users, if relevant.
  • Consider including REST API or ARM template JSON examples, which are platform-neutral.
  • If PowerShell is included, note that it is available on Linux/macOS, or provide guidance for non-Windows users.
GitHub Create Pull Request
Frontdoor Troubleshoot common issues ...cs/blob/main/articles/frontdoor/troubleshoot-issues.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific troubleshooting tools (Fiddler) and listing them before cross-platform alternatives (browser developer tools). The only explicit command-line example provided uses OpenSSL, which is cross-platform, but the mention of Fiddler as a primary tool may create friction for Linux/macOS users unfamiliar with it or unable to use it.
Recommendations
  • When suggesting troubleshooting tools, list cross-platform options first (e.g., browser developer tools, curl, OpenSSL) and mention Windows-specific tools like Fiddler as alternatives.
  • Provide Linux/macOS-specific examples or tool recommendations where appropriate (e.g., Wireshark, tcpdump, curl).
  • Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific steps.
  • Explicitly state that OpenSSL commands work on Linux/macOS and provide installation guidance if needed.
GitHub Create Pull Request
Frontdoor Secure your Origin with Private Link in Azure Front Door Premium ...zure-docs/blob/main/articles/frontdoor/private-link.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as a method for approving private endpoint connections alongside Azure CLI and Azure Portal, listing PowerShell before CLI. No explicit Linux/macOS examples or tools are highlighted, and no command-line examples are shown at all. The documentation does not provide parity guidance for Linux users or clarify cross-platform equivalence for management tasks.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide example commands for both Azure CLI and Azure PowerShell, with CLI examples shown first or side-by-side.
  • Clarify that all management actions (approval, removal, etc.) can be performed equally on Linux/macOS using Azure CLI.
  • Add a note or section on platform compatibility for management tools.
GitHub Create Pull Request
Frontdoor Endpoints in Azure Front Door ...cs/azure-docs/blob/main/articles/frontdoor/endpoint.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring endpoint domain reuse, but PowerShell (a Windows-centric tool) is given equal prominence to the CLI. The CLI is cross-platform, but PowerShell is primarily associated with Windows. No Linux/macOS-specific shell examples (such as Bash) are given, and PowerShell is presented before Bicep, which is platform-neutral. There are no explicit Linux/macOS instructions or notes.
Recommendations
  • Emphasize Azure CLI as the primary example since it is cross-platform and works natively on Linux/macOS.
  • Add explicit Bash or shell script examples for Linux/macOS users, if relevant.
  • Clarify that Azure CLI commands work on all platforms, and note any platform-specific requirements for PowerShell.
  • Consider listing Azure CLI examples before PowerShell to reduce perceived Windows-first bias.
  • Add a note or section for Linux/macOS users to ensure parity and clarity.
GitHub Create Pull Request
Frontdoor Configure HTTPS on Front Door (classic) custom domain ...n/articles/frontdoor/front-door-custom-domain-https.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by presenting PowerShell instructions and references before Azure CLI equivalents, and by using PowerShell as the default example in several sections. However, Azure CLI instructions are provided for most tasks, and the use of Azure Cloud Shell mitigates platform-specific issues. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks using the CLI or portal.
Recommendations
  • Present Azure CLI and PowerShell instructions side-by-side or in a neutral order, rather than defaulting to PowerShell first.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and is accessible from any OS.
  • Add a brief note clarifying that all steps can be completed on Linux/macOS using Azure CLI and Cloud Shell.
  • Where possible, use generic terms like 'command line' or 'terminal' instead of 'PowerShell' when referring to cross-platform actions.
GitHub Create Pull Request
Frontdoor Azure Front Door ...cs/blob/main/articles/frontdoor/front-door-overview.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Front Door demonstrates mild Windows bias. In the 'Deliver modern apps and architectures' section, PowerShell is explicitly mentioned as a supported DevOps tool, and it is listed before other cross-platform tools like CLI, Bicep, and ARM templates. There are no explicit Linux/macOS examples or tools highlighted, and no mention of Bash, shell scripting, or Linux-specific patterns. However, the bias is limited to tool listing order and does not prevent Linux/macOS users from understanding or using the service.
Recommendations
  • Explicitly mention Bash or shell scripting alongside PowerShell when listing supported DevOps tools.
  • Provide example commands for both Azure CLI and PowerShell in relevant sections.
  • Ensure that cross-platform tools (e.g., Azure CLI, Bicep) are listed before or alongside Windows-specific tools like PowerShell.
  • Add a note clarifying that all major features are accessible from Linux/macOS environments using Azure CLI and SDKs.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →