Nat Gateway

21
Total Pages
11
Linux-Friendly Pages
10
Pages with Bias
47.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (23)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-outbound-nat.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell or Windows command-line patterns, but there is also a complete absence of CLI examples (such as Azure CLI or Bash scripts) that would be relevant for Linux or cross-platform users. This omission creates a bias by not addressing the needs of users who prefer or require command-line automation, which is common in Linux environments.
Recommendations:
  • Add Azure CLI examples alongside portal instructions for each major step (resource creation, deletion, configuration).
  • Ensure CLI examples are presented in Bash syntax to maximize Linux compatibility.
  • Where relevant, mention both Azure CLI and PowerShell options, but do not prioritize Windows tooling.
  • Include links to documentation for automating NAT Gateway configuration using CLI tools.
  • Explicitly state that all steps can be performed via CLI and provide a parity table or section for command-line equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation provides comprehensive examples for Azure Portal, Azure PowerShell, Azure CLI, and Bicep. However, there is a notable emphasis on Azure PowerShell, which is most commonly used on Windows, and PowerShell examples are often presented before Azure CLI. The PowerShell sections are more verbose and detailed, and prerequisites for PowerShell include specific instructions for Windows environments. While Azure CLI is cross-platform and suitable for Linux, it is consistently listed after PowerShell, and there are no explicit Linux shell (bash) or scripting examples. There is no mention of Linux-specific tools, nor is there guidance for Linux users beyond Azure CLI.
Recommendations:
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell environments (e.g., bash) where appropriate.
  • Add a short section or note for Linux users, clarifying that Azure CLI is the recommended tool for Linux and macOS, and that PowerShell is optional.
  • Where PowerShell is referenced, clarify that it is available cross-platform, but that Azure CLI may be more familiar to Linux users.
  • Consider including bash script snippets or references to Linux shell usage, especially in the prerequisites and setup sections.
  • Ensure parity in detail and explanation between PowerShell and CLI sections, so Linux users are not disadvantaged.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but exhibits a Windows/PowerShell bias in several ways. PowerShell is given a prominent, detailed walkthrough with extensive explanations and code samples, often before CLI/Linux-native alternatives. The PowerShell sections reference Windows-specific tools and installation patterns (e.g., Azure PowerShell module, Get-Module), and the ARM template cleanup instructions reference PowerShell rather than CLI/bash. While Linux is represented (e.g., Ubuntu VM examples, CLI usage), the documentation structure and depth of PowerShell content suggest a Windows-first approach.
Recommendations:
  • Ensure that CLI (az) and bash examples are as detailed and prominent as PowerShell, including explanations for environment setup and troubleshooting.
  • Where PowerShell-specific instructions are given (e.g., module installation, cleanup), provide equivalent bash/CLI/Linux-native instructions alongside or before them.
  • In ARM and Bicep template deployment and cleanup sections, include both PowerShell and CLI/bash commands for parity.
  • Review the order of tabs and sections to avoid consistently placing PowerShell/Windows content before CLI/Linux content.
  • Audit for references to Windows-specific tools or patterns (such as 'Get-Module') and ensure Linux equivalents (such as checking az CLI version) are also provided.
  • Highlight that Azure Cloud Shell supports both bash and PowerShell, and provide instructions for both where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a moderate Windows bias. In troubleshooting steps, PowerShell commands and Windows-specific tools (like PsPing and Invoke-WebRequest) are highlighted, while Linux equivalents are either less detailed or omitted. In sections on resolving failed states, only PowerShell and Azure Resource Explorer (browser-based, with a browser recommendation) are provided, with no CLI or Linux-native alternatives. In the connectivity validation table, Windows tools are linked and described in more detail than their Linux counterparts. Windows approaches are often listed before Linux ones.
Recommendations:
  • Provide equivalent Linux CLI (e.g., Azure CLI, Bash) commands alongside PowerShell examples for managing network interfaces and troubleshooting failed states.
  • Expand Linux tool recommendations in the connectivity validation table, e.g., suggest 'curl' or 'wget' for TCP tests, and 'socat' or 'iperf' for UDP tests, with example commands.
  • Avoid recommending only Windows-specific tools (like PsPing) without mentioning cross-platform or Linux alternatives.
  • Where PowerShell is used, add Azure CLI or REST API examples for parity.
  • Ensure Linux and Windows instructions are presented with equal detail and prominence, and avoid consistently listing Windows approaches first.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a moderate Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) before Azure CLI in all code example tabs. The PowerShell sections are more detailed, with additional context and troubleshooting steps, and the documentation assumes familiarity with PowerShell cmdlets and patterns. There is no explicit mention of Linux or Bash-specific instructions, and the CLI examples, while present, are always listed after PowerShell, reinforcing a Windows-first approach. The documentation also refers to 'PowerShell' generically in some places, which may confuse cross-platform users, as PowerShell Core is available on Linux/macOS but is less commonly used than Bash.
Recommendations:
  • Alternate the order of PowerShell and CLI examples, or present CLI (which is cross-platform) before PowerShell to avoid reinforcing a Windows-first workflow.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and clarify that PowerShell examples are also compatible with PowerShell Core on non-Windows platforms.
  • Add Bash-specific notes or examples where relevant, especially for scripting scenarios.
  • In prerequisite sections, clarify installation instructions for both Windows and Linux environments for all tools (Azure CLI, PowerShell).
  • Use neutral language such as 'Azure CLI' and 'PowerShell' (with platform notes) rather than assuming a Windows environment.
  • Consider including troubleshooting tips or environment setup notes for Linux users, especially regarding authentication and module installation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-and-azure-services.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any OS-specific command-line examples or troubleshooting steps, but where it does mention validation (e.g., 'ping a virtual machine on your Web Apps and check the traffic via a network capture'), it does not specify tools or commands for either Windows or Linux. There is a lack of parity in that no Linux-specific or cross-platform CLI examples are given for network troubleshooting, and the only command-line reference is to the Azure CLI (az), which is cross-platform. However, the absence of any concrete examples (Windows or Linux) means Linux users are not directly disadvantaged, but also not supported with tailored guidance.
Recommendations:
  • Add explicit, cross-platform command-line examples for common troubleshooting tasks (e.g., using curl, traceroute, tcpdump for Linux; PowerShell equivalents for Windows).
  • When suggesting network capture or validation, provide both Windows (e.g., Wireshark, PowerShell commands) and Linux (e.g., tcpdump, ip, netstat) tool examples.
  • Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
  • Where possible, link to Azure documentation that covers both Windows and Linux troubleshooting techniques for networking.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/region-move-nat-gateway.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page exclusively describes how to deploy a NAT gateway using the Azure Portal UI, without providing any command-line examples. There are no references to Windows-specific tools (such as PowerShell) or Linux-specific tools (such as Azure CLI or Bash). However, the absence of CLI examples (which are commonly used on Linux and cross-platform environments) means Linux users do not have parity with Windows users who may be more accustomed to GUI or PowerShell workflows.
Recommendations:
  • Add Azure CLI examples for each step of the NAT gateway deployment process, as Azure CLI is cross-platform and widely used on Linux.
  • Where applicable, provide Bash script snippets to automate the process for Linux users.
  • If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are included alongside.
  • Explicitly mention that the steps can be performed using Azure CLI or ARM templates, and link to relevant documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a moderate Windows bias. In troubleshooting sections, PowerShell and Windows-specific tools (e.g., PsPing, Invoke-WebRequest) are provided for Windows users, while Linux examples are less detailed or missing. For some tasks (e.g., resolving failed network interfaces), only PowerShell and Azure Resource Explorer (browser-based, with a browser recommendation) are described, with no equivalent Linux CLI or cross-platform Azure CLI guidance. In the connectivity validation table, Windows tools are named and linked, but Linux examples are generic and less supported. Windows approaches are sometimes presented first or exclusively.
Recommendations:
  • For all PowerShell-based instructions, provide equivalent Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
  • In troubleshooting steps involving network interfaces, include az network nic commands for querying and updating provisioning state.
  • In the connectivity validation table, provide more detailed Linux examples (e.g., using nc, curl, or ss for TCP/UDP tests) and link to relevant documentation.
  • Avoid recommending specific browsers unless necessary; if a browser-based tool is required, clarify that it is platform-agnostic.
  • Where Windows tools are linked (e.g., PsPing, Invoke-WebRequest), provide Linux tool links (e.g., netcat, curl, socat) and usage examples.
  • Ensure that for every Windows-specific example or tool, there is a Linux (and ideally macOS) equivalent provided with equal detail and prominence.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-connectivity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing PowerShell-specific commands and Windows-native tools (e.g., 'ps ping', 'netsh') without providing equivalent Linux commands or guidance. Examples and troubleshooting steps assume a Windows environment, and there are no Linux/Unix alternatives or parity in the instructions. This may hinder users operating Linux-based Azure VMs or those more familiar with Linux tooling.
Recommendations:
  • For every PowerShell or Windows-native tool example (such as 'ps ping' or 'netsh'), provide equivalent Linux commands (e.g., 'ping', 'ss', 'tcpdump', 'traceroute', 'ncat', or 'ip netns').
  • When referencing command-line examples, clearly indicate both Windows and Linux syntax, or provide tabs/switches for each OS.
  • Avoid assuming the use of Windows VMs; explicitly mention that instructions apply to both Windows and Linux, or provide OS-specific guidance where necessary.
  • Include troubleshooting steps and diagnostic tool recommendations that are available and commonly used on Linux (e.g., 'tcpdump', 'netstat', 'ss', 'lsof').
  • Review all sections for implicit Windows-first language or assumptions, and revise to ensure Linux users are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-route-nat.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias in several areas: (1) Windows Server virtual machines are used exclusively for test workloads, with no Linux VM alternatives or examples; (2) IIS (a Windows-only web server) is installed for testing, with no mention of Linux-based web servers (e.g., Apache, Nginx); (3) All test and verification steps (such as browsing with Microsoft Edge and using PowerShell scripts) are Windows-centric, with no Linux equivalents; (4) PowerShell and Windows tools are referenced heavily, and Linux alternatives are not provided or are only mentioned in passing.
Recommendations:
  • Provide parallel Linux-based examples for test workloads, such as deploying Ubuntu or other Linux VMs in the spokes, and using Apache or Nginx for web server testing.
  • Include Linux command-line instructions (e.g., using curl or wget) for testing outbound connectivity and inter-spoke routing, alongside the Microsoft Edge/Windows instructions.
  • Offer Bash shell scripts or Azure CLI examples for configuration and testing, not just PowerShell.
  • When demonstrating installation of web servers or other software, show both Windows (IIS) and Linux (Apache/Nginx) options.
  • Explicitly mention that either Windows or Linux can be used for test VMs, and provide guidance for both.
  • Balance the order of presentation so that Linux and Windows are given equal prominence, or alternate which OS is presented first in examples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-ilip-nat.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing only the Windows virtual machine creation quickstart in the prerequisites and not mentioning or linking to the equivalent Linux VM documentation. There are no command-line examples (PowerShell, CLI, Bash), but the only example VM is Windows, and Linux is not referenced at all.
Recommendations:
  • In the prerequisites, provide links to both Windows and Linux VM creation quickstarts (e.g., /azure/virtual-machines/linux/quick-create-portal).
  • Explicitly state that the process applies to both Windows and Linux VMs, or provide examples for both.
  • Where example VM names or screenshots are used, consider using neutral or alternating examples (e.g., myWinVM and myLinuxVM) to show parity.
  • If mentioning RDP for Windows, also mention SSH for Linux in the context of remote access.
  • Review other sections for implicit Windows assumptions and ensure Linux users are equally supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-outbound-nat.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal UI for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While this avoids explicit Windows or PowerShell bias, it also omits parity for Linux users who commonly use CLI tools. The absence of CLI examples (especially Azure CLI, which is cross-platform and preferred by many Linux users) constitutes a bias of omission, as Linux users are not shown how to perform these tasks from their typical environment.
Recommendations:
  • Add Azure CLI examples for each major step, such as creating a NAT gateway, assigning public IPs, and updating subnet associations. Azure CLI is cross-platform and will serve both Linux and Windows users.
  • If PowerShell examples are added in the future, ensure Azure CLI examples are always provided alongside them.
  • Explicitly mention that all steps can be performed via CLI and provide links to relevant CLI documentation.
  • Consider including Bash script snippets for automation scenarios, which are common in Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but exhibits a Windows/PowerShell bias in several areas. PowerShell instructions are detailed and extensive, with more narrative and explanation than the equivalent Azure CLI (cross-platform) sections. PowerShell is often listed before CLI, and Windows/PowerShell-specific tools and patterns (such as Get-Credential, PowerShell module installation/upgrade, and PowerShell-specific resource management) are described in depth. There is no explicit mention of Linux shell or scripting environments in the PowerShell sections, and the CLI sections, while present, are less detailed in terms of setup and troubleshooting. The documentation does not provide Windows-only commands, but the prominence and depth of PowerShell coverage, as well as the ordering, suggest a subtle Windows-first bias.
Recommendations:
  • Ensure that Azure CLI instructions are as detailed and comprehensive as PowerShell instructions, including setup, troubleshooting, and environment preparation.
  • When listing deployment methods or tabs, alternate the order or list CLI before PowerShell to avoid a Windows-first impression.
  • Where PowerShell-specific guidance is given (e.g., module installation, credential prompts), provide equivalent guidance for Linux/macOS environments (e.g., Azure CLI installation, using SSH keys, environment variables for credentials).
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide links or notes for installing and using CLI in those environments.
  • In sections describing resource cleanup or management, include bash/zsh scripting examples or notes for Linux users, not just PowerShell.
  • Review narrative and instructional text to ensure parity in depth and clarity between PowerShell and CLI/Linux sections.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-route-nat.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example Powershell Heavy
Summary:
The documentation demonstrates a notable Windows bias, particularly in the testing and validation phases. While the infrastructure setup is cross-platform (Portal, PowerShell, CLI), the test virtual machines in both spokes are exclusively Windows Server 2022, and all test/validation steps (IIS installation, browser-based tests using Microsoft Edge, PowerShell scripts) are Windows-centric. There are no equivalent examples or instructions for deploying or testing with Linux-based VMs in the spokes, nor are Linux tools (e.g., curl, Apache/nginx, SSH) mentioned for validation. The use of PowerShell and Windows tools is prevalent, and Windows-based patterns are presented as the default for validation.
Recommendations:
  • Provide parallel Linux-based test VM instructions for the spokes, including deployment, configuration, and validation steps (e.g., using Ubuntu or CentOS, installing Apache/nginx, and using curl or wget for testing).
  • Include Linux command-line examples for validation (e.g., curl http://<ip-address> to test web server connectivity, or using lynx/w3m as text browsers).
  • When demonstrating IIS installation and testing, also show how to install and test a web server on Linux (e.g., sudo apt install apache2, echo 'Hello World' > /var/www/html/index.html).
  • Instruct on using SSH and Linux shell commands for connectivity and troubleshooting, not just RDP/Edge/PowerShell.
  • Balance the use of Windows and Linux tools in all test and validation sections, and avoid assuming the user will always use Windows VMs or Microsoft browsers.
  • Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a moderate Windows bias. In troubleshooting steps, PowerShell commands are provided for resolving failed network interface states, but there are no equivalent CLI or Linux-native instructions. In the connectivity validation table, Windows-specific tools (PsPing, PowerShell Invoke-WebRequest) are listed, while Linux tools are mentioned but with less detail. The PowerShell method is described first and in more detail than the Azure Resource Explorer method, and there is no mention of Azure CLI or Linux-native alternatives for managing network interfaces. This may disadvantage users working primarily in Linux environments or using cross-platform automation.
Recommendations:
  • Provide equivalent Azure CLI commands for all PowerShell examples, especially for managing network interfaces in failed states.
  • Expand Linux tool recommendations in the connectivity validation table (e.g., suggest 'ss', 'telnet', or 'curl' for UDP where appropriate).
  • Ensure that Linux and cross-platform tools are mentioned alongside or before Windows-specific tools, or present both together.
  • Where PowerShell is used, add corresponding Bash/Azure CLI scripts to ensure parity.
  • Clarify that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
  • Consider adding a section or callout for cross-platform troubleshooting approaches.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-ilip-nat.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing only the Windows virtual machine quickstart in the prerequisites, without mentioning or linking to a Linux equivalent. There are no Linux-specific instructions or examples, and the only VM creation link is for Windows, which may lead Linux users to feel unsupported or overlooked.
Recommendations:
  • Include a link to the Linux virtual machine quickstart alongside the Windows quickstart in the prerequisites section.
  • Explicitly mention that the tutorial applies to both Windows and Linux VMs, unless there are platform-specific caveats.
  • Where examples or screenshots reference Windows VMs, consider providing parallel examples or clarifying that the steps are the same for Linux VMs.
  • Review the documentation for other subtle Windows-first language or assumptions and update to be platform-neutral where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-outbound-nat.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While this avoids explicit Windows or PowerShell bias, it also omits parity for Linux users who may prefer or require CLI-based workflows. The absence of CLI examples (especially Azure CLI, which is cross-platform) can be considered a subtle bias, as it does not address the needs of users on Linux or those automating deployments.
Recommendations:
  • Add Azure CLI examples alongside portal instructions for all major steps (resource creation, configuration, deletion).
  • If PowerShell examples are added in the future, ensure Azure CLI (or Bash) equivalents are provided and presented with equal prominence.
  • Explicitly mention that the Azure CLI can be used from Linux, macOS, and Windows, and provide links to relevant installation guides.
  • Consider including a table or section summarizing equivalent commands for Azure CLI, PowerShell, and portal actions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/nat-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation page for Azure NAT Gateway is generally platform-neutral, focusing on conceptual overviews and Azure-specific features. However, there is a subtle Windows bias in the 'NAT gateway and basic resources' section, where the only example for upgrading a basic load balancer to standard references a PowerShell-based process. No equivalent Linux/CLI or cross-platform example is provided, and the PowerShell reference appears before any mention of portal-based or CLI-based upgrades.
Recommendations:
  • Provide equivalent Azure CLI (cross-platform) commands alongside PowerShell examples for resource upgrades and management tasks.
  • When referencing upgrade or management procedures, list Azure Portal and Azure CLI methods before or alongside PowerShell to avoid implying Windows/PowerShell primacy.
  • Ensure that all procedural links and examples are available for both Windows (PowerShell) and Linux/macOS (Azure CLI, Bash) users.
  • Add explicit notes or sections for Linux/macOS users where relevant, especially for command-line operations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides extensive Azure PowerShell examples and guidance, which is a Windows-centric toolset, and references PowerShell-specific installation and usage patterns. PowerShell is presented before Azure CLI in both prerequisites and procedural sections, and there is no mention of native Linux shell scripting or Linux-specific nuances. While Azure CLI is cross-platform, the documentation's structure and emphasis favor Windows/PowerShell users.
Recommendations:
  • Present Azure CLI examples before PowerShell examples, as CLI is more universally available across platforms.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide any Linux-specific notes if needed.
  • Add Bash script examples for common tasks, especially in sections where PowerShell scripting is demonstrated.
  • Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported and highlight cross-platform compatibility.
  • Where PowerShell installation is discussed, provide equivalent instructions for Bash/CLI environments on Linux and macOS.
  • Consider adding a short section or callout for Linux/macOS users, summarizing the parity and any differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but the PowerShell sections are notably more detailed and verbose than their CLI (cross-platform) counterparts. PowerShell (a Windows-centric tool, though available on Linux) is often presented with more context, explanations, and step-by-step breakdowns. In several places, PowerShell is listed before CLI, and guidance on installing and updating Azure PowerShell is included, but there is no equivalent Linux shell or Bash-specific guidance. The documentation assumes familiarity with PowerShell cmdlets and patterns, which may be less accessible to Linux-first users.
Recommendations:
  • Ensure CLI (az) examples are as detailed as PowerShell examples, including explanations and context for each step.
  • Add explicit Bash/Linux shell guidance where appropriate, such as using Bash variables, loops, or environment setup.
  • When listing deployment methods, alternate the order or explicitly state that CLI is cross-platform and suitable for Linux/macOS/Windows.
  • Provide links or references for installing/updating Azure CLI on Linux, similar to the PowerShell installation guidance.
  • Where PowerShell-specific patterns are explained (e.g., use of hashtables, cmdlet pipelines), offer analogous Bash/CLI scripting tips.
  • Review all sections for assumptions of Windows/PowerShell familiarity and add clarifying notes for Linux users as needed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/region-move-nat-gateway.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively describes how to deploy and configure a NAT gateway using the Azure Portal GUI, without providing any command-line examples. There are no references to PowerShell or Windows-specific tools, but there is also a lack of Azure CLI (cross-platform) or Bash/Linux shell examples. This omission can be seen as a subtle Windows bias, as Azure Portal workflows are often more familiar to Windows users, and the absence of CLI or script-based instructions may disadvantage Linux users or those automating deployments.
Recommendations:
  • Add Azure CLI examples for each step, demonstrating how to create and configure a NAT gateway and associate resources using cross-platform commands.
  • Include Bash script snippets for automating the process, making the documentation more accessible to Linux users.
  • Explicitly mention that the steps can be performed via Azure CLI or ARM templates, and provide links or references to relevant documentation.
  • Ensure parity by presenting both Portal and CLI/script-based instructions side by side, or clearly indicating alternative methods for non-Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-and-azure-services.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides troubleshooting steps and configuration guidance for Azure NAT Gateway integration with various Azure services, but it does not include any command-line examples, scripts, or troubleshooting steps specific to either Windows or Linux. However, in areas where validation or troubleshooting is suggested (such as 'ping a virtual machine on your Web Apps and check the traffic via a network capture'), there are no examples or tool recommendations for either platform. The documentation is neutral in terms of explicit Windows bias (no PowerShell, Windows tools, or Windows-first ordering), but it also lacks parity by not providing Linux (or cross-platform) command-line examples or tool suggestions.
Recommendations:
  • Add cross-platform command-line examples for validating NAT gateway usage, such as using curl, wget, or traceroute for Linux/macOS and their Windows equivalents.
  • When suggesting network capture, recommend tools available on both platforms (e.g., tcpdump for Linux, Wireshark for both, or Windows equivalents) and provide example commands.
  • Explicitly mention that the troubleshooting steps can be performed from either Windows or Linux VMs, and provide sample commands for both.
  • If referencing Azure CLI, clarify that it is cross-platform and provide example commands for common tasks (e.g., checking public IP, updating NAT gateway settings) that work on all supported OSes.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-connectivity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page exhibits a moderate Windows bias. Troubleshooting steps and examples reference Windows-specific tools (such as 'ps ping', 'netsh', and PowerShell usage with curl) without providing equivalent Linux commands or guidance. There are no Linux or cross-platform examples for network troubleshooting, and the only code/tooling examples are Windows-centric. The mention of PowerShell and Windows tools appears before or instead of Linux alternatives, and there is no mention of common Linux utilities (e.g., ping, traceroute, tcpdump, ip, netcat) for network diagnostics.
Recommendations:
  • Provide equivalent Linux command-line examples alongside Windows/PowerShell commands (e.g., use 'ping', 'nc', 'ss', 'tcpdump', 'traceroute' for Linux).
  • When referencing tools like 'ps ping' or 'netsh', add corresponding Linux alternatives (e.g., 'ping', 'ss', 'tcpdump', 'ip route').
  • Avoid using only PowerShell-specific flags (such as '-DisableKeepalive') in examples; show how to achieve the same in Bash or Linux shells.
  • Explicitly mention that the troubleshooting steps apply to both Windows and Linux VMs, and clarify any OS-specific differences.
  • Include .NET examples for both Windows and Linux environments, or provide cross-platform code samples.
  • Balance the order of presentation so that Linux and Windows tools are mentioned together or in alternating order, rather than Windows-first.