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 51-75 of 172 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-portal.md
...in/articles/application-gateway/quick-create-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments. The only virtual machine example provided is Windows Server 2016 Datacenter, with no mention of Linux VM alternatives. The instructions for backend setup and testing exclusively use Windows tools (IIS) and Azure PowerShell, with no Linux equivalent (e.g., Apache/Nginx, Bash/SSH) provided or referenced. The step-by-step VM creation process is Windows-centric, and the installation/testing steps rely on Windows-specific technologies.
Recommendations
- Add parallel instructions for creating and configuring a Linux VM (e.g., Ubuntu) as a backend server.
- Provide Linux-based examples for installing a web server (e.g., Apache or Nginx) and testing connectivity.
- Include Azure CLI and Bash/SSH commands for Linux VM setup and web server installation, alongside PowerShell examples.
- Explicitly mention that Application Gateway supports both Windows and Linux backends, and link to relevant Linux documentation.
- Present Windows and Linux options side-by-side, or alternate which is shown first, to avoid 'windows_first' bias.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/renew-certificates.md
...ain/articles/application-gateway/renew-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, referencing PowerShell-specific patterns (such as SecureString), and omitting any Linux-specific guidance or examples. There are no mentions of Linux tools, shell environments, or platform-specific considerations for certificate file handling or scripting. The CLI example is generic and does not address Linux-specific nuances.
Recommendations
- Add explicit Linux shell (bash) examples for certificate renewal, including file path conventions and password handling.
- Clarify any platform-specific differences in certificate file formats or command usage between Windows and Linux.
- Present Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
- Include troubleshooting tips or notes for Linux users, such as file permissions or environment setup.
- Reference Linux-native tools (e.g., OpenSSL) for certificate management where relevant.
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
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of Azure PowerShell scripts for migration guidance, with no mention of Linux-friendly alternatives such as Azure CLI or Bash scripts. All automation and migration examples reference PowerShell, a Windows-centric tool, and there is no parity for Linux users. Additionally, Windows tools and patterns are mentioned first and exclusively, with no consideration for cross-platform usage.
Recommendations
- Provide equivalent Azure CLI and Bash script examples for migration tasks, especially for retaining public IPs and configuration migration.
- Explicitly mention cross-platform support and clarify which steps can be performed on Linux/macOS systems.
- Add notes or sections for Linux users, including troubleshooting and environment setup guidance.
- Ensure that all PowerShell script references are accompanied by Azure CLI alternatives where possible.
- Review and update documentation to avoid assuming Windows as the default platform for automation.
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 Linux equivalents or Bash/CLI alternatives. The instructions assume a Windows environment (e.g., file paths like c:\appgwcert.pfx) and do not provide guidance for users on Linux or macOS platforms. There are no Azure CLI or Bash script examples, and Windows tools/patterns are mentioned exclusively and first.
Recommendations
- Add equivalent Azure CLI (az) commands for each step, especially for resource creation and configuration.
- Provide instructions and examples for generating self-signed certificates on Linux/macOS (e.g., using openssl).
- Use platform-neutral file paths and note differences for Windows vs. Linux/macOS.
- Include a section or callout for Linux/macOS users, highlighting any required changes or alternative commands.
- Where possible, use cross-platform tools and avoid exclusive reliance on Windows-specific utilities.
- Consider reordering or parallelizing examples so Linux/macOS options are presented alongside Windows/PowerShell.
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
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates some Windows bias. Windows and Windows-specific tools (IIS, PowerShell) are mentioned before or more prominently than Linux equivalents. The Azure PowerShell example is provided in detail, while no Azure CLI (cross-platform) example is given. IIS instructions are listed before Apache/NGINX, and the PowerShell upload sample is provided without a Linux/CLI alternative.
Recommendations
- Add Azure CLI examples for uploading certificates and configuring Application Gateway, alongside PowerShell.
- Present Linux and Windows web server configuration instructions in parallel, or alternate the order to avoid Windows-first bias.
- Include explicit instructions for certificate management on Linux (e.g., how to add a root certificate to Linux trusted store).
- Reference Linux tools and patterns (such as using systemd or Linux file paths) where appropriate.
- Ensure parity in troubleshooting and verification steps for both Windows and Linux environments.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides a link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, but does not mention or link to equivalent instructions for Azure CLI or ARM templates, which are cross-platform. The PowerShell example is highlighted in the 'Next steps' section, potentially signaling Windows-first bias.
Recommendations
- Add links or references to tutorials for creating autoscaling, zone-redundant Application Gateway using Azure CLI and ARM/Bicep templates.
- Ensure that cross-platform tools (Azure CLI, REST API, ARM/Bicep) are mentioned alongside PowerShell in 'Next steps' and throughout the documentation.
- Where PowerShell is referenced, clarify that equivalent functionality is available via CLI and templates, and provide links.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration examples and references primarily using Azure PowerShell, with PowerShell examples shown first and in greater detail. Azure CLI is mentioned, but with less detail and fewer examples. There are no explicit Linux/macOS-specific instructions or examples, and the 'Next steps' section directs users to a PowerShell-focused guide. Portal support is noted as unavailable, but no Linux-specific tools or workflows are highlighted.
Recommendations
- Provide equally detailed Azure CLI examples alongside PowerShell, including step-by-step instructions for all major configuration tasks.
- Add explicit guidance for Linux/macOS users, such as how to prepare certificates using common Linux tools (e.g., OpenSSL), and reference relevant Linux command-line workflows.
- Ensure that CLI examples are not only present but also comprehensive, covering all configuration scenarios addressed in PowerShell.
- In 'Next steps', link to both PowerShell and CLI/Linux-focused guides for mutual authentication configuration.
- Consider including Bicep or ARM template examples, which are platform-neutral, for users who prefer declarative approaches.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent Azure CLI, Bash, or cross-platform instructions. It also references tools like Excel and Visual Studio for log analysis, which are primarily Windows-focused, and does not mention Linux/macOS alternatives. There are no Linux/macOS-specific examples or guidance, which may hinder non-Windows users.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples where appropriate.
- Mention cross-platform tools for log analysis, such as jq, pandas (Python), or open-source log viewers, in addition to Excel and Visual Studio.
- Clarify that PowerShell Core is available cross-platform, if PowerShell must be used, and provide installation guidance.
- Reference Power BI Desktop for macOS (if/when available) or suggest alternative visualization tools for non-Windows users.
Application Gateway
Configure Azure Application Gateway TCP/TLS proxy
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively using a Windows-based SQL Server VM as the backend and referencing SQL Server Management Studio (a Windows-only tool) for client connectivity. No Linux or macOS alternatives are provided for either the backend (e.g., SQL Server on Linux) or client (e.g., sqlcmd, Azure Data Studio, or other cross-platform tools). The instructions and screenshots are Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
- Include instructions for deploying SQL Server on Linux as a backend VM, or clarify that Windows is required if that's the case.
- Provide examples of connecting to the SQL Server via cross-platform tools such as sqlcmd (available on Linux/macOS), Azure Data Studio, or other open-source SQL clients.
- Mention any OS-specific requirements or limitations explicitly, so Linux/macOS users know if Windows is required.
- Add screenshots or command-line examples relevant to Linux/macOS environments where appropriate.
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 is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples and instructions provided exclusively in PowerShell syntax. There is no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The installation and execution instructions assume a Windows/PowerShell environment, and there are no Linux/macOS-specific guidance or parity. This creates friction for users on Linux/macOS who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands and Bash script examples for all migration steps.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports PowerShell and Bash) and provide guidance for Linux/macOS users.
- Add explicit instructions for running migration scripts from Linux/macOS, including prerequisites and troubleshooting.
- Mention and link to any available cross-platform tools or REST API alternatives for migration.
- If PowerShell is required, state this clearly and explain how Linux/macOS users can install and use PowerShell Core.
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 First
Summary
The documentation page for Azure Application Gateway v2 shows moderate Windows bias. Migration guidance and tutorials are centered on Azure PowerShell scripts, with no mention of Azure CLI or ARM templates for Linux/macOS users. The registration/unregistration preview commands are labeled as Azure CLI but use PowerShell cmdlets, which may confuse non-Windows users. Additionally, the 'Next steps' section links only to PowerShell-based tutorials, omitting Linux-friendly alternatives.
Recommendations
- Provide equivalent Azure CLI and/or ARM template examples for migration and deployment tasks.
- Clarify command syntax: If PowerShell is used, label it accurately; if Azure CLI is intended, provide true CLI commands.
- Add links to tutorials or guides that use Azure CLI or portal-based workflows.
- Ensure that Linux/macOS users can follow all critical workflows without requiring PowerShell.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation repeatedly references and recommends an Azure PowerShell script as the primary migration tool, without mentioning Azure CLI, Bash, or Linux/macOS-compatible alternatives. All migration automation examples and scripts are PowerShell-based, and there are no Linux/macOS-specific instructions or parity guidance. This creates friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for migration tasks, or clearly state if such alternatives are unavailable.
- Explicitly mention platform compatibility for the PowerShell script (e.g., if it works with PowerShell Core on Linux/macOS).
- Add guidance for Linux/macOS users on how to run the migration scripts (e.g., using Azure Cloud Shell, which supports PowerShell and Bash).
- If only PowerShell is supported, acknowledge this limitation and provide workarounds or alternatives for non-Windows users.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page includes a 'Next steps' section that links only to an Azure PowerShell tutorial for creating an autoscaling, zone redundant application gateway. No equivalent example or guidance is provided for Linux/macOS users using Azure CLI, which is cross-platform. This creates friction for non-Windows users who may not have access to PowerShell or prefer CLI tools.
Recommendations
- Add links or examples for creating autoscaling, zone redundant application gateways using Azure CLI, which is available on Linux and macOS.
- Ensure that tutorials and walkthroughs cover both PowerShell and CLI approaches, or clarify platform requirements where relevant.
- Consider listing CLI examples before or alongside PowerShell examples to promote parity.
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
Missing Linux Example
Summary
The documentation for Azure Application Gateway v2 shows a notable bias towards Windows/PowerShell tooling. Migration guidance and preview registration/unregistration steps are provided only as Azure PowerShell commands, with no equivalent Azure CLI (bash) or ARM template examples. The main tutorial link also points to a PowerShell-based guide, and there are no Linux/macOS-specific instructions or examples. This creates friction for users on Linux or macOS who prefer or require bash/CLI workflows.
Recommendations
- Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for migration and preview registration/unregistration.
- Include links to tutorials using Azure CLI, ARM templates, or the Azure Portal for cross-platform parity.
- Explicitly state that both PowerShell and CLI can be used, and clarify any platform-specific requirements.
- Add examples or notes for Linux/macOS users where workflows or commands differ.
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
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets, with all migration instructions, examples, and downloadable tools provided exclusively in PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples given. The installation and usage patterns assume a Windows/PowerShell environment, creating friction for users on Linux or macOS who may prefer or require Bash or Azure CLI.
Recommendations
- Provide equivalent Azure CLI scripts and examples for all migration steps, including configuration cloning and public IP retention.
- Add explicit instructions for running PowerShell scripts on Linux/macOS (e.g., using PowerShell Core), including prerequisites and troubleshooting tips.
- Offer Bash script alternatives or at least document how to adapt the PowerShell scripts for Bash/CLI environments.
- Include notes or sections highlighting cross-platform compatibility and any limitations for non-Windows users.
- Present examples for both PowerShell and Azure CLI, and alternate their order or group them together to avoid 'windows_first' bias.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration instructions for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell examples and references. PowerShell instructions are presented first and in greater detail than Azure CLI, and the 'Next steps' section directs users to a PowerShell-specific guide. There is no mention of Linux/macOS-specific tools or workflows, and the CLI example is minimal compared to PowerShell. No Linux or macOS certificate management tools (e.g., OpenSSL) are referenced for extracting or preparing certificates.
Recommendations
- Provide equally detailed Azure CLI examples alongside PowerShell, including step-by-step instructions for all major configuration tasks.
- Include references or examples using cross-platform tools (such as OpenSSL) for certificate extraction and management.
- In 'Next steps', offer links to CLI and ARM template/Bicep guides, not just PowerShell.
- Explicitly mention that both PowerShell and CLI are cross-platform, and clarify any platform-specific limitations if present.
- Ensure that instructions for certificate file preparation (PEM/CER) include Linux/macOS workflows.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation repeatedly references an Azure PowerShell script as the primary or sole migration tool for Application Gateway V1 to V2, without mention of Azure CLI, Bash, or cross-platform alternatives. All migration automation examples and scripts are PowerShell-based, and there are no Linux/macOS-specific instructions or parity guidance. This creates friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration steps, or explicitly state if CLI support is unavailable.
- Include Bash or cross-platform script examples where possible, or clarify PowerShell Core compatibility on Linux/macOS.
- Add a section outlining migration options for Linux/macOS users, including prerequisites for running PowerShell scripts cross-platform.
- If PowerShell is required, link to documentation on installing and using PowerShell Core on Linux/macOS.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides a 'Next steps' link that exclusively references Azure PowerShell for creating an autoscaling, zone redundant application gateway, without mentioning or linking to equivalent Azure CLI or ARM template instructions. This prioritizes Windows/PowerShell tooling and may create friction for Linux/macOS users who typically use Azure CLI or other cross-platform tools.
Recommendations
- Add links or examples for creating autoscaling, zone redundant Application Gateway v2 using Azure CLI and ARM templates.
- Present cross-platform instructions (Azure CLI, ARM/Bicep) alongside PowerShell examples in the 'Next steps' section.
- Explicitly state that Azure PowerShell is not required and that equivalent functionality is available via CLI and templates.
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
Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 demonstrates a moderate Windows/PowerShell bias. Key migration and registration/unregistration steps are provided only using Azure PowerShell commands, with no equivalent Azure CLI (bash) or REST API examples. The migration script is referenced as a PowerShell Gallery resource, and the main tutorial link is for PowerShell. There is no mention of Linux/macOS-friendly alternatives or parity in examples, which may create friction for users on non-Windows platforms.
Recommendations
- Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for registration, unregistration, and migration steps.
- Reference cross-platform scripts or tools (e.g., Azure CLI, REST API, ARM templates) alongside PowerShell resources.
- Ensure tutorial links include both PowerShell and Azure CLI options, or clarify platform compatibility.
- Explicitly state that all management operations can be performed from Linux/macOS using Azure CLI or portal, where applicable.
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 is heavily focused on Azure PowerShell scripts for migration, with all examples, instructions, and downloadable tools provided in PowerShell format. There are no Bash, Azure CLI, or Linux/macOS shell equivalents, nor any guidance for users who do not use PowerShell. The instructions assume the use of PowerShell modules and cmdlets, which are most commonly used on Windows, and do not mention cross-platform alternatives or considerations for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all major migration steps, including configuration cloning and IP retention.
- Include example workflows for Bash or shell environments, especially for Linux/macOS users.
- Explicitly state whether the provided PowerShell scripts can be run in Azure Cloud Shell (which supports PowerShell and Bash) and clarify any OS-specific limitations.
- Add notes or links to cross-platform installation instructions for Azure PowerShell modules and scripts.
- Consider offering downloadable scripts or templates in other languages (e.g., Python, Bash) if PowerShell is not strictly required.
- Reorder examples or add parallel examples so Linux/macOS users are not required to adapt Windows-centric instructions.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides configuration instructions and examples for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell. PowerShell examples are given in detail, with CLI examples present but less comprehensive. The 'Next steps' section directs users specifically to a PowerShell-based guide, and there is no mention of Linux/macOS-specific tools or workflows. Portal support is noted as unavailable, but Linux users are expected to use Azure CLI, which is referenced but not explained in depth. There are no Linux/macOS-specific certificate management or extraction examples, nor are cross-platform considerations discussed.
Recommendations
- Provide equally detailed Azure CLI examples alongside PowerShell, especially for critical configuration steps.
- Include links to Linux/macOS certificate management workflows, such as using OpenSSL for certificate extraction and chain management.
- In 'Next steps', offer parallel guides for Azure CLI and ARM/Bicep templates, not just PowerShell.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes or examples for certificate file handling on Linux/macOS (e.g., file formats, permissions, OpenSSL commands).
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, including configuration migration and public IP retention. There is no mention of Azure CLI, Bash, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples provided. This creates friction for users who do not use Windows or PowerShell.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration steps, especially for configuration migration and public IP retention.
- Explicitly state whether the PowerShell scripts can be run on PowerShell Core (cross-platform) or if they are Windows-only.
- Include Bash or shell script examples where relevant, or clarify if only PowerShell is supported.
- Add a section addressing migration for Linux/macOS users, including any limitations or workarounds.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides a link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, without mentioning or linking to equivalent instructions for Linux/macOS users (such as Azure CLI or ARM templates). This prioritizes Windows/PowerShell tooling and may create friction for users on other platforms.
Recommendations
- Add links or sections for creating autoscaling, zone-redundant Application Gateway using Azure CLI and ARM templates.
- Ensure that examples and tutorials are provided for both Windows (PowerShell) and cross-platform tools (CLI, REST API).
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or clarify cross-platform options.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation repeatedly references and recommends an Azure PowerShell script for migration from Application Gateway V1 to V2, without mentioning Azure CLI or Bash alternatives. There are no Linux/macOS-specific instructions or examples, and the only automation tool referenced is PowerShell, which is more familiar to Windows users. This may create friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration tasks, or clarify if such tools are not available.
- Explicitly state whether the PowerShell script can be run cross-platform (e.g., using PowerShell Core on Linux/macOS) and provide installation guidance if so.
- Add Bash or shell script examples where appropriate, or link to cross-platform migration tooling if available.
- Mention any limitations or requirements for non-Windows users when using the provided PowerShell scripts.
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
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tools, such as the use of PowerShell cmdlets and the New-SelfSignedCertificate/Export-PfxCertificate commands, which are only available on Windows. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or OpenSSL for certificate creation. This creates friction for non-Windows users attempting to follow the tutorial.
Recommendations
- Provide equivalent Azure CLI commands for all steps, especially for resource creation and management.
- For certificate creation, include OpenSSL-based instructions for Linux/macOS users alongside the PowerShell examples.
- Clarify in the prerequisites that the tutorial is PowerShell-focused, and link to any available Azure CLI or cross-platform tutorials.
- Where possible, use cross-platform tools and commands, or clearly indicate which steps are Windows-only and provide alternatives.