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 251-275 of 981 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing only a PowerShell example for resource cleanup and focusing on IIS (a Windows web server) for validation. There are no Linux/CLI/bash examples for resource deletion, nor is there mention of Linux-based web servers (such as Apache or Nginx) for backend validation. The only explicit command-line example is PowerShell, and the validation step assumes Windows VMs with IIS, omitting Linux alternatives.
Recommendations
- Provide equivalent Azure CLI and/or Bash examples for resource group deletion (e.g., az group delete --name <group-name>).
- Include instructions or notes for validating the deployment using Linux VMs (e.g., with Apache or Nginx) as backend servers.
- When referencing command-line tools or scripts, present both Windows (PowerShell) and Linux (CLI/bash) options, or link to relevant cross-platform documentation.
- Clarify that the backend VMs can run either Windows or Linux, and provide sample templates or links for both scenarios.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing only a PowerShell example for resource cleanup and referencing IIS (a Windows-only web server) for validation. There are no equivalent Linux/bash/CLI examples for resource deletion, nor is there mention of Linux-based web servers for validation. The use of Windows-centric tools and lack of Linux parity may hinder users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (bash) commands for resource cleanup, such as 'az group delete --name <your resource group name>'.
- Include validation steps using a Linux-based web server (e.g., Nginx or Apache) in addition to IIS, or clarify that the template can be modified to deploy Linux VMs.
- Ensure that all PowerShell examples are accompanied by Azure CLI/bash equivalents, especially for common tasks like resource deletion.
- Explicitly mention cross-platform options and link to relevant Linux/CLI documentation where appropriate.
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 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 equivalent Bash or Linux-native CLI examples. The 'Next steps' and migration sections highlight PowerShell before Azure CLI or Linux-friendly tooling, and all code snippets use PowerShell syntax. There are no explicit Linux/Bash examples or mentions of Linux-specific tools or workflows.
Recommendations
- Provide equivalent Azure CLI (bash) examples alongside or before PowerShell scripts for all operations, especially migration and preview registration.
- Explicitly mention that all features and scripts are cross-platform where applicable, and clarify any OS-specific limitations.
- In the 'Next steps' and tutorial links, ensure parity by linking to both PowerShell and Azure CLI (bash) tutorials.
- Where PowerShell is referenced, add a note or section for Linux/macOS users on how to perform the same tasks using Azure CLI or Bash.
- Review all code blocks and add bash/CLI alternatives, using code block annotations (e.g., ```azurecli or ```bash) to distinguish them.
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
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration tasks, with no equivalent Bash or Linux-native CLI examples. The 'Next steps' section also prioritizes PowerShell tutorials, and the use of 'Set-AzContext' and similar commands is specific to PowerShell, which is more familiar to Windows users. There is no mention of Bash, Linux, or cross-platform CLI usage, and Linux users are not directly addressed.
Recommendations
- Provide Azure CLI (bash/shell) command examples alongside or before PowerShell commands for all tasks, especially for migration and preview registration.
- Include explicit references to Linux/macOS compatibility and usage where relevant.
- Balance tutorial links in the 'Next steps' section by including guides that use Azure CLI in Bash or cross-platform environments.
- Avoid assuming PowerShell as the default scripting environment; clarify when commands are PowerShell-specific.
- Where possible, use generic Azure CLI commands (az ...) instead of PowerShell-specific cmdlets (Set-AzContext, Register-AzProviderFeature, etc.), or provide both.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell example for resource cleanup (Remove-AzResourceGroup), referencing IIS (a Windows web server) as the default backend for validation, and omitting any Linux/CLI equivalents or examples for these steps. There are no instructions or examples for users on Linux or macOS platforms, particularly for resource cleanup or backend validation.
Recommendations
- Provide equivalent Azure CLI commands for resource group deletion (e.g., az group delete --name <group-name>), and present them alongside or before PowerShell examples.
- Include backend validation steps using a Linux-friendly web server (such as Nginx or Apache) or clarify how to adapt the validation for non-Windows environments.
- Ensure that all code snippets and instructions are cross-platform, or clearly indicate which steps are specific to Windows and provide alternatives for Linux/macOS users.
- Consider using neutral language and examples (e.g., 'web server' instead of 'IIS') unless the scenario specifically requires Windows.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing only a PowerShell example for resource cleanup (Remove-AzResourceGroup), referencing IIS (a Windows web server) as the default backend for validation, and omitting any Linux/CLI equivalents for these steps. There are no Linux-specific instructions or examples for deploying, validating, or cleaning up resources.
Recommendations
- Provide equivalent Azure CLI (cross-platform) commands for resource cleanup, such as 'az group delete --name <resource group name>'.
- Include examples using a Linux-based backend (e.g., NGINX or Apache) for validation, or at least mention how to adapt the template for Linux VMs.
- Where PowerShell is referenced, always offer Azure CLI alternatives and present them with equal prominence.
- Clarify that the instructions apply to both Windows and Linux users, and link to relevant Linux/CLI quickstarts where appropriate.
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 commands, both for migration and preview registration/unregistration. The only command-line examples provided use Azure PowerShell cmdlets (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature), with no equivalent Azure CLI (az) or Bash/Linux shell examples. The 'Next steps' section also lists a PowerShell-based tutorial first, and the page metadata references 'devx-track-azurepowershell', further reinforcing the Windows/PowerShell focus. There is no mention of Linux or cross-platform tooling, nor are there examples for Linux users.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell cmdlets for all operations, including preview registration, unregistration, and migration.
- Explicitly mention that all features and scripts are available cross-platform, and clarify any platform-specific requirements.
- Include Bash/Linux shell script examples where relevant, especially for migration and automation scenarios.
- Balance tutorial and 'Next steps' links by including both PowerShell and Azure CLI/Bash-based guides.
- Update page metadata to reflect cross-platform support, not just Azure PowerShell.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In sections where command-line examples are provided, Azure PowerShell (a Windows-centric tool) is consistently presented before Azure CLI, and PowerShell-specific cmdlets are referenced for status checks even in the CLI section. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or workflows. The documentation assumes familiarity with PowerShell, which may disadvantage Linux users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- When referencing status checks or outputs, provide both Azure CLI and PowerShell equivalents, rather than only PowerShell cmdlets (e.g., use 'az feature show' for CLI status instead of 'Get-AzProviderFeature').
- Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide Bash shell snippets where appropriate.
- Consider including a short section or note for Linux users, clarifying that all portal and CLI steps are fully supported on Linux systems.
- Avoid assuming PowerShell as the default scripting environment; where scripting is discussed, offer Bash or shell script alternatives.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In all command-line example sections, Azure PowerShell is presented before Azure CLI, and PowerShell cmdlets are referenced multiple times (including for status checks, even in the CLI section). There are no explicit Linux-specific examples or mentions of Linux-native tools or shell environments. The documentation assumes familiarity with PowerShell and the Azure Portal, both of which are more commonly used by Windows administrators. There are no Bash or Linux shell script examples, and the CLI output references PowerShell cmdlets for status checks, which may confuse Linux users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- In CLI sections, use only Azure CLI commands for all steps, including status checks (replace 'Get-AzProviderFeature' with 'az feature show' or similar).
- Explicitly mention that Azure CLI commands work cross-platform (Linux, macOS, Windows) and provide Bash-friendly syntax where appropriate.
- Add examples or notes for Linux users, such as running Azure CLI in Bash or using shell scripting for automation.
- Avoid referencing PowerShell cmdlets in CLI sections; keep each section self-contained and relevant to the tool/environment.
- Consider including a table or section summarizing parity between PowerShell and CLI commands, clarifying cross-platform support.
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
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Powershell bias by exclusively referencing Azure PowerShell scripts and cmdlets for migration and preview registration/unregistration tasks. There are no Bash, Linux shell, or cross-platform CLI examples provided, despite Azure CLI being cross-platform. The only automation tooling mentioned is PowerShell, and the tutorial link also points to a PowerShell-based walkthrough. No Linux-specific or neutral (Bash) examples are given.
Recommendations
- Provide equivalent Azure CLI (bash/shell) command examples alongside PowerShell commands for all tasks, especially for migration and preview registration/unregistration.
- Include links to tutorials or walkthroughs that use Azure CLI in Bash or cross-platform environments, not just PowerShell.
- When referencing scripts or automation, mention both PowerShell and Bash/CLI options, or clarify when a task is only possible in PowerShell.
- Ensure that documentation language and examples are inclusive of both Windows and Linux users by alternating or combining examples where appropriate.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows by providing only PowerShell commands (specifically Remove-AzResourceGroup) for resource cleanup, referencing IIS (a Windows web server) as the default backend and validation method, and omitting equivalent Linux/CLI examples for these steps. No Linux-native tools or instructions are provided for validation or resource management.
Recommendations
- Provide Azure CLI examples alongside PowerShell for resource group deletion (e.g., az group delete --name <group-name>).
- Include instructions for deploying and validating with a Linux-based web server (such as Nginx or Apache) on the backend VMs, or clarify how to adapt the template for Linux VMs.
- Offer browser-based validation instructions that are OS-agnostic, or explicitly mention that the validation step works regardless of backend OS.
- Where possible, avoid assuming the use of Windows-specific tools (like IIS) and provide parity for Linux users in both deployment and validation steps.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI in tabbed sections, referencing PowerShell-specific cmdlets (e.g., Get-AzProviderFeature) even in CLI sections, and omitting explicit Linux shell or Bash examples. The use of PowerShell is emphasized, and there is no mention of Linux-specific tools, shell environments, or command-line nuances that would assist Linux users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially since CLI is cross-platform and more common on Linux.
- Ensure that all CLI output and instructions are shown using native az CLI commands, not PowerShell cmdlets, in CLI sections.
- Add explicit Bash or Linux shell examples where relevant, such as using az CLI in Bash, and clarify any OS-specific steps or differences.
- Mention that Azure CLI works natively on Linux/macOS and provide links or notes for Linux users where appropriate.
- Avoid assuming the use of PowerShell as the default scripting environment; clarify that both PowerShell and Bash are supported.
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 featuring Azure PowerShell commands and referencing the PowerShell Gallery for migration scripts, with no mention of Bash, Linux, or cross-platform alternatives. The command-line examples use PowerShell cmdlets (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature), and the migration tooling is described as a PowerShell script. There are no Bash/Azure CLI (az) examples or explicit Linux instructions, and the PowerShell approach is presented as the default/only method.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell commands, especially for registration/unregistration and migration tasks.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- If migration scripts are only available in PowerShell, offer Bash or Python alternatives, or clarify cross-platform usage (e.g., using PowerShell Core on Linux).
- Ensure that documentation and tutorials reference both PowerShell and CLI approaches equally, or at least indicate parity.
- Add explicit Linux/macOS instructions or notes where relevant, especially for command-line operations.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows by providing only PowerShell commands for resource cleanup and configuring backend VMs with IIS (a Windows web server). There are no Linux/CLI/bash examples for resource deletion or for validating the deployment using a Linux-based web server, and the backend pool is implicitly Windows-centric.
Recommendations
- Provide equivalent Azure CLI (bash) commands for resource cleanup, such as 'az group delete'.
- Include instructions or a note on how to use a Linux-based web server (e.g., Nginx or Apache) in the backend pool, or link to a Linux VM template.
- When referencing PowerShell, always offer a CLI/bash alternative in parallel.
- Avoid assuming IIS as the default test workload; offer both Windows (IIS) and Linux (Nginx/Apache) validation steps.
- Explicitly mention cross-platform options in all procedural steps, especially for common operations like resource deletion.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell example for resource cleanup, referencing IIS (a Windows-only web server) for validation, and omitting Linux/CLI-based alternatives for key steps. No Linux-native tools or commands are mentioned, and the validation process assumes Windows VMs and tooling.
Recommendations
- Provide equivalent Azure CLI and/or Bash examples for resource cleanup (e.g., az group delete).
- Include instructions for deploying and validating with a Linux-based web server (such as Nginx or Apache) on the backend VMs.
- Offer both Windows and Linux VM configuration options in the ARM template or as selectable parameters.
- When referencing tools (like IIS), clarify that it is a Windows example and provide a parallel Linux example.
- Ensure that all critical steps (deployment, validation, cleanup) have both Windows and Linux command-line options presented side-by-side or in tabs.
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
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration tasks, with no equivalent Bash or Linux shell examples. The use of 'Set-AzContext', 'Get-AzProviderFeature', and 'Register-AzProviderFeature' are PowerShell-specific and the only code blocks provided are in PowerShell syntax. There is no mention of Linux-native tools or cross-platform command-line alternatives, and the PowerShell approach is presented as the default or only method for several operations.
Recommendations
- Provide equivalent Azure CLI (az) commands in Bash syntax for all PowerShell examples, especially for migration and feature registration/unregistration.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Include links or references to Linux/macOS setup guides for Azure CLI and relevant tools.
- Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash alternatives side-by-side.
- Review tutorial and next steps links to ensure Linux users are equally supported (e.g., link to CLI-based tutorials, not just PowerShell).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by consistently presenting Azure PowerShell instructions before Azure CLI, and by referencing PowerShell-specific cmdlets for status checks even in CLI sections. There are no explicit Linux or Bash shell examples, and the CLI output examples reference PowerShell cmdlets rather than native CLI commands. The documentation does not mention or illustrate Linux-specific tools, shell environments, or scripting approaches, which may disadvantage Linux users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially in sections likely to be used by Linux administrators.
- Ensure that CLI output examples use native Azure CLI commands (e.g., 'az feature show') rather than PowerShell cmdlets, and provide sample outputs for both.
- Add explicit Bash shell examples for common tasks, such as feature registration and status checks, to support Linux users.
- Reference cross-platform scripting approaches (e.g., Bash, Cloud Shell) where appropriate, and clarify that both PowerShell and CLI are available in Azure Cloud Shell.
- When listing tools or methods, avoid always listing PowerShell first; alternate or clarify that order does not imply preference.
- Include notes or links to Linux-specific guidance or troubleshooting where relevant.
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
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration, without providing equivalent Azure CLI (cross-platform) or Bash examples. The only command-line examples use PowerShell syntax, and the migration script is specifically described as a PowerShell script. There is no mention of Linux-specific tools, nor are cross-platform alternatives (such as Bash or native Azure CLI commands) presented alongside or before the PowerShell examples.
Recommendations
- Provide Azure CLI (bash/shell) examples alongside all PowerShell commands, especially for migration and preview registration/unregistration.
- Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- If migration scripts are only available in PowerShell, offer equivalent scripts or guidance for Bash or Python where possible.
- In 'Next steps', include links to tutorials or modules that use Azure CLI and/or Bash, not just PowerShell.
- Review and update language to avoid implying PowerShell is the default or only supported automation tool.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions and references before Azure CLI in all relevant sections. PowerShell is a Windows-centric tool, and its precedence over CLI (which is cross-platform and more common on Linux/macOS) may disadvantage Linux users. Additionally, there are no explicit Linux-specific examples or screenshots, and the use of PowerShell cmdlets as the primary scripting example further reinforces the Windows-first approach.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell in all sections, as CLI is cross-platform and preferred by many Linux users.
- Include explicit notes or examples for Linux/macOS environments, such as shell commands or terminal screenshots.
- Where scripting is shown, provide Bash or shell script equivalents to PowerShell cmdlets.
- Clarify that both Azure CLI and PowerShell are supported on all platforms, and link to installation guides for each.
- Ensure screenshots and UI walkthroughs do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows by providing only a PowerShell example for resource cleanup (Remove-AzResourceGroup), referencing IIS (a Windows web server) as the default backend for validation, and omitting Linux/CLI alternatives for these steps. There are no Linux-specific examples or mentions of Linux tools for validation or resource management.
Recommendations
- Provide equivalent Azure CLI commands for resource group deletion (e.g., az group delete --name <resource group name>), which work cross-platform.
- Include instructions or examples for validating the deployment using a Linux-based backend (such as Apache or Nginx) in addition to IIS.
- When referencing backend VMs, clarify that Linux VMs can be used and provide sample scripts or guidance for setting up a simple web server on Linux.
- Ensure that all PowerShell examples are paired with Azure CLI equivalents, and present both options side-by-side or in parallel sections.
- Avoid assuming IIS as the default test method; offer browser-based or curl-based validation steps that are OS-agnostic.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation presents Azure PowerShell examples and references before Azure CLI, and uses PowerShell-specific cmdlets for status checks even in CLI sections. There are no explicit Linux/Bash shell examples, and the workflow assumes familiarity with PowerShell. The Azure Portal is also emphasized, which is platform-neutral but often associated with Windows-centric workflows. No Linux-specific tools, commands, or screenshots are provided.
Recommendations
- Ensure that CLI (az) examples are fully self-contained and do not reference PowerShell cmdlets (e.g., use 'az feature show' instead of 'Get-AzProviderFeature' in CLI sections).
- Provide Bash/Linux shell command examples alongside or before PowerShell, especially for status checks and scripting scenarios.
- Include explicit notes or sections for Linux/macOS users, clarifying that all CLI commands work cross-platform and providing sample shell commands where appropriate.
- Where screenshots or UI steps are shown, consider including CLI/Bash alternatives for parity.
- Review and update output examples to match the tool being demonstrated (e.g., show 'az' output in CLI sections, not PowerShell output).
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
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing migration and registration/unregistration examples exclusively using Azure PowerShell cmdlets (e.g., Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature), which are primarily associated with Windows environments. There are no equivalent Bash or cross-platform Azure CLI examples, and the only tutorial linked is for PowerShell. The documentation does not mention or provide Linux-native workflows or examples, nor does it clarify cross-platform compatibility for the provided commands.
Recommendations
- Provide equivalent Azure CLI (bash) examples for all PowerShell scripts and registration/unregistration steps, ensuring Linux and macOS users have clear guidance.
- Explicitly mention when a command is cross-platform, and clarify any platform-specific requirements.
- Include links to tutorials and documentation that use Azure CLI and/or ARM templates, not just PowerShell.
- Balance references to PowerShell and CLI in both text and linked resources, ensuring neither is prioritized without justification.
- Add a section or note highlighting cross-platform management options for Azure Application Gateway, including Linux/macOS support.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only a PowerShell command for resource cleanup, referencing IIS (a Windows-only web server) for validation, and not offering Linux/CLI alternatives for these steps. There are no examples or guidance for users on Linux systems, and the validation step assumes a Windows environment.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell examples, especially for resource cleanup (e.g., az group delete).
- Include instructions for validating the deployment using a Linux-based web server (such as Nginx or Apache) in the backend VMs, or clarify how to adapt the template for Linux VMs.
- Offer both Windows and Linux examples side-by-side where possible, especially in testing and validation steps.
- Explicitly mention that the template deploys Windows VMs with IIS, and provide a link or alternative template for deploying Linux VMs if appropriate.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only PowerShell commands for resource cleanup and configuring backend virtual machines with IIS (a Windows web server). There are no Linux-specific examples, such as using Azure CLI for cleanup or deploying Linux-based backend VMs (e.g., with Nginx or Apache). The only command-line example is PowerShell, and the backend validation relies on IIS, which is Windows-specific.
Recommendations
- Include Azure CLI examples for resource cleanup (e.g., az group delete) alongside or before PowerShell commands.
- Provide instructions or template modifications for deploying Linux-based backend VMs (e.g., Ubuntu with Nginx or Apache) in addition to Windows/IIS.
- Show how to validate the deployment using a Linux-based web server (e.g., by browsing to a default Nginx/Apache page).
- When referencing command-line tools, present cross-platform options (CLI and PowerShell) or clearly indicate which is platform-specific.
- Consider alternating the order of examples or providing parallel instructions for both Windows and Linux users.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets for status checks (even in CLI sections), and omitting explicit Linux or Bash shell examples. The workflow and screenshots are oriented toward the Azure Portal UI, which is platform-agnostic, but the command-line guidance prioritizes Windows-native tools and patterns.
Recommendations
- Present Azure CLI (cross-platform) instructions before or alongside PowerShell examples to avoid implying Windows-first workflows.
- In CLI sections, use 'az' commands exclusively for both registration and status checks, rather than referencing PowerShell cmdlets for status.
- Include explicit Bash or shell script examples for Linux users, especially for automation scenarios.
- Where possible, clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide sample shell prompts (e.g., $ for Bash, PS> for PowerShell) to reinforce cross-platform applicability.
- Add links or references to Linux-specific guidance for related tasks (e.g., using Azure CLI on Linux, installing prerequisites, troubleshooting).