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 676-700 of 981 flagged pages
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 as the primary migration tooling, with no mention of equivalent Azure CLI or ARM template approaches. All example scripts and automation guidance are PowerShell-based, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or examples, and no guidance for users who may prefer or require cross-platform tools.
Recommendations
- Add equivalent Azure CLI commands and scripts for migration tasks, including public IP retention and configuration migration.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links or examples.
- Clarify whether ARM templates or REST API can be used for migration, and provide sample templates or API calls if possible.
- Where PowerShell scripts are referenced, note any cross-platform compatibility (e.g., PowerShell Core on Linux/macOS) or provide alternatives.
- Ensure that troubleshooting and support instructions do not assume Windows/PowerShell usage only.
Create Pull Request
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 shows a notable bias toward Windows/PowerShell tooling. Migration and preview registration/unregistration instructions are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI (bash/zsh) or ARM template alternatives. The main tutorial linked is PowerShell-based, and there are no Linux/macOS-specific examples or guidance. This creates friction for users on non-Windows platforms who may prefer or require cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (bash/zsh) commands for all PowerShell instructions, especially for migration and preview registration/unregistration.
- Link to or create tutorials using Azure CLI and ARM templates for creating and managing Application Gateway v2.
- When referencing scripts or automation, clarify platform compatibility and offer alternatives for Linux/macOS users.
- Ensure that examples and walkthroughs are not exclusively PowerShell-based, and consider showing CLI examples first or side-by-side.
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
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation and resource management. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. Windows tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) are used for certificate creation, which are not available on Linux/macOS. This creates friction for non-Windows users, who must find alternative methods to complete key steps.
Recommendations
- Provide equivalent Azure CLI (az) commands for all resource management steps, as Azure CLI is cross-platform.
- Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting to PFX format.
- Add notes or links for Linux/macOS users on how to adapt PowerShell-specific steps, or reference cross-platform PowerShell (pwsh) usage.
- Consider reordering examples so that cross-platform methods (Azure CLI, OpenSSL) are shown first or alongside PowerShell.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation heavily references Azure PowerShell scripts as the primary (and seemingly only) migration tooling, with no mention of Azure CLI, Bash, or cross-platform alternatives. All migration automation examples and scripts are PowerShell-based, and there are no Linux/macOS-specific instructions or parity guidance. This creates friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration steps, or clearly state if they are not available.
- Add Bash/shell script examples or guidance for Linux/macOS users where possible.
- Explicitly mention platform requirements for the PowerShell scripts (e.g., if they require Windows PowerShell or can run in PowerShell Core on Linux/macOS).
- Link to or document any cross-platform migration tooling, or provide a roadmap for parity.
- If PowerShell is the only supported method, acknowledge this limitation and suggest workarounds (e.g., using Azure Cloud Shell, which supports PowerShell and Bash).
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 using Azure PowerShell for creating an autoscaling, zone redundant application gateway. No equivalent example or guidance is provided for Linux/macOS users (e.g., Azure CLI, ARM templates, or Bicep). Azure PowerShell is typically associated with Windows environments, and its mention without parity for cross-platform tools may create friction for non-Windows users.
Recommendations
- Add links or examples for creating autoscaling, zone redundant application gateways using Azure CLI, ARM templates, or Bicep, which are cross-platform and commonly used on Linux/macOS.
- In the 'Next steps' section, provide parallel tutorials for Azure CLI and/or ARM/Bicep to ensure Linux/macOS users have clear guidance.
- Explicitly note that Azure PowerShell is available cross-platform, but highlight alternatives for users who prefer CLI or template-based workflows.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides explicit instructions for enabling diagnostic logging using PowerShell, with no equivalent CLI, Bash, or Linux/macOS example. The PowerShell method is presented before the Azure portal method, and there is no mention of Azure CLI or REST API alternatives, which are cross-platform. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Add equivalent instructions and examples for enabling diagnostic logging using Azure CLI (az monitor diagnostic-settings) and/or REST API, which are cross-platform.
- Present cross-platform methods (CLI, REST API) before or alongside PowerShell examples to avoid Windows-first bias.
- Explicitly state that PowerShell is one option and provide guidance for Linux/macOS users.
- Include Bash or shell script examples where appropriate.
- Add a note clarifying that PowerShell Core is available cross-platform, if relevant, but still provide CLI examples.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and downloadable tools provided exclusively in PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS usage patterns or prerequisites addressed. The documentation assumes the user is familiar with PowerShell and Windows-centric tooling, which creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash scripting.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning and IP retention.
- Add explicit instructions and examples for running migration from Linux/macOS environments, including use of Azure Cloud Shell (Bash) and Azure CLI.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (Bash) or only in PowerShell, and if so, provide guidance for Linux/macOS users.
- List prerequisites for Linux/macOS environments, such as installation of Azure CLI and authentication steps.
- Where possible, offer downloadable Bash scripts or cross-platform alternatives alongside PowerShell scripts.
- Reorder examples so that cross-platform (Azure CLI/Bash) instructions are presented before or alongside PowerShell examples.
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
Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 shows a moderate Windows/PowerShell bias. Migration guidance and preview registration/unregistration are provided exclusively with Azure PowerShell commands, without equivalent Azure CLI (cross-platform) or Bash examples. The main tutorial link is also PowerShell-focused. This creates friction for Linux/macOS users who may prefer or require CLI/Bash instructions.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell commands for migration and preview registration/unregistration steps.
- Provide links to tutorials using Azure CLI or ARM templates, not just PowerShell.
- Ensure that all procedural instructions are available in cross-platform formats, especially for critical operations like migration.
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 exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation, resource management, and file paths. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. Windows tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) are used for certificate creation, which are not available on Linux/macOS by default.
Recommendations
- Provide equivalent Azure CLI (az) commands for all resource creation and management steps.
- Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting them to PFX format.
- Use platform-neutral file paths in examples, or note differences for Linux/macOS.
- Add a section clarifying cross-platform options and limitations, with links to relevant Linux/macOS documentation.
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 for creating an autoscaling, zone redundant application gateway using Azure PowerShell, but does not provide equivalent guidance or links for Linux/macOS users (e.g., Azure CLI or ARM templates). The only example for creating the gateway is PowerShell-focused, which is most commonly used on Windows.
Recommendations
- Add equivalent tutorials or links for creating autoscaling, zone redundant application gateways using Azure CLI and ARM templates.
- Ensure that examples and walkthroughs are provided for both PowerShell and CLI, and consider listing CLI examples first or side-by-side to avoid implicit Windows-first bias.
- Explicitly mention cross-platform options for management (e.g., Azure CLI, REST API) in relevant sections.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides explicit instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent examples for Azure CLI, Bash, or other cross-platform tools. PowerShell is Windows-centric, and its use is presented before any mention of platform-neutral alternatives. There are no Linux/macOS-specific instructions or CLI examples, which may create friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Clarify that PowerShell is one option and provide links or inline instructions for Bash/CLI users.
- Consider including sample scripts for log retrieval and analysis using platform-neutral tools (e.g., jq, awk, Azure CLI).
- Mention that the Azure portal is accessible from any OS and highlight its parity.
- If referencing log converter tools, note their compatibility or 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, instructions, and downloadable tools provided exclusively in PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell equivalents or guidance. The installation and usage instructions assume a Windows/PowerShell environment and do not address how Linux/macOS users can perform the migration or run the scripts.
Recommendations
- Provide equivalent migration instructions and scripts using Azure CLI and/or Bash for Linux/macOS users.
- Explicitly document how to run the PowerShell scripts in cross-platform environments, such as via PowerShell Core (pwsh) on Linux/macOS, including prerequisites and troubleshooting tips.
- Add examples for Azure CLI commands to retrieve resource IDs and manage certificates, as alternatives to PowerShell.
- Clarify whether the provided scripts are compatible with PowerShell Core and, if so, include installation and usage steps for Linux/macOS.
- If some migration steps are only possible via PowerShell, state this explicitly and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell, which supports PowerShell in-browser).
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
Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 shows 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 REST API examples. The main tutorial link points to a PowerShell-based workflow. This creates friction for Linux/macOS users who may prefer bash/CLI or other cross-platform tools.
Recommendations
- Add Azure CLI (bash) examples alongside PowerShell for migration and preview registration/unregistration steps.
- Provide REST API or ARM template alternatives for key operations.
- Ensure tutorial links include both PowerShell and Azure CLI workflows.
- Explicitly mention that all commands can be run from Azure Cloud Shell (which supports both bash and PowerShell), and clarify platform-neutral options.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation repeatedly references an Azure PowerShell script as the primary or sole migration tool, without mentioning Azure CLI, Bash, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the PowerShell script is referenced as the default approach for migration tasks.
Recommendations
- Provide equivalent Azure CLI commands or scripts for migration tasks, or clarify if only PowerShell is supported.
- Explicitly state platform compatibility for the PowerShell script (e.g., if it works with PowerShell Core on Linux/macOS).
- Add Linux/macOS usage examples or troubleshooting notes for non-Windows users.
- If PowerShell is the only supported method, clarify this and provide installation guidance for PowerShell Core on Linux/macOS.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides explicit instructions for enabling diagnostic logging using PowerShell, but does not offer equivalent examples for Azure CLI, Bash, or other cross-platform tools. The PowerShell method is presented before the Azure portal method, and no Linux/macOS command-line alternatives are mentioned. This creates friction for users who do not use Windows or PowerShell.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging alongside the PowerShell example.
- Present cross-platform command-line options (such as Bash/CLI) before or alongside PowerShell to avoid Windows-first bias.
- Explicitly mention that both PowerShell and Azure CLI can be used, and link to relevant CLI documentation.
- Include notes or examples for Linux/macOS users where applicable.
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 is generally platform-neutral in its conceptual sections, but the 'Next steps' section prominently features a tutorial link that uses Azure PowerShell for creating an autoscaling, zone-redundant Application Gateway. This may suggest a Windows-first approach and PowerShell-heavy bias, as Linux/macOS users typically use Azure CLI or ARM templates. No Linux/macOS-specific examples or alternatives are mentioned.
Recommendations
- Add links to equivalent tutorials using Azure CLI and ARM/Bicep templates for creating autoscaling, zone-redundant Application Gateways.
- In the 'Next steps' section, present Azure CLI and template-based options alongside PowerShell, or mention that PowerShell is cross-platform but CLI is preferred on Linux/macOS.
- Clarify that PowerShell is available on Linux/macOS, or provide guidance for non-Windows users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation repeatedly references an Azure PowerShell script as the primary or sole migration tool for moving from Application Gateway V1 to V2. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools. The PowerShell script is mentioned as the main automation method, and there is no mention of Linux/macOS compatibility or alternatives, which may create friction for non-Windows users.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for migration tasks, or explicitly state if only PowerShell is supported.
- Clarify whether the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS) and provide installation guidance if so.
- If only PowerShell is supported, offer guidance or workarounds for Linux/macOS users, such as using Azure Cloud Shell.
- Add notes or links to documentation for running Azure PowerShell on non-Windows platforms.
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
Windows First
Missing Linux Example
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts, with all migration steps, examples, and code snippets provided exclusively in PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are there instructions or examples for Linux/macOS users. The guidance assumes familiarity with PowerShell and Windows-centric tooling, which may create friction for users on non-Windows platforms.
Recommendations
- Provide equivalent migration instructions and examples using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
- Include Bash script examples for common operations, such as retrieving resource IDs, uploading certificates, and running migration scripts.
- Clarify whether the provided PowerShell scripts can be run in Azure Cloud Shell (which supports PowerShell and Bash) and, if so, provide explicit instructions for both environments.
- Add a section addressing Linux/macOS users, including prerequisites for running PowerShell Core on those platforms if PowerShell scripts are required.
- Where possible, link to or provide alternative tooling or scripts for users who prefer not to use PowerShell.
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
Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 shows a notable Windows bias. Migration guidance and preview registration/unregistration instructions are provided exclusively using Azure PowerShell commands, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The main tutorial linked is PowerShell-based, and PowerShell is mentioned before any cross-platform alternatives. This creates friction for users on Linux or macOS who may prefer or require Azure CLI or Bash.
Recommendations
- Add Azure CLI and Bash examples for all PowerShell commands, especially for migration and preview registration/unregistration.
- Link to tutorials that use Azure CLI or Bash, or provide parity for the PowerShell tutorial.
- Explicitly note that both PowerShell and Azure CLI are supported and provide guidance for choosing the right tool based on OS.
- Ensure that future documentation sections do not default to PowerShell-only unless the feature is Windows-specific.
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 Linux/macOS users (e.g., Azure CLI, ARM templates, or Terraform). This suggests a bias toward Windows/PowerShell tooling and may create friction for users on other platforms.
Recommendations
- Add links or sections for creating autoscaling, zone-redundant Application Gateway using Azure CLI, which is cross-platform.
- Include references to ARM template or Bicep deployment methods for infrastructure-as-code parity.
- Ensure that Linux/macOS users are aware of alternative tools and provide examples or tutorials for those platforms.
- When listing tutorials, present cross-platform options first or together, rather than PowerShell-only.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides explicit instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). The PowerShell method is presented before the Azure portal method, and no Linux-friendly command-line alternatives are shown. The log converter tool referenced is C#/.NET-based, which may be less accessible for non-Windows users.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Present command-line examples for both PowerShell and Azure CLI side-by-side, or indicate which platforms each method supports.
- Reference log conversion tools or scripts that work natively on Linux/macOS (e.g., Python-based converters) in addition to the C#/.NET tool.
- Clarify that PowerShell Core is available cross-platform, if relevant, and provide installation guidance for non-Windows users.
- Ensure that screenshots and instructions for the Azure portal are platform-neutral.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation heavily references Azure PowerShell scripts for migration tasks, including configuration migration and public IP retention. There are no examples or guidance for users who may prefer or require Azure CLI, Bash, or other cross-platform tools. The exclusive mention of PowerShell and lack of Linux/macOS-specific instructions or parity creates friction for non-Windows users.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for all migration steps currently covered only by PowerShell.
- Explicitly state platform compatibility for the PowerShell scripts (e.g., if they work in PowerShell Core on Linux/macOS).
- Add Bash or cross-platform scripting examples where possible, or link to relevant Azure CLI documentation.
- Clarify any limitations or requirements for Linux/macOS users in the migration process.
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
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell scripts and commands, with all migration tooling, examples, and instructions provided exclusively in Azure PowerShell syntax. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific usage patterns or considerations addressed. The documentation assumes the use of PowerShell (including local PowerShell environments and modules), which is natively available only on Windows and requires extra setup on Linux/macOS. This creates friction for non-Windows users and may hinder their ability to follow the migration process smoothly.
Recommendations
- Provide equivalent Azure CLI scripts and examples for all migration steps, including configuration cloning and IP retention.
- Explicitly state cross-platform compatibility for the provided PowerShell scripts (e.g., test and document usage in PowerShell Core on Linux/macOS).
- Include instructions for running the scripts in Azure Cloud Shell (which is cross-platform) and clarify any limitations or requirements.
- Add Bash/Azure CLI examples for common tasks such as retrieving resource IDs, managing certificates, and setting context.
- Mention prerequisites for Linux/macOS users (e.g., installing PowerShell Core, Az modules) and provide troubleshooting tips for non-Windows environments.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Application Gateway v2 exhibits a moderate Windows bias. Key migration and registration tasks reference Azure PowerShell scripts and cmdlets, with no mention of Linux/macOS alternatives or Azure CLI equivalents. The 'Next steps' section prioritizes a PowerShell-based tutorial, and the migration guidance is PowerShell-centric. While the core product is cross-platform, the documentation's operational guidance leans toward Windows tooling and patterns.
Recommendations
- Provide Azure CLI and/or REST API examples alongside PowerShell scripts for migration and registration tasks.
- Explicitly mention that Azure CLI is supported on Linux/macOS and provide sample commands for those platforms.
- Balance tutorial links to include both PowerShell and Azure CLI-based guides.
- Clarify any platform-specific requirements for scripts or tools, and offer alternatives where possible.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell-based workflows, with all migration scripts, examples, and installation instructions provided exclusively for PowerShell. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The use of PowerShell Gallery and PowerShell modules is assumed throughout, and the documentation does not mention or provide alternatives for users on Linux or macOS, nor does it clarify cross-platform compatibility of the scripts.
Recommendations
- Explicitly state whether the provided PowerShell scripts are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions for those platforms.
- Add equivalent Azure CLI (az) commands and workflows for key migration steps, or clarify if CLI-based migration is not supported.
- Include Bash or shell script examples for common tasks (e.g., fetching resource IDs, uploading certificates) where possible.
- Add a section addressing cross-platform usage, including any limitations or requirements for Linux/macOS users.
- If migration is only supported via PowerShell, clearly state this limitation up front and provide guidance for Linux/macOS users on how to use PowerShell Core or Azure Cloud Shell.