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 551-575 of 981 flagged pages
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples, instructions, and tooling centered around PowerShell. There are no references to Azure CLI, Bash, or Linux/macOS-native tooling, nor are there alternative examples for non-Windows environments. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all script downloads and usage are PowerShell-specific. 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 all migration steps, including configuration cloning and IP retention.
  • Add Bash shell examples for certificate handling and script execution, especially for Linux/macOS users.
  • Clearly state that PowerShell is required, and offer guidance for installing PowerShell Core on Linux/macOS if PowerShell-only scripts are unavoidable.
  • Mention Azure Cloud Shell's Bash environment as an alternative, and clarify which steps can be performed there.
  • Consider linking to cross-platform migration tools or documenting limitations for Linux/macOS users.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway v2 exhibits moderate Windows bias, primarily through exclusive use of Azure PowerShell examples and references, and by linking to tutorials that use PowerShell as the primary method. While the core content is platform-agnostic, Linux/macOS users may encounter friction due to the lack of Azure CLI or ARM template examples and the prominence of PowerShell-based workflows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for registration, migration, and other operations.
  • Provide ARM template or Terraform examples for deployment and migration tasks.
  • Ensure tutorials and quickstarts offer both PowerShell and CLI options, or clearly indicate which platforms are supported.
  • Explicitly mention that PowerShell commands can be run cross-platform (with Azure PowerShell Core), but also provide native CLI alternatives for Linux/macOS users.
GitHub 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 →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides a conceptual overview of end-to-end TLS on Azure Application Gateway, but the only 'Next steps' link is to a PowerShell-based configuration guide. There are no Linux/macOS CLI (Azure CLI, Bash, etc.) examples or links, and Windows/PowerShell tooling is referenced first and exclusively for practical configuration. Additionally, the certificate format guidance references a Windows API (PFXImportCertStore) without mentioning cross-platform alternatives.
Recommendations
  • Add links to equivalent Azure CLI and/or ARM template guides for configuring end-to-end TLS on Application Gateway.
  • Provide Linux/macOS-friendly instructions and examples for certificate creation, conversion, and upload (e.g., using OpenSSL, Azure CLI).
  • When referencing certificate formats and APIs, mention cross-platform tools (such as OpenSSL for PFX creation) alongside Windows-specific APIs.
  • Ensure that practical configuration steps are available for all supported platforms, not just Windows/PowerShell.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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. There are no Bash, Azure CLI, or Linux/macOS-compatible examples, and Windows tools are referenced without alternatives. This creates friction for Linux/macOS users, especially for certificate generation and local scripting.
Recommendations
  • Add Azure CLI examples for all steps, especially resource creation and management.
  • Provide Linux/macOS-compatible instructions for generating self-signed certificates (e.g., using OpenSSL).
  • Mention that Azure PowerShell can be installed and used cross-platform, but highlight Azure CLI as a viable alternative.
  • Include Bash shell examples alongside PowerShell, or link to equivalent tutorials for Linux/macOS users.
  • Clarify which steps are Windows-specific and offer alternatives where possible.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples primarily using Azure PowerShell, with PowerShell commands shown first and in more detail than Azure CLI. There is no mention of Linux/macOS-specific tools or workflows, and the CLI example is minimal. The 'Next steps' section links only to a PowerShell guide, omitting Linux-focused or CLI-based guides. Azure portal support is noted as unavailable, but Linux users are not given parity in guidance or examples.
Recommendations
  • Provide Azure CLI examples with equal detail and prominence as PowerShell, including step-by-step instructions.
  • Add links to Linux/macOS-focused guides for configuring mutual authentication, or explicitly mention that Azure CLI can be used cross-platform.
  • In 'Next steps', include links to CLI and ARM template guides, not just PowerShell.
  • Where PowerShell is referenced, clarify that Azure CLI is available and suitable for Linux/macOS users.
  • Consider including sample certificate extraction commands using OpenSSL (common on Linux/macOS) alongside any Windows-specific tools.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 CLI or Bash example for Linux/macOS users. The only command-line automation shown is via PowerShell, and there are references to tools like Excel and Visual Studio, which are primarily Windows-centric. There is no mention of Azure CLI, Bash, or cross-platform scripting alternatives.
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 snippets where automation is discussed, or at least reference that Azure CLI can be used from any OS.
  • When mentioning tools for log analysis (e.g., Excel, Visual Studio), also mention cross-platform alternatives such as jq, pandas (Python), or open-source log viewers.
  • Ensure that references to PowerShell are clearly marked as Windows-specific, and provide links or guidance for Linux/macOS users.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates the configuration using a SQL Server VM running Windows Server and recommends SQL Server Management Studio (SSMS) as the client tool, both of which are Windows-centric. There are no examples or guidance for deploying a SQL Server VM on Linux or connecting from Linux/macOS clients, nor are cross-platform SQL client tools mentioned.
Recommendations
  • Include instructions for deploying SQL Server on a Linux VM in Azure, or clarify that Linux is supported if applicable.
  • Mention and provide examples for connecting to the SQL Server via cross-platform SQL clients such as Azure Data Studio, sqlcmd, or other open source tools.
  • Add notes or links for Linux/macOS users regarding SQL authentication setup and client connectivity.
  • If SSMS is Windows-only, recommend alternative tools for Linux/macOS users.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all migration instructions, examples, and tooling based exclusively on PowerShell. There are no references to Azure CLI, Bash, or cross-platform scripting alternatives, nor are Linux/macOS usage patterns or prerequisites mentioned. The guidance assumes a Windows/PowerShell environment throughout, which creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
  • Provide Azure CLI equivalents for all migration steps, including configuration migration, certificate handling, and traffic migration.
  • Include Bash script examples and instructions for Linux/macOS users, especially for certificate manipulation and script installation.
  • Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which is cross-platform), and explicitly mention this as an option for non-Windows users.
  • Add a section outlining Linux/macOS prerequisites and environment setup for running migration scripts.
  • Where possible, link to Azure CLI documentation and tools for Application Gateway management.
  • Consider providing downloadable Bash or Python scripts for migration tasks, or note limitations if PowerShell is required.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway v2 shows moderate Windows bias. Migration guidance and tutorials reference Azure PowerShell scripts and provide PowerShell-centric instructions, with no mention of Bash, Linux CLI, or cross-platform alternatives. The registration/unregistration steps for the Basic SKU use Azure CLI, but the commands shown are PowerShell-style (e.g., Set-AzContext), which is not standard Bash or Linux Azure CLI syntax. Additionally, the 'Next steps' section links primarily to PowerShell-based tutorials, with no Linux/Bash alternatives or parity.
Recommendations
  • Provide Bash/Linux Azure CLI command examples alongside PowerShell commands, especially for registration/unregistration and migration tasks.
  • Link to or create tutorials that use cross-platform Azure CLI (az) commands, not just PowerShell.
  • Clarify which commands are PowerShell-specific and offer equivalent Bash/Linux syntax where possible.
  • Ensure migration scripts and guidance are available for Linux/macOS users, not just Windows/PowerShell.
  • In 'Next steps', include links to Linux/Bash tutorials or documentation for creating and managing Application Gateway.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 frequently references Azure PowerShell scripts as the primary migration tooling. There are no examples or mentions of Azure CLI or Bash alternatives, nor guidance for Linux/macOS users. PowerShell is a Windows-native tool, and its prominence creates friction for users on other platforms. Additionally, the documentation does not clarify cross-platform compatibility or provide Linux/macOS-specific instructions.
Recommendations
  • Add Azure CLI examples and scripts for migration tasks, especially for configuration and public IP retention.
  • Explicitly state whether the PowerShell scripts can be run on Linux/macOS (using PowerShell Core), and provide installation guidance if so.
  • Provide Bash or shell script alternatives where feasible.
  • Mention Azure Portal as a platform-agnostic option for migration steps, if available.
  • Ensure that migration instructions are not solely dependent on Windows tools.
GitHub 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 →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a conceptual overview of end-to-end TLS on Azure Application Gateway. While the main content is platform-neutral, the 'Next steps' section directs users exclusively to a PowerShell-based configuration guide, implying Windows as the primary platform for hands-on tasks. No Linux or cross-platform CLI examples or links are provided, and Windows-specific terminology (e.g., PFXImportCertStore) is referenced before any Linux equivalents.
Recommendations
  • Add links to equivalent Azure CLI and/or ARM template guides for configuring end-to-end TLS on Application Gateway, ensuring Linux/macOS users have clear, supported paths.
  • Include examples or references for certificate management and conversion using cross-platform tools (e.g., OpenSSL) alongside Windows-specific tools.
  • Mention that PowerShell is available cross-platform, but clarify if the referenced guide is Windows-only or provide guidance for PowerShell Core on Linux/macOS.
  • Where Windows APIs or formats (like PFXImportCertStore) are mentioned, briefly note Linux/macOS alternatives or relevant documentation.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is a PowerShell cmdlet, and there is no mention of Azure CLI or Bash scripting alternatives. Additionally, the 'log converter tools' tip references a C#/Visual Studio-based tool, which is more accessible to Windows users. This creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Where PowerShell is shown, provide Bash or CLI alternatives side-by-side or in tabs.
  • For log conversion, mention or link to cross-platform tools or scripts (e.g., Python-based converters) if available, or clarify if the provided tool can be used on Linux/macOS via .NET Core.
  • Review the 'Next steps' section to include links to cross-platform visualization tools or instructions, not just Power BI/Excel.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page frequently references Azure PowerShell scripts as the primary method for migrating Application Gateway V1 to V2, without mentioning or providing equivalent examples for Azure CLI or other cross-platform tools. There are no Linux/macOS-specific instructions or alternatives, and PowerShell is presented as the default migration tool, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples or scripts for migration tasks, especially for configuration and public IP retention.
  • Explicitly mention that PowerShell scripts can be run on Linux/macOS via PowerShell Core, or provide guidance for cross-platform usage.
  • Where possible, provide Bash or Azure CLI alternatives alongside PowerShell instructions.
  • Clarify any limitations or prerequisites for running PowerShell scripts on non-Windows systems.
GitHub Create Pull Request
Application Gateway Azure Application Gateway infrastructure configuration ...es/application-gateway/configuration-infrastructure.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides Azure PowerShell links for restarting Application Gateway instances, but does not offer equivalent Azure CLI or Linux/macOS command examples. PowerShell is mentioned first and exclusively, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. No Windows-specific tools or patterns are otherwise referenced, and the rest of the documentation is platform-neutral.
Recommendations
  • Add Azure CLI examples alongside PowerShell commands for operations such as restarting Application Gateway instances.
  • When referencing command-line tools, mention both PowerShell and Azure CLI, or provide links to both.
  • Ensure that any procedural instructions are not phrased in a way that assumes Windows/PowerShell as the default or only option.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates notable Windows bias. It exclusively uses Windows Server as the SQL backend VM, and the SQL client connection example relies on SQL Server Management Studio (SSMS), a Windows-only tool. There are no Linux or macOS alternatives mentioned for either the SQL backend or client connection. The instructions and screenshots are all based on Windows environments, and Linux-compatible SQL Server images, tools, or connection methods are not referenced.
Recommendations
  • Include instructions for deploying SQL Server on Linux (e.g., Ubuntu-based SQL Server VM) as an alternative backend.
  • Provide examples of connecting to SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible clients.
  • Mention Linux/macOS compatibility in relevant sections and clarify any limitations.
  • Add screenshots or CLI instructions for Linux users where appropriate.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway v2 exhibits moderate Windows bias. Key migration and creation tutorials are linked as PowerShell-based, and the only migration script mentioned is a PowerShell script. Azure CLI commands are shown, but the examples use PowerShell cmdlets (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature) rather than cross-platform Azure CLI commands. There is no explicit mention of Linux/macOS-specific instructions or parity for migration scripts or tutorials.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for migration and creation tasks, ensuring cross-platform compatibility.
  • Clearly indicate whether migration scripts are usable on Linux/macOS (e.g., if PowerShell Core is supported, specify this).
  • Add links to tutorials or guides using Azure CLI or ARM templates for Application Gateway v2 creation and migration.
  • Where PowerShell is used, note if the commands are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
GitHub 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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides a conceptual overview of enabling end-to-end TLS on Azure Application Gateway, which is a cross-platform Azure service. However, the 'Next steps' section exclusively links to a PowerShell-based guide for configuration, with no mention of Azure CLI, Bash, or Linux/macOS-compatible instructions. Additionally, certificate format references (PFX) and links to Windows API documentation (PFXImportCertStore) are given without Linux equivalents or guidance. This creates friction for Linux/macOS users who may prefer or require non-Windows tooling.
Recommendations
  • Add links to Azure CLI and/or ARM template guides for configuring end-to-end TLS on Application Gateway, ensuring Linux/macOS users have parity.
  • Provide examples or references for certificate management and conversion on Linux/macOS (e.g., using OpenSSL to create PFX files).
  • When referencing certificate formats or APIs, include cross-platform guidance or note that PFX files can be generated on any OS.
  • In 'Next steps', offer multiple paths (PowerShell, Azure CLI, Portal, ARM templates) for configuration.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily biased toward Windows/PowerShell environments. All migration scripts, examples, and instructions are provided exclusively for Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible alternatives. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all code samples are PowerShell-based. There is no parity for Linux/macOS users who may prefer or require Azure CLI or Bash scripting.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning, certificate handling, and IP migration.
  • Include Bash shell examples for script execution and parameter handling.
  • Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports both PowerShell and Bash), and provide guidance for Linux/macOS users.
  • Add a section explicitly addressing Linux/macOS environments, listing any limitations or workarounds.
  • Where possible, link to cross-platform tools or documentation, and avoid assuming PowerShell as the default shell.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples and next steps primarily using Azure PowerShell, with CLI examples included but less detailed. The 'Next steps' section directs users to a PowerShell-specific guide, and PowerShell is consistently mentioned before CLI. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux-native tools for certificate management or validation.
Recommendations
  • Provide equal depth of examples for Azure CLI alongside PowerShell, including full configuration flows.
  • In the 'Next steps' section, include links to both PowerShell and Azure CLI guides for mutual authentication setup.
  • When referencing certificate extraction or management, include Linux/macOS command-line examples (e.g., using OpenSSL) for extracting and preparing certificate chains.
  • Alternate the order of PowerShell and CLI examples, or present them in parallel tabs, to avoid Windows-first bias.
  • Explicitly state that all configuration steps can be performed from Linux/macOS using Azure CLI where applicable.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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. It also references tools like Excel and Visual Studio for log analysis and conversion, which are primarily Windows-centric, without mentioning Linux/macOS alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Windows-specific tools.
Recommendations
  • Add Azure CLI and/or Azure Cloud Shell examples for enabling diagnostic logging, as these are cross-platform and widely used by Linux/macOS users.
  • When mentioning log analysis, include Linux/macOS-friendly tools such as jq, csvkit, or open-source alternatives to Excel (e.g., LibreOffice Calc), and note that Power BI has web-based options.
  • For log conversion, reference cross-platform scripting options (e.g., Python scripts) or provide guidance for users not using Visual Studio.
  • Where possible, present examples in a platform-neutral way or provide both Windows and Linux/macOS command-line options.
GitHub Create Pull Request
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway configuration concepts. However, there are two notable instances of Windows bias: troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, and IIS configuration, without mentioning Linux equivalents or alternatives. Additionally, Windows tools and patterns are mentioned first or exclusively in these troubleshooting sections, potentially creating friction for Linux users.
Recommendations
  • When discussing authentication troubleshooting (NTLM/Kerberos), add references or guidance for Linux-based backend servers, such as Samba, Apache, or NGINX configurations for Kerberos.
  • Include links or notes about how to review logs or configure authentication on Linux web servers (e.g., Apache, NGINX) in addition to IIS.
  • Clarify that NTLM is Windows-specific, but Kerberos can be used cross-platform, and provide Linux guidance where applicable.
  • Ensure troubleshooting steps are not solely focused on Windows tools and documentation.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for migrating Azure Application Gateway from V1 to V2 is heavily biased toward Windows/PowerShell environments. All migration scripts, examples, and instructions are exclusively provided for Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all code samples are PowerShell cmdlets. There is no parity for Linux/macOS users who prefer Azure CLI or Bash scripting, nor is there guidance for running these scripts in cross-platform environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for configuration and traffic migration.
  • Add Bash shell examples for script installation and execution, especially for users on Linux/macOS.
  • Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports both Bash and PowerShell), and provide instructions for both environments.
  • Mention any limitations or requirements for Linux/macOS users, such as PowerShell Core compatibility or prerequisites.
  • Consider linking to cross-platform migration tools or providing guidance for users who do not have access to PowerShell.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples for mutual authentication on Azure Application Gateway primarily using PowerShell, with CLI examples included but PowerShell shown first and in more detail. There are no explicit Linux/macOS-specific instructions or examples (e.g., Bash scripting, OpenSSL usage for certificate extraction), and the 'Next steps' section directs users to a PowerShell-focused guide. This may create friction for Linux/macOS users who do not use PowerShell as their primary tool.
Recommendations
  • Ensure all configuration examples are provided for both Azure PowerShell and Azure CLI, and consider showing CLI (cross-platform) examples first or equally.
  • Add Linux/macOS-specific instructions or examples for certificate extraction and management (e.g., using OpenSSL commands).
  • In 'Next steps', provide links to both PowerShell and CLI-based guides for mutual authentication setup.
  • Clarify that all features can be configured using CLI and REST API, and provide parity in documentation depth for these methods.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway v2 shows mild Windows bias, primarily through the use of Azure PowerShell scripts for migration and registration examples, and by referencing PowerShell gallery resources. While Azure CLI commands are shown for preview registration, they use PowerShell cmdlets, which may confuse Linux/macOS users. There are no explicit Linux/macOS examples or mentions of Bash or cross-platform CLI usage. The 'Next steps' section links to a PowerShell-based tutorial, and the migration script is PowerShell-only, creating friction for non-Windows users.
Recommendations
  • Provide Bash/Azure CLI examples alongside PowerShell for registration, migration, and management tasks.
  • Clarify whether the PowerShell migration script can be run on Linux/macOS (using PowerShell Core), or provide a cross-platform alternative.
  • Link to tutorials or guides that use Azure CLI or ARM templates for deployment and migration.
  • Explicitly mention cross-platform compatibility where applicable, and avoid implying PowerShell is the only supported method.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 equivalent CLI (az) or Bash/Linux shell options. All migration automation examples and guidance are PowerShell-centric, and there are no Linux/macOS-friendly alternatives or examples. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI (az) examples or scripts for migration tasks, especially for configuration and public IP retention.
  • Explicitly mention whether migration scripts can be run cross-platform (e.g., PowerShell Core on Linux/macOS), and provide guidance for Linux/macOS users.
  • Provide Bash or shell script alternatives where possible, or clarify limitations.
  • List both PowerShell and CLI options side-by-side in migration instructions to ensure parity.
GitHub Create Pull Request
← Previous Page 23 of 40 Next →