Application Gateway
188
Total Pages
113
Linux-Friendly Pages
75
Pages with Bias
39.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
981 issues found
Showing 401-425 of 981 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.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 command-line operations, referencing PowerShell before (or instead of) Azure CLI or other cross-platform tools, and omitting Linux/Unix-specific instructions or examples. The use of PowerShell commands and terminology assumes a Windows environment, and there are no equivalent CLI/bash examples or guidance for Linux users.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Where PowerShell is referenced, explicitly mention that the steps can be performed on any OS with PowerShell Core, or provide equivalent bash/CLI scripts.
- Add Linux-specific notes or screenshots where portal navigation or file formats may differ.
- Ensure that all ARM template and scripting examples are presented in a platform-neutral way, or provide both Windows (PowerShell) and Linux (CLI/bash) variants.
- Update the 'Next steps' section to include links to CLI-based guides, not just PowerShell.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS equivalents. The tutorial assumes a Windows environment (e.g., file paths like c:\appgwcert.pfx), and does not provide alternative instructions for Linux or cross-platform users.
Recommendations
- Provide equivalent Azure CLI (az) commands for each step, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include instructions for generating self-signed certificates using OpenSSL, which is available on all platforms, not just New-SelfSignedCertificate (Windows-only).
- Use platform-agnostic file paths or note differences (e.g., c:\appgwcert.pfx vs. ~/appgwcert.pfx).
- Explicitly mention that the tutorial can be followed on Linux/macOS and provide any required adjustments.
- Add a section or callouts for Linux/macOS users, including how to install and use Azure PowerShell or Azure CLI on those platforms.
- Consider providing a toggle or tabs for PowerShell and Azure CLI/Bash examples throughout the tutorial.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking settings, exclusively referencing Fiddler (a Windows-centric tool) for network debugging, and using Windows-specific instructions such as 'Run as administrator.' There are no Linux or cross-platform alternatives or examples provided for these key troubleshooting steps.
Recommendations
- Provide Azure CLI and/or Azure Cloud Shell examples alongside or instead of PowerShell for checking Application Gateway settings, as these are cross-platform.
- Include examples of using Linux-compatible network debugging tools such as tcpdump, Wireshark, or mitmproxy for capturing and analyzing HTTP/HTTPS traffic.
- When referencing tools like Fiddler, mention cross-platform alternatives and provide installation and usage instructions for Linux and macOS.
- Avoid instructions that are specific to Windows (e.g., 'right click and run as administrator') or provide equivalent steps for Linux/macOS environments.
- Ensure screenshots and walkthroughs are not exclusively from Windows environments; include or link to examples from other platforms where possible.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.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 PowerShell-based examples for configuring Azure Application Gateway with Key Vault certificates. There are no equivalent Azure CLI (cross-platform) or Bash/Linux examples, and PowerShell is referenced as the primary automation tool. The guidance and code snippets assume a Windows-centric workflow, with no mention of Linux shell environments or tooling. Additionally, the 'Next steps' section links only to a PowerShell-based guide.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell code snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Where automation steps are described, provide both PowerShell and Bash/Azure CLI workflows.
- In sections referencing PowerShell, mention Azure CLI as an alternative and provide links to relevant CLI documentation.
- Ensure that all portal-based instructions clarify that they are OS-agnostic, and avoid implying that PowerShell is the only automation option.
- Update the 'Next steps' section to include links to Azure CLI and ARM/Bicep template guides, not just PowerShell.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-overview.md
...blob/main/articles/application-gateway/ssl-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as the PFXImportCertStore function), providing configuration guidance and next steps primarily via PowerShell, and omitting Linux or cross-platform CLI examples. There is no mention of Linux tools or workflows for certificate management or Application Gateway configuration, and the only automation examples referenced are Windows-centric.
Recommendations
- Provide equivalent Azure CLI and/or Azure Cloud Shell examples for configuring Application Gateway and end-to-end TLS, alongside or before PowerShell instructions.
- Reference cross-platform certificate management tools (such as OpenSSL) for preparing certificates, including how to generate and convert certificates to PFX format on Linux/macOS.
- Link to documentation or guides for Linux users on how to manage certificates and interact with Azure Application Gateway.
- Avoid referencing Windows APIs (such as PFXImportCertStore) as the primary or only source for supported algorithms; instead, summarize requirements in a platform-neutral way or provide equivalent Linux references.
- Ensure that troubleshooting and next steps sections include both Windows and Linux workflows, or explicitly state that the instructions are cross-platform where applicable.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS equivalents. The instructions assume a Windows environment (e.g., file paths like c:\appgwcert.pfx), and there are no alternative steps or code samples for Linux users.
Recommendations
- Provide parallel examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
- Include instructions for creating self-signed certificates using OpenSSL, which is standard on Linux/macOS, alongside the PowerShell method.
- Use platform-neutral file paths (e.g., ~/appgwcert.pfx or ./appgwcert.pfx) or clarify the differences for Windows and Linux/macOS.
- Explicitly state that the tutorial can be followed from Linux/macOS and provide any necessary prerequisites or differences.
- Add a section or callouts for Linux/macOS users, highlighting any steps that differ or require alternative tools.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md
...es/application-gateway/configuration-infrastructure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, primarily through the exclusive use of PowerShell cmdlets for operational instructions (such as restarting the Application Gateway), and by referencing Azure PowerShell before Azure CLI when discussing how to change the subnet of an existing Application Gateway. There are no Linux shell or Azure CLI command examples provided, and no mention of Linux-specific tools or workflows, which may disadvantage users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all operational tasks, such as stopping and starting the Application Gateway.
- When referencing tools for management (e.g., 'use Azure PowerShell or the Azure CLI'), list Azure CLI first or equally, and provide direct links to both sets of documentation.
- Include example commands or scripts for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) environments to ensure platform parity.
- Where possible, avoid assuming the use of PowerShell as the default, and clarify that all operations can be performed from any supported OS using the Azure CLI.
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
Missing Linux Example
Windows First
Summary
The documentation exclusively provides step-by-step instructions and screenshots for exporting certificates using Windows Certificate Manager, a Windows-only tool. There are no examples or guidance for performing equivalent tasks on Linux or macOS. The only command-line reference is to PowerShell/certmgr, and the 'Next steps' section links to a PowerShell-specific guide. Linux tools and workflows are not mentioned or demonstrated.
Recommendations
- Add parallel instructions for exporting certificates using common Linux tools such as openssl, including command-line examples for exporting public keys and root certificates in Base-64 encoded X.509 (.CER) format.
- Include screenshots or terminal output from Linux environments to illustrate the process.
- Mention Linux and macOS as supported platforms explicitly, and provide guidance for users on those systems.
- Balance references to Windows tools by listing Linux and cross-platform alternatives (e.g., openssl, certutil).
- Update the 'Next steps' section to include links to Linux and cross-platform guides, not just PowerShell.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell command examples for certificate management, omitting equivalent Azure CLI (cross-platform) or Bash examples. The troubleshooting steps and automation guidance focus on PowerShell, which is traditionally associated with Windows environments. There is no mention of Linux or cross-platform workflows, and the use of PowerShell is presented as the default or only option for scripting and automation.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell for all certificate management and troubleshooting tasks.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash script examples where appropriate.
- Where PowerShell is referenced, clarify that it is available cross-platform, but also offer Bash/CLI alternatives to ensure Linux users are not excluded.
- Review all automation and scripting guidance to ensure parity between Windows and Linux tooling, and avoid presenting Windows tools as the default.
- Include a section or note highlighting cross-platform support and linking to relevant Azure CLI documentation.
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
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. It exclusively uses Windows Server as the backend VM OS, provides only PowerShell commands for configuration (with no Bash or Linux CLI alternatives), and instructs users to edit the Windows hosts file using Windows-specific paths and tools. There are no examples or instructions for Linux users, either for backend VM creation, web server installation, or local name resolution.
Recommendations
- Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
- Include Azure CLI/Bash examples alongside PowerShell for tasks like installing web servers or managing resources.
- Add a section on editing the /etc/hosts file for Linux/macOS users, including appropriate commands (e.g., using sudo nano /etc/hosts).
- Mention cross-platform tools and commands where possible, or clearly indicate when steps are Windows-specific.
- Balance screenshots and code snippets to show both Windows and Linux environments where relevant.
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 toward Windows environments. All command-line examples for certificate creation and backend server setup use Windows PowerShell and Windows Server. There are no Linux or cross-platform alternatives provided for creating self-signed certificates, exporting PFX files, or setting up backend servers. The documentation assumes the user is running Windows locally and uses Windows-specific tools and patterns throughout.
Recommendations
- Provide equivalent Linux and macOS instructions for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
- Include examples for deploying Linux-based backend servers (such as Ubuntu VMs) and installing a web server (e.g., Apache or Nginx) for testing.
- When referencing command-line tools, offer both Windows (PowerShell) and Linux/macOS (Bash/OpenSSL) alternatives side by side.
- Clarify in the prerequisites that the tutorial is currently Windows-centric, or update it to be explicitly cross-platform.
- Consider using Azure CLI examples, which are cross-platform, for steps such as VM creation and extension installation.
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 providing only Windows-based SQL Server VM creation instructions (with the default image being 'SQL Server 2022 Developer on Windows Server 2022'), and by instructing users to connect using SQL Server Management Studio, a Windows-only tool. There are no examples or guidance for deploying a Linux-based SQL Server VM or for connecting from Linux clients using cross-platform tools.
Recommendations
- Include instructions for creating a SQL Server VM on Linux (e.g., Ubuntu) as an alternative to the Windows-based VM.
- Provide examples of connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI clients available on Linux and macOS.
- Mention both Windows and Linux options when describing VM image selection, and clarify that the procedure works for both OS types.
- Add screenshots or command-line examples for Linux users where appropriate, such as using the Azure CLI or SSH.
- Ensure that any references to client tools (like SQL Server Management Studio) are accompanied by alternatives that work on Linux and macOS.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for HTTP debugging, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor are Linux-friendly web debugging tools (like tcpdump, Wireshark, or mitmproxy) mentioned. Instructions and screenshots are tailored to Windows environments, and Windows tools are introduced before any alternatives.
Recommendations
- Provide equivalent Azure CLI (az network application-gateway ...) and/or Bash examples for checking Application Gateway settings, alongside or before PowerShell.
- Mention and give examples for cross-platform or Linux-friendly web debugging tools such as mitmproxy, Wireshark, or tcpdump, not just Fiddler.
- Include installation and usage instructions for these tools on Linux/macOS as well as Windows.
- Avoid Windows-specific instructions like 'Run as administrator' unless also providing the equivalent for other platforms.
- Where screenshots are used, consider including examples from Linux desktops or web-based tools to ensure parity.
- Explicitly state that the troubleshooting steps can be performed on any OS, and provide guidance for users on non-Windows systems.
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 detailed instructions and code samples for enabling diagnostic logs using the Azure Portal and PowerShell, both of which are Windows-centric tools. There are no equivalent CLI or Bash examples for Linux/macOS users, and PowerShell is presented as the only scripting option. This creates a bias toward Windows environments and leaves out Linux-native workflows.
Recommendations
- Add Azure CLI (az) examples for enabling diagnostic logging, as the Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell script examples alongside PowerShell, or at least reference how Linux users can accomplish the same tasks.
- Explicitly mention that PowerShell Core is cross-platform if retaining PowerShell examples, but still provide native Bash/Azure CLI alternatives.
- Ensure that documentation sections do not assume a Windows environment by default; present cross-platform options equally or list Linux-friendly methods first where appropriate.
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 a bias toward Windows environments by only providing a PowerShell command (Remove-AzResourceGroup) for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting any Linux-based examples or equivalent CLI commands. There are no instructions or examples for performing these tasks using Azure CLI, Bash, or Linux-native tools.
Recommendations
- Provide equivalent Azure CLI (az group delete) and/or Bash commands for resource cleanup alongside the PowerShell example.
- Include validation steps using a Linux-based web server (such as Apache or Nginx) in addition to IIS, or clarify that the backend VMs could run either Windows or Linux.
- Offer guidance or examples for users deploying and validating the setup from Linux/macOS environments, not just Windows.
- Ensure that all code snippets and instructions are cross-platform where possible, or explicitly provide alternatives for both Windows and Linux users.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell by providing only PowerShell-based command-line examples for configuring Application Gateway with Key Vault certificates. There are no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. The instructions and code samples assume the use of PowerShell, which is most commonly associated with Windows environments, and the 'Next steps' section links exclusively to a PowerShell guide. This may hinder Linux or macOS users who prefer or require CLI/Bash-based workflows.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and managing Application Gateway.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or Bash, and provide links to relevant documentation.
- In the 'Next steps' section, include links to guides for Azure CLI and ARM/Bicep templates, not just PowerShell.
- Where possible, provide Bash script snippets or instructions for common Linux workflows (e.g., using environment variables, jq for JSON parsing, etc.).
- Ensure that references to tools and commands are cross-platform or, if not, that alternatives are clearly documented.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md
...ob/main/articles/application-gateway/retirement-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively references Azure PowerShell scripts for migration, without mentioning or providing examples for Azure CLI or other cross-platform tools. There are no Linux-specific instructions or examples, and the guidance assumes use of PowerShell, which is traditionally associated with Windows environments. This creates a bias towards Windows users and may hinder Linux or cross-platform users.
Recommendations
- Provide equivalent Azure CLI commands and scripts for all migration steps, ensuring Linux and macOS users have clear, supported options.
- Explicitly mention that Azure PowerShell is cross-platform, if relevant, and provide installation instructions for Linux/macOS if PowerShell must be used.
- Include examples or references for Bash scripting or automation, not just PowerShell.
- Add a section comparing migration approaches/tools for both Windows and Linux environments.
- Ensure all tooling recommendations are platform-agnostic or offer parity between Windows and Linux.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-overview.md
...blob/main/articles/application-gateway/ssl-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and APIs (such as the PFXImportCertStore function), providing configuration guidance primarily via PowerShell, and omitting equivalent Linux or cross-platform command-line examples. The 'Next steps' section directs users to a PowerShell-based guide, and there is no mention of Azure CLI, Bash, or Linux certificate management tools. The documentation assumes familiarity with Windows-centric certificate formats and management patterns, with no guidance for Linux users.
Recommendations
- Include Azure CLI and/or Bash examples alongside or before PowerShell instructions for configuring Application Gateway and TLS.
- Reference cross-platform certificate management tools (e.g., OpenSSL) for creating and managing certificates, and provide sample commands for exporting to PFX format on Linux.
- Link to or provide guidance for Linux/macOS users on how to generate, convert, and upload certificates, including how to handle certificate chains.
- Mention that PFX files can be created and managed on non-Windows systems, and provide relevant documentation links.
- In the 'Next steps' section, add links to guides for configuring end-to-end TLS using Azure CLI, ARM templates, and the Azure Portal, not just PowerShell.
- Where Windows APIs or tools are referenced, provide equivalent cross-platform alternatives or clarify that the process is not Windows-specific.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/migrate-v1-v2.md
...lob/main/articles/application-gateway/migrate-v1-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All migration instructions, code samples, and tooling references are exclusively for Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform scripting. The prerequisites, script download, and execution steps assume a PowerShell environment, and there are no Linux- or macOS-specific instructions or examples. This creates a significant barrier for users on non-Windows platforms or those who prefer CLI/Bash scripting.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for each PowerShell example, including authentication, resource queries, and migration steps.
- Include explicit instructions for running the migration from Linux/macOS environments, such as using Azure Cloud Shell (Bash) or installing PowerShell Core cross-platform.
- Mention and demonstrate how to use the Azure CLI to retrieve resource IDs, manage certificates, and perform other prerequisite steps.
- Clarify whether the migration script can be run in Azure Cloud Shell (Bash) or if it requires PowerShell, and provide alternatives if possible.
- Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
- Ensure that any references to downloading and running scripts include Linux/macOS-compatible instructions (e.g., using wget/curl, handling .nupkg files without Windows tools).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md
...ticles/application-gateway/self-signed-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation displays a moderate Windows bias. While the main certificate generation workflow uses cross-platform OpenSSL commands, several sections and examples prioritize or exclusively reference Windows tools, paths, or procedures. The Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example. Instructions for editing the hosts file and importing certificates into IIS link to Windows-specific resources, and file paths in PowerShell examples use Windows conventions. Linux-specific instructions or parity are often missing or appear after Windows references.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Include Linux-specific instructions for editing the hosts file (e.g., /etc/hosts) and importing certificates into popular Linux web servers.
- When referencing file paths, use cross-platform conventions or show both Windows and Linux examples.
- When linking to web server documentation, include links for both Windows (IIS) and Linux (Apache, NGINX) equally and in parallel.
- Explicitly mention Linux procedures for adding a root certificate to the trusted store (e.g., update-ca-certificates on Debian/Ubuntu).
- Balance the order of presentation so that Linux and Windows tools/examples are given equal prominence.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md
...configure-application-gateway-with-private-frontend-ip.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a clear Windows bias: it only provides instructions for deploying Windows Server virtual machines, uses PowerShell exclusively for scripting (including the Azure Cloud Shell example), and installs IIS (a Windows web server) as the backend workload. There are no examples or guidance for deploying Linux VMs, using Bash/CLI, or installing a Linux-based web server such as Apache or Nginx.
Recommendations
- Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
- Include examples for installing a web server on Linux VMs (e.g., using apt to install Apache or Nginx).
- Offer Azure CLI (Bash) equivalents for all PowerShell commands, especially for VM extension/script installation.
- When referencing OS images, mention both Windows and popular Linux distributions, allowing users to choose.
- Balance screenshots and walkthroughs to show both Windows and Linux scenarios where applicable.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell cmdlets, with no mention or examples of Azure CLI (which is cross-platform and preferred on Linux/macOS) or ARM templates. The prerequisites and instructions reference Windows PowerShell and related tools exclusively. There are no Linux shell, Bash, or Azure CLI equivalents provided, nor any guidance for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include a section or callout for Linux/macOS users, clarifying that all steps can be performed using Azure CLI and linking to relevant CLI documentation.
- Avoid language that assumes the user is on Windows or using PowerShell (e.g., 'switch PowerShell mode'), or at least provide parallel instructions for Bash/CLI environments.
- Consider including ARM/Bicep template examples for users who prefer declarative infrastructure-as-code approaches, which are platform-agnostic.
- Update the prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation instructions for all major platforms.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for enabling logging, omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The use of PowerShell is presented as the primary (and only) scripting interface, and there is no mention of cross-platform tools or Linux-specific workflows. Additionally, tools like Excel and Visual Studio are referenced for log analysis and conversion, which are traditionally Windows-centric, without suggesting Linux-friendly alternatives. The ordering of examples and tool recommendations further reinforces a Windows-first perspective.
Recommendations
- Add equivalent Azure CLI and/or Bash examples alongside PowerShell commands for enabling diagnostic logging.
- Explicitly mention that Azure CLI is cross-platform and provide usage instructions for Linux/macOS users.
- Include references to Linux-friendly tools for log analysis, such as jq, csvkit, or open-source alternatives to Excel and Visual Studio.
- Ensure that tool recommendations (e.g., for log conversion) include cross-platform or Linux-native options, such as Python scripts or open-source utilities.
- Balance the order of presentation so that Windows and Linux approaches are given equal prominence, or alternate which is presented first.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health.md
...lication-gateway/application-gateway-backend-health.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 a dedicated PowerShell example and section before the Azure CLI example, without offering any Linux shell or Bash-specific guidance. There is no mention of Linux-native tools or workflows, and the PowerShell example is more prominently featured. This may make Linux users feel less supported or require them to adapt Windows-centric instructions.
Recommendations
- Add explicit Bash or Linux shell examples alongside PowerShell, especially for common tasks.
- Present Azure CLI examples before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Include troubleshooting steps or tool recommendations that are relevant for Linux environments (e.g., using curl, openssl, or Linux-based network troubleshooting tools).
- Ensure that any references to scripts or automation include both PowerShell and Bash equivalents where possible.
- Review the order of examples and avoid always listing Windows/PowerShell first unless there is a clear reason.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-web-app.md
...main/articles/application-gateway/configure-web-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides extensive PowerShell-based automation and scripting examples for configuring Azure Application Gateway with App Service, but does not include equivalent examples for Linux/Unix users (e.g., Azure CLI, Bash). All command-line automation is shown exclusively in PowerShell, which is primarily associated with Windows environments. There is no mention of cross-platform tools or Linux-native workflows, and no Bash, Azure CLI, or REST API examples are provided.
Recommendations
- Add Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Where automation is shown, provide both PowerShell and Bash/Azure CLI tabs, or at least link to equivalent Azure CLI documentation.
- Explicitly mention that all PowerShell commands can be run on Linux/macOS with PowerShell Core, or provide guidance for non-Windows users.
- Include REST API or ARM template examples for users who prefer declarative or cross-platform approaches.
- Review and update the 'ms.custom' metadata to reflect cross-platform tooling, not just 'devx-track-azurepowershell'.