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 751-775 of 981 flagged pages
Application Gateway
Quickstart: Direct web traffic using a Resource Manager template
.../articles/application-gateway/quick-create-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias. The only explicit command-line example for resource cleanup uses PowerShell (`Remove-AzResourceGroup`), with no equivalent Azure CLI or Bash example provided. The validation steps focus on IIS (a Windows web server), and the virtual machines in the backend pool are configured with IIS, implicitly favoring Windows environments. While the page mentions that the quickstart can be completed via Azure CLI, PowerShell, or Portal, the actual step-by-step instructions and code samples are Windows-centric, and Linux/macOS users are left to infer or adapt steps for their platforms.
Recommendations
- Provide Azure CLI and Bash examples for all command-line operations, especially for resource cleanup (e.g., `az group delete --name <your resource group name>`).
- Include instructions or notes for validating deployment using a Linux web server (such as Apache or Nginx), or clarify how Linux users can test the gateway.
- Ensure that examples and instructions are presented in a platform-neutral order, or alternate between Windows and Linux examples.
- Explicitly mention Linux/macOS compatibility and provide links to relevant documentation for those platforms.
Create Pull Request
Application Gateway
Renew an Azure Application Gateway certificate
...ain/articles/application-gateway/renew-certificates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides step-by-step instructions for renewing an Azure Application Gateway certificate via the Azure portal, Azure PowerShell, and Azure CLI. The PowerShell example is detailed and presented before the CLI example, which may suggest a Windows-first approach. There are no explicit Linux/macOS-specific instructions or examples (e.g., bash scripting, OpenSSL usage, or platform caveats). The CLI example is cross-platform, but the lack of Linux/macOS context and the prominence of PowerShell may create friction for non-Windows users.
Recommendations
- Add explicit notes confirming Azure CLI commands work on Linux/macOS, and mention any platform-specific differences.
- Provide bash or shell script examples for certificate renewal, especially for uploading or manipulating certificate files.
- Include troubleshooting tips for Linux/macOS users (e.g., file permissions, certificate formats).
- Balance the order of examples by presenting CLI and PowerShell side-by-side, or leading with the cross-platform CLI example.
Application Gateway
Configure Request and Response Buffers
...lob/main/articles/application-gateway/proxy-buffers.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides examples for Azure CLI, PowerShell, and ARM templates. PowerShell (a Windows-centric tool) is given a dedicated section with both creation and update examples, while Linux/macOS-native alternatives (such as Bash scripting or cross-platform SDKs) are not mentioned. The reference link is to the .NET SDK, which is also more common on Windows. PowerShell examples are shown before ARM templates, and no Linux/macOS-specific guidance is provided.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for tasks shown in PowerShell.
- Include references to cross-platform SDKs (e.g., Python, Java) and provide example code snippets.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- If PowerShell is shown, also show equivalent Bash or shell commands for parity.
- Reference documentation for Linux/macOS users (e.g., Azure CLI installation guides for those platforms).
Application Gateway
Redirect overview for Azure Application Gateway
...main/articles/application-gateway/redirect-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page references a tutorial for configuring URL redirection using PowerShell, which is primarily a Windows tool. There are no examples or links for Linux/macOS users (such as Azure CLI or ARM templates), and the only next step provided is PowerShell-based. This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
- Add equivalent tutorials and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Provide ARM template or Bicep configuration examples for automation that are OS-independent.
- Ensure that links to next steps include both PowerShell and CLI/REST API options.
- Explicitly mention platform compatibility and recommend tools for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a notable Windows bias. Migration instructions and tooling are centered around Azure PowerShell scripts, with no mention of Azure CLI, Bash, or Linux/macOS-compatible alternatives. All examples and references to automation use PowerShell, and there are no Linux-specific instructions or parity in migration tooling. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Provide equivalent Azure CLI scripts and instructions for migration tasks, including configuration and public IP retention.
- Explicitly mention cross-platform compatibility for migration scripts, or provide Bash/Python alternatives.
- Include examples and guidance for Linux/macOS users, such as how to run migration steps without PowerShell.
- List both PowerShell and CLI options side-by-side, or indicate which steps are platform-agnostic.
- Clarify any prerequisites for running scripts on non-Windows platforms (e.g., PowerShell Core on Linux).
Application Gateway
Generate self-signed certificate with a custom root CA
...ticles/application-gateway/self-signed-certificates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates moderate Windows bias. While the core certificate generation steps use OpenSSL (cross-platform), Windows is mentioned first in prerequisites, and the only detailed Azure automation example is via Azure PowerShell, with no Azure CLI or Linux-native automation shown. IIS (Windows web server) instructions are presented before Apache/NGINX, and file paths in PowerShell examples use Windows conventions. There is no explicit Linux example for uploading certificates to Application Gateway.
Recommendations
- Add Azure CLI examples for uploading certificates and configuring Application Gateway, with Linux/macOS-friendly file paths.
- Present Linux and Windows prerequisites equally (e.g., 'on Windows, Linux, or macOS').
- Alternate or parallelize web server configuration instructions (e.g., show Apache/NGINX before or alongside IIS).
- Include screenshots and file path examples for Linux/macOS environments.
- Clarify that OpenSSL commands work identically on Linux/macOS, and provide troubleshooting tips for those platforms.
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (PFXImportCertStore), providing PowerShell as the only example for configuration, and linking exclusively to PowerShell-based next steps. There is no mention of Linux/macOS equivalents, nor are CLI or portal examples provided. Windows terminology and tooling are referenced before any cross-platform alternatives.
Recommendations
- Add Azure CLI and/or Azure Portal instructions for configuring end-to-end TLS, alongside PowerShell.
- Reference cross-platform certificate management tools (e.g., OpenSSL) for certificate creation and conversion, not just Windows APIs.
- Include Linux/macOS-specific troubleshooting and example workflows.
- Ensure that next steps link to documentation for all supported platforms, not only PowerShell.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium 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 and instructions use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Linux/macOS alternatives or cross-platform CLI options. This creates friction for Linux/macOS users, who may not have access to these tools or may need to install PowerShell Core and adapt commands. The tutorial does not provide Azure CLI equivalents or guidance for non-Windows environments.
Recommendations
- Provide Azure CLI examples alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include instructions for creating self-signed certificates using OpenSSL, which is available on Linux/macOS.
- Explicitly mention that PowerShell Core can be installed on Linux/macOS and provide installation guidance.
- Reorder examples so that cross-platform solutions (Azure CLI, OpenSSL) are presented first or alongside Windows-specific tools.
- Add notes or links for Linux/macOS users to relevant documentation for equivalent tasks.
Application Gateway
Tutorial: Protect your application gateway with Azure DDoS Network Protection
...n-gateway/tutorial-protect-application-gateway-ddos.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a notable Windows bias, especially in the backend VM creation and configuration steps. Only Windows Server is suggested for backend VMs, and IIS installation is shown exclusively via Azure PowerShell using Windows-specific commands. There are no examples or guidance for deploying Linux VMs or configuring a Linux-based web server (e.g., Apache, Nginx). The only automation example uses PowerShell, with no Bash or Linux CLI alternatives. This creates friction for Linux/macOS users and implies a preference for Windows environments.
Recommendations
- Include parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Provide examples for installing a web server on Linux VMs (e.g., Apache or Nginx) using Bash scripts or Azure CLI.
- Offer both PowerShell and Bash/CLI commands for VM extension installation and configuration.
- Explicitly state that backend pools can use Linux VMs and provide sample configurations.
- Reorder examples or alternate between Windows and Linux to avoid Windows-first presentation.
Application Gateway
Configure Azure Monitor alerts for Application Gateway
...application-gateway/configure-alerts-with-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references a procedure link that prioritizes CLI and PowerShell methods for deploying ARM templates, with PowerShell being a Windows-centric tool. There is no explicit mention of Linux/macOS equivalents (e.g., Bash, Azure CLI on Linux), and the 'Deploy to Azure' button directs users to the Azure Portal, which is platform-agnostic, but the guidance for automation leans toward Windows-first tooling.
Recommendations
- Explicitly mention and provide examples for using Azure CLI on Linux/macOS to deploy ARM templates.
- Ensure that referenced procedures include Bash and cross-platform CLI instructions alongside PowerShell.
- Add a note clarifying that all ARM template deployment methods work on Linux/macOS, and link to platform-specific guides.
- Reorder examples so that platform-agnostic or Linux/macOS methods are shown first or equally with Windows/PowerShell.
Application Gateway
Common key vault errors in Application Gateway
...gateway/application-gateway-key-vault-common-errors.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides troubleshooting steps for Azure Application Gateway key vault errors, but command-line examples are exclusively in PowerShell, with no Azure CLI or Bash alternatives. This creates friction for Linux/macOS users, as PowerShell is not their default environment. Additionally, PowerShell examples are presented first and exclusively, and there are no Linux-specific instructions or screenshots.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, especially for certificate updates and key vault interactions.
- Include notes or sections indicating how Linux/macOS users can perform these tasks using Bash or Azure CLI.
- Where screenshots are shown, clarify that the Azure Portal experience is cross-platform, but highlight any OS-specific differences if relevant.
- Present CLI examples before or alongside PowerShell to avoid Windows-first bias.
Application Gateway
Azure Application Gateway listener configuration
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a code example for enabling HTTP/2 support using Azure PowerShell, which is primarily a Windows tool. There are no equivalent CLI or Linux/macOS examples (such as Azure CLI or REST API), and PowerShell is the only automation method shown. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell snippets, especially for enabling HTTP/2 support.
- Include REST API or ARM template examples where relevant, to ensure platform neutrality.
- Explicitly mention that all configuration steps can be performed using Azure CLI, portal, or REST API, and link to relevant cross-platform guides.
- When showing code samples, present Azure CLI and PowerShell side-by-side, or show CLI first to avoid Windows-first bias.
Application Gateway
Application Gateway high traffic volume support
...n/articles/application-gateway/high-traffic-support.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell as the primary method for configuring WAF custom rules and TLS policy versions, without mentioning or providing equivalent CLI or Linux/macOS instructions. There are no explicit Linux/macOS examples or guidance, and the only tool-specific references are to PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide equivalent Azure CLI examples for all tasks currently described with PowerShell, especially for configuring WAF custom rules and TLS policy versions.
- Explicitly mention that PowerShell is available cross-platform, but also offer Bash/CLI instructions for Linux/macOS users.
- Ensure links to configuration guides include both PowerShell and Azure CLI/Bash options.
- Add a note or section clarifying cross-platform management options for Application Gateway.
Application Gateway
Quickstart: Direct web traffic using the portal
...in/articles/application-gateway/quick-create-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, especially in the backend VM creation and configuration steps. Only Windows Server is suggested for backend VMs, and IIS installation is shown exclusively via Azure PowerShell using Windows-specific commands. There are no Linux VM examples, nor is there guidance for deploying a Linux web server (e.g., Apache, Nginx) or using Bash/CLI for configuration. The use of PowerShell and Windows tools is presented as the default, with no parity for Linux/macOS users.
Recommendations
- Include parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Provide examples for installing a web server on Linux (e.g., Apache or Nginx) using Azure CLI or Bash scripts.
- Show how to use Azure CLI or Bash in Cloud Shell for VM extension installation and configuration.
- Explicitly mention that Application Gateway supports both Windows and Linux backend pools.
- Alternate or parallelize example order so Linux and Windows are equally represented.
Application Gateway
TLS termination with Azure Key Vault certificates
...b/main/articles/application-gateway/key-vault-certs.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell examples for critical configuration steps, referencing Azure PowerShell and CLI together but showing only PowerShell code, and linking to PowerShell-specific guides. There are no Bash/Azure CLI examples, and PowerShell is presented as the default automation tool. This creates friction for Linux/macOS users, who typically use Bash and Azure CLI.
Recommendations
- Add equivalent Azure CLI (bash) examples for all PowerShell commands, especially for referencing Key Vault secrets and configuring Application Gateway.
- Ensure that both PowerShell and CLI examples are presented side-by-side, or provide tabs for each platform.
- Update 'Next steps' to include links to CLI and ARM/Bicep template guides, not just PowerShell.
- Explicitly mention platform-neutral options (ARM templates, Bicep, REST API) where possible.
- Avoid implying PowerShell is required by clarifying that CLI and other tools are equally supported.
Application Gateway
Externally managed scheduled autoscaling for Application Gateway v2
...ation-gateway-externally-managed-scheduled-autoscaling.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides PowerShell runbook examples for scheduled autoscaling, with no mention of Bash, Python, or other cross-platform scripting options. This creates friction for Linux/macOS users who may prefer or require non-PowerShell solutions, and implicitly prioritizes Windows tooling.
Recommendations
- Provide equivalent runbook examples using Azure CLI (Bash), Python, or other cross-platform languages supported by Azure Automation.
- Explicitly mention that Azure Automation supports Python and graphical runbooks, and link to relevant documentation.
- List both PowerShell and non-PowerShell options side-by-side, or clarify which platforms are supported for each example.
- Add a note on how Linux/macOS users can author and test runbooks locally, including prerequisites and tooling.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Azure PowerShell in the 'Next steps' section as the only tool for creating an autoscaling, zone redundant application gateway with a reserved virtual IP address. No mention is made of equivalent Linux/macOS-friendly tools (such as Azure CLI, ARM templates, or Terraform), nor are examples for those platforms provided. The PowerShell example is listed first and exclusively, indicating a Windows-first and Windows-tools bias.
Recommendations
- Add equivalent instructions and links for Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include ARM template or Terraform examples for infrastructure-as-code parity.
- When listing tooling in 'Next steps', present cross-platform options (e.g., 'using Azure CLI or PowerShell') rather than only PowerShell.
- Explicitly state which tools are supported on which platforms, and avoid implying PowerShell is the only or preferred method.
Application Gateway
Create a custom probe using the portal
...ion-gateway/application-gateway-create-probe-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents three entry points for creating a custom probe: Azure portal, Azure Resource Manager PowerShell, and Azure Classic PowerShell. PowerShell is a Windows-centric tool, and there is no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash scripting). The PowerShell options are listed immediately after the portal, suggesting a Windows-first approach. No Linux-specific tools, examples, or instructions are provided.
Recommendations
- Add Azure CLI instructions/examples for creating and managing custom probes, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell usage is required, and provide guidance for installation and usage on those platforms.
- Reorder or present entry points in a way that does not prioritize Windows tools (e.g., list Azure CLI and PowerShell together, or clarify platform compatibility).
- Include notes or links for Linux/macOS users to ensure parity and clarity.
Application Gateway
Troubleshoot backend health issues in Azure Application Gateway
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Troubleshooting steps and command-line examples are primarily provided using PowerShell and Windows tools, with explicit instructions for Windows environments (e.g., certlm.msc, netstat via cmd). Linux alternatives are mentioned only in a few places (e.g., OpenSSL for certificate inspection), and there are no CLI/bash examples for core troubleshooting tasks such as network connectivity checks or certificate management. Windows tools and workflows are often described first or exclusively, leaving Linux/macOS users to infer their own equivalents.
Recommendations
- Provide equivalent Azure CLI and bash commands alongside PowerShell examples for all troubleshooting steps.
- Include Linux/macOS-specific instructions for certificate inspection, network connectivity (e.g., using curl, nc, or ss/netstat), and file management.
- Present Windows and Linux/macOS examples in parallel, or clarify which steps apply to which OS.
- Reference cross-platform tools (e.g., OpenSSL, curl) more consistently, and avoid assuming Windows as the default environment.
- Add screenshots or terminal output from Linux/macOS where relevant.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias. The only CLI example for enabling logging is provided using PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible commands. The log converter tool is referenced as a Visual Studio/C# solution, which is Windows-centric. Additionally, examples for viewing logs suggest using Excel and Power BI, both of which are primarily Windows tools. There are no Linux/macOS-specific instructions or parity in tooling or workflow examples.
Recommendations
- Add equivalent Azure CLI commands for enabling diagnostic logging, with example usage for Linux/macOS terminals.
- Reference cross-platform log conversion tools (e.g., Python scripts, jq, csvkit) for handling JSON logs.
- Include instructions or examples for viewing logs using open-source or Linux-native tools (e.g., grep, awk, pandas, LibreOffice Calc).
- Mention PowerShell Core as cross-platform if PowerShell is retained, but clarify compatibility.
- Reorder examples so that cross-platform solutions appear before or alongside Windows-specific ones.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through exclusive use of Azure PowerShell cmdlets for configuration examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch), and references to PowerShell-based workflows for probe configuration. There are no CLI (az), ARM template, REST API, or Linux/macOS shell examples provided, and the 'Next steps' section lists PowerShell before the Azure Portal. This may create friction for Linux/macOS users who prefer cross-platform tools.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, especially for probe matching and configuration.
- Include ARM template and/or REST API snippets for probe configuration to support automation and platform neutrality.
- Explicitly mention that all configuration steps can be performed on Linux/macOS using CLI or portal, not just PowerShell.
- In 'Next steps', list cross-platform options (CLI, portal, REST) before or alongside PowerShell.
- Where possible, avoid referencing only Windows-specific tools or patterns (e.g., PowerShell cmdlets) in conceptual sections.
Application Gateway
Troubleshoot Bad Gateway errors - Azure Application Gateway
...ion-gateway/application-gateway-troubleshooting-502.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell examples for troubleshooting, referencing Windows-centric tools and patterns (such as PowerShell cmdlets and IIS), and omitting equivalent Azure CLI or Bash examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer command-line tools native to their platforms. The order of presentation also places Windows/PowerShell solutions first, with no mention of Linux-specific troubleshooting steps or cross-platform alternatives.
Recommendations
- Add Azure CLI examples alongside PowerShell for all troubleshooting steps.
- Explicitly mention that PowerShell commands can be run on Linux/macOS (if true), or provide Bash equivalents.
- Include troubleshooting guidance for common Linux web servers (e.g., Apache, Nginx) where IIS is referenced.
- Reorder examples or provide parallel instructions for both Windows and Linux users.
- Clarify tool requirements and provide installation instructions for non-Windows platforms.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references Azure PowerShell cmdlets for critical operations (such as restarting the Application Gateway after DNS changes) without providing equivalent Azure CLI or Linux/macOS instructions. PowerShell is a Windows-centric tool, and its mention without parity for CLI or Bash creates friction for Linux/macOS users. Additionally, when tools are mentioned, PowerShell is referenced first or exclusively.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all operations, especially for restarting or managing Application Gateway resources.
- Explicitly mention cross-platform tools (Azure CLI, Bash scripts) wherever PowerShell is referenced.
- Ensure that any command-line instructions are available for Linux/macOS users and are presented with equal prominence.
- Add a note clarifying that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant documentation.
Application Gateway
Private Application Gateway deployment
...tion-gateway/application-gateway-private-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides platform-specific instructions for feature registration and unregistration using Azure Portal, PowerShell, and CLI. The PowerShell examples (Windows-centric) are presented before CLI (cross-platform), and output examples reference PowerShell cmdlets even in the CLI section. There are no Linux/macOS-specific examples or notes, and PowerShell is emphasized as a primary automation method, which may create friction for Linux/macOS users who are more likely to use Bash and Azure CLI.
Recommendations
- Present Azure CLI examples before PowerShell, or at least alternate the order to avoid implicit prioritization.
- Ensure output examples in the CLI section use actual Azure CLI output, not PowerShell cmdlet output.
- Add explicit notes clarifying that Azure CLI works on Linux/macOS and is recommended for non-Windows users.
- Include Bash script examples for common automation scenarios where PowerShell is referenced.
- Mention cross-platform tools (e.g., Terraform, ARM templates) earlier and more prominently when discussing automation options.
Application Gateway
TLS policy overview for Azure Application Gateway
...ion-gateway/application-gateway-ssl-policy-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits a moderate Windows bias by referencing PowerShell and CLI as the primary tools for viewing and configuring TLS policies, with PowerShell mentioned first in several places. There are no explicit Linux/macOS examples or mentions of Linux-native tools, and the guidance for configuration and details retrieval is centered around PowerShell, CLI, REST API, and the Azure Portal, with PowerShell often listed first. The 'Next steps' section links only to a PowerShell-based configuration guide.
Recommendations
- Provide explicit Linux/macOS examples using Azure CLI (az), Bash, or REST API, and reference these before or alongside PowerShell.
- Ensure that configuration guides linked in 'Next steps' include Linux/macOS instructions and examples, not just PowerShell.
- Mention cross-platform tools and clarify that Azure CLI and REST API are available on all major operating systems.
- Avoid listing PowerShell first unless it is truly the most common or recommended method for all users; consider rotating or balancing the order.
- Add a dedicated section or callout for Linux/macOS users, highlighting any platform-specific considerations or parity.