Application Gateway
372
Total Pages
310
Linux-Friendly Pages
62
Pages with Bias
16.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
172 issues found
Showing 26-50 of 172 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md
...rticles/application-gateway/configuration-listeners.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support, with no equivalent example for Linux users (e.g., Azure CLI, Bash, or ARM templates). The only code snippet uses Azure PowerShell, which is primarily a Windows tool, and there are no references to cross-platform alternatives. This may hinder Linux or macOS users who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI examples for all configuration steps currently shown only with PowerShell.
- Explicitly mention that Azure CLI and ARM templates can be used for listener configuration, and provide links or examples.
- Ensure that code snippets are provided for both PowerShell and CLI (Bash) where applicable.
- Review the documentation for other areas where only Windows-centric tools or workflows are described, and add Linux/macOS-friendly alternatives.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md
...gateway/application-gateway-key-vault-common-errors.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for certificate management and update operations, with no equivalent Azure CLI or Linux shell commands. The troubleshooting steps and guidance are oriented around the Azure portal and PowerShell, which are more commonly used on Windows platforms. There is no mention of Linux tools or cross-platform alternatives, and PowerShell is presented as the default method for scripting tasks.
Recommendations
- Add Azure CLI examples alongside PowerShell for all certificate management and troubleshooting steps, ensuring parity for Linux and macOS users.
- Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and link to cross-platform installation guides.
- Include screenshots or instructions for Azure CLI usage in addition to Azure portal steps.
- Review all scripting and automation guidance to ensure both Windows and Linux users are supported equally.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its 'Next steps' section, which links only to a PowerShell-based tutorial for creating an autoscaling, zone-redundant Application Gateway. There are no equivalent examples or references for Linux users (e.g., Azure CLI or ARM templates), and PowerShell—a Windows-centric tool—is presented as the default or sole method for deployment tasks.
Recommendations
- Add equivalent tutorials and examples using Azure CLI, which is cross-platform and widely used on Linux.
- Include ARM/Bicep template deployment instructions for infrastructure-as-code parity.
- Explicitly mention that PowerShell is just one of several supported tools, and provide links to Linux-friendly alternatives.
- Review all code samples and ensure that both Windows and Linux usage scenarios are covered equally.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md
...les/application-gateway/application-gateway-ilb-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Windows PowerShell and Azure PowerShell cmdlets for all steps, with no mention of Linux, Bash, Azure CLI, or cross-platform alternatives. Windows-centric tools and patterns are referenced throughout, and there are no examples or instructions for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Add a section or callouts for Linux/macOS users, including prerequisites and installation instructions for Azure CLI.
- Reference Bash scripting and show how to perform the same operations using shell scripts.
- Avoid language such as 'switch PowerShell mode' or 'Using Windows PowerShell' without mentioning alternatives.
- Ensure that links to further documentation include both PowerShell and CLI/Bash options.
- Consider adding a table comparing PowerShell and CLI commands for each major step.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md
...application-gateway/application-gateway-diagnostics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux or cross-platform CLI instructions (such as Azure CLI or Bash). The guidance for log conversion and analysis also centers on Windows developer tools, with no mention of Linux-friendly alternatives. Windows/PowerShell methods are presented first and exclusively in the automation section.
Recommendations
- Add equivalent Azure CLI (az) examples for enabling diagnostic logging, suitable for Linux/macOS users.
- Include instructions or scripts using Bash or other cross-platform shells for log retrieval and processing.
- Mention and provide examples for viewing and analyzing logs with Linux-native tools (e.g., jq, awk, grep, pandas in Python).
- Reference cross-platform data visualization tools (e.g., Grafana, Kibana) alongside Power BI and Excel.
- Provide log conversion examples using open-source or platform-neutral tools (e.g., Python scripts) rather than Visual Studio/C#.
- Ensure that automation and scripting sections present both Windows and Linux approaches, or use platform-neutral methods where possible.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the primary method for viewing cipher suite ordering and configuring TLS policies. There is no mention of Linux-specific tools or command-line examples (such as Bash, OpenSSL, or Linux Azure CLI usage). The 'Next steps' section links only to a PowerShell-based configuration guide, and instructions for setting policies mention PowerShell before CLI, with no Linux shell or cross-platform parity. This may hinder Linux administrators or those using non-Windows environments.
Recommendations
- Add Linux-specific examples for configuring TLS policies, such as using Azure CLI in Bash or shell scripts.
- Include references to Linux tools (e.g., OpenSSL, curl) for verifying TLS versions and cipher suites.
- Ensure that CLI instructions are presented alongside or before PowerShell examples to promote cross-platform parity.
- Provide links to documentation for configuring TLS policies from Linux/macOS environments.
- Clarify that Azure CLI is cross-platform and provide explicit instructions for its use on Linux.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell examples before Azure CLI, referencing PowerShell-specific cmdlets, and using terminology and screenshots that align with Windows-centric workflows (e.g., Azure portal navigation, PowerShell commands). There is no explicit mention of Linux shell scripting or alternative Linux-native tools, and the CLI examples are less detailed than their PowerShell counterparts. The documentation does not provide parity for Linux users in terms of command-line examples, troubleshooting, or tool recommendations.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
- Include Bash shell scripting examples for common tasks, especially for feature registration and NSG/route table configuration.
- Add explicit references to Linux environments, such as using Azure CLI on Linux/macOS, and clarify that CLI commands work cross-platform.
- Provide troubleshooting steps and screenshots for Linux users (e.g., Azure CLI in Bash, terminal output).
- Mention and link to Linux-native automation tools (e.g., Ansible, shell scripts) where appropriate.
- Ensure that all instructions and examples are validated on both Windows and Linux platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/certificates-for-backend-authentication.md
...ion-gateway/certificates-for-backend-authentication.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Windows Certificate Manager and PowerShell for certificate export instructions. All screenshots and step-by-step guidance are based on Windows GUI tools, with no mention of Linux or cross-platform alternatives. There are no CLI or OpenSSL examples, and the only reference to further configuration is via PowerShell, further reinforcing the Windows-centric approach.
Recommendations
- Add equivalent instructions for exporting certificates using OpenSSL or other common Linux tools.
- Include CLI-based examples for both Windows and Linux to ensure parity and accessibility for users on non-Windows platforms.
- Mention and demonstrate how to perform these tasks on macOS, if relevant.
- Provide links or references to cross-platform certificate management documentation.
- Avoid implying that Windows tools are the default or only option; present alternatives side-by-side.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-ssl-portal.md
...main/articles/application-gateway/create-ssl-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows, with all certificate creation and VM setup examples using Windows PowerShell and Windows Server. There are no Linux equivalents or alternative instructions for creating self-signed certificates or deploying backend servers with Linux. Windows tools and patterns (e.g., New-SelfSignedCertificate, Export-PfxCertificate, Add-WindowsFeature) are used exclusively, and Windows is presented as the default/first option throughout.
Recommendations
- Add equivalent Linux instructions for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
- Provide examples for deploying Linux VMs as backend servers, including installation of a web server (e.g., Apache or Nginx) for testing.
- Include Bash/Azure CLI commands alongside PowerShell for resource management and VM extension installation.
- Clearly state that both Windows and Linux are supported as backend targets, and provide parity in step-by-step guidance.
- Mention cross-platform certificate management tools and reference relevant documentation for Linux users.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-multiple-sites-portal.md
...es/application-gateway/create-multiple-sites-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a clear Windows bias: virtual machine creation is demonstrated exclusively with Windows Server, IIS installation is shown only via PowerShell, and host file editing and DNS commands use Windows-specific paths and tools. There are no Linux VM examples, nor instructions for Apache/Nginx setup, nor Linux shell commands for host file editing or DNS cache management.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend server.
- Provide Linux-based web server setup steps (e.g., install Apache or Nginx) using Bash or Azure CLI.
- Include host file editing instructions for Linux/macOS (e.g., /etc/hosts) and relevant commands for DNS cache flushing (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service network-manager restart').
- Show Azure CLI examples alongside PowerShell for VM extension installation and other automation tasks.
- Clarify that Application Gateway supports both Windows and Linux backend servers, and provide links to relevant Linux documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/deploy-basic-portal.md
...in/articles/application-gateway/deploy-basic-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 command-line examples for preview registration and IIS installation use Azure PowerShell, with no mention of Bash, CLI, or Linux alternatives. The VM creation walkthrough exclusively uses Windows Server 2019, and IIS (a Windows-only web server) is used for backend testing, with no Linux VM or Apache/Nginx examples. The documentation does not provide parity for Linux users, omitting instructions for deploying Linux VMs or using Linux-native tools.
Recommendations
- Provide Azure CLI (bash) examples alongside PowerShell for preview registration and unregistration.
- Include instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Offer guidance for installing and testing with Apache or Nginx on Linux VMs, in addition to IIS on Windows.
- Mention Linux as a supported backend OS in the VM creation section.
- Ensure screenshots and walkthroughs are not exclusively tied to Windows Server, and clarify that backend pools can use both Windows and Linux VMs.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/diagnostics.md
...cles/application-gateway/for-containers/diagnostics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides a detailed PowerShell example for enabling diagnostic logs, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only automation example is Windows-centric, and Windows tools (PowerShell, Excel) are mentioned before or instead of cross-platform or Linux-native alternatives. This creates a bias toward Windows users and may hinder Linux users from easily following the instructions.
Recommendations
- Add Azure CLI and Bash examples for enabling diagnostic logs, alongside the PowerShell example.
- Mention cross-platform tools (such as jq, grep, or Linux text editors) for viewing and analyzing logs, in addition to Excel and Power BI.
- Ensure that instructions and screenshots are not Windows-specific, or provide parity for Linux/macOS environments.
- Present examples for both Windows and Linux environments side-by-side, or in tabs, to improve accessibility for all users.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-tcp-tls-proxy.md
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the SQL backend example and referencing SQL Server Management Studio (a Windows-only tool) for client connectivity. There are no instructions or examples for deploying SQL Server on Linux, nor for connecting from Linux clients or using cross-platform tools. Windows options are mentioned first and exclusively throughout the guide.
Recommendations
- Provide parallel instructions for deploying SQL Server on Linux (e.g., Ubuntu) using supported images.
- Include examples for connecting to SQL Server from Linux clients, such as using sqlcmd, Azure Data Studio, or other cross-platform tools.
- Mention both Windows and Linux options when describing SQL Server license selection and deployment.
- Add screenshots or CLI commands relevant to Linux environments.
- Clarify that Application Gateway TCP/TLS proxy works with both Windows and Linux backends.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation displays mild Windows bias in the Helm installation section, where Windows installation instructions (including use of Windows Package Manager 'winget' and PowerShell syntax) are presented before Linux instructions. The use of 'winget' is a Windows-specific tool, and the PowerShell example is given explicitly. Most other commands are cross-platform (Azure CLI, Helm, kubectl, bash), and Linux instructions are present, but Windows is prioritized in ordering and tooling.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or in the same order, or default to Linux first as it is more common for Kubernetes workloads.
- Provide explicit Bash examples for all commands where PowerShell is shown, especially for Azure CLI and Helm usage.
- Mention Linux package managers (apt, yum, dnf, snap) for Helm installation alongside 'winget' for Windows.
- Clarify that Azure CLI and Helm commands are cross-platform and can be run in Bash, PowerShell, or Azure Cloud Shell.
- Avoid presenting Windows-specific tools (like 'winget') before Linux equivalents; give equal prominence to both.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/troubleshooting-guide.md
...cation-gateway/for-containers/troubleshooting-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is given after the Linux example (using grep), which is a positive sign for parity. However, the Windows example uses the generic 'cli' tag rather than 'powershell', and there are no PowerShell-specific examples or Windows-only tools referenced. The rest of the documentation is platform-neutral, focusing on kubectl and helm commands, which are cross-platform. There is no evidence of missing Linux examples, but the Windows example could be improved by specifying PowerShell usage if relevant.
Recommendations
- Ensure that both Linux and Windows examples are provided wherever OS-specific commands are needed.
- Clarify whether the Windows example is intended for Command Prompt or PowerShell, and provide PowerShell syntax if different.
- Consider using tabs or callouts to make OS-specific instructions more visually distinct and easy to follow.
- Review future updates to ensure Linux and Windows parity in troubleshooting steps, especially for log filtering and file redirection.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/http-response-codes.md
...in/articles/application-gateway/http-response-codes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing NTLM authentication (a Windows-specific protocol) and linking to Microsoft Windows documentation. In the 504 Gateway time-out section, IIS (a Windows web server) is mentioned and described first, with configuration details and links, while Nginx (a common Linux web server) is mentioned second with less detail. There are no Linux-specific troubleshooting examples or parity in tool coverage, and no PowerShell or CLI examples are present, but the overall pattern prioritizes Windows technologies and documentation.
Recommendations
- Provide equivalent Linux examples and troubleshooting steps, such as Apache or Nginx configuration details for time-out settings, with links to official documentation.
- When discussing authentication issues, mention Linux-compatible authentication mechanisms (e.g., Kerberos, OAuth) and provide troubleshooting steps for those.
- Ensure that references to backend server configuration (IIS, Nginx) are presented in parallel, with equal detail and prominence.
- Include examples or links for both Windows and Linux environments when discussing backend pool health, diagnostics, or probe configuration.
- Avoid referencing Windows-specific protocols (like NTLM) without mentioning alternatives or implications for Linux-based backends.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-arm-template.md
...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively using IIS (a Windows web server) for backend validation, referencing only PowerShell (Remove-AzResourceGroup) for resource cleanup, and omitting Linux-based alternatives or examples (such as using Nginx/Apache or Azure CLI/Bash commands). No Linux VM configuration or validation steps are provided.
Recommendations
- Include examples of deploying Linux-based VMs (e.g., Ubuntu with Nginx or Apache) in the backend pool.
- Provide validation steps using Linux tools (e.g., curl, wget) to test the application gateway.
- Offer resource cleanup instructions using Azure CLI (az group delete) and Bash commands alongside PowerShell.
- Clarify that IIS is optional and suggest Linux alternatives for users preferring open-source stacks.
- Ensure screenshots and walkthroughs are platform-neutral or show both Windows and Linux scenarios.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-install-existing.md
...ication-gateway/ingress-controller-install-existing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Several command examples use PowerShell syntax and variables, especially in identity and role assignment steps, rather than pure Bash or cross-platform shell. The backup instructions reference the Azure portal's export, which includes PowerShell scripts, and Windows-centric tools are mentioned. PowerShell examples are given before or instead of equivalent Bash commands in some cases. While Cloud Shell is recommended (which is cross-platform), the documentation assumes familiarity with PowerShell scripting and does not always provide Linux/Bash alternatives for all steps.
Recommendations
- Provide Bash equivalents for all PowerShell command examples, especially for identity and role assignment steps.
- Clarify that PowerShell examples are for Windows users and add explicit Bash alternatives for Linux/macOS users.
- When referencing exported scripts (e.g., from Azure portal), note which are for Windows (PowerShell) and which are for Linux (Bash), and provide guidance for both.
- Avoid using PowerShell variable syntax ($variable) in command examples unless specifically targeting Windows; use Bash syntax where appropriate.
- Ensure that all instructions and examples are platform-neutral or include both Windows and Linux/macOS variants.
- Review the order of examples to avoid presenting Windows/PowerShell commands before Linux/Bash equivalents unless justified.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-overview.md
.../application-gateway/mutual-authentication-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing detailed PowerShell examples and references before Azure CLI equivalents, and by linking to a PowerShell-specific configuration guide as the primary next step. There are no Linux-specific examples or mentions of Linux tools for certificate management or configuration, and the CLI example is minimal compared to the PowerShell section. The documentation does not mention or demonstrate Linux-native workflows, such as using OpenSSL or Bash scripting, for certificate extraction or management.
Recommendations
- Provide Linux-specific examples for certificate extraction and management, such as using OpenSSL commands.
- Expand Azure CLI examples to match the detail and coverage of PowerShell examples.
- Include Bash or shell script snippets for common tasks, such as uploading certificates or verifying OCSP status.
- Link to both PowerShell and CLI configuration guides in the 'Next steps' section, and consider adding a Linux-focused guide.
- Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux administrators throughout the documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/multiple-site-overview.md
...articles/application-gateway/multiple-site-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by consistently mentioning Azure PowerShell before Azure CLI in instructions and examples, and by providing explicit PowerShell parameter details (e.g., '-HostNames') prior to CLI equivalents. The references to Azure PowerShell and CLI are presented as separate, but PowerShell is often listed first, and the step-by-step guides link to PowerShell before CLI. There is also a focus on Windows-centric tooling (PowerShell), with no mention of Linux-specific shell usage or examples, nor any explicit parity checks for Linux environments.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI references, or present CLI examples first to balance platform representation.
- Provide explicit bash or Linux shell examples where relevant, especially for Azure CLI usage.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, while PowerShell is primarily Windows-centric (though now available cross-platform).
- Include notes or links for Linux users regarding installation and usage of Azure CLI and PowerShell on Linux.
- Ensure that all example commands are shown in both PowerShell and bash/CLI syntax, and avoid assuming the reader is using Windows tools.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-certificate-management.md
...ateway/mutual-authentication-certificate-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively describing certificate export procedures using Windows GUI tools (Certificate Manager, Certificate Export Wizard) and referencing PowerShell for certificate management. There are no Linux-specific instructions or examples for exporting certificates, and the Linux command is only mentioned for concatenating files, not for the main certificate export workflow. Windows tools and screenshots dominate the guide, with Linux alternatives missing or relegated to a secondary role.
Recommendations
- Add step-by-step instructions for exporting certificates using Linux command-line tools such as openssl.
- Include Linux-specific screenshots or terminal output examples for certificate export and inspection.
- Present Linux and Windows procedures in parallel, or clearly separate them, to ensure parity and clarity for users of both platforms.
- Reference Linux certificate stores and management tools (e.g., certtool, openssl, keytool) where appropriate.
- Avoid assuming the use of Windows GUI tools; provide CLI alternatives for cross-platform accessibility.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is given a dedicated section with detailed step-by-step instructions and full command examples before the Azure CLI section. The PowerShell section is more verbose and references Windows-specific cmdlets, while the CLI section is somewhat shorter and less explanatory. There are no Linux shell or scripting examples (e.g., Bash), and no mention of Linux-specific tools or considerations. The ordering and depth of PowerShell coverage suggest a 'Windows-first' approach.
Recommendations
- Add Bash shell examples for key steps, especially for subnet and endpoint configuration, to improve Linux parity.
- Ensure CLI instructions are as detailed and explanatory as PowerShell instructions, including troubleshooting and verification steps.
- Explicitly mention cross-platform compatibility for Azure CLI and clarify that PowerShell Core can be used on Linux/macOS.
- Consider reordering sections so that CLI and Bash examples appear before or alongside PowerShell, rather than after.
- Add notes or links for Linux users regarding installation and usage of Azure CLI and PowerShell Core on non-Windows platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-http-to-https-portal.md
...s/application-gateway/redirect-http-to-https-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 command-line examples use PowerShell, including certificate creation and IIS installation. The virtual machine scale set is configured with Windows Server 2016 by default, and instructions for backend web server setup exclusively use IIS and Windows-centric tooling. There are no examples or guidance for Linux-based VMSS, certificate creation on Linux, or using Linux web servers such as Apache or Nginx.
Recommendations
- Provide equivalent Linux examples for certificate creation (e.g., using OpenSSL) and exporting PFX files.
- Include instructions for creating a VMSS with a Linux OS image (such as Ubuntu or CentOS) and installing a Linux web server (Apache, Nginx) in the backend pool.
- Offer Bash/Azure CLI alternatives to PowerShell commands throughout the tutorial.
- Clarify that both Windows and Linux are supported and link to relevant Linux-focused documentation.
- Add screenshots and walkthroughs for Linux-based backend configuration and testing.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates Windows bias by referencing configuration via the Azure portal and linking to a PowerShell-based tutorial for next steps, without mentioning or providing equivalent Linux-oriented instructions (such as Azure CLI or Bash). There are no examples or references to Linux tools or workflows, and the only actionable configuration guidance is Windows-centric.
Recommendations
- Include equivalent instructions and examples using Azure CLI and Bash for Linux users.
- Provide links to tutorials or documentation for configuring Application Gateway redirection via Linux-friendly tools.
- Ensure that next steps and code samples are presented for both Windows (PowerShell) and Linux (CLI/Bash) environments.
- Explicitly mention cross-platform options in the overview and configuration sections.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/proxy-buffers.md
...lob/main/articles/application-gateway/proxy-buffers.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides configuration examples using Azure CLI, PowerShell, and ARM templates. PowerShell is given a dedicated section with detailed examples for both creating and updating Application Gateways, while no equivalent Linux shell or Bash examples are provided. The PowerShell method is presented before the ARM template method, and PowerShell is a Windows-centric tool. There is also a reference to the Azure SDK for .NET, another Windows-preferred technology, without mention of cross-platform SDKs. No explicit Linux/Bash or cross-platform scripting alternatives are shown.
Recommendations
- Add Bash shell examples for configuring buffer settings using Azure CLI to demonstrate parity for Linux users.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide explicit Bash syntax where relevant.
- Include examples using cross-platform SDKs (e.g., Python, Java) in addition to .NET.
- Reorder example sections so that cross-platform methods (Azure CLI, ARM templates) are presented before Windows-specific tools like PowerShell.
- Explicitly mention that PowerShell Core is available on Linux, if relevant, or provide guidance for Linux users on using PowerShell Core.