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 651-675 of 981 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page frequently references Azure PowerShell scripts as the primary migration tooling, without mentioning Azure CLI or Bash alternatives. All migration automation examples and scripts are PowerShell-based, and there is no guidance for Linux/macOS users or parity in scripting options. This creates friction for non-Windows users, as PowerShell is not always installed or preferred on Linux/macOS, and Azure CLI is a common cross-platform tool.
Recommendations
- Provide equivalent Azure CLI/Bash scripts for migration tasks, especially for public IP retention and configuration migration.
- Explicitly mention that PowerShell scripts can be run cross-platform (on Linux/macOS) if applicable, and link to installation instructions.
- Add examples or guidance for Linux/macOS users, including any prerequisites or differences in script execution.
- Where possible, offer both PowerShell and Azure CLI options for key migration steps.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent example for Azure CLI, Bash, or other cross-platform tools. It also references Excel and Visual Studio-based log converter tools, which are Windows-centric, without mentioning Linux/macOS alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Windows-based tools.
Recommendations
- Add equivalent Azure CLI (az) commands for enabling diagnostic logging, as Azure CLI is cross-platform.
- Mention or provide Bash scripts or REST API examples for enabling diagnostic logging.
- When referencing log analysis, suggest cross-platform tools (e.g., jq, pandas, or open-source CSV viewers) in addition to Excel.
- If referencing log converter tools, note if they are cross-platform or provide alternatives for Linux/macOS users.
- Clarify that PowerShell Core is available cross-platform, if that is the intended usage, or link to installation instructions.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts as the primary or only migration tooling. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools, nor is it clarified whether the PowerShell scripts are compatible with PowerShell Core on Linux/macOS. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration tasks where possible.
- Clarify whether the referenced PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide installation guidance if so.
- Add explicit examples or links for Linux/macOS users, such as Bash scripts or instructions for running PowerShell scripts cross-platform.
- Mention Azure Portal or ARM template options for migration steps, if available, as these are platform-agnostic.
Application Gateway
Configure Azure Application Gateway TCP/TLS proxy
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by exclusively using Windows Server as the SQL backend, referencing SQL Server Management Studio (a Windows-only tool) for client connectivity, and omitting Linux-based alternatives or examples. There are no instructions for deploying a Linux SQL server or connecting from Linux/macOS clients, which may hinder users on those platforms.
Recommendations
- Provide examples for deploying SQL Server on Linux (e.g., Ubuntu VM with SQL Server 2022).
- Include instructions for connecting to the SQL server using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible clients.
- Mention that SQL Server is available on Linux and clarify any limitations or differences in configuration.
- Add screenshots or command-line examples relevant to Linux/macOS environments.
- Ensure that backend pool configuration steps are generic and not tied to Windows-specific VM images.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page includes a 'Next steps' section that links only to a PowerShell-based tutorial for creating an autoscaling, zone redundant application gateway. No equivalent Linux/macOS CLI (Azure CLI or ARM template) example is provided or referenced. This creates friction for users on non-Windows platforms, as PowerShell is not the default or preferred tool for many Linux/macOS administrators.
Recommendations
- Add links to tutorials or examples using Azure CLI (az) and/or ARM templates for creating autoscaling, zone redundant application gateways.
- Ensure that PowerShell and Azure CLI examples are presented together, or Azure CLI is mentioned first, to avoid Windows-first bias.
- Explicitly state that PowerShell is cross-platform, but provide CLI alternatives for Linux/macOS users.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Azure PowerShell scripts for migration, with all examples, installation instructions, and script usage shown exclusively in PowerShell syntax. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The guidance assumes users are comfortable with PowerShell and Windows tooling, which creates friction for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, or explicitly state if PowerShell is required.
- Add Bash/Linux/macOS installation and execution instructions for the migration scripts, including how to use PowerShell Core (pwsh) on non-Windows platforms.
- Clarify script compatibility with PowerShell Core and cross-platform environments; if scripts are Windows-only, state this clearly.
- Offer downloadable scripts or containerized solutions that can be run from any OS, not just Windows.
- Include examples and guidance for running migration from Azure Cloud Shell (which supports Bash and PowerShell), highlighting cross-platform options.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS-compatible certificate creation methods. All code examples are PowerShell, and the prerequisites require an 'administrative Azure PowerShell session locally', which is typically Windows-centric. There are no Linux/macOS instructions or alternatives provided, creating friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI examples for all steps, as Azure CLI is cross-platform and works natively on Linux/macOS.
- Provide instructions for creating self-signed certificates using OpenSSL, which is available on Linux/macOS.
- Clarify that Azure PowerShell can be installed and run on Linux/macOS (via PowerShell Core), and provide installation guidance for those platforms.
- Consider including Bash shell examples alongside PowerShell, or link to Linux/macOS-specific tutorials.
- Mention any limitations or differences for Linux/macOS users explicitly in the prerequisites section.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 includes several references to Azure PowerShell scripts and cmdlets, especially for migration and preview registration/unregistration. While Azure CLI is mentioned, the examples provided use PowerShell cmdlets (e.g., Set-AzContext, Get-AzProviderFeature), which are not native to Linux/macOS and may require additional setup. There are no Bash or cross-platform CLI examples, and the 'Next steps' section links to a PowerShell-based tutorial. This creates friction for Linux/macOS users who may prefer or expect Azure CLI/Bash examples.
Recommendations
- Provide Azure CLI (az) command examples alongside or instead of Azure PowerShell cmdlets, especially for common tasks like migration and feature registration.
- Clearly indicate when a script or example is PowerShell-only, and offer Bash/CLI equivalents where possible.
- In the 'Next steps' section, include links to tutorials that use Azure CLI or ARM templates, not just PowerShell.
- Where possible, use cross-platform tools and patterns in examples to ensure parity for Linux/macOS users.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration instructions and examples primarily using Azure PowerShell, with CLI examples present but less detailed. PowerShell is a Windows-centric tool, and the 'Next steps' section directs users to a PowerShell-specific guide, potentially creating friction for Linux/macOS users. There is no mention of Linux-native tools or workflows (e.g., Bash scripting, OpenSSL usage for certificate management), and PowerShell examples are shown before CLI equivalents.
Recommendations
- Ensure parity between Azure PowerShell and Azure CLI instructions, providing equally detailed CLI examples for all configuration steps.
- Include explicit Linux/macOS workflows for certificate extraction and management, such as using OpenSSL commands.
- In 'Next steps', provide links to both PowerShell and CLI-based configuration guides, or a cross-platform guide.
- When listing configuration options (Portal, PowerShell, CLI), avoid listing PowerShell first unless it is the most widely used option for the audience.
- Add notes clarifying that all CLI commands are cross-platform and provide troubleshooting tips for Linux/macOS users where relevant.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page references Azure PowerShell in the 'Next steps' section as the only example for creating an autoscaling, zone-redundant Application Gateway. No equivalent Azure CLI or ARM template example is provided, which may create friction for Linux/macOS users who typically use CLI or templates rather than PowerShell.
Recommendations
- Add links or examples for creating an autoscaling, zone-redundant Application Gateway using Azure CLI.
- Include ARM/Bicep template instructions for cross-platform automation.
- Present PowerShell and CLI examples side-by-side, or clarify that PowerShell is available cross-platform.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily PowerShell-centric, with all migration scripts, examples, and instructions provided exclusively for Azure PowerShell. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. The documentation assumes the use of PowerShell modules and tools, which are native to Windows and require additional setup or workarounds on Linux/macOS. This creates friction for users on non-Windows platforms, as they must install PowerShell Core and manually adapt the instructions.
Recommendations
- Provide equivalent migration instructions and scripts for Azure CLI (az), which is cross-platform and natively supported on Linux/macOS.
- Include Bash or shell script examples where possible, especially for certificate handling and resource management.
- Explicitly document how to run PowerShell scripts on Linux/macOS using PowerShell Core, including installation steps and platform-specific caveats.
- Add a section comparing PowerShell and CLI approaches, and recommend the CLI for cross-platform users.
- Where scripts are only available in PowerShell, clarify this limitation and provide links or guidance for Linux/macOS users.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page for Azure Application Gateway v2 shows a moderate Windows/PowerShell bias. Migration guidance and registration/unregistration steps are provided exclusively using Azure PowerShell and Azure CLI commands, with no mention of Bash, Linux, or macOS-specific instructions. The primary tutorial linked is PowerShell-based, and there is no parity for Linux shell or cross-platform examples. However, the core product features are platform-agnostic, and most of the documentation is not inherently Windows-specific.
Recommendations
- Add equivalent Bash/Azure CLI examples for registration, unregistration, and migration steps.
- Provide links to tutorials using Bash or cross-platform Azure CLI, not just PowerShell.
- Clarify that Azure CLI commands can be run on Linux/macOS, and provide sample commands for those environments.
- When referencing scripts or automation, specify if they are PowerShell-only and offer alternatives for Bash users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions for enabling diagnostic logging on Azure Application Gateway using PowerShell, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The PowerShell method is presented before the Azure portal method, and there is no mention of Azure CLI or Bash scripting alternatives. This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer command-line tools native to their OS.
Recommendations
- Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Present both PowerShell and CLI examples side-by-side, or at least mention CLI alternatives and link to relevant documentation.
- Ensure that command-line instructions are not Windows-centric and clarify that PowerShell is optional, not required.
- Consider listing the Azure portal method first, as it is platform-neutral.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, such as configuration migration and public IP retention. There are no CLI (az CLI), Bash, or Linux/macOS-specific examples or guidance. The migration process is described almost exclusively in terms of PowerShell tooling, which is native to Windows and less commonly used on Linux/macOS. This creates friction for users on non-Windows platforms who may prefer or require cross-platform tools.
Recommendations
- Provide equivalent migration instructions and scripts using Azure CLI (az), which is fully cross-platform and widely used on Linux/macOS.
- Include Bash script examples or guidance for key migration steps, especially for public IP retention and configuration migration.
- Explicitly note PowerShell Core compatibility if scripts are cross-platform, or clarify Windows-only requirements.
- Add a section comparing PowerShell and Azure CLI approaches, and recommend the best option for Linux/macOS users.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The tutorial is heavily focused on Azure PowerShell and Windows tooling. All code examples use PowerShell cmdlets, and the creation of a self-signed certificate relies on the Windows-specific New-SelfSignedCertificate cmdlet. There are no CLI (az), Bash, or Linux/macOS-compatible instructions or alternatives provided. File paths and certificate management steps assume a Windows environment. This creates significant friction for Linux/macOS users, who may not have access to PowerShell or the same certificate tooling.
Recommendations
- Provide equivalent instructions and code samples using the Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
- For certificate creation, include OpenSSL-based instructions for Linux/macOS users alongside the PowerShell example.
- Use platform-agnostic file paths or clarify when a step is Windows-specific, and offer alternatives for other OSes.
- Add a note at the beginning clarifying that the tutorial is PowerShell-focused, and link to any available CLI or portal-based tutorials for Linux/macOS users.
- Where possible, structure examples so that Linux/macOS steps are presented alongside or before Windows-specific ones.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration instructions for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell examples and references. PowerShell instructions are presented first and in greater detail than Azure CLI, and the 'Next steps' section directs users to a PowerShell-specific guide. There are no explicit Linux/macOS shell examples (e.g., Bash), and the CLI instructions are minimal by comparison. This creates friction for Linux/macOS users who may prefer Bash or other non-Windows tools.
Recommendations
- Provide Bash examples for Azure CLI commands, including certificate management steps relevant to Linux/macOS environments.
- Ensure parity in example depth and clarity between PowerShell and CLI sections.
- In 'Next steps', include links to both PowerShell and CLI/Bash configuration guides.
- Clarify that PowerShell is cross-platform, but also highlight CLI/Bash workflows for Linux/macOS users.
- Add notes or sections on extracting and managing certificates using Linux tools (e.g., openssl) where relevant.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a detailed PowerShell example for enabling diagnostic logging but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line instructions are Windows-centric (PowerShell), and the referenced log converter tool is a .NET/C# utility, which is more familiar to Windows developers. There is no mention of Azure CLI, Bash, or cross-platform alternatives for enabling or managing diagnostic settings.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script snippets where appropriate, especially for tasks like downloading and converting logs.
- Reference cross-platform log conversion tools or provide instructions for using Python or other open-source utilities to process logs.
- Ensure that command-line instructions are presented for both PowerShell and Azure CLI, ideally with CLI examples shown first or side-by-side.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples, instructions, and tooling based on PowerShell. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. The documentation assumes users are familiar with PowerShell and does not mention or provide alternatives for those using Linux/macOS environments, despite Azure PowerShell being cross-platform. This creates friction for users who prefer or require Bash/CLI workflows.
Recommendations
- Add equivalent Azure CLI (az) commands and scripts for all migration steps, including resource ID retrieval, certificate management, and gateway creation.
- Explicitly state that Azure PowerShell is available on Linux/macOS and in Azure Cloud Shell, and provide instructions for installing/running PowerShell on those platforms.
- Provide Bash script examples or guidance for certificate handling and automation tasks where possible.
- Include a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
- Clarify any limitations or requirements for running the provided scripts on non-Windows platforms.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page includes a 'Next steps' section that links to a tutorial specifically for creating an autoscaling, zone redundant application gateway using Azure PowerShell. No equivalent Linux/macOS CLI (az CLI, Bash, etc.) example or tutorial is referenced, which may create friction for non-Windows users. The main content does not reference Windows-specific tools, but the PowerShell tutorial is highlighted before any cross-platform alternatives.
Recommendations
- Add links to tutorials or examples using Azure CLI (az), which is cross-platform and preferred by many Linux/macOS users.
- Ensure that any step-by-step guides for configuring autoscaling and zone redundancy are available for both PowerShell and Azure CLI.
- In the 'Next steps' section, present cross-platform options (Azure CLI, REST API, ARM templates) alongside PowerShell, or list Azure CLI first to avoid implicit Windows-first bias.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 demonstrates a moderate Windows/PowerShell bias. Migration guidance and preview registration/unregistration instructions are provided exclusively using Azure PowerShell commands, with no equivalent Azure CLI (bash) or ARM template examples. The primary tutorial linked is also PowerShell-focused, and there is no mention of Linux/macOS workflows or parity in command-line tooling.
Recommendations
- Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for migration and preview registration/unregistration steps.
- Include links to tutorials or quickstarts that use Azure CLI and ARM templates, not just PowerShell.
- Explicitly mention that all features and management operations are available cross-platform, and clarify any exceptions.
- Where possible, show both PowerShell and CLI examples side-by-side, or indicate which commands work on Linux/macOS.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, including configuration and public IP retention. There are no CLI (az), Bash, or Linux/macOS-specific migration instructions or examples provided. The exclusive focus on PowerShell may create friction for users on Linux or macOS platforms who prefer or require cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration steps, especially for configuration migration and public IP retention.
- Include Bash or shell script examples where appropriate, or clarify if PowerShell scripts are compatible with PowerShell Core on Linux/macOS.
- Explicitly mention cross-platform options and limitations, and link to relevant Linux/macOS documentation if available.
- Order migration tooling sections to present CLI and PowerShell options equally, or clarify if PowerShell is required and why.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The tutorial is heavily focused on Azure PowerShell, with all setup and configuration steps provided exclusively as PowerShell commands. It assumes the use of Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate) and file paths (e.g., c:\appgwcert.pfx), with no mention of Bash, Azure CLI, or Linux/macOS alternatives for certificate creation or resource management. There are no instructions or examples for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI (az) commands for all steps, especially for resource creation and management.
- Include instructions for generating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and explain how to export to PFX format.
- Use platform-agnostic file paths or clarify how to adapt file paths for non-Windows systems.
- Add a note at the beginning clarifying that the tutorial is PowerShell-focused, and link to a CLI-based or cross-platform version if available.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI, Bash, or Azure CLI instructions. The log converter tool referenced is a .NET/C# solution, which is more Windows-centric. There is no mention of Linux/macOS command-line workflows or tools, and PowerShell is presented as the sole scripting method for automation.
Recommendations
- Add equivalent Azure CLI (az) commands for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples for common log management tasks, such as downloading and converting logs.
- Reference or provide log converter tools that run natively on Linux/macOS (e.g., Python-based solutions), or clarify cross-platform usage of the existing .NET tool.
- Explicitly state that PowerShell examples are also available on Linux/macOS (if true), or link to cross-platform PowerShell installation guides.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides a link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, without mentioning or linking to equivalent instructions for Azure CLI, ARM templates, or Bicep. Azure PowerShell is most commonly used on Windows, and its exclusive mention may create friction for Linux/macOS users who typically use Azure CLI or other cross-platform tools.
Recommendations
- Add links or examples for creating autoscaling, zone-redundant Application Gateway using Azure CLI, ARM templates, or Bicep.
- Ensure that cross-platform tools are mentioned alongside PowerShell, or provide a section comparing approaches for different operating systems.
- In 'Next steps', include tutorials for Linux/macOS users or clarify that PowerShell can be used cross-platform (with installation instructions if necessary).
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples, instructions, and tooling based on PowerShell. There are no equivalent examples or guidance for Linux/macOS users who may prefer Bash, Azure CLI, or scripting in other environments. The documentation assumes the use of PowerShell and Windows-centric patterns throughout, which may create friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) examples for all migration steps, including resource ID retrieval, certificate management, and script execution.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and offer Bash/CLI instructions for users who choose that environment.
- Explicitly mention cross-platform compatibility of the provided PowerShell scripts, or offer alternative scripts in Bash or Python if possible.
- Add a section addressing Linux/macOS users, including prerequisites and environment setup for running migration scripts.
- Where PowerShell is required, note how to install and run PowerShell Core on Linux/macOS, and test scripts for compatibility.