Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1351-1375 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/ip-groups.md
...s/azure-docs/blob/main//articles/firewall/ip-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by providing only Azure PowerShell cmdlets for managing IP Groups, without including equivalent Azure CLI (cross-platform) examples or references. The 'Related Azure PowerShell cmdlets' section exclusively lists PowerShell commands, and there are no Linux- or Bash-oriented instructions or examples. This may disadvantage users on Linux or macOS, who are more likely to use Azure CLI or REST API directly.
Recommendations
- Add a section listing equivalent Azure CLI commands for creating, updating, and managing IP Groups (e.g., az network ip-group create, az network ip-group update, etc.).
- Provide example usage of the REST API for IP Group management, especially for automation scenarios.
- Ensure that references to management tools (Azure CLI, REST API, PowerShell) are presented together, or alternate the order so Windows tools are not always listed first.
- Include sample scripts or command snippets for both PowerShell and Bash (Azure CLI) to demonstrate parity.
- Review and update the documentation to clarify that all features are available via cross-platform tools, not just PowerShell.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/premium-deploy.md
...re-docs/blob/main//articles/firewall/premium-deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM), instructing users to open an 'administrator command prompt', and omitting any mention of Linux-based test VMs or examples. All test instructions and deployment steps assume a Windows environment, with no parallel guidance for Linux users. Additionally, certificate deployment is described only for Windows, and browser-based testing is implied to occur on Windows.
Recommendations
- Provide parallel instructions and examples for deploying and testing with a Linux-based WorkerVM, including Linux command-line equivalents.
- When referencing command prompts or shells, use neutral language (e.g., 'open a terminal window') and specify both Windows and Linux options.
- Include steps for deploying certificates on Linux test VMs, not just Windows.
- Demonstrate curl and browser-based testing from both Windows and Linux environments.
- Explicitly state that the test VM can be either Windows or Linux, and provide guidance for both.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/premium-migrate.md
...e-docs/blob/main//articles/firewall/premium-migrate.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong bias towards Windows and PowerShell. All command-line examples and automation scripts are provided exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. The instructions assume the use of PowerShell modules and Windows-centric scripting patterns, and there are no equivalent examples or guidance for Linux or cross-platform users. The only non-PowerShell automation mentioned is Terraform, but this is referenced as an external link and not integrated into the main migration workflow.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all migration steps, including policy transformation and firewall SKU upgrades.
- Include Bash shell script examples or guidance for Linux/macOS users.
- Mention cross-platform tools (such as Azure CLI and REST API) alongside PowerShell, and present them in parallel or before PowerShell examples.
- Clarify that PowerShell Core is cross-platform if PowerShell must be used, and provide installation instructions for Linux/macOS.
- Where automation scripts are provided, offer both PowerShell and Bash/CLI versions, or reference official cross-platform scripts.
- Explicitly state which steps are platform-agnostic (e.g., Azure Portal, Terraform) and which require Windows/PowerShell, to help users plan accordingly.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/premium-deploy-certificates-enterprise-ca.md
.../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All certificate management steps rely on Windows-specific tools (e.g., certtmpl.msc, Internet Explorer, Active Directory Certification Services), and there are no Linux or cross-platform alternatives provided. The instructions assume a Windows Server environment and do not mention how to perform equivalent tasks on Linux or with open-source tools. The workflow is tightly coupled to Windows administrative patterns and omits any mention of Linux-based PKI solutions or command-line alternatives.
Recommendations
- Provide equivalent Linux/OpenSSL-based instructions for generating and exporting CA certificates.
- Mention and, where possible, demonstrate how to use cross-platform tools (such as OpenSSL, certbot, or cfssl) for certificate creation and management.
- Include guidance for organizations using Linux-based PKI (e.g., Dogtag, EJBCA) or cloud-native CA services.
- Avoid assuming the use of Internet Explorer or Windows-specific certificate stores; offer browser-agnostic or CLI-based certificate export/import steps.
- Structure the documentation so that Windows and Linux approaches are presented in parallel, or at least mention Linux alternatives where Windows tools are referenced.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/management-nic.md
...re-docs/blob/main//articles/firewall/management-nic.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a significant Windows bias. All command-line examples use Azure PowerShell cmdlets, which are most commonly used on Windows and require PowerShell. There are no examples using Azure CLI (az), which is cross-platform and preferred by many Linux users. The documentation does not mention or provide guidance for Linux or bash users, and the only automation examples are in PowerShell. This may make it harder for Linux administrators to follow or automate these procedures.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell scripts, especially for stopping/starting the firewall and assigning public IP addresses.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to both tool documentations.
- Where possible, use neutral, cross-platform terminology and avoid assuming the user is on Windows.
- Include bash shell examples or note any differences in command usage for Linux/macOS environments.
- Consider adding a section or callout for Linux users, highlighting any platform-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/quick-create-ipgroup-template.md
...in//articles/firewall/quick-create-ipgroup-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell example (Remove-AzResourceGroup) for cleaning up resources, with no equivalent command or instructions for Linux users (such as Azure CLI or Bash). There is a reliance on Windows-centric tooling and no mention of Linux-native approaches, despite the template itself deploying a Linux jumpbox.
Recommendations
- Provide equivalent Azure CLI (az group delete) and/or Bash examples for deleting the resource group, alongside the PowerShell example.
- Explicitly mention that the deployment and management steps can be performed from any OS, not just Windows.
- Wherever PowerShell is used, offer parallel Linux-friendly commands or scripts.
- Add a note or section on how to perform post-deployment management (such as SSH access to the Linux jumpbox) from Linux/macOS environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/protect-azure-virtual-desktop.md
...in//articles/firewall/protect-azure-virtual-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows a Windows bias by focusing exclusively on Windows-based environments and tools. It references Windows-specific service tags (e.g., WindowsVirtualDesktop), provides proxy configuration examples only for Microsoft Edge (a Windows-centric browser), and omits any mention of Linux session hosts or cross-platform considerations. There are no Linux-specific instructions, examples, or references to Linux-compatible tools or browsers.
Recommendations
- Include explicit guidance for Linux-based session hosts, such as how to configure outbound access and firewall rules for Linux VMs in Azure Virtual Desktop.
- Provide proxy configuration examples for popular Linux browsers (e.g., Firefox, Chromium) and command-line tools.
- Mention that Azure Virtual Desktop supports both Windows and Linux session hosts, and clarify any differences in firewall or network configuration.
- Reference Linux-compatible tools and patterns where relevant, and avoid assuming all deployments are Windows-based.
- Add links to documentation or templates specifically for Linux session host scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/firewall-sftp.md
...ure-docs/blob/main//articles/firewall/firewall-sftp.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows by exclusively using Azure PowerShell for all deployment and configuration steps. There are no CLI (az), Bash, or Linux-native scripting examples. The only example for testing SFTP uses a generic 'command prompt' without clarifying cross-platform usage, and all setup instructions assume PowerShell, which is most commonly used on Windows.
Recommendations
- Provide equivalent examples using the Azure CLI (az) for all resource creation and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script snippets alongside PowerShell, especially for deployment and automation tasks.
- Clarify that the SFTP client example works on both Windows and Linux, and provide explicit Linux/Bash command-line examples (e.g., using the sftp command in a Linux terminal).
- Mention and link to installation instructions for Azure CLI and PowerShell Core on Linux/macOS, to support users on non-Windows platforms.
- Where possible, avoid language that assumes the user is on Windows (e.g., 'command prompt'), and instead use neutral terms like 'terminal' or 'shell'.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/snat-private-range.md
...ocs/blob/main//articles/firewall/snat-private-range.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed configuration steps and code samples for Azure PowerShell and Azure CLI, but the PowerShell examples are presented first and in greater depth. There are no explicit Linux shell or Bash examples, and the CLI examples do not clarify cross-platform usage or show Linux-specific command-line patterns. The documentation assumes familiarity with PowerShell, which is traditionally a Windows-centric tool, and does not address Linux users' needs or mention differences in experience between platforms.
Recommendations
- Present Azure CLI (which is cross-platform) examples before or alongside PowerShell examples to avoid implying a Windows-first workflow.
- Include explicit Bash/shell command examples where appropriate, especially for steps that might differ on Linux (e.g., environment variable syntax, file paths).
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary notes about platform-specific prerequisites or behaviors.
- Where PowerShell is used, mention that PowerShell Core is available cross-platform, or provide equivalent Bash commands if possible.
- Add a section or callout for Linux users, highlighting any differences or confirming parity in the experience.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/secured-hub-customer-public-ip.md
...n//articles/firewall/secured-hub-customer-public-ip.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration instructions only for the Azure portal and Azure PowerShell, with no mention of Azure CLI or Bash/Linux-based workflows. PowerShell is highlighted as the sole command-line example, and there are no Linux-native or cross-platform CLI instructions. This may disadvantage users on Linux or macOS systems who prefer or require Azure CLI over PowerShell.
Recommendations
- Add Azure CLI examples alongside PowerShell for all configuration steps.
- Explicitly mention that Azure CLI can be used for configuration, if supported.
- Ensure screenshots and instructions are platform-neutral or include notes for both Windows and Linux users.
- Consider including Bash script examples or references for Linux users.
- Review the documentation for any other Windows-specific terminology or tools and provide Linux equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/tutorial-hybrid-portal.md
...blob/main//articles/firewall/tutorial-hybrid-portal.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. All virtual machine creation steps use Windows Server images, and the only automation example for configuring IIS uses Azure PowerShell with Windows-specific commands. There are no examples or instructions for deploying or testing with Linux VMs, nor are there Bash/CLI or Linux-native automation alternatives. The documentation assumes the use of Windows tools and patterns throughout, with no parity for Linux users.
Recommendations
- Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu) in both the spoke and on-premises networks.
- Include examples for installing and configuring a web server (e.g., Apache or Nginx) on a Linux VM using Azure CLI and Bash scripts.
- Offer automation examples using Azure CLI (az commands) alongside or instead of PowerShell, especially for tasks like installing software or configuring VMs.
- When demonstrating remote access, mention SSH for Linux VMs in addition to RDP for Windows.
- Ensure that all steps referencing Windows-specific tools or features have Linux equivalents or alternatives.
- Rephrase sections that refer to Windows tools or patterns as the default, and present Linux options with equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/tutorial-firewall-dnat.md
...blob/main//articles/firewall/tutorial-firewall-dnat.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using a Windows Server virtual machine as the workload example and instructing users to test connectivity via Remote Desktop (RDP), which is a Windows-centric protocol. There are no examples or instructions for deploying a Linux VM or testing with Linux-native tools (e.g., SSH). The only OS-specific tool mentioned is Windows Server and RDP, with no mention of Linux alternatives.
Recommendations
- Provide parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) alongside the Windows Server example.
- Include steps for testing DNAT using SSH to a Linux VM, in addition to RDP for Windows.
- Mention and demonstrate the use of Linux-native tools (such as SSH clients) for connectivity testing.
- Where possible, use OS-neutral terminology or provide both Windows and Linux options in all relevant steps.
- Explicitly state that the procedure applies to both Windows and Linux workloads, and link to additional resources for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/tutorial-hybrid-portal-policy.md
...in//articles/firewall/tutorial-hybrid-portal-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server virtual machines for all examples, providing only PowerShell commands for VM configuration (IIS installation), and omitting any Linux-based VM or CLI (Bash/Azure CLI) examples. The workflow for deploying and configuring resources is tailored to Windows administrators, with no mention of Linux alternatives or parity in tooling.
Recommendations
- Provide parallel examples for deploying and configuring Linux-based virtual machines (e.g., Ubuntu) in both the spoke and on-premises roles.
- Include Azure CLI (Bash) commands alongside PowerShell for resource creation and configuration, especially for tasks like installing web servers (e.g., using apt and nginx or apache2).
- Demonstrate how to test connectivity using Linux tools (e.g., curl, ssh) in addition to Windows tools (RDP, browser).
- When referencing VM extensions or scripts, show both PowerShell and Bash/CLI equivalents for installing and configuring software.
- Explicitly mention that the tutorial is applicable to both Windows and Linux environments, and provide guidance for users who prefer or require Linux-based solutions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firmware-analysis/firmware-analysis-faq.md
...n//articles/firmware-analysis/firmware-analysis-faq.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prominently mentioning Azure PowerShell alongside Azure CLI in every instance, listing PowerShell before Python, and including custom metadata tags for Azure PowerShell. There is no mention of Linux-specific shells or tools, and the examples and quickstarts focus on Azure CLI (which is cross-platform but often associated with Windows) and PowerShell (which is historically Windows-centric), with Python as an afterthought. There are no explicit Linux shell (e.g., bash) examples or references.
Recommendations
- Include explicit bash or Linux shell examples alongside PowerShell and Azure CLI.
- When listing tools or quickstarts, alternate the order or mention Linux-native tools first in some cases.
- Add metadata tags for Linux or bash where appropriate, not just Azure CLI and PowerShell.
- Clarify that Azure CLI is cross-platform and provide Linux-specific usage notes if relevant.
- Consider adding a section or FAQ entry about using firmware analysis tools on Linux systems, including any Linux-specific considerations or best practices.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/service-tags.md
...zure-docs/blob/main//articles/firewall/service-tags.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 configuring Azure Firewall service tags. There are no equivalent examples for Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there references to Linux-native tools or shell commands. The configuration section leads with and exclusively uses PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown, ensuring Linux and macOS users have clear guidance.
- Explicitly mention that Azure CLI can be used from any platform, and provide bash/zsh-friendly command samples.
- Consider including a table or section that compares PowerShell and CLI usage for common tasks.
- Review and update the documentation to ensure that Linux and cross-platform users are not required to interpret or translate PowerShell scripts themselves.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firmware-analysis/quickstart-upload-firmware-using-azure-command-line-interface.md
...art-upload-firmware-using-azure-command-line-interface.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias in its command-line examples. All variable assignment and scripting examples use Windows batch syntax (set, for /f, %var%), with no equivalent Bash or Linux shell examples provided. This can confuse or exclude Linux/macOS users, despite the Azure CLI being cross-platform. There is also a tendency to present Windows-style commands first or exclusively, and the documentation does not mention or show Linux-native patterns for variable usage or scripting.
Recommendations
- Provide equivalent Bash/Linux shell examples for all scripting and variable assignment sections, using export, $(...), and $VAR syntax.
- Clearly indicate which code blocks are for Windows (cmd) and which are for Linux/macOS (bash), using tabs or callouts.
- In introductory sections, avoid language that suggests Windows as the default platform; mention Linux and macOS equally.
- Where possible, use cross-platform command examples, or explicitly show both Windows and Linux/macOS variants side by side.
- Link to Azure CLI documentation on using variables in both Bash and Windows shells.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firmware-analysis/release-notes.md
...blob/main//articles/firmware-analysis/release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. In the March 2024 update, automation is described with both Azure CLI and PowerShell commands, but PowerShell is mentioned explicitly and linked, while no explicit mention or link is provided for Linux-native shell or scripting environments. There are no Linux-specific examples, tools, or workflows discussed, and the documentation does not clarify cross-platform parity for command-line automation. The overall focus is on Azure Portal and Microsoft tooling, with no reference to Linux-specific user experiences or tools.
Recommendations
- Provide explicit Linux/bash/zsh command-line examples alongside PowerShell, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Include links to Azure CLI documentation for Linux and macOS users, not just PowerShell.
- Add a section or note about cross-platform support, including any differences or requirements for Linux users.
- Where PowerShell is mentioned, also mention bash or other common Linux shells to ensure parity.
- Consider including screenshots or walkthroughs from a Linux environment to demonstrate inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/create-front-door-bicep.md
...ob/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 all deployment and validation steps, but PowerShell is consistently presented as an equal alternative to CLI, and the output screenshots are exclusively from PowerShell. There is no mention of Linux-specific shells or tools, and PowerShell (a Windows-centric tool, though now cross-platform) is highlighted, including in output imagery. The documentation does not reference Linux or bash explicitly, nor does it provide any Linux-specific guidance or troubleshooting.
Recommendations
- Include explicit references to Linux environments and shells (e.g., bash, zsh) in the prerequisites or deployment steps.
- Provide example screenshots of CLI output from a Linux terminal, not just PowerShell.
- Clarify that Azure CLI commands work cross-platform and can be run in bash or other Linux shells.
- Mention that PowerShell Core is available on Linux, if PowerShell examples are retained.
- Consider adding a 'Linux' or 'Bash' tab alongside CLI and PowerShell, or clarify that the CLI examples are suitable for Linux users.
- Balance the imagery and examples so that Linux users feel equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firmware-analysis/automate-firmware-analysis-service-principals.md
...lysis/automate-firmware-analysis-service-principals.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page primarily provides Azure CLI and PowerShell examples, with explicit mention of Azure PowerShell before Python. There are no Linux- or bash-specific examples, nor are there references to Linux-native tools or shell environments. The structure and language implicitly prioritize Windows workflows, with PowerShell highlighted as a main scripting option and no mention of bash, zsh, or Linux-specific considerations.
Recommendations
- Add explicit bash/zsh/Linux shell examples alongside Azure CLI and PowerShell, especially for authentication and scripting.
- Mention that Azure CLI works cross-platform and provide guidance for both Windows (PowerShell, CMD) and Linux/macOS (bash, zsh) environments.
- Reorder scripting examples to avoid always listing PowerShell before Linux/Python, or alternate their order.
- Include notes or links for Linux users regarding environment setup, such as installing Azure CLI on Linux, and any differences in command usage.
- Where possible, provide sample scripts in bash for common automation tasks, not just PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/create-front-door-template.md
...main//articles/frontdoor/create-front-door-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots focus exclusively on PowerShell commands and output, and the workflow assumes use of the Azure Cloud Shell in PowerShell mode. Although it briefly mentions that other deployment methods exist, it does not provide concrete examples or guidance for Linux or macOS users.
Recommendations
- Add Azure CLI (az) command examples for all deployment and cleanup steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell script examples alongside PowerShell, especially for steps involving variable assignment and resource group management.
- Reorder or present PowerShell and CLI/Bash examples in parallel, or default to CLI/Bash first to improve parity.
- Provide screenshots or output examples from both PowerShell and CLI/Bash where relevant.
- Explicitly mention that the Azure Cloud Shell supports both Bash and PowerShell, and show how to select the preferred shell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/endpoint.md
...s/azure-docs/blob/main//articles/frontdoor/endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring endpoint domain reuse, but it does not include explicit Linux shell (bash) examples or mention Linux-specific tooling. Azure PowerShell is Windows-centric, and its example is given equal prominence to the CLI, which may not be as familiar or available to Linux users. There is also no explicit mention of running the Azure CLI example in a Linux shell, nor are there bash script examples.
Recommendations
- Add explicit bash (Linux shell) examples for Azure CLI commands, showing usage in a Linux terminal.
- Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider de-emphasizing Azure PowerShell unless there is a specific need, or move it after CLI and Bicep examples.
- Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
- If relevant, mention how to install and use Azure CLI and Bicep on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/migrate-cdn-to-front-door.md
.../main//articles/frontdoor/migrate-cdn-to-front-door.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows tools and patterns are mentioned first or exclusively in several places: PowerShell's Invoke-WebRequest is listed alongside wget, but Windows is named first; the Windows hosts file path is listed before Linux; and PowerShell is the only scripting environment mentioned for Windows. There are no Linux-specific command-line examples, and the documentation assumes familiarity with Windows tools and conventions.
Recommendations
- When listing tools or commands, alternate the order (e.g., mention wget and curl before Invoke-WebRequest, or list Linux and Windows paths together or in alternating order).
- Provide equivalent Linux command-line examples (e.g., show both wget/curl and Invoke-WebRequest commands for header inspection).
- Mention cross-platform alternatives where possible (e.g., curl, which is available on both Windows and Linux).
- When referencing file paths (such as the hosts file), present both Linux and Windows locations together, or in a neutral order.
- If scripting is required, provide both Bash and PowerShell script snippets.
- Explicitly state that the steps are applicable to both Linux and Windows, and clarify any OS-specific differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/origin-security.md
...-docs/blob/main//articles/frontdoor/origin-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides configuration examples for several origin types, including App Service, Application Gateway, Application Gateway for Containers, IIS, and AKS NGINX controller. However, the IIS example is Windows-specific and includes a detailed IIS configuration file, while there is no equivalent example for common Linux web servers such as Apache or NGINX (outside of AKS). The ordering of examples places IIS before AKS NGINX, and there are no PowerShell or CLI command examples, but the presence of a Windows-only example and lack of parity for standalone Linux web servers indicates a Windows bias.
Recommendations
- Add configuration examples for popular Linux web servers such as Apache (httpd) and standalone NGINX (outside of AKS), showing how to filter requests based on the X-Azure-FDID header.
- Ensure that Linux-based examples are presented alongside or before Windows/IIS examples to avoid the perception of Windows-first bias.
- Where possible, provide cross-platform configuration snippets or scripts (e.g., for both Windows and Linux environments).
- Include guidance for configuring header-based filtering in common Linux distributions, not just within Kubernetes or managed Azure services.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/standard-premium/tls-policy.md
...ain//articles/frontdoor/standard-premium/tls-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically referencing Windows operating systems and their compatibility with cipher suites, while omitting any mention of Linux or other non-Windows platforms. There are no examples or compatibility notes for Linux clients or tools, and the only OS-specific guidance is for Windows versions. No Linux command-line tools (such as OpenSSL or curl) are referenced, despite the context of TLS and cipher suites where such tools are commonly used.
Recommendations
- Add compatibility notes for popular Linux distributions and browsers regarding supported cipher suites and TLS versions.
- Include examples or references for testing TLS connections and cipher suite support using Linux tools such as OpenSSL or curl.
- When providing OS-specific recommendations (such as for Windows 10 and earlier), also provide equivalent information for Linux and macOS clients.
- Avoid mentioning Windows exclusively in notes about compatibility; instead, provide a balanced view that covers all major platforms.
- Consider adding a section or table that summarizes cipher suite and TLS version support across Windows, Linux, and macOS clients.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/tier-migration.md
...e-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 prioritizing Azure PowerShell and CLI tools, mentioning PowerShell before CLI, and providing a 'Next steps' link specifically for PowerShell migration without equivalent Linux/bash or cross-platform examples. There are no explicit Linux or bash shell examples, and the documentation does not reference Linux-specific tools or workflows.
Recommendations
- Provide migration instructions and examples using Azure CLI (az), which is cross-platform, alongside or before PowerShell examples.
- Include bash shell script examples for common migration tasks to ensure Linux users are supported.
- In the 'Next steps' section, add a link to a migration guide using Azure CLI or bash, not just PowerShell.
- When referencing scripting or automation, use neutral language (e.g., 'Azure CLI or PowerShell') and avoid listing Windows tools first unless there is a technical reason.
- Explicitly state that all instructions are applicable on both Windows and Linux, or note any platform-specific differences.