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 576-600 of 981 flagged pages
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 demonstrates notable Windows bias. The SQL Server VM is created using a Windows Server image, and the only SQL client example provided is SQL Server Management Studio (SSMS), a Windows-only tool. There are no instructions or examples for Linux-based SQL Server VMs or for connecting from Linux/macOS clients (e.g., sqlcmd, Azure Data Studio). The documentation assumes Windows environments throughout, creating friction for Linux/macOS users.
Recommendations
- Provide instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu with SQL Server 2022).
- Include examples for connecting to the SQL Server via cross-platform tools such as sqlcmd or Azure Data Studio.
- Mention Linux/macOS alternatives for SQL client connectivity and clarify any differences in configuration.
- Add screenshots or CLI steps relevant to Linux environments where appropriate.
Create Pull Request
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page is generally platform-neutral in its conceptual explanation of TLS on Azure Application Gateway. However, the 'Next steps' section directs users specifically to a PowerShell-based configuration guide, implying Windows as the primary platform for hands-on tasks. There is no mention of Linux/macOS CLI or Azure Portal equivalents in the 'Next steps', and PowerShell is referenced before any cross-platform alternatives.
Recommendations
- Add links to equivalent configuration guides using Azure CLI (which is cross-platform) and Azure Portal UI.
- Mention that PowerShell is available on Linux/macOS, but also provide Azure CLI examples for Linux users.
- In 'Next steps', list cross-platform options (Azure CLI, Portal) before or alongside PowerShell.
- Ensure that any referenced tools or commands are not Windows-exclusive, or provide Linux/macOS alternatives.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) for all steps, including certificate creation. No Bash, Azure CLI, or Linux/macOS-compatible instructions are provided. The prerequisites and all examples assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all steps, especially resource creation and configuration.
- For certificate creation, include Linux/macOS-compatible commands (e.g., using OpenSSL) alongside PowerShell examples.
- Clarify that Azure PowerShell can be used cross-platform, but highlight any Windows-only steps and offer alternatives.
- Add notes or sections for Linux/macOS users, including how to install Azure PowerShell or Azure CLI on their platforms.
- Consider reordering examples so that cross-platform tools (Azure CLI, OpenSSL) are shown first or alongside PowerShell.
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page on enabling end-to-end TLS for Azure Application Gateway is generally platform-neutral in its conceptual explanations. However, there are notable signs of Windows/PowerShell bias: (1) PowerShell is the only automation/configuration tool explicitly referenced for configuring SNI, and the only 'Next steps' link is to a PowerShell-based guide; (2) The only API reference for certificate format support is to a Windows-specific function (PFXImportCertStore); (3) ARM templates are mentioned, but only after PowerShell, and no Linux/macOS CLI (e.g., Azure CLI, Bash) or portal-based workflows are highlighted; (4) There are no Linux/macOS-specific examples or parity guidance.
Recommendations
- Add Azure CLI (cross-platform) examples and references for configuring Application Gateway TLS/SNI settings, alongside or before PowerShell.
- Provide links to documentation for configuring end-to-end TLS using the Azure Portal and/or ARM/Bicep templates, not just PowerShell.
- Reference platform-agnostic certificate handling guidance (e.g., OpenSSL commands for creating/managing PFX files) rather than only linking to Windows API documentation.
- Ensure that 'Next steps' includes links to Linux/macOS-friendly guides (e.g., Azure CLI, Portal) and not just PowerShell.
- Clarify that all configuration steps can be performed from any OS using Azure CLI or Portal, where applicable.
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 viewing logs in Excel and Visual Studio-based log converter tools, which are primarily Windows-centric. There are no Linux/macOS-specific or cross-platform alternatives provided for these tasks.
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 viewing and converting logs, such as jq for JSON processing, csvkit for CSV conversion, or Python scripts.
- Reference open-source or platform-agnostic log analysis tools in addition to Excel and Visual Studio.
- Clearly indicate when a tool or workflow is Windows-only and provide alternatives for Linux/macOS users.
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, but there are subtle signs of Windows bias. References to troubleshooting NTLM and Kerberos authentication link to Windows and IIS documentation, and Windows Authentication configuration is mentioned in the context of backend troubleshooting. Additionally, Windows tools and terminology (e.g., Service Principal Name, IIS, Windows Authentication) are referenced before any Linux equivalents, with no mention of Linux authentication mechanisms or troubleshooting guidance for Linux-based backends.
Recommendations
- Add troubleshooting guidance and documentation links for Linux-based authentication mechanisms (such as SPNEGO, mod_auth_kerb, or Samba for NTLM/Kerberos).
- Include examples or references for configuring backend authentication on popular Linux web servers (e.g., Apache, Nginx) alongside IIS/Windows examples.
- When discussing backend logs and authentication, mention both Windows and Linux approaches, and provide links to relevant Linux documentation.
- Ensure that terminology and guidance are inclusive of both Windows and Linux backend environments.
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), a Windows-only tool, for client connectivity. There are no examples or guidance for Linux-based SQL Server VMs, nor are cross-platform SQL client tools mentioned. The instructions and screenshots focus solely on Windows environments, potentially creating friction for Linux/macOS users.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative backend.
- Mention and provide examples for connecting to SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux-compatible SQL clients.
- Clarify that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends, if applicable.
- Add screenshots or text-based examples for Linux/macOS users where relevant.
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 for both Azure PowerShell and Azure CLI, but PowerShell is presented first and in more detail, with CLI examples being less comprehensive. The 'Next steps' section only links to a PowerShell-based guide, and there is no mention of Linux/macOS-specific tools or workflows. There are no explicit Linux/macOS command-line examples (e.g., using OpenSSL for certificate extraction), and the documentation assumes familiarity with PowerShell, which is more common on Windows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Include Linux/macOS-friendly instructions for certificate extraction and management (e.g., using OpenSSL commands).
- Provide 'Next steps' links to Azure CLI and ARM/Bicep template guides, not just PowerShell.
- Clarify that all configuration steps can be performed on Linux/macOS using Azure CLI or REST API.
- Where possible, add screenshots or instructions for cross-platform tools (e.g., Visual Studio Code, Azure Cloud Shell) rather than assuming a Windows environment.
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 page is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and tooling based on PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell equivalents provided. The guidance assumes the user is using PowerShell locally or in Azure Cloud Shell, and all script downloads are from the PowerShell Gallery. This creates friction for Linux/macOS users who may prefer Bash or Azure CLI, and may not have PowerShell installed or be familiar with its syntax.
Recommendations
- Provide Azure CLI (az) equivalents for all migration steps, including resource ID retrieval, certificate management, and gateway creation.
- Add Bash script examples for downloading and running migration scripts, or clarify if the scripts are cross-platform (PowerShell Core) and can be run on Linux/macOS.
- Explicitly mention PowerShell Core compatibility and provide installation instructions for Linux/macOS if PowerShell is required.
- Include guidance for using Azure Cloud Shell (Bash) and Azure CLI for users who do not want to use PowerShell.
- Add a section comparing PowerShell and Azure CLI approaches, and link to Azure CLI documentation for Application Gateway management.
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 evidence of Windows bias. The migration section references an Azure PowerShell script as the primary migration tool, and the registration/unregistration steps for the Basic SKU preview use Azure CLI commands that are presented in a PowerShell-like syntax (e.g., Set-AzContext). Additionally, the 'Next steps' section links to a tutorial that is PowerShell-focused. There are no explicit Linux/bash examples or references to Linux-native tools, and Windows/PowerShell patterns are mentioned first and exclusively.
Recommendations
- Provide equivalent bash/Linux shell examples for Azure CLI commands, as Azure CLI is cross-platform.
- Mention that Azure CLI commands can be run in bash or other shells, not just PowerShell.
- Offer migration guidance using Azure CLI or ARM templates, not only PowerShell scripts.
- Ensure tutorials and 'Next steps' include Linux/macOS-friendly instructions and links.
- Clarify that Azure CLI is available on Linux/macOS and provide links to installation guides for those platforms.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation repeatedly references and relies on Azure PowerShell scripts for migration tasks, such as configuration migration and public IP retention. There are no examples or guidance for users who prefer or require Azure CLI, ARM templates, or other cross-platform tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Provide equivalent Azure CLI commands or scripts for migration tasks, especially for configuration migration 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 ARM/Bicep template examples or REST API alternatives for users who prefer infrastructure-as-code or scripting.
- Add a note clarifying tool requirements and offering alternatives for non-Windows users.
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 example for Azure CLI, Bash, or other cross-platform tools. The only command-line automation guidance is Windows-centric, and there is no mention of Linux/macOS-friendly alternatives. Additionally, the log conversion tool referenced is a C#/.NET-based solution, which is more familiar to Windows users.
Recommendations
- Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but clarify if the example requires Windows PowerShell or works on all platforms.
- Provide example scripts or commands for downloading and converting logs using common Linux/macOS tools (e.g., jq for JSON parsing, csvkit for CSV conversion).
- Reference or link to log conversion tools or scripts that do not require Visual Studio or C#/.NET, or provide instructions for using open-source, platform-agnostic alternatives.
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 deploying a SQL Server VM using Windows Server and connecting via SQL Server Management Studio (SSMS), which is a Windows-only tool. There are no examples or guidance for Linux-based SQL Server VMs, nor for connecting from Linux/macOS clients. The instructions and screenshots focus solely on Windows environments, creating friction for Linux users.
Recommendations
- Add instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) in Azure, including relevant screenshots and settings.
- Provide examples for connecting to the SQL Server backend using cross-platform SQL clients (such as Azure Data Studio, sqlcmd, or DBeaver) that work on Linux/macOS.
- Explicitly mention that SQL Server can be deployed on Linux and provide links to relevant documentation.
- Where possible, clarify that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends.
- Include troubleshooting tips or notes relevant to Linux-based SQL Server deployments.
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 using PowerShell syntax. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions provided. The guidance assumes the reader is using PowerShell (locally or via Azure Cloud Shell), and script installation and usage steps are PowerShell-centric. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for configuration and traffic migration, or explicitly state if PowerShell is required.
- Add Bash script examples or instructions for Linux/macOS users, especially for certificate handling and resource management.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports both Bash and PowerShell), and provide guidance for Bash users.
- Include a section comparing PowerShell and Azure CLI approaches, and link to Azure CLI documentation where relevant.
- Mention prerequisites for Linux/macOS users (e.g., installing PowerShell Core, if required), and provide installation guidance.
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 for Azure PowerShell first, with more detailed PowerShell guidance and command breakdowns than for Azure CLI. Azure CLI is included, but with less detail and no Linux/macOS-specific guidance. There are no explicit Linux/macOS shell examples for certificate extraction or management, and the 'Next steps' section directs users to a PowerShell-focused guide, omitting Linux-first or cross-platform alternatives.
Recommendations
- Provide equal depth of examples for Azure CLI as for PowerShell, including step-by-step breakdowns.
- Include Linux/macOS shell commands (e.g., OpenSSL) for certificate extraction, chain creation, and file management where relevant.
- In 'Next steps', link to both PowerShell and Azure CLI guides, or a cross-platform guide, not just PowerShell.
- Explicitly mention that all Azure CLI commands can be run on Linux/macOS, and provide troubleshooting or environment notes for non-Windows users.
- Where PowerShell is referenced, clarify if Azure Cloud Shell can be used cross-platform, or suggest alternatives for Linux/macOS 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 Tools
Windows First
Summary
The documentation page for Azure Application Gateway v2 shows evidence of Windows bias. The migration section references an Azure PowerShell script as the primary migration tool, and the registration/unregistration examples use Azure CLI commands with PowerShell syntax (e.g., Set-AzContext), which are Windows-centric. Additionally, the 'Next steps' section links first to a PowerShell-based tutorial. There are no explicit Linux/bash examples or instructions, and Windows tools/patterns are mentioned before any Linux equivalents.
Recommendations
- Provide equivalent bash/Linux shell examples for Azure CLI commands (e.g., using az instead of Set-AzContext).
- Clarify that Azure CLI is cross-platform and show examples in both PowerShell and bash syntax.
- Offer migration scripts or guidance for Linux/macOS users, or note if the PowerShell script can be run via Azure Cloud Shell (which is platform-agnostic).
- In 'Next steps', include links to tutorials using Azure CLI in bash or via the Azure Portal, not just PowerShell.
- Explicitly state platform compatibility for tools/scripts where relevant.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page repeatedly references Azure PowerShell scripts as the primary migration tooling, without mentioning or providing alternatives for Linux/macOS users (such as Azure CLI or ARM templates). There are no Linux/macOS-specific examples or guidance, and PowerShell is presented as the default approach for migration tasks.
Recommendations
- Provide equivalent Azure CLI commands or scripts for migration tasks, especially for public IP retention and configuration migration.
- Mention that Azure PowerShell can be run cross-platform (on Linux/macOS), but also clarify any prerequisites or limitations.
- Add examples or links for ARM template-based migration, if available.
- Explicitly state if certain scripts are Windows-only, and offer guidance for Linux/macOS users.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tools, such as New-SelfSignedCertificate and Export-PfxCertificate, with all examples and instructions provided only for Windows/PowerShell environments. There are no Bash, Azure CLI, or Linux/macOS alternatives, and Windows-centric commands (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 certificate tools.
Recommendations
- Add equivalent Azure CLI (bash) instructions and examples for all steps, especially resource creation and configuration.
- Provide Linux/macOS-compatible methods for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
- Use platform-neutral file paths or clarify how to adapt them for Linux/macOS.
- Mention that Azure PowerShell can be installed on Linux/macOS, or provide links to cross-platform installation guides.
- Consider including a note about cross-platform compatibility and alternative tooling for non-Windows users.
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits Windows bias primarily through the exclusive mention of PowerShell and Windows-specific certificate tooling. The 'Next steps' section directs users only to a PowerShell-based configuration guide, and certificate format references link to Windows APIs. There are no Linux/macOS CLI or tooling examples, and Windows tools are mentioned before any cross-platform alternatives.
Recommendations
- Add equivalent Linux/macOS configuration guides using Azure CLI or ARM templates.
- Provide examples for certificate creation and management using OpenSSL or cross-platform tools, not just referencing Windows APIs.
- Include links to cross-platform documentation in the 'Next steps' section alongside PowerShell.
- Mention Azure Portal and REST API options for configuration, which are platform-agnostic.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation heavily references Azure PowerShell scripts for migration tasks, with no mention of Azure CLI or Bash alternatives. All migration automation examples and guidance are PowerShell-centric, which is typically associated with Windows environments. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the default/only automation tool for migration.
Recommendations
- Add Azure CLI examples and scripts for migration tasks, especially for configuration and public IP retention.
- Explicitly mention that PowerShell can be used cross-platform, or provide Bash-compatible scripts.
- Include guidance for Linux/macOS users on how to perform migration steps without PowerShell.
- Present both PowerShell and CLI/Bash options side-by-side in migration sections.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure Application Gateway diagnostic logs provides a detailed PowerShell example for enabling logging, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is PowerShell, and references to log conversion tools are tied to Visual Studio and C#, which are Windows-centric. There is no mention of Azure CLI or Bash scripting, nor are Linux/macOS-friendly tools or workflows discussed.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash scripting examples for log retrieval and processing.
- Mention or link to cross-platform log conversion tools (e.g., Python-based converters) instead of only Visual Studio/C# tools.
- Ensure that references to data visualization tools include Linux/macOS-compatible options (e.g., Jupyter, matplotlib, etc.) alongside Excel and Power BI.
- Where possible, present CLI examples before or alongside PowerShell examples to signal parity.
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 page consistently uses Windows-based SQL Server VM examples and references SQL Server Management Studio (SSMS), a Windows-only client, for connectivity testing. There are no examples or guidance for Linux-based SQL Server VMs or for connecting from Linux/macOS clients. The Windows VM is presented as the default backend, and Windows tools are referenced exclusively.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative backend.
- Provide examples of connecting to the SQL Server via cross-platform clients such as Azure Data Studio, sqlcmd, or other CLI tools available on Linux/macOS.
- Mention that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends, and clarify any OS-specific requirements.
- Add screenshots or command-line examples relevant to Linux/macOS environments.
- Explicitly state that the procedure is applicable regardless of the backend OS, unless there are Azure limitations.
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 highlights an Azure PowerShell tutorial for creating an autoscaling, zone redundant application gateway. No equivalent Linux/macOS CLI (Azure CLI or ARM template) example or link is provided. The PowerShell example is mentioned before any Linux-friendly alternatives, which may create friction for non-Windows users.
Recommendations
- Add links or examples for Azure CLI and ARM template approaches to create autoscaling, zone redundant Application Gateway v2.
- Ensure that Linux/macOS users are provided with parity in guidance and examples, especially in 'Next steps' and tutorial sections.
- Consider listing Azure CLI or cross-platform options before or alongside PowerShell examples to avoid implicit Windows-first bias.
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 concepts and configuration. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, and (2) backend authentication troubleshooting links point to IIS and Windows-specific resources. These Windows references appear before any mention of Linux equivalents or generic guidance, potentially creating friction for Linux users seeking similar troubleshooting information.
Recommendations
- Add troubleshooting guidance and links for Linux-based authentication mechanisms (e.g., Kerberos on Linux, Apache/Nginx configuration) alongside Windows/IIS references.
- Include examples or references for backend server log review on Linux systems (such as Apache, Nginx, or other common web servers) in the troubleshooting section.
- When referencing authentication protocols, clarify that NTLM and Windows Authentication are Windows-specific, and provide guidance for Linux-based alternatives where applicable.
- Ensure that troubleshooting steps are not exclusively tied to Windows documentation, but also mention cross-platform approaches.
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, instructions, and tooling based on PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions provided. The guidance assumes a Windows/PowerShell environment, which creates friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning and IP retention.
- Include Bash shell examples and instructions for script execution, especially for users leveraging Azure Cloud Shell or running locally on Linux/macOS.
- Explicitly state PowerShell requirements and offer guidance for installing PowerShell Core on Linux/macOS, or recommend using Azure Cloud Shell for cross-platform compatibility.
- Add a section comparing PowerShell and Azure CLI approaches, highlighting any limitations or differences.
- Where possible, offer downloadable scripts in both PowerShell and Bash/Azure CLI formats.