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 76-100 of 172 flagged pages
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell-based workflows, with all examples, scripts, and tooling provided exclusively for Azure PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples provided. The use of PowerShell is assumed throughout, and installation/usage instructions are tailored to Windows/PowerShell environments. This creates friction for users on Linux or macOS, who may prefer or require Azure CLI or Bash scripting.
Recommendations
- Provide equivalent Azure CLI scripts and examples for all migration steps, including configuration cloning and IP retention.
- Explicitly note cross-platform compatibility for PowerShell scripts (e.g., Azure Cloud Shell, PowerShell Core on Linux/macOS) and provide instructions for running scripts in those environments.
- Add Bash/CLI examples for common operations (e.g., retrieving resource IDs, uploading certificates) alongside PowerShell examples.
- Clarify any limitations or requirements for running provided scripts on non-Windows platforms.
- Consider linking to or referencing Azure CLI documentation for Application Gateway management.
Create Pull Request
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Application Gateway v2 shows a moderate Windows/PowerShell bias. Migration and registration/unregistration examples use Azure PowerShell (Set-AzContext, Register-AzProviderFeature, etc.) rather than cross-platform Azure CLI or Bash equivalents. The 'Next steps' section links to a PowerShell tutorial first. There are no explicit Linux/macOS CLI or Bash examples, and PowerShell is implicitly assumed as the primary automation tool.
Recommendations
- Provide Azure CLI and/or Bash equivalents for all PowerShell command examples, especially for registration, unregistration, and migration steps.
- When listing tutorials or quickstarts, offer both PowerShell and Azure CLI (or Bash) options, or clearly indicate cross-platform options.
- Clarify in the text that Azure PowerShell commands can be run on any platform, or link to cross-platform installation guides.
- Consider reordering or balancing the prominence of PowerShell and CLI/Bash examples to avoid the impression of Windows-first bias.
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
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools first and exclusively when discussing how to view or configure TLS policy details. There are no explicit Linux or macOS command examples, nor are cross-platform CLI instructions provided alongside PowerShell references. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting Linux-friendly Azure CLI or REST API walkthroughs.
Recommendations
- Add Azure CLI examples for all configuration and inspection tasks, ensuring parity with PowerShell instructions.
- Explicitly mention REST API and Portal methods where applicable, and provide step-by-step guides for Linux/macOS users.
- In tables and notes, reference CLI and REST API options alongside PowerShell, not after or instead of.
- Update 'Next steps' to link to both PowerShell and CLI/REST API guides for configuring TLS policies.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Migration instructions and preview registration/unregistration are presented exclusively with Azure PowerShell commands, which are most commonly used and best supported on Windows. The 'Next steps' section links to a tutorial with a '-ps' suffix, suggesting PowerShell as the primary method. There are no Linux/macOS-specific CLI examples, nor are cross-platform Azure CLI commands provided for key operations. Windows-centric tooling is mentioned before any alternatives, and Linux parity is not addressed.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all registration, migration, and management tasks.
- Explicitly mention that Azure CLI is cross-platform and supported on Linux/macOS.
- Add links to tutorials using Azure CLI or ARM templates for creating and managing Application Gateway v2.
- Clarify which commands/tools are available and supported on Linux/macOS.
- Ensure that Linux/macOS users are not required to use PowerShell for critical operations.
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 a moderate Windows bias. Windows and PowerShell are referenced first or exclusively in several key sections, such as the prerequisites (listing Windows before Linux), IIS configuration, and especially in the Application Gateway upload section, which provides only Azure PowerShell examples with Windows file paths. Linux equivalents (e.g., Azure CLI, Linux certificate store instructions) are missing or less emphasized.
Recommendations
- Provide Azure CLI examples for uploading certificates to Application Gateway, using Linux/macOS file paths.
- Include instructions for adding root certificates to Linux/macOS trusted stores (e.g., update-ca-certificates, Keychain Access for macOS).
- List Linux before or alongside Windows in prerequisites and examples, or use neutral phrasing.
- Offer NGINX and Apache configuration screenshots/images, not just IIS.
- Clarify that OpenSSL commands work cross-platform and show example file paths for both OS types.
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 First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, with troubleshooting steps and command-line examples predominantly using PowerShell and Windows-specific tools. Windows methods (PowerShell, certlm.msc, netstat via cmd) are described in detail, often before or instead of Linux equivalents. Linux guidance is sparse, with only brief mentions of OpenSSL and no CLI or shell command examples for common troubleshooting tasks. This bias may hinder Linux/macOS users from efficiently following the documentation.
Recommendations
- Provide equivalent Linux/macOS command-line examples for all PowerShell commands (e.g., use Azure CLI, curl, netcat, ss, openssl).
- Include Linux/macOS methods for certificate inspection and export (e.g., using openssl, keytool, or system certificate stores).
- Present troubleshooting steps for both Windows and Linux environments side-by-side, or clearly indicate platform-specific instructions.
- Reference Linux/macOS tools (e.g., systemctl, journalctl, firewall-cmd/ufw) when discussing server/network troubleshooting.
- Ensure Azure CLI examples are given equal prominence to PowerShell, as CLI is cross-platform.
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. The only command-line example for enabling logging uses PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS alternatives. The log conversion tip references Visual Studio and a C# tool, both Windows-centric, without alternatives for other platforms. Additionally, the examples for viewing and analyzing logs focus on Excel and Power BI, which are primarily Windows tools, and these are mentioned before any cross-platform or open-source options. There are no Linux/macOS-specific instructions or parity in tooling or examples.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, which work on Linux/macOS and Windows.
- Include instructions or examples for using Bash or shell scripting to interact with logs.
- Reference cross-platform log conversion tools (e.g., Python scripts) or provide guidance for using jq or csvkit.
- Mention open-source or cross-platform data visualization tools (e.g., Grafana, Kibana) alongside Excel and Power BI.
- Explicitly state that all steps can be performed on Linux/macOS and provide any necessary platform-specific notes.
Application Gateway
Create Azure Application Gateway custom error pages
...blob/main/articles/application-gateway/custom-error.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration instructions only using Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-friendly alternatives. The PowerShell examples are presented as the sole programmatic method, which may create friction for users on Linux or macOS who typically use Azure CLI or scripting languages other than PowerShell.
Recommendations
- Add equivalent Azure CLI examples for configuring custom error pages at both global and listener levels.
- Explicitly mention that Azure PowerShell is cross-platform, but provide installation and usage notes for Linux/macOS users.
- Include Bash or shell script examples where appropriate.
- Reorder or parallelize example sections so that CLI and PowerShell instructions are presented together, not PowerShell-only.
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 lists Azure PowerShell (a Windows-centric tool) as the only example for creating an autoscaling, zone redundant application gateway. No Linux/macOS CLI or ARM template examples are provided, and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include ARM/Bicep template instructions for infrastructure-as-code parity.
- Ensure that references to PowerShell are accompanied by links or notes about alternative methods for non-Windows users.
- Reorder examples so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell.
Application Gateway
Azure Monitor metrics for Application Gateway
...les/application-gateway/application-gateway-metrics.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Power BI as the primary tool for visualizing Azure activity logs, which is a Windows-centric application. No equivalent Linux/macOS visualization tools (such as Grafana, Kibana, or open-source alternatives) are mentioned. Additionally, Power BI is listed first and exclusively in the 'Next steps' section, reinforcing a Windows-first perspective.
Recommendations
- Include examples and links for visualizing Azure logs and metrics using cross-platform or Linux-native tools such as Grafana, Kibana, or open-source dashboard solutions.
- Mention Azure CLI and Azure Monitor REST API usage for metric retrieval and alert configuration, with example commands for Linux/macOS terminals.
- Add parity in visualization recommendations by listing Power BI alongside alternatives, rather than exclusively.
- Clarify that Power BI is available as a web service, but also highlight its desktop client is Windows-only.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias, primarily by providing only PowerShell examples for enabling diagnostic logging, with no equivalent CLI, Bash, or Linux-native instructions. Windows-centric tools (PowerShell, Visual Studio, Excel) are mentioned for log conversion and analysis, while Linux/macOS alternatives are omitted. The order of presentation also puts Windows/PowerShell methods before more platform-neutral options like the Azure portal.
Recommendations
- Add equivalent Azure CLI and Bash examples for enabling diagnostic logging, suitable for Linux/macOS users.
- Include instructions for log conversion and analysis using Linux/macOS tools (e.g., jq, awk, pandas in Python, LibreOffice Calc).
- Mention cross-platform editors and viewers for JSON/CSV files, not just Excel and Visual Studio.
- Consider presenting platform-neutral methods (Azure portal, REST API, Azure CLI) before platform-specific ones.
- Reference log converter tools or scripts that run on Linux/macOS, or clarify cross-platform compatibility.
Application Gateway
Manage traffic to App Service
...main/articles/application-gateway/configure-web-app.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides extensive step-by-step PowerShell scripts for all configuration and testing tasks, but does not offer any equivalent examples for Linux/macOS users (such as Azure CLI, Bash, or REST API). All automation and scripting guidance is Windows-centric, relying exclusively on PowerShell and Windows-specific tooling. This creates friction for users on Linux or macOS, who must translate PowerShell commands to their platform or use the Azure portal UI.
Recommendations
- Add Azure CLI examples for all configuration steps alongside PowerShell scripts.
- Include Bash or shell script snippets for common tasks, especially for testing and automation.
- Reference cross-platform tools (e.g., curl, az CLI) for testing and verification, not just PowerShell's Invoke-WebRequest.
- Explicitly state that PowerShell examples can be run on Linux/macOS (if true), or provide alternatives.
- Ensure all automation and scripting sections have Linux/macOS parity.
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 notable Windows bias. Troubleshooting steps and examples frequently use Windows-specific tools (PowerShell, certlm.msc, netstat via cmd) and commands, with little or no equivalent Linux/macOS guidance. PowerShell commands are shown for backend health checks and network troubleshooting, and Windows GUI tools are referenced for certificate inspection. Linux alternatives are only briefly mentioned in a few places (e.g., OpenSSL for certificates), and are not provided for most command-line or GUI steps. Windows methods are often described first or exclusively.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows GUI steps (e.g., use Azure CLI, OpenSSL, netstat, and certificate management commands).
- Include Linux/macOS examples for backend health checks, network troubleshooting, and certificate inspection.
- Present cross-platform instructions in parallel, or clearly indicate which steps apply to which OS.
- Reference Azure CLI and REST API usage equally alongside PowerShell, and provide sample outputs for each.
- Avoid assuming Windows as the default environment; clarify when instructions are OS-specific.
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. Both PowerShell options are Windows-centric and are listed immediately after the portal method, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or ARM templates via Bash). The main guide focuses on the portal, which is cross-platform, but the presence and prioritization of PowerShell methods suggest a Windows-first approach and a lack of Linux parity in automation examples.
Recommendations
- Add equivalent instructions for Azure CLI (az network application-gateway probe) to support Linux/macOS users.
- Include ARM template or Bicep examples for probe creation, which are platform-agnostic.
- Reorder entry points so that cross-platform methods (portal, CLI, ARM templates) are listed before Windows-specific PowerShell options.
- Explicitly state that PowerShell examples are primarily for Windows and provide links to Linux/macOS alternatives.
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 alternatives. This creates friction for Linux/macOS users, as PowerShell is traditionally a Windows-centric tool, and the lack of Linux-native examples may hinder adoption or require extra effort to adapt.
Recommendations
- Provide equivalent examples using Bash and/or Python runbooks, which are natively supported in Azure Automation and widely used on Linux/macOS.
- Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Bash) and link to relevant documentation for each.
- List both PowerShell and Linux-native examples side by side, or at least clarify how Linux/macOS users can achieve the same outcome.
- Avoid language that implies PowerShell is the only or preferred method for automation tasks.
Application Gateway
Use with Internal Load Balancer - Azure Application Gateway
...les/application-gateway/application-gateway-ilb-arm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. References to 'Windows PowerShell' and instructions to install the Azure PowerShell module further reinforce a Windows-centric approach. There are no Linux/macOS-specific notes, nor any CLI or Bash examples, making it difficult for users on non-Windows platforms to follow the guide directly.
Recommendations
- Add equivalent Azure CLI (az) commands for each step alongside PowerShell examples.
- Include notes or sections for Linux/macOS users, such as installation instructions for Azure CLI and PowerShell Core.
- Rephrase references to 'Windows PowerShell' to 'PowerShell' or clarify cross-platform compatibility.
- Present CLI/Bash examples before or alongside PowerShell to avoid Windows-first bias.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or PowerShell Core.
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/Linux/macOS alternatives. The PowerShell examples are presented as the only method for updating certificates, and there is no mention of Linux/macOS workflows or parity in command-line instructions. Portal-based instructions are platform-neutral, but the scripting guidance is Windows-centric.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along.
- Explicitly mention that both PowerShell and Azure CLI can be used, and link to CLI documentation.
- Where scripting is required, provide both PowerShell and Bash/CLI snippets side-by-side.
- Review screenshots and instructions to ensure they do not assume Windows-only environments.
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
Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. References to PowerShell are frequent and appear before CLI or REST API, and the main 'Next steps' link directs users to a PowerShell-based configuration guide. There are no explicit Linux/macOS command examples or instructions, and the CLI is mentioned only in passing. This creates friction for Linux/macOS users who may prefer Azure CLI or other cross-platform tools.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all configuration tasks.
- Ensure that Linux/macOS users are given equal prominence in instructions and links.
- Add explicit guidance or links for configuring TLS policy using Azure CLI and REST API.
- Avoid referencing PowerShell as the primary or sole method for viewing or configuring policies.
- Include notes or examples for Linux/macOS environments where relevant.
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 by exclusively providing PowerShell examples and cmdlet references (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) for configuring health probe match criteria, without mentioning or providing equivalent Azure CLI, REST API, or ARM template examples. The 'devx-track-azurepowershell' custom tag and the 'Next steps' section also prioritize PowerShell for automation, suggesting a Windows-centric approach. No Linux/macOS-specific tools or workflows are referenced, and PowerShell is presented as the default automation method.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for probe match criteria configuration.
- Include REST API and ARM template snippets for probe configuration to support cross-platform automation.
- In 'Next steps', mention Azure CLI and other cross-platform options alongside PowerShell.
- Remove or balance the 'devx-track-azurepowershell' tag with 'devx-track-azurecli' if CLI coverage is added.
- Explicitly state that all configuration steps can be performed from Linux/macOS environments using CLI or portal.
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 for troubleshooting Azure Application Gateway 502 errors demonstrates a notable Windows bias. All command-line examples use Azure PowerShell cmdlets, which are most commonly used on Windows and require installation on Linux/macOS. There are no Azure CLI, Bash, or Linux-native tool examples. Troubleshooting steps and references (such as IIS and classic VM endpoints) are Windows-centric, and Windows tools/patterns are mentioned exclusively or before any Linux alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Windows-based web servers.
Recommendations
- Add equivalent Azure CLI (az) commands alongside PowerShell examples for all troubleshooting steps.
- Include Linux-native troubleshooting commands (e.g., curl, dig, netstat) for checking DNS, connectivity, and health probes.
- Reference Linux web servers (e.g., Apache, Nginx) in health probe and SSL certificate sections, not just IIS.
- Explicitly state that PowerShell cmdlets can be run cross-platform, or provide links to installation guides for Linux/macOS.
- Reorder examples so that CLI or platform-neutral solutions are shown first or in parallel with Windows-specific ones.
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 only, with no equivalent example for Azure CLI, Bash, or other Linux/macOS-friendly tools. This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer using the Azure CLI.
Recommendations
- Add equivalent Azure CLI (az) examples for enabling HTTP/2 support and other configuration tasks.
- Where code snippets are provided, show both PowerShell and CLI/Bash alternatives side-by-side.
- Explicitly mention cross-platform options for all configuration steps, especially those currently shown only with Windows-centric tooling.
Application Gateway
Configure an internal load balancer (ILB) endpoint
...configure-application-gateway-with-private-frontend-ip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All virtual machine examples use Windows Server images, and IIS installation is performed exclusively via PowerShell commands. There are no Linux VM examples, nor are there instructions for installing a web server on Linux (such as Apache or Nginx). The use of PowerShell in Azure Cloud Shell is assumed, with no mention of Bash or Linux alternatives. This creates friction for users wishing to deploy Linux-based backend pools.
Recommendations
- Provide parallel Linux VM examples (e.g., Ubuntu) alongside Windows Server.
- Include instructions for installing a web server (such as Apache or Nginx) on Linux VMs, using Bash commands.
- Show how to use Bash in Azure Cloud Shell for Linux VM configuration.
- When presenting code snippets, offer both Windows (PowerShell) and Linux (Bash) alternatives.
- Avoid assuming Windows as the default platform for backend servers.
Application Gateway
Create Azure Application Gateway custom error pages
...blob/main/articles/application-gateway/custom-error.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration instructions exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible tooling. The only code examples are PowerShell scripts, and the 'devx-track-azurepowershell' metadata further signals a Windows-centric approach. There are no Linux or cross-platform command-line examples, nor is it clarified whether the PowerShell commands work on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for both global and listener-level custom error page configuration.
- Explicitly mention cross-platform compatibility of Azure PowerShell (if applicable) or provide Bash/CLI alternatives.
- Reorder or balance example sections so that Linux/macOS-friendly tools (Azure CLI, REST API) are presented alongside or before PowerShell.
- Clarify any platform-specific limitations or prerequisites for the PowerShell commands.
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 references PowerShell and Windows-centric tooling for configuring Application Gateway features (e.g., WAF custom rules, TLS policy configuration) without mentioning or providing equivalent Azure CLI, Bash, or ARM template examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools. No explicit Linux/macOS examples or parity guidance is provided.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell for all configuration tasks, especially for WAF custom rules and TLS policy management.
- Reference ARM template and REST API options where possible for platform-neutral automation.
- Explicitly state that all tasks can be performed using cross-platform tools and link to relevant documentation.
- Reorder examples so that cross-platform (CLI/ARM) options are presented before or alongside PowerShell/Windows-specific instructions.
Application Gateway
Diagnostic logs for Application Gateway for Containers
...cles/application-gateway/for-containers/diagnostics.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides step-by-step instructions for enabling diagnostic logs via the Azure Portal (GUI) and PowerShell, but does not include equivalent examples for Linux/macOS users, such as Azure CLI or Bash scripts. PowerShell is a Windows-centric tool, and its use without alternatives creates friction for non-Windows users. No Linux-native tools or commands are mentioned, and the PowerShell example is presented before any mention of cross-platform options.
Recommendations
- Add Azure CLI examples for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash script samples for log configuration where appropriate.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
- Present Azure CLI or Bash examples before or alongside PowerShell to avoid Windows-first bias.
- Reference Linux/macOS tools for log consumption (e.g., jq, grep) in addition to Excel and Power BI.