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 326-350 of 981 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary method for configuration and details, mentioning PowerShell before CLI, and lacking any explicit Linux or Bash examples. The 'Next steps' section links only to a PowerShell-based configuration guide, and throughout the document, PowerShell is consistently listed before CLI or REST. There are no Linux-native command examples or references to Bash/Unix shell usage, which may disadvantage Linux users.
Recommendations
- Provide parallel Linux/Bash examples alongside PowerShell, especially in configuration and 'Next steps' sections.
- Ensure Azure CLI examples are given equal prominence to PowerShell, and mention them first or together.
- Link to both PowerShell and Azure CLI/Bash configuration guides in 'Next steps' and throughout the documentation.
- Explicitly state that all operations can be performed on Linux/macOS using Azure CLI, and provide sample commands.
- Avoid listing PowerShell before CLI unless there is a technical reason; alternate ordering or group them together.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing 'Run as administrator' for installation. There are no Linux or cross-platform alternatives or examples provided for these tasks, and Windows tools and patterns are mentioned before any platform-neutral options.
Recommendations
- Provide equivalent Azure CLI or Azure Cloud Shell examples for checking Application Gateway settings, as these are cross-platform and work on Linux, macOS, and Windows.
- Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or mitmproxy, and provide instructions or examples for their use.
- When referencing file paths, commands, or installation steps, include Linux/macOS equivalents (e.g., use 'sudo' instead of 'Run as administrator').
- When suggesting tools like Fiddler, mention cross-platform alternatives and clarify that Fiddler is primarily for Windows, while other tools are available for Linux/macOS.
- Structure troubleshooting steps and tool recommendations to be platform-neutral or to present Windows and Linux options side-by-side.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based automation examples for configuring Azure Application Gateway with Key Vault certificates. There are no CLI/bash/Linux shell examples, and PowerShell is referenced as the primary automation tool. The 'Next steps' section links exclusively to a PowerShell guide, and there is no parity for Linux or cross-platform users. Azure CLI is mentioned in passing, but no concrete CLI or bash examples are provided.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell scripts for all configuration steps, especially for certificate referencing and listener configuration.
- Where automation is discussed, present both PowerShell and bash/CLI options, and clarify that Azure CLI is cross-platform.
- In the 'Next steps' section, provide links to both PowerShell and Azure CLI guides.
- Avoid referencing PowerShell steps as the default or only automation path; instead, present both PowerShell and CLI equally.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide sample commands.
- Where ARM/Bicep templates are referenced, include CLI deployment examples (e.g., az deployment group create) in addition to PowerShell.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md
.../blob/main/articles/application-gateway/overview-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of Azure PowerShell commands and references to PowerShell scripts for migration and preview registration. Azure CLI is mentioned, but the examples provided are all PowerShell-based, and there are no Linux shell/bash equivalents. The migration tooling is described as a PowerShell script, and the documentation custom metadata includes 'devx-track-azurepowershell', further emphasizing the focus on Windows tooling. There are no explicit Linux or cross-platform examples, and PowerShell is presented as the default or only automation method.
Recommendations
- Provide equivalent Azure CLI (bash/shell) examples alongside PowerShell commands for all operations, including preview registration and unregistration.
- Mention and link to cross-platform tools and scripts (e.g., Azure CLI, ARM templates, Bicep) wherever PowerShell scripts are referenced.
- Ensure that migration tooling is available and documented for both PowerShell and Azure CLI users.
- Adjust language to refer to 'Azure CLI or PowerShell' instead of only PowerShell when discussing automation or scripting.
- Include explicit Linux/macOS instructions or notes where platform-specific steps may differ.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions and tools (winget, PowerShell) are presented before Linux equivalents. The Windows instructions are more detailed and reference Windows-specific package managers, while the Linux instructions are less prominent and less detailed. The rest of the guide uses cross-platform tools (Azure CLI, Helm, kubectl) and Bash-style scripting, which are generally Linux-friendly, but the initial ordering and emphasis favor Windows.
Recommendations
- Present Linux and Windows installation instructions for Helm with equal prominence and detail, possibly starting with Linux or providing both side-by-side.
- Include explicit Bash and PowerShell examples where relevant, or clarify that all CLI commands are cross-platform unless otherwise noted.
- Avoid referencing Windows-specific tools (like winget) before more universal installation methods.
- In general, ensure that Linux instructions are not treated as secondary or afterthoughts, and provide parity in troubleshooting and usage notes for both platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation presents configuration methods in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is more detailed, with extensive code samples and a dedicated cmdlet reference, while the Azure CLI section is less detailed and lacks parity in explanation and references. There are no explicit Linux or Bash shell examples, and the documentation does not mention or provide guidance for Linux-specific environments or tools. This structure and content may unintentionally favor Windows users and PowerShell workflows.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell to avoid implying Windows/PowerShell as the primary method.
- Ensure CLI and PowerShell sections have equivalent depth, including references and explanations.
- Add explicit Bash/Linux shell examples or notes, especially for CLI commands, to clarify cross-platform compatibility.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Where possible, provide troubleshooting or environment setup notes for Linux users (e.g., package installation, permissions).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md
...ticles/application-gateway/self-signed-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides cross-platform OpenSSL instructions for certificate generation and covers web server configuration for both Windows (IIS) and Linux (Apache, NGINX). However, there is a Windows-first bias in several areas: (1) Windows tools and patterns (e.g., IIS, PowerShell, C:\ paths) are mentioned before Linux equivalents; (2) the Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example; (3) references to editing the hosts file and certificate import are Windows-centric, with no Linux-specific guidance.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell examples for uploading certificates to Application Gateway, as Azure CLI is cross-platform.
- When referencing file paths (e.g., C:\Users\...), include Linux path equivalents (e.g., /home/user/...).
- For instructions on importing root certificates into the trusted store, include Linux-specific steps (e.g., update-ca-certificates on Ubuntu) in addition to Windows instructions.
- When mentioning editing the hosts file, provide the Linux path (/etc/hosts) and editing instructions.
- Consider presenting web server configuration sections (IIS, Apache, NGINX) in a neutral or rotating order, or group them by platform to avoid implicit prioritization.
- Where possible, avoid assuming the user is on Windows, and explicitly state when steps differ between platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-install-new.md
.../application-gateway/ingress-controller-install-new.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by recommending Azure Cloud Shell (which defaults to Bash or PowerShell, but is often associated with Windows users), visually highlighting the Azure PowerShell icon, and not providing explicit Linux shell or terminal instructions. The instructions and screenshots prioritize Windows-centric tools and workflows, and there is no mention of Linux-specific environments or alternative Linux-native tools. All command-line examples are generic Bash/Azure CLI, but the visual cues and tool recommendations are Windows-oriented.
Recommendations
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify that all instructions work equally well in Linux terminals.
- Add screenshots or references to Linux terminal environments (e.g., GNOME Terminal, Konsole) alongside the Azure PowerShell icon.
- Provide a brief note for Linux users on how to install and use the required tools (az, kubectl, helm, jq) natively on Linux, with links to Linux-specific installation guides.
- Avoid using only Windows/PowerShell icons or imagery; include cross-platform visuals.
- Where possible, add a section or callout confirming that all steps are cross-platform and tested on Linux, macOS, and Windows.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md
...ob/main/articles/application-gateway/retirement-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively references Azure PowerShell scripts for migration, with no mention of Azure CLI, Bash, or Linux-native tools. All automation and scripting guidance is centered on PowerShell, which is traditionally associated with Windows environments. There are no examples or instructions for users who may prefer or require Linux-based workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, alongside PowerShell examples.
- Explicitly mention that migration can be performed from Linux/macOS using Azure CLI or cross-platform PowerShell Core.
- Include Bash script examples or references for common migration tasks.
- Clarify any platform dependencies or prerequisites for the provided scripts.
- Ensure documentation parity by presenting both Windows and Linux options side-by-side where automation or scripting is discussed.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a significant Windows bias. PowerShell is the only scripting example provided for automating Key Vault integration, with no equivalent Azure CLI or Bash/Linux shell examples. References to automation and scripting consistently mention PowerShell first or exclusively. There are no Linux-specific instructions or parity in command-line examples, and the 'Next steps' section links only to a PowerShell-based guide.
Recommendations
- Provide equivalent Azure CLI examples alongside PowerShell for all automation steps, especially for referencing Key Vault secrets and configuring Application Gateway.
- Include Bash or Linux shell scripting examples where relevant, to ensure parity for Linux users.
- When mentioning automation tools (PowerShell, CLI, ARM templates, Bicep), list them in a neutral or rotating order, not always with PowerShell first.
- Add a 'Next steps' link to an Azure CLI-based guide for configuring TLS termination with Key Vault certificates.
- Explicitly state that all steps can be performed on both Windows and Linux, and clarify any OS-specific considerations.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows instructions (including a PowerShell/winget example) are presented before Linux instructions. The use of Windows-specific tooling (winget) is highlighted, while the Linux section is less detailed and lacks parity in installation options. However, most core deployment and management commands use cross-platform tools (Azure CLI, Helm, kubectl) and Bash syntax, which are suitable for both Linux and Windows environments.
Recommendations
- Present Linux and Windows instructions in parallel or with equal prominence, rather than listing Windows first.
- For Helm installation, provide equivalent detail and multiple installation options for both Linux and Windows (e.g., package managers like apt, yum, snap for Linux, and choco for Windows).
- Avoid highlighting Windows-specific tools (like winget) without mentioning Linux equivalents (such as apt, yum, or snap).
- Where possible, use cross-platform installation instructions or clearly indicate which commands are OS-specific.
- Consider including macOS instructions for broader parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. There are no equivalent instructions or links for Linux users (e.g., using Azure CLI or ARM templates), and the only explicit tooling example is PowerShell, which is most commonly associated with Windows environments.
Recommendations
- Add equivalent Azure CLI (az) tutorials and references for Linux/macOS users alongside PowerShell instructions.
- Include ARM/Bicep template examples for cross-platform automation.
- In the 'Next steps' section, ensure that links to Linux-friendly tools (Azure CLI, REST API) are presented with equal prominence as PowerShell.
- Explicitly mention that the features and configuration steps are platform-agnostic where possible, and clarify when a tool is available on multiple platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page does not provide any OS-specific command-line examples, but the only linked tutorial for further configuration uses PowerShell, which is Windows-centric. There is no mention of Linux tools, Bash, or cross-platform CLI alternatives, and the documentation implicitly assumes a Windows-first approach by directing users to a PowerShell-based guide.
Recommendations
- Include links to equivalent tutorials using Azure CLI (az), which is cross-platform and works on both Linux and Windows.
- Explicitly mention that configuration can be performed using Azure CLI, ARM templates, or the Azure portal, not just PowerShell.
- Provide example commands or references for both PowerShell and Bash/Azure CLI where relevant.
- Ensure that next steps and further reading sections offer parity between Windows and Linux users by linking to platform-agnostic or platform-specific guides as appropriate.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and CLI as the primary configuration tools, with PowerShell mentioned first and linked as the main method for configuring TLS policies. There are no explicit Linux or Bash examples, and the 'Next steps' section only links to a PowerShell-based guide. The documentation does not mention or provide parity for Linux-native tools or workflows.
Recommendations
- Provide explicit Bash/Azure CLI examples alongside or before PowerShell examples for configuring TLS policies.
- In the 'Next steps' section, include links to both PowerShell and Bash/CLI documentation for configuring TLS policies.
- Avoid referencing PowerShell as the sole or primary method; instead, present both Windows and Linux workflows equally.
- Wherever configuration is discussed, clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
- If portal or REST API methods are available, mention them as platform-neutral alternatives.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md
.../blob/main/articles/application-gateway/overview-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and commands for migration and preview registration/unregistration tasks. The examples and instructions for registering/unregistering the Basic SKU preview use PowerShell cmdlets (e.g., Set-AzContext, Register-AzProviderFeature), and the migration script is only mentioned as being available in the PowerShell Gallery. There are no equivalent Bash, Azure CLI (cross-platform), or Linux-native instructions provided. Additionally, in the 'Next steps' section, the tutorial linked is specifically for PowerShell, and PowerShell is mentioned before Azure CLI or portal options.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell-based instructions, especially for registration, unregistration, and migration tasks.
- When referencing scripts or automation, mention both PowerShell and Bash/CLI options, or clarify if a cross-platform solution is available.
- In 'Next steps' and similar sections, list Azure CLI and portal options before or alongside PowerShell to avoid the impression that Windows tools are preferred.
- If migration scripts are only available in PowerShell, note this limitation explicitly and provide guidance or alternatives for Linux/macOS users.
- Consider including example commands or scripts that are platform-agnostic or specify which platforms are supported for each example.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples, nor are Linux-friendly tools (such as tcpdump, Wireshark, or curl) mentioned. The document also assumes a Windows environment in its troubleshooting steps and screenshots.
Recommendations
- Provide equivalent Azure CLI and/or Azure Cloud Shell examples for checking Application Gateway settings, alongside or instead of PowerShell.
- Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or curl, and provide instructions or examples for their use.
- When referencing downloadable tools, mention cross-platform alternatives (e.g., Wireshark, mitmproxy) and provide installation instructions for Linux/macOS.
- Avoid Windows-specific instructions like 'Run as administrator' unless also providing the Linux/macOS equivalent (e.g., 'run with sudo').
- Ensure screenshots and step-by-step instructions are not exclusively based on Windows UI/tools.
- Rephrase sections to be OS-neutral where possible, or clearly separate instructions for Windows and Linux/macOS users.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md
...ob/main/articles/application-gateway/retirement-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, without mentioning or providing examples for Azure CLI, Bash, or other cross-platform tools. There are no Linux-specific instructions or examples, and the reliance on PowerShell may disadvantage users on Linux or macOS systems.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, alongside PowerShell examples.
- Explicitly mention that migration can be performed from Linux/macOS using Azure CLI or Bash, and provide guidance or links.
- Include a section comparing PowerShell and CLI approaches, highlighting cross-platform compatibility.
- Ensure that all tooling references (e.g., for scripting, automation) are not Windows-specific unless absolutely necessary, and note any platform limitations.
- Add troubleshooting and support instructions relevant to Linux users, such as common issues with CLI or Bash environments.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md
...ticles/application-gateway/self-signed-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates some Windows bias, particularly in the order and emphasis of examples and tooling. While the core certificate generation steps use OpenSSL (cross-platform), Windows-specific tools and workflows are often mentioned first or exclusively. The Azure PowerShell example is provided in detail, with no equivalent Azure CLI (cross-platform) example. IIS (Windows) is listed before Apache and NGINX, and references to editing the hosts file link to Windows-centric documentation. The PowerShell script uses Windows file paths, and there is no explicit Linux or macOS guidance for uploading certificates to Application Gateway.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell, especially for certificate upload and Application Gateway configuration.
- Include Linux/macOS-specific instructions for tasks like editing the hosts file and importing root certificates into the trusted store.
- When listing web server configuration examples, rotate or randomize the order (e.g., sometimes start with Apache or NGINX instead of IIS).
- Use platform-neutral file paths in code samples, or provide both Windows and Linux/macOS path examples.
- Link to cross-platform documentation for tasks like editing the hosts file or importing certificates, rather than Windows-only resources.
- Explicitly mention that all OpenSSL commands work on both Windows and Linux, and note any OS-specific differences if relevant.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits a Windows bias by referencing Azure PowerShell as the only example for creating an autoscaling, zone redundant application gateway with a reserved virtual IP address. There are no equivalent instructions or links for Linux users (e.g., Azure CLI, ARM templates, or Bicep). The 'Next steps' section specifically highlights a PowerShell tutorial, implicitly prioritizing Windows tooling and workflows.
Recommendations
- Add equivalent Linux-friendly instructions and links, such as tutorials using Azure CLI, ARM templates, or Bicep, alongside the PowerShell example.
- In the 'Next steps' section, provide parallel links for both PowerShell and Azure CLI (and/or ARM/Bicep) to ensure users on all platforms have clear guidance.
- Review the documentation for any implicit assumptions about the user's operating system and strive for neutral, cross-platform language and examples.
- Consider a table or section comparing how to perform key tasks (like autoscaling configuration) using different tools (PowerShell, CLI, ARM, Bicep) to promote parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md
.../blob/main/articles/application-gateway/overview-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration tasks, with no mention of Bash or Linux shell equivalents. The command-line examples use PowerShell syntax exclusively, and the only automation tool referenced is PowerShell. There is no guidance or example for users on Linux/macOS, nor are cross-platform Azure CLI examples provided. The documentation also refers to the Azure PowerShell Gallery as the source for migration scripts, reinforcing a Windows-centric approach.
Recommendations
- Provide Azure CLI (bash-compatible) examples alongside or before PowerShell examples for all command-line tasks, including migration and preview registration.
- Mention cross-platform compatibility for tools and scripts, clarifying when a script or tool is Windows-only or works on Linux/macOS.
- Reference the Azure CLI as a first-class tool for automation and management, not just PowerShell.
- Include links to Linux/macOS setup guides for Azure CLI and PowerShell, if relevant.
- Ensure that all code blocks are clearly labeled with the shell or environment they are intended for.
- If a PowerShell script is the only migration tool available, provide instructions for running it on Linux/macOS using PowerShell Core, or offer an equivalent Azure CLI script.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools and patterns as the primary or sole method for configuring and viewing TLS policies. There are no explicit Linux or cross-platform command examples, and PowerShell is mentioned before or instead of Azure CLI in several places. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting Linux-friendly or CLI-based alternatives.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all configuration steps, as Azure CLI is cross-platform and widely used on Linux.
- Include explicit references and links to Linux/macOS-compatible instructions or documentation, especially in the 'Next steps' section.
- When mentioning tools or methods for viewing or configuring policies (e.g., 'refer to the PowerShell, CLI, REST API or the Listeners blade in portal'), ensure CLI is listed first or equally with PowerShell.
- Add sample commands for both PowerShell and Azure CLI in relevant sections to ensure parity.
- Consider including a section or callout specifically for Linux/macOS users to highlight any differences or additional steps.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for web debugging, and referencing 'Run as administrator' and .NET versions. There are no Linux or cross-platform alternatives or examples for these tasks, and Windows tools and patterns are mentioned first and exclusively.
Recommendations
- Provide Azure CLI (az) and/or Azure Resource Manager (ARM) REST API examples alongside or instead of PowerShell for configuration checks, as these are cross-platform.
- Include examples using Linux-compatible web debugging tools such as mitmproxy, Wireshark, or tcpdump, and provide instructions for their use.
- Avoid instructions that are specific to Windows environments (e.g., 'Run as administrator', '.NET 4 installed') unless also providing Linux/macOS equivalents.
- When referencing tools, use language like 'for example, Fiddler or mitmproxy' and link to both Windows and Linux tool documentation.
- Add screenshots or command-line snippets from Linux environments where appropriate to ensure parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for critical configuration steps, referencing PowerShell and Windows-centric tooling first and exclusively, and omitting equivalent Azure CLI (cross-platform) or Bash scripting examples. There are no Linux-specific instructions or examples, and the 'Next steps' section directs users to a PowerShell-based guide, further reinforcing the bias.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
- Include Bash scripting examples where appropriate to support Linux users.
- In sections where PowerShell is referenced, mention Azure CLI as an alternative and provide links to relevant CLI documentation.
- Ensure that the 'Next steps' section includes links to both PowerShell and Azure CLI guides for TLS termination with Key Vault certificates.
- Review the documentation for any terminology or instructions that assume a Windows environment and generalize them for cross-platform applicability.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows instructions (including a PowerShell/winget example) are presented before Linux instructions. The use of Windows-specific tooling (winget) is highlighted, while the Linux section is less detailed. However, the majority of the CLI examples use cross-platform Azure CLI and Bash syntax, and Linux installation is covered.
Recommendations
- Present Linux and Windows instructions in parallel tabs or in the same order throughout the documentation, rather than listing Windows first.
- Provide equally detailed installation steps and context for both Windows and Linux users (e.g., mention popular Linux package managers like apt, yum, or snap for Helm).
- Avoid emphasizing Windows-specific tools (like winget) without offering equivalent Linux alternatives (such as apt, snap, or direct binary download instructions).
- Where possible, use cross-platform shell examples (Bash or Azure CLI) as the default, and only provide OS-specific instructions when necessary.
- Explicitly state that all Azure CLI and Helm commands can be run from Linux, macOS, or Windows (with WSL or native shells), to reinforce cross-platform parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page demonstrates bias toward Windows environments by referencing only a PowerShell-based tutorial for next steps, without mentioning or linking to Linux-native tools or CLI examples. There are no Bash, Azure CLI, or Linux shell command examples, and the only configuration guidance points to a PowerShell tutorial, which is most commonly used on Windows.
Recommendations
- Include equivalent Azure CLI (az network application-gateway) examples for configuring redirects, as Azure CLI is cross-platform and widely used on Linux.
- Provide Bash shell command examples for common redirection scenarios.
- Link to or create tutorials for configuring Application Gateway redirects using Azure CLI and ARM templates, not just PowerShell.
- Explicitly mention that PowerShell examples can be run on Linux (if applicable), or clarify platform requirements for each method.
- Ensure that references to configuration steps or tutorials are balanced, offering both Windows/PowerShell and Linux/Azure CLI options side by side.