Nat Gateway

55
Total Pages
46
Linux-Friendly Pages
9
Pages with Bias
16.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

23 issues found
Showing 1-23 of 23 flagged pages
Nat Gateway Manage a Standard V2 NAT Gateway ...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides step-by-step instructions for managing a Standard V2 NAT Gateway using the Azure portal and Azure PowerShell. However, it does not include any examples or instructions for using the Azure CLI, which is cross-platform and widely used on Linux and macOS. All command-line examples are PowerShell-specific, and there is no mention of Bash, Azure CLI, or Cloud Shell Bash usage. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add Azure CLI (az) command examples for all operations currently shown with PowerShell, such as creating, associating, and deleting NAT gateways, and managing public IPs/prefixes.
  • Include a tab or section for Azure CLI alongside the existing Azure portal and Azure PowerShell tabs.
  • In the prerequisites, mention that Azure CLI can be used and provide installation or usage links for Linux/macOS users.
  • Where possible, clarify that Azure PowerShell can be run in Azure Cloud Shell (which supports Bash and PowerShell), but recommend Azure CLI for Linux/macOS parity.
GitHub Create Pull Request
Nat Gateway Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates ...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment instructions for both ARM and Bicep templates, but the primary ARM template deployment example is PowerShell-focused and uses Azure Cloud Shell with PowerShell commands. Azure CLI (cross-platform) is only shown for Bicep, and PowerShell is consistently presented first. There are no Linux-specific deployment examples for the ARM template path, and PowerShell is emphasized throughout.
Recommendations
  • Add Azure CLI examples for ARM template deployment alongside the PowerShell examples, since Azure CLI is cross-platform and widely used on Linux/macOS.
  • Present Azure CLI and PowerShell examples in parallel tabs for both ARM and Bicep sections, or default to CLI first for parity.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Ensure that any references to copying/pasting scripts or using the shell mention both Bash and PowerShell users.
GitHub Create Pull Request
Nat Gateway Troubleshoot Azure NAT Gateway ...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, particularly in troubleshooting and example sections. Windows tools (PsPing, PowerShell Invoke-WebRequest) are highlighted with direct links, while Linux equivalents are mentioned more generically and without links. Some troubleshooting steps (e.g., resolving failed network interfaces) provide detailed PowerShell instructions but lack equivalent Linux CLI or Azure CLI examples, making it harder for Linux/macOS users to follow along.
Recommendations
  • Provide Azure CLI or REST API examples alongside PowerShell for resource management and troubleshooting tasks, especially for resolving failed states.
  • Include direct links to Linux tool documentation (e.g., nc, curl) similar to those provided for Windows tools.
  • Ensure troubleshooting steps are platform-neutral or explicitly offer both Windows and Linux/macOS procedures.
  • Present Linux and Windows examples side-by-side, rather than listing Windows tools first.
  • Clarify that Azure Resource Explorer and portal-based steps are OS-agnostic, and avoid browser recommendations that imply Windows preference (e.g., 'recommended to use Microsoft Edge browser').
GitHub Create Pull Request
Nat Gateway Manage a Standard V2 NAT Gateway ...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed step-by-step instructions and code samples exclusively for the Azure portal and Azure PowerShell, with no mention or examples for Azure CLI, Bash, or other Linux/macOS-native tools. All command-line automation is shown using PowerShell cmdlets, which are Windows-centric, though PowerShell Core is cross-platform. There is no guidance for users who prefer or require Linux-native workflows.
Recommendations
  • Add equivalent Azure CLI examples for all operations (create, update, remove NAT gateway, manage IPs/prefixes).
  • Explicitly mention that PowerShell Core is available cross-platform, but also provide Bash/Azure CLI commands for parity.
  • Consider including a tab for 'Azure CLI' alongside 'Azure PowerShell' and 'Azure portal' in all code sections.
  • Link to Azure CLI installation and authentication guides for Linux/macOS users.
  • Ensure terminology and instructions do not assume a Windows environment (e.g., avoid references to Windows-only tools or patterns).
GitHub Create Pull Request
Nat Gateway Manage a Standard V2 NAT Gateway ...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed step-by-step instructions for managing Azure NAT Gateway resources using the Azure portal and Azure PowerShell. All command-line examples use PowerShell cmdlets, with no mention or examples of Azure CLI, Bash, or other cross-platform tools. This creates a bias toward Windows users, as PowerShell is natively available on Windows and its usage patterns are closely associated with Windows administration. Linux/macOS users are left without native, platform-agnostic command-line instructions, despite Azure CLI being widely supported and recommended for cross-platform automation.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command sequences, ensuring Linux/macOS users can follow along without installing PowerShell.
  • Explicitly mention that Azure CLI is supported on all platforms and provide links to installation guides.
  • Where possible, show Azure CLI examples before or alongside PowerShell to reinforce cross-platform parity.
  • Clarify that PowerShell Core is available on Linux/macOS, but Azure CLI is often preferred for cross-platform scripting.
GitHub Create Pull Request
Nat Gateway Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates ...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. ARM template deployment is presented exclusively using Azure PowerShell, with no Azure CLI or Bash example for Linux/macOS users. PowerShell is used first and most extensively, and instructions for copying/pasting scripts reference Windows-centric interaction patterns. While Bicep deployment does offer both CLI and PowerShell options, the ARM template section lacks Linux-friendly alternatives. There are no explicit Bash or Linux terminal examples for ARM template deployment, and PowerShell is the default throughout. This creates friction for Linux/macOS users who may prefer Azure CLI or Bash.
Recommendations
  • Add Azure CLI/Bash examples for ARM template deployment alongside PowerShell.
  • Present CLI and PowerShell instructions in parallel tabs for both ARM and Bicep sections.
  • Avoid Windows-centric instructions like 'Right-click and Paste' in shell consoles; use platform-neutral language.
  • Ensure all critical deployment steps have both PowerShell and CLI/Bash equivalents.
  • Consider listing CLI/Bash examples before or alongside PowerShell to avoid 'Windows first' bias.
GitHub Create Pull Request
Nat Gateway Troubleshoot Azure NAT Gateway ...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. In troubleshooting sections, Windows tools (PsPing, PowerShell Invoke-WebRequest) are mentioned with direct links, while Linux equivalents are referenced generically (e.g., 'application specific' for UDP, no mention of Linux PowerShell or Bash alternatives). In the 'failed state' resolution, only PowerShell and Azure Resource Explorer (browser-based, recommended with Edge) are described, with no Linux CLI or Bash/Azure CLI alternatives. Windows tools and patterns are often listed before or instead of Linux/macOS equivalents.
Recommendations
  • Add explicit Linux/macOS CLI examples for all troubleshooting steps, especially for resolving failed states (e.g., using Azure CLI or REST API via curl).
  • Provide Linux-specific tools for UDP testing (e.g., socat, netcat with UDP flags) and link to their documentation.
  • Include Bash/Azure CLI commands alongside PowerShell examples for managing network interfaces and NAT gateway resources.
  • Avoid recommending Microsoft Edge browser exclusively; clarify cross-browser compatibility for Azure Resource Explorer.
  • Ensure all tool recommendations are presented in parallel for Windows and Linux/macOS, not Windows-first.
GitHub Create Pull Request
Nat Gateway Troubleshoot Azure NAT Gateway connectivity .../articles/nat-gateway/troubleshoot-nat-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias. Troubleshooting steps and examples reference Windows-specific tools (e.g., PowerShell, PsPing, netsh) without mentioning Linux/macOS equivalents. In the section about flushing connection state, PowerShell/curl is referenced, and the example for probing port response uses 'ps ping', a Windows tool. Network tracing is described using 'netsh', which is Windows-only. No Linux/macOS commands (e.g., curl, netcat, tcpdump) are provided, and Windows tools are mentioned first and exclusively in critical troubleshooting steps.
Recommendations
  • Provide Linux/macOS equivalents for all command-line examples, such as using 'curl', 'nc', or 'ss' for connection testing, and 'tcpdump' or 'wireshark' for packet capture.
  • When referencing PowerShell or Windows tools, add parallel instructions for Bash or other common Linux shells.
  • Explicitly state that troubleshooting steps apply to both Windows and Linux, and clarify any OS-specific differences.
  • Include example commands for both platforms side-by-side, or use tabs to switch between Windows and Linux/macOS instructions.
  • Avoid referencing Windows tools exclusively in critical troubleshooting sections.
GitHub Create Pull Request
Nat Gateway Integrate NAT Gateway with Azure Firewall in Hub and Spoke Network ...rticles/nat-gateway/tutorial-hub-spoke-nat-firewall.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
This documentation page provides step-by-step instructions for integrating NAT Gateway with Azure Firewall in a hub and spoke network, offering examples via the Azure Portal and PowerShell. PowerShell is featured as the sole command-line automation method, with no Bash, Azure CLI, or Linux-native scripting alternatives. Windows/PowerShell tools and patterns are used exclusively, and PowerShell examples are presented before any Linux-relevant CLI options. This creates friction for Linux/macOS users who typically use Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) commands for each PowerShell example, ensuring parity for Linux/macOS users.
  • Include Bash scripting examples where appropriate, especially for VM creation and network configuration.
  • Explicitly mention that PowerShell can be used cross-platform, but highlight Azure CLI as the recommended option for Linux/macOS.
  • Reorder examples so that Portal and CLI (az) instructions appear before PowerShell, or present all options side-by-side.
  • Clarify prerequisites for Linux/macOS users, such as installing Azure CLI and using Bash.
  • Avoid exclusive references to Windows tools (e.g., Get-Credential) and provide platform-neutral alternatives.
GitHub Create Pull Request
Nat Gateway Tutorial: Use a NAT gateway with a hub and spoke network ...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Examples Missing Linux Example
Summary
The documentation provides detailed steps for deploying and testing a hub-and-spoke network with Azure NAT Gateway, including both Portal and PowerShell instructions. However, for the critical 'test virtual machine' steps, only Windows Server 2022 is used for testing, and all test procedures (such as installing IIS and verifying NAT gateway functionality) are Windows-centric. There are no equivalent Linux VM test instructions, and all connectivity and validation examples use Windows tools (Microsoft Edge, IIS, PowerShell scripts), with no mention of Linux alternatives (e.g., curl, nginx, Firefox, etc.). This creates friction for users who prefer or require Linux-based test environments.
Recommendations
  • Add parallel instructions for deploying a Linux test VM (e.g., Ubuntu) in the spokes, including portal and PowerShell steps.
  • Provide Linux-based test procedures, such as installing nginx or Apache, and using curl or a browser like Firefox to verify outbound NAT and inter-spoke connectivity.
  • Include example commands for Linux users to validate NAT gateway functionality (e.g., curl https://ifconfig.me or wget).
  • When presenting test VM options, offer both Windows and Linux choices, and show examples for each.
  • Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both.
GitHub Create Pull Request
Nat Gateway Integrate NAT Gateway with Azure Firewall in Hub and Spoke Network ...rticles/nat-gateway/tutorial-hub-spoke-nat-firewall.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for integrating NAT Gateway with Azure Firewall in a hub and spoke network, offering examples via the Azure Portal and PowerShell. There are no Azure CLI (az) examples, which are platform-neutral and preferred by many Linux/macOS users. PowerShell is featured as the only command-line automation method, and prerequisites and instructions for PowerShell installation are given, but not for Azure CLI. The structure consistently presents Portal instructions first, then PowerShell, with no Linux shell or CLI parity.
Recommendations
  • Add Azure CLI (az) examples for every step alongside PowerShell, ensuring Linux/macOS users have a first-class experience.
  • Include prerequisites for Azure CLI installation and authentication (az login), similar to the PowerShell section.
  • Where command-line examples are given, present CLI and PowerShell in parallel tabs, or alternate the order to avoid Windows-first bias.
  • Explicitly mention that PowerShell is available cross-platform, but highlight CLI as the most platform-neutral option.
  • Add notes or links for Linux/macOS users regarding environment setup and troubleshooting.
GitHub Create Pull Request
Nat Gateway Manage a Standard V2 NAT Gateway ...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed Azure PowerShell examples for all CLI-based operations but does not include any Azure CLI (az) or Bash examples, which are preferred by Linux/macOS users. PowerShell is a Windows-centric tool, and its usage is described and required for all command-line instructions. There is no mention of Azure CLI, Bash, or cross-platform scripting alternatives, and PowerShell instructions are presented before any mention of Linux-compatible tools. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all operations alongside PowerShell examples.
  • Include Bash script snippets for common tasks where appropriate.
  • Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux/macOS.
  • Reorder examples so that Azure CLI/Bash instructions are presented before or alongside PowerShell, not after.
  • Clarify that PowerShell Core is available for Linux/macOS, but recommend Azure CLI for native experience.
GitHub Create Pull Request
Nat Gateway What is Azure NAT Gateway? ...re-docs/blob/main/articles/nat-gateway/nat-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is largely platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there is a notable Windows bias in the 'Default outbound access' section, where only Windows-specific services (Windows Activation and Windows Updates) are mentioned as requiring outbound connectivity, with no mention of Linux equivalents (such as OS package updates). Additionally, upgrade instructions for basic Load Balancer resources reference PowerShell, a Windows-centric tool, without providing CLI or Linux-friendly alternatives. These instances may cause friction for Linux/macOS users by implying Windows is the primary use case and omitting Linux-specific considerations.
Recommendations
  • Include examples or notes about Linux VM outbound connectivity requirements (e.g., package updates via apt/yum/zypper) alongside Windows Activation/Updates.
  • Provide upgrade instructions using Azure CLI or ARM templates in addition to PowerShell, ensuring parity for Linux/macOS users.
  • Where tools are referenced (e.g., PowerShell), mention cross-platform alternatives and link to relevant documentation.
  • Review all sections for implicit Windows-first language and ensure Linux/macOS scenarios are equally represented.
GitHub Create Pull Request
Nat Gateway Troubleshoot Azure NAT Gateway ...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In troubleshooting sections, Windows tools (PsPing, PowerShell Invoke-WebRequest) are listed before or instead of Linux equivalents. PowerShell is the only CLI method described for resolving failed network interfaces, with no Linux CLI or Azure CLI alternative. Some troubleshooting steps reference browser-based tools but recommend Microsoft Edge, reinforcing a Windows-centric approach.
Recommendations
  • Provide Azure CLI or REST API examples for managing network interfaces in failed states, ensuring Linux/macOS users have parity with PowerShell instructions.
  • List Linux tools (e.g., nc, curl) alongside Windows tools in all troubleshooting tables and sections, and present them in parallel or alternate order.
  • Include Bash or shell script examples for common tasks where only PowerShell is shown.
  • Avoid recommending specific browsers unless strictly necessary; if so, clarify cross-platform compatibility.
  • Ensure all troubleshooting steps can be completed from Linux/macOS environments, not just Windows.
GitHub Create Pull Request
Nat Gateway Tutorial: Use a NAT gateway with a hub and spoke network ...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Windows Heavy Powershell Heavy Missing Linux Example
Summary
This documentation demonstrates a notable Windows bias. While the simulated NVA is Ubuntu-based and its configuration is shown with Linux commands, all test virtual machines in the spokes are Windows Server 2022. The only provided examples for testing NAT gateway and inter-spoke routing use Windows tools (Microsoft Edge, IIS, PowerShell), with no equivalent Linux VM or test instructions. All CLI examples are exclusively PowerShell, with no Bash/Azure CLI alternatives. Windows VM creation and configuration steps are detailed, while Linux VM creation for spokes is omitted.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the spokes, including portal and PowerShell/Azure CLI steps.
  • Provide Linux-based test procedures (e.g., using curl or wget to test outbound NAT and inter-spoke connectivity) alongside Windows/IIS examples.
  • Include Azure CLI (Bash) examples for all resource creation steps, not just PowerShell.
  • When presenting examples, alternate or parallelize Windows and Linux instructions, or provide a clear choice at the start.
  • Explicitly state that either Windows or Linux VMs can be used for testing, and link to relevant documentation for both.
GitHub Create Pull Request
Nat Gateway Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates ...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the ARM template deployment section, where only Azure PowerShell examples are provided and detailed step-by-step instructions reference PowerShell and Windows-centric workflows. Linux/macOS users must infer how to use Azure CLI or adapt PowerShell commands, which creates friction. The Bicep section does provide both CLI and PowerShell options, but the ARM template section lacks parity.
Recommendations
  • Add Azure CLI examples for ARM template deployment alongside PowerShell, with equivalent step-by-step instructions.
  • Present CLI and PowerShell options side-by-side or in tabs for all deployment steps, not just Bicep.
  • Ensure instructions for copying/pasting scripts and interacting with Cloud Shell are platform-neutral or include Linux/macOS-specific guidance.
  • Explicitly mention that both Azure CLI and PowerShell are available in Cloud Shell, and clarify usage for non-Windows users.
GitHub Create Pull Request
Nat Gateway Troubleshoot Azure NAT Gateway connectivity .../articles/nat-gateway/troubleshoot-nat-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias. Troubleshooting steps and examples reference Windows-specific tools (e.g., PowerShell, PsPing, netsh) without mentioning Linux/macOS equivalents. In the section on resolving outbound IP issues, the example for forcing new connections uses PowerShell/curl, and the network capture guidance exclusively references Windows tools. No Linux/macOS commands or troubleshooting patterns are provided, and Windows-centric terminology appears first or exclusively in several places.
Recommendations
  • Include Linux/macOS equivalents for all troubleshooting steps, such as using tcpdump, ping, traceroute, and curl with appropriate flags.
  • Provide examples using Bash or Linux shell commands alongside PowerShell examples.
  • Reference cross-platform tools (e.g., Wireshark, nmap) where possible.
  • Clarify that steps can be performed on any OS and provide OS-specific instructions as needed.
  • Avoid using Windows tools exclusively in critical troubleshooting sections; always offer alternatives.
GitHub Create Pull Request
Nat Gateway What is Azure NAT Gateway? ...re-docs/blob/main/articles/nat-gateway/nat-overview.md
Low Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there are minor instances of Windows bias: (1) Windows-specific services (Windows Activation and Windows Updates) are mentioned as requiring outbound connectivity, while Linux equivalents are not referenced; (2) upgrade guidance for basic public IPs and Load Balancers links to PowerShell-based instructions, which are typically Windows-centric, and does not mention CLI or Linux alternatives first.
Recommendations
  • When discussing outbound connectivity requirements, mention Linux equivalents (e.g., package updates via apt/yum) alongside Windows Activation/Updates.
  • Where upgrade instructions are linked (e.g., upgrading Load Balancer or public IP), ensure that Azure CLI and/or portal-based instructions are referenced equally or before PowerShell, and clarify cross-platform options.
  • Add explicit examples or notes for Linux/macOS users where relevant, especially in sections referencing tooling or OS-specific outbound needs.
GitHub Create Pull Request
Nat Gateway What is Azure NAT Gateway? ...re-docs/blob/main/articles/nat-gateway/nat-overview.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is largely platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there is a notable Windows bias in the 'Default outbound access' section, where only Windows-specific services (Windows Activation and Windows Updates) are mentioned as requiring outbound connectivity. Additionally, upgrade instructions for basic resources reference PowerShell (a Windows-centric tool) first, with no mention of Linux/macOS alternatives (e.g., Azure CLI, Bash). No Linux/macOS-specific examples, tools, or considerations are provided.
Recommendations
  • Include Linux/macOS-specific outbound connectivity requirements (e.g., package updates, activation for Linux VMs) alongside Windows examples.
  • Provide upgrade instructions using cross-platform tools such as Azure CLI or Bash scripts, not just PowerShell.
  • Explicitly mention that NAT Gateway supports outbound connectivity for all VM OS types, and clarify any OS-specific caveats.
  • Where PowerShell is referenced, add equivalent Azure CLI or REST API documentation links/examples.
GitHub Create Pull Request
Nat Gateway What is Azure NAT Gateway? ...re-docs/blob/main/articles/nat-gateway/nat-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform and conceptual, but it contains some Windows bias. Specifically, it references Windows-specific services (Windows Activation and Windows Updates) as examples of workloads requiring outbound connectivity, and links to upgrade guides that use PowerShell (a Windows-centric tool) before mentioning other methods. No Linux/macOS-specific examples, tools, or scenarios are provided, and Windows is mentioned first in relevant sections.
Recommendations
  • Include Linux/macOS-specific examples of services that require outbound connectivity (e.g., package managers like apt/yum, OS updates, or cloud-init).
  • Provide links to upgrade guides using Azure CLI or ARM templates, which are cross-platform, alongside or before PowerShell guides.
  • Mention Linux/macOS scenarios explicitly when discussing outbound connectivity requirements.
  • Ensure that examples and references do not prioritize Windows tools or patterns unless necessary.
GitHub Create Pull Request
Nat Gateway Create an Azure NAT Gateway .../articles/nat-gateway/quickstart-create-nat-gateway.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides parallel instructions for Azure Portal, PowerShell, CLI, and Terraform, but PowerShell (a Windows-centric tool) is given a dedicated section with extensive, step-by-step examples. PowerShell instructions are detailed and appear before CLI examples, which are more cross-platform. There is a slight preference for Windows tools and patterns, with PowerShell cmdlets and guidance on installing/updating Azure PowerShell modules. However, Linux parity is generally maintained via CLI and Terraform examples, and the VM creation examples use Ubuntu images.
Recommendations
  • Present CLI examples before PowerShell, as CLI is more cross-platform.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide installation instructions for those platforms.
  • Add notes or links for Linux/macOS users on how to use Azure Cloud Shell or install Azure CLI locally.
  • Balance the level of detail between PowerShell and CLI sections to avoid giving the impression that PowerShell is the preferred or primary method.
  • Where PowerShell-specific troubleshooting or module installation is discussed, provide equivalent guidance for CLI on Linux/macOS.
GitHub Create Pull Request
Nat Gateway Manage a NAT gateway ...s/blob/main/articles/nat-gateway/manage-nat-gateway.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parity between Azure Portal, Azure PowerShell, Azure CLI, and Bicep for all major tasks. However, PowerShell examples are given in detail and are presented before Azure CLI examples in each section. This ordering and the extensive use of PowerShell may create a subtle Windows bias, as PowerShell is most commonly used on Windows. There are no explicit Linux/macOS-only gaps, but the prominence and ordering of PowerShell may signal a preference for Windows tooling.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and Windows, while PowerShell requires installation on non-Windows platforms.
  • Balance example depth: ensure CLI examples are as detailed as PowerShell ones.
  • Add a note in prerequisites clarifying that both CLI and PowerShell are available in Azure Cloud Shell, which is OS-agnostic.
  • Consider adding Bash scripting examples for advanced scenarios, if relevant.
GitHub Create Pull Request
Nat Gateway Create an Azure NAT Gateway .../articles/nat-gateway/quickstart-create-nat-gateway.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure Portal, PowerShell, CLI, and Terraform, but consistently lists PowerShell (a Windows-centric tool) before CLI (cross-platform) in both prerequisites and step-by-step instructions. PowerShell examples are detailed and extensive, matching the CLI coverage, but are presented first, which may subtly prioritize Windows workflows. No critical Linux functionality is missing, and Linux VM creation is included in all methods.
Recommendations
  • Alternate the order of PowerShell and CLI sections, or present CLI examples before PowerShell to avoid implicit prioritization.
  • Explicitly note that Azure CLI and Cloud Shell are cross-platform and suitable for Linux/macOS users.
  • Add a short note in the prerequisites clarifying that PowerShell is available in Cloud Shell and on macOS/Linux, but CLI is generally preferred for cross-platform usage.
  • Ensure that any advanced scenarios or troubleshooting are equally covered for CLI and PowerShell.
GitHub Create Pull Request