Document Details
Gateway Deploy Dual Stack Load Balancer
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation consistently presents PowerShell (a Windows-centric tool) examples before Azure CLI examples in every procedural section. This ordering and the heavy use of PowerShell may suggest a bias toward Windows users, even though all steps are also provided for Azure CLI (which is cross-platform). There are no Linux-specific tools or shell examples (e.g., Bash scripts), and no mention of Linux environments or considerations.
Recommendations
- Alternate the order of example tabs, sometimes presenting Azure CLI before PowerShell, or default to CLI as it is cross-platform.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell context where appropriate.
- Add a brief section or note for Linux users, clarifying that all CLI steps are fully supported on Linux and macOS.
- Consider including sample Bash scripts or guidance for automating these steps in Linux environments.
- Avoid implying PowerShell is the primary or preferred method unless there is a technical reason.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
 Clean
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Clean
|
Flagged Code Snippets
--- ## Add an IPv6 frontend to gateway load balancer Now that you've added IPv6 prefix ranges to your Gateway Load Balancer's subnet and virtual network, we can create a new IPv6 frontend configuration on the Gateway Load Balancer, with an IPv6 address from your subnet's range. # [PowerShell](#tab/powershell)
--- ## Add an IPv6 backend pool to gateway load balancer In order to distribute IPv6 traffic, you need a backend pool containing instances with IPv6 addresses. First, you create a backend pool on the Gateway Load Balancer. In the following step, you create IPv6 configurations to your existing backend NICs for IPv4 traffic, and attach them to this backend pool. # [PowerShell](#tab/powershell)
--- ## Add IPv6 configuration to network interfaces # [PowerShell](#tab/powershell)
--- ## Add a load balancing rule for IPv6 traffic Load balancing rules determine how traffic is routed to your backend instances. For Gateway Load Balancer, you create a load balancing rule with HA ports enabled, so that you can inspect traffic of all protocols, arriving on all ports. # [PowerShell](#tab/powershell)
--- ## Chain the IPv6 load balancer frontend to gateway load balancer In this final step, you'll chain your existing Standard Load Balancer's IPv6 frontend to the Gateway Load Balancer's IPv6 frontend. Now, all IPv6 traffic headed to your Standard Load Balancer's frontend is forwarded to your Gateway Load Balancer for inspection by the configured NVAs before reaching your application. # [PowerShell](#tab/powershell)