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 626-650 of 981 flagged pages
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 First
Missing Linux Example
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tools, such as New-SelfSignedCertificate and Export-PfxCertificate, with all examples and instructions provided in PowerShell. There are no Linux/macOS equivalents or CLI alternatives given, and Windows patterns (e.g., certificate creation, file paths) are used throughout. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-only cmdlets.
Recommendations
- Provide Azure CLI examples alongside PowerShell for each step, as Azure CLI is cross-platform.
- Offer Linux/macOS-compatible instructions for creating self-signed certificates (e.g., using OpenSSL).
- Use generic file paths or note differences for Linux/macOS users.
- Explicitly mention that PowerShell Core is available cross-platform, and clarify which steps require Windows-only tools.
- Link to relevant Linux/macOS documentation for certificate management and Azure resource creation.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation consistently references Azure PowerShell scripts as the primary or sole migration tooling, with no 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, especially for configuration and public IP retention.
- Explicitly state whether the PowerShell scripts can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation guidance if so.
- Include Bash or shell script examples where possible, or link to community-supported alternatives.
- Clarify any limitations or requirements for non-Windows users in the migration process.
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 and examples for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell. PowerShell examples are given first and in more detail, while Azure CLI examples are present but less comprehensive. There is no mention of Linux-specific tools or workflows, and the 'Next steps' section directs users to a PowerShell-focused guide, omitting Linux or macOS parity. This creates friction for Linux/macOS users who may prefer CLI or ARM/Bicep templates.
Recommendations
- Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including step-by-step instructions.
- Provide ARM template and Bicep configuration examples for mutual authentication, as these are cross-platform.
- Include explicit guidance for Linux/macOS users, such as using Azure CLI or REST API, and link to relevant documentation.
- In 'Next steps', offer links to both PowerShell and CLI/ARM/Bicep guides, not just PowerShell.
- When referencing certificate extraction or management, mention cross-platform tools (e.g., OpenSSL) and provide examples for Linux/macOS.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides a detailed PowerShell example for enabling diagnostic logging, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The PowerShell method is presented before portal-based instructions, and no mention is made of Azure CLI or other cross-platform tools. This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-agnostic solutions.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used by Linux/macOS users.
- Present CLI/Bash examples alongside PowerShell, or before PowerShell, to ensure parity and inclusivity.
- Explicitly mention that PowerShell is Windows-centric and provide guidance for Linux/macOS users.
- Include references to relevant tools or scripts for Linux/macOS environments, such as Bash or Python.
- Where possible, use generic REST API examples or links to Azure REST documentation.
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 in the 'Next steps' section to a tutorial for creating an autoscaling, zone redundant application gateway using Azure PowerShell, which is a Windows-centric tool. There are no equivalent examples or links for Linux/macOS users (e.g., Azure CLI or ARM templates), and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
- Add links or examples for creating autoscaling, zone redundant application gateways using Azure CLI, which is cross-platform.
- Include ARM/Bicep template examples for infrastructure-as-code parity.
- In 'Next steps', ensure that PowerShell tutorials are accompanied by CLI or template-based alternatives, or clearly indicate platform applicability.
- Consider a brief note clarifying that PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway configuration concepts. However, in the troubleshooting section for Dedicated Backend Connections, Windows-specific tools and patterns are referenced (Kerberos documentation and Windows Authentication configuration in IIS), and Windows terminology (Service Principal Name, NTLM, Kerberos) is used without mentioning Linux equivalents or alternatives. Additionally, Windows authentication is discussed before any mention of non-Windows authentication methods, creating a 'windows_first' bias.
Recommendations
- Add guidance or links for troubleshooting authentication issues on Linux-based backend servers (e.g., using Apache, NGINX, or Samba for Kerberos/NTLM).
- Include references to Linux authentication documentation or tools where relevant, such as mod_auth_kerb for Apache or sssd for Kerberos.
- Clarify that NTLM and Kerberos are cross-platform protocols and provide examples or troubleshooting steps for Linux environments.
- When referencing backend server logs, mention both Windows (IIS) and Linux (Apache/Nginx) log locations and formats.
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
Windows Tools
Summary
The documentation exclusively demonstrates the configuration using a Windows-based SQL Server VM and recommends SQL Server Management Studio (SSMS) as the client tool, which is Windows-only. There are no examples or guidance for Linux-based SQL Server VMs or Linux/macOS-compatible SQL client tools. The Windows VM and SSMS are mentioned first and exclusively, creating friction for Linux/macOS users who wish to follow the guide.
Recommendations
- Add instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu with SQL Server 2019/2022).
- Include examples of connecting to the SQL Server via cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible SQL clients.
- Clarify that the Application Gateway TCP/TLS proxy feature is not limited to Windows SQL Server backends and can be used with Linux-based SQL Server instances.
- Provide screenshots or command-line examples relevant to Linux/macOS environments where possible.
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 migration scripts, examples, and installation instructions centered around PowerShell. There are no CLI (az), Bash, or Linux-native examples or alternatives provided, and the use of PowerShell Gallery and PowerShell modules is assumed throughout. This creates friction for Linux/macOS users who may prefer or require Bash, Azure CLI, or other cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, or clarify if PowerShell is required for specific operations.
- Include Bash or shell script examples for common tasks, such as retrieving resource IDs, uploading certificates, and running migration scripts.
- Document how to run PowerShell scripts on Linux/macOS (e.g., using PowerShell Core), and note any platform-specific limitations or requirements.
- If migration scripts are only available in PowerShell, explicitly state this and provide guidance for Linux/macOS users on installing and using PowerShell Core.
- Consider offering downloadable scripts in other languages (e.g., Python, Bash) or providing REST API equivalents for advanced users.
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 exhibits moderate Windows bias. Migration instructions and registration/unregistration steps are provided exclusively using Azure PowerShell commands, with no equivalent Bash or Linux CLI examples. Additionally, the 'Next steps' section links to a tutorial that is PowerShell-focused, suggesting Windows as the primary platform for operational tasks. Azure CLI is referenced, but the commands shown are PowerShell cmdlets, not cross-platform Bash CLI commands.
Recommendations
- Provide equivalent Azure CLI (bash) examples for registration, unregistration, and migration tasks alongside PowerShell examples.
- Ensure tutorials and linked guides include both PowerShell and Azure CLI/Bash instructions.
- Clarify that Azure CLI commands can be run on Linux/macOS and provide explicit examples for those platforms.
- Review linked migration scripts and ensure Linux/macOS users are supported or alternative instructions are given.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, such as configuration migration and public IP retention. There are no examples or guidance for users who may prefer or require Azure CLI, Bash, or other cross-platform tools. The exclusive mention of PowerShell (a tool with strong Windows associations, despite cross-platform support) and lack of Linux/macOS-specific migration guidance creates friction for non-Windows users.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for all migration steps currently covered by PowerShell scripts.
- Explicitly state whether the PowerShell scripts are supported and tested on Linux/macOS (PowerShell Core), and provide troubleshooting tips if there are known issues.
- Add Bash or shell script examples for common migration tasks, or link to cross-platform tooling where available.
- Reorder sections or add callouts to clarify that migration can be performed from any OS, not just Windows, if that is the case.
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 primarily references Azure PowerShell for creating autoscaling, zone-redundant Application Gateway v2 resources. No Linux/macOS CLI examples or tools (such as Azure CLI or ARM templates) are mentioned, and the only 'Next steps' tutorial is PowerShell-focused, which may create friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI examples and tutorials for autoscaling and zone-redundant Application Gateway v2.
- Mention ARM template or Bicep options for cross-platform resource deployment.
- Ensure 'Next steps' links include both PowerShell and CLI-based guides, or clearly indicate platform requirements.
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 exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Linux/macOS alternatives or Azure CLI. All code examples and instructions assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI examples throughout the tutorial for cross-platform compatibility.
- Offer instructions for creating self-signed certificates using OpenSSL (commonly available on Linux/macOS) alongside the Windows PowerShell method.
- Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
- Add a note in the prerequisites section indicating that the tutorial is PowerShell-centric and suggest Azure CLI documentation for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI or Bash example for Linux/macOS users. The PowerShell method is presented before the Azure portal method, and there is no mention of Azure CLI or ARM template approaches. Additionally, references to log conversion tools are tied to Visual Studio and C#, which are Windows-centric, with no alternatives for Linux/macOS users.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as CLI is cross-platform and widely used by Linux/macOS users.
- Include Bash or shell script snippets where appropriate, or reference ARM template methods for automation.
- Mention or link to log conversion tools that work on Linux/macOS, such as Python scripts or open-source alternatives.
- Present portal-based instructions first or equally, as they are platform-agnostic.
- Explicitly state that PowerShell examples are for Windows users and provide parity for other platforms.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions throughout, but PowerShell is featured heavily and often shown immediately after Azure CLI. Windows-specific tools (winget) are mentioned for Helm installation, while Linux instructions are less prominent and lack detail. There are no Bash-only or Linux-native examples for Azure resource management; all resource provisioning is via Azure CLI (cross-platform) or PowerShell (Windows-centric). The Helm install section for Linux is brief, and Windows installation is described first. No macOS-specific instructions are given.
Recommendations
- Provide Bash-native examples for Azure CLI steps, highlighting cross-platform compatibility.
- List Linux installation instructions for Helm before Windows instructions, or group them equally.
- Include macOS installation instructions for Helm and clarify Azure CLI usage on macOS.
- Add explicit notes that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider including a table or section summarizing tool compatibility across OSes.
- Where PowerShell is used, clarify that Azure CLI is recommended for Linux/macOS 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
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. It exclusively uses a Windows-based SQL Server VM as the backend example, references Windows Server images, and instructs users to connect using SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for deploying a Linux-based SQL Server VM, nor for connecting from Linux/macOS clients (e.g., using Azure Data Studio, sqlcmd, or other cross-platform tools). This may create friction for users who prefer or require Linux environments.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative backend.
- Provide connection examples using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI clients available on Linux/macOS.
- Clarify that the backend can be any SQL Server VM (Windows or Linux), and highlight any differences in configuration steps.
- Add screenshots or CLI commands 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
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and downloadable scripts provided in PowerShell syntax. There is no mention of Bash, Azure CLI, or Linux/macOS-specific workflows, nor are there alternative instructions for users who do not use PowerShell. The guidance assumes the reader is using PowerShell, which is most commonly associated with Windows environments, and does not address how to perform the migration from Linux or macOS systems.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration and traffic migration.
- Include explicit instructions or examples for running migration tasks from Linux/macOS environments, such as using Azure Cloud Shell (Bash) or local Azure CLI.
- Clarify whether the PowerShell scripts can be run cross-platform (e.g., via PowerShell Core on Linux/macOS) and provide installation guidance for non-Windows users.
- Add a section comparing PowerShell and Azure CLI approaches, and recommend the most cross-platform method for users.
- Where possible, offer downloadable Bash scripts or templates for common migration scenarios.
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 and code samples for both Azure PowerShell and Azure CLI, but PowerShell is consistently presented first, and the 'Next steps' section links only to a PowerShell-based guide. There are no explicit Linux/macOS-specific examples or guidance, and the CLI section is less detailed than the PowerShell section. This may create friction for Linux/macOS users who prefer or require CLI or ARM/Bicep approaches.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Expand the Azure CLI section to match the detail and step-by-step guidance provided in the PowerShell section.
- Include a 'Next steps' link to a CLI-based mutual authentication configuration guide, or provide parity in walkthroughs for both PowerShell and CLI.
- Explicitly mention that all configuration steps can be performed from Linux/macOS using Azure CLI, and provide any relevant platform-specific notes if needed.
- Consider adding ARM/Bicep template examples for users who prefer declarative infrastructure as code approaches, which are platform-agnostic.
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 (and seemingly only) migration tool, without mentioning Azure CLI, Bash, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the term 'PowerShell script' is used exclusively, which may cause confusion or friction for users on non-Windows platforms.
Recommendations
- Explicitly state whether the PowerShell migration script is supported on PowerShell Core (pwsh) for Linux/macOS, and provide installation guidance if so.
- If available, provide equivalent Azure CLI commands or scripts for migration, or clarify if only PowerShell is supported.
- Add examples or notes for Linux/macOS users, such as how to run the PowerShell script on their platforms.
- Mention any prerequisites or platform-specific considerations for running the migration script on non-Windows systems.
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 instructions and tutorials are PowerShell-centric, with no Linux/bash equivalents provided. Azure CLI commands are shown, but the registration/unregistration examples use PowerShell context-setting commands. The 'Next steps' section links to a PowerShell tutorial as the primary onboarding path. There are no explicit Linux/macOS examples or references to bash or cross-platform scripting.
Recommendations
- Provide equivalent bash/Azure CLI examples for migration and onboarding tasks, especially for Linux/macOS users.
- Add links to tutorials using Azure CLI or ARM templates for Application Gateway v2 creation and migration.
- Clarify which commands are cross-platform and which are Windows-specific, and offer alternatives where possible.
- In 'Next steps', include links to Linux/macOS-friendly guides or CLI-based tutorials alongside PowerShell options.
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 for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell examples and references. PowerShell instructions 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-specific tools or workflows (e.g., Bash scripting, OpenSSL usage for certificate extraction, or Linux-based automation). This creates friction for Linux/macOS users who may prefer Bash/CLI or require platform-agnostic guidance.
Recommendations
- Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including step-by-step instructions for all major configuration tasks.
- Add Linux/macOS-specific guidance for certificate extraction and management, such as using OpenSSL commands.
- Provide parity in 'Next steps' by linking to CLI/Bash-based configuration guides alongside PowerShell guides.
- Clarify that both PowerShell and CLI are cross-platform, and highlight any platform-specific limitations if present.
- Consider including example workflows for certificate management and upload using Bash or Linux-native tools.
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 primarily references Azure PowerShell for creating autoscaling, zone-redundant Application Gateway v2 instances, with no mention of Azure CLI or ARM template equivalents. The 'Next steps' section links only to a PowerShell tutorial, which may create friction for Linux/macOS users who typically use Azure CLI or other tools.
Recommendations
- Add equivalent Azure CLI and ARM template examples and tutorials for creating autoscaling, zone-redundant Application Gateway v2.
- In the 'Next steps' section, provide links to both PowerShell and CLI/ARM template guides, or clarify that PowerShell is not required.
- Ensure that all procedural instructions are platform-neutral or include cross-platform options.
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 ARM template example. The only programmatic example is Windows-centric, and there is a reference to using Visual Studio and a .NET-based log converter tool, which are also Windows-focused. There are no Linux/macOS-specific instructions or parity in scripting examples.
Recommendations
- Add equivalent 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 and link to cross-platform log conversion tools (e.g., Python-based or jq for JSON processing) instead of only Visual Studio/.NET tools.
- Reorder or supplement sections so that cross-platform methods (Azure portal, Azure CLI) are presented before or alongside PowerShell.
- Explicitly state that PowerShell Core is available cross-platform if retaining PowerShell examples, and provide installation guidance if relevant.
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
Windows Tools
Summary
The documentation exclusively uses Windows-based SQL Server VM and SQL Server Management Studio (SSMS) for client connectivity. There are no examples or guidance for Linux-based SQL Server VMs or Linux/macOS client tools. Windows options are mentioned first and solely, creating friction for Linux/macOS users who wish to test or deploy the TCP/TLS proxy feature.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu with SQL Server 2019/2022).
- Provide examples of connecting to the Application Gateway using cross-platform SQL clients such as Azure Data Studio, sqlcmd, or other CLI tools available on Linux/macOS.
- Mention Linux-compatible SQL Server images in the VM creation step, or clarify that Linux is supported if applicable.
- Add notes or links for Linux/macOS users about alternative client tools and any relevant configuration differences.
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, installation instructions, and script usage exclusively referencing PowerShell. There are no CLI (az), Bash, or Linux/macOS shell examples or guidance. Script installation and execution instructions assume a Windows/PowerShell environment, and PowerShell Gallery is referenced as the primary distribution method. The documentation does not mention or provide alternatives for Linux/macOS users, nor does it clarify whether the scripts are cross-platform compatible.
Recommendations
- Add Azure CLI (az) equivalents for key migration steps, or clarify if migration is only possible via PowerShell.
- Explicitly state PowerShell cross-platform support (if available), and provide instructions for running scripts on Linux/macOS (e.g., using PowerShell Core).
- Include Bash or shell script alternatives, or at least note limitations for Linux/macOS users.
- Mention prerequisites for Linux/macOS environments (e.g., PowerShell Core installation, compatibility notes).
- Provide guidance for users who prefer Azure Cloud Shell (which supports PowerShell and Bash), and clarify which script methods are supported there.
- Consider reordering or balancing examples so that Windows and Linux/macOS users are equally addressed.
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 notable bias towards Windows/PowerShell tooling. Azure PowerShell is referenced as the primary method for migration and for registering/unregistering the Basic SKU preview, with no equivalent Azure CLI (bash), ARM template, or Terraform examples. The 'Next steps' section also links to a PowerShell-based tutorial first. This creates friction for Linux/macOS users who may prefer cross-platform tools.
Recommendations
- Provide Azure CLI (bash) equivalents for all PowerShell commands and scripts, especially for migration and feature registration/unregistration.
- Include ARM template and/or Terraform examples for common deployment and migration scenarios.
- When listing tutorials or next steps, offer both PowerShell and CLI/ARM/other cross-platform options, or clarify which tools are supported.
- Explicitly state if certain operations are only possible with PowerShell, and provide guidance for non-Windows users (e.g., using Azure Cloud Shell).