Nat Gateway
28
Total Pages
13
Linux-Friendly Pages
15
Pages with Bias
53.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
89 issues found
Showing 51-75 of 89 flagged pages
Nat Gateway
Troubleshoot Azure NAT Gateway
...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides troubleshooting steps and examples for both Windows and Linux in some areas (e.g., connectivity validation), but several sections show Windows bias. PowerShell and Windows-specific tools (PsPing, PowerShell cmdlets) are mentioned for critical troubleshooting tasks, while equivalent Linux commands or workflows are missing or less detailed. In some cases, Windows tools are listed before Linux alternatives, and Linux users are left to infer their own solutions.
Recommendations
- For sections that use PowerShell to resolve VM NIC failed states, provide equivalent Azure CLI commands or REST API steps for Linux/macOS users.
- Where Windows tools like PsPing and PowerShell Invoke-WebRequest are mentioned, add Linux equivalents (e.g., nc, curl, ss, telnet) with example usage.
- Ensure troubleshooting steps (such as resource state recovery) include platform-neutral or cross-platform instructions, not just PowerShell or GUI.
- When listing tools or commands, alternate the order or present both Linux and Windows options together to avoid Windows-first bias.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions for managing Azure NAT Gateway V2 using the Azure portal and Azure PowerShell, but does not include any examples or guidance for Linux/macOS users via Azure CLI or Bash. All command-line examples use PowerShell cmdlets, which are Windows-centric and less familiar to many Linux/macOS users. There is no mention of Azure CLI, Bash, or cross-platform scripting alternatives, and PowerShell is treated as the default automation tool.
Recommendations
- Add equivalent Azure CLI examples for all operations (create, associate, remove, delete, add/remove IPs and prefixes).
- Include Bash script snippets where appropriate, especially for Linux/macOS users.
- Explicitly mention that Azure PowerShell can be used on Linux/macOS, but provide CLI alternatives for parity.
- Reorganize sections to present Azure CLI and PowerShell examples side-by-side, or allow users to select their preferred tool in tabs.
- Clarify prerequisites for Linux/macOS users, including installation steps for Azure CLI.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there is a notable Windows bias in the section discussing outbound connectivity for private subnets: only Windows-specific services (Windows Activation and Windows Updates) are mentioned as requiring explicit outbound connectivity, with no reference to Linux equivalents. Additionally, upgrade instructions for basic resources reference PowerShell (a Windows-centric tool) first, without mentioning cross-platform alternatives like Azure CLI or ARM templates.
Recommendations
- Include examples or notes about Linux/macOS scenarios that require outbound connectivity (e.g., package updates via apt/yum, OS activation if applicable).
- When referencing upgrade instructions, provide Azure CLI and/or ARM template examples alongside PowerShell, or mention them as alternatives.
- Ensure that any tooling or operational guidance is presented in a cross-platform manner, with equal visibility for Linux/macOS users.
- Where outbound connectivity is discussed, clarify that Linux VMs also require outbound access for updates and other system functions.
Nat Gateway
Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates
...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority
View Details →
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, which exclusively provides a PowerShell example and workflow. There is no Azure CLI or Bash example for ARM template deployment, making it less accessible for Linux/macOS users. Additionally, PowerShell is presented first or exclusively in several sections, and the instructions for copying/pasting code reference Windows-centric actions (right-click, paste). While the Bicep deployment section does offer both CLI and PowerShell options, the ARM template section does not, creating friction for non-Windows users.
Recommendations
- Add Azure CLI and Bash examples for ARM template deployment alongside PowerShell.
- Ensure instructions for copying/pasting code are platform-neutral (e.g., mention keyboard shortcuts for macOS/Linux).
- Present CLI and PowerShell options in parallel or with equal prominence.
- Explicitly state that both CLI and PowerShell can be used for deployments, and link to cross-platform installation guides.
Nat Gateway
Deploy a NAT gateway after moving resources between regions
...b/main/articles/nat-gateway/region-move-nat-gateway.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (GUI) instructions, which are platform-neutral but implicitly favor Windows users due to the historical association of the Azure Portal with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux/macOS tooling or patterns. This omission may create friction for Linux/macOS users who prefer or require CLI-based workflows.
Recommendations
- Add Azure CLI examples for creating and configuring NAT gateways, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include PowerShell examples only if parity with Azure CLI is maintained, and clearly indicate which commands work on Linux/macOS.
- Explicitly mention that the Azure Portal is accessible from any modern browser and is not Windows-specific.
- Provide links to CLI documentation for users who prefer command-line automation.
Nat Gateway
Troubleshoot Azure NAT Gateway connectivity
.../articles/nat-gateway/troubleshoot-nat-connectivity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Troubleshooting examples and tool references (such as 'ps ping', 'netsh', and PowerShell-specific curl usage) are Windows-centric, with no equivalent Linux/macOS commands or guidance provided. Windows tools are mentioned exclusively, and examples (e.g., disabling keepalive in curl via PowerShell) are given only for Windows environments. This may create friction for Linux/macOS users who need to perform similar diagnostics or troubleshooting.
Recommendations
- Provide equivalent Linux/macOS commands for network troubleshooting (e.g., use 'ping', 'nc', 'tcpdump', 'ss', 'curl' with appropriate flags).
- Include examples for disabling keepalive in curl for Linux/macOS (e.g., 'curl --no-keepalive').
- Mention cross-platform tools (e.g., Wireshark, tcpdump) for packet capture and analysis.
- When referencing PowerShell or Windows-specific tools, add parallel instructions for Bash or other common Linux shells.
- Avoid assuming Windows as the default environment; present examples for both platforms side-by-side or in tabs.
Nat Gateway
Troubleshoot Azure NAT Gateway
...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several areas. In the connectivity validation table, Windows tools (PsPing, PowerShell Invoke-WebRequest) are listed with explicit links, while Linux tools are mentioned generically and without links. In troubleshooting sections, PowerShell commands are provided for resolving VM NIC failed states, but no equivalent CLI or Linux-native instructions are given. Azure Resource Explorer instructions recommend Microsoft Edge, a Windows-centric browser, without alternatives. Overall, Linux users are left to infer or research their own methods for several key troubleshooting steps.
Recommendations
- Provide Azure CLI or Bash examples alongside PowerShell commands for managing network interfaces and other resources.
- Include explicit Linux tool links and usage examples (e.g., nc, curl) in the connectivity validation table, matching the detail given for Windows tools.
- Offer browser-agnostic instructions for Azure Resource Explorer, or mention alternatives for non-Windows users.
- Ensure troubleshooting steps are platform-neutral or include both Windows and Linux/macOS workflows.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides step-by-step instructions for the Azure Portal and PowerShell, but omits Azure CLI (az) examples, which are cross-platform and preferred by many Linux/macOS users. All command-line automation is shown only in PowerShell, a tool most natural to Windows environments. There are no Bash or Azure CLI equivalents, and the prerequisites section only discusses PowerShell installation, not CLI. This creates friction for Linux/macOS users who may not have or want to use PowerShell.
Recommendations
- Add Azure CLI (az) command examples for each step alongside PowerShell and Portal instructions.
- Include a prerequisites section for Azure CLI, with installation and login instructions for Linux/macOS.
- Where possible, provide Bash script snippets or highlight that Azure CLI can be used in Bash, Zsh, etc.
- Clarify that PowerShell is available cross-platform, but Azure CLI is often more familiar to Linux/macOS users.
- Consider the order of examples: show Portal, then Azure CLI, then PowerShell, to avoid Windows-first bias.
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 →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
This documentation page demonstrates a notable Windows bias in its test and validation steps. While infrastructure setup uses both Ubuntu (for the simulated NVA) and Windows Server, all test virtual machines in the spokes are Windows Server 2022, and all validation instructions (IIS installation, connectivity tests) are exclusively for Windows (using Microsoft Edge, IIS, PowerShell). There are no equivalent Linux examples for deploying, configuring, or testing with a Linux VM in the spokes. The instructions for installing and testing web servers, as well as connectivity validation, are Windows-centric, making it harder for Linux/macOS users to follow or adapt the tutorial.
Recommendations
- Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the spokes, including portal and PowerShell steps.
- Provide Linux equivalents for IIS installation, such as installing Apache or Nginx, and show how to test connectivity using curl or a browser.
- Include validation steps for Linux VMs (e.g., SSH into the VM, check outbound IP with curl, verify inter-spoke routing with curl or wget).
- Ensure all PowerShell scripts have Bash/Azure CLI equivalents for Linux users.
- Present both Windows and Linux examples side-by-side, or allow users to choose their preferred OS path.
Nat Gateway
Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates
...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page shows a notable Windows bias, especially in the ARM template deployment section, which exclusively provides a PowerShell example and workflow. Linux/macOS users are not given an Azure CLI example for ARM template deployment, and PowerShell is presented first and in more detail throughout. While Bicep deployment includes both CLI and PowerShell options, ARM template deployment is Windows-centric, creating friction for non-Windows users.
Recommendations
- Add Azure CLI examples for ARM template deployment, showing equivalent steps for Linux/macOS users.
- Present CLI and PowerShell options side-by-side or in tabs for all deployment sections, not just Bicep.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify which shell is being used in each example.
- Ensure that Linux/macOS users have clear, step-by-step instructions for all major tasks, including resource group deletion.
Nat Gateway
Troubleshoot Azure NAT Gateway
...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits several Windows-centric biases. In troubleshooting and validation sections, Windows tools (PsPing, PowerShell Invoke-WebRequest) are highlighted, with PowerShell-based instructions provided for resolving failed network interface states. Linux equivalents are either missing or referenced only generically (e.g., 'application specific' for UDP tests), and Windows tools are described in more detail. The order of presentation often puts Windows tools and methods first, and Linux-specific guidance is minimal.
Recommendations
- Provide explicit Linux/macOS command-line examples for all troubleshooting steps, including resolving failed network interface states (e.g., using Azure CLI or REST API via curl/jq).
- Include Linux/macOS tools for TCP/UDP connectivity validation (e.g., socat, netcat, curl, iperf) with concrete command examples.
- Ensure parity in troubleshooting instructions by offering Azure CLI and REST API alternatives alongside PowerShell for all resource management tasks.
- Present Linux/macOS and Windows examples side-by-side or in parallel tabs, rather than listing Windows tools first.
- Clarify which steps are platform-agnostic and which require OS-specific tooling.
Nat Gateway
Manage a Standard V2 NAT Gateway
...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions and code samples exclusively for Azure PowerShell, which is primarily associated with Windows and PowerShell environments. There are no examples or guidance for Azure CLI, Bash, or Linux/macOS-native tooling. The PowerShell instructions are presented as the only command-line automation option, and there is no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash scripts.
Recommendations
- Add equivalent Azure CLI examples for all operations (create, associate, remove, update NAT gateway, public IPs, and prefixes).
- Explicitly mention that Azure CLI is cross-platform and provide links to its installation and usage.
- Where PowerShell is referenced, clarify that Azure PowerShell can be used in Azure Cloud Shell (which is cross-platform), but still provide CLI/Bash alternatives.
- Reorder or parallelize example sections so that CLI and PowerShell are presented equally, not PowerShell-first.
- Include notes or tables comparing PowerShell and CLI commands for each task.
Medium Priority
View Details →
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, in the 'NAT Gateway and basic resources' section, the link for upgrading a Load Balancer from basic to standard is provided only for PowerShell, which is primarily a Windows tool, with no equivalent CLI or Linux/macOS instructions referenced. These instances may create friction for Linux/macOS users seeking parity in examples and guidance.
Recommendations
- Include examples or references for Linux/macOS users, such as using Azure CLI or Bash scripts, especially for resource upgrades and configuration tasks.
- Mention Linux-specific scenarios that require outbound connectivity (e.g., package updates via apt/yum, activation of enterprise Linux subscriptions) alongside Windows examples.
- Provide links to documentation for upgrading resources using Azure CLI or portal, not just PowerShell.
- Ensure that all platform-specific instructions are presented together or in parallel, rather than Windows-first.
Nat Gateway
Troubleshoot Azure NAT Gateway connectivity
.../articles/nat-gateway/troubleshoot-nat-connectivity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits moderate Windows bias, primarily through the use of PowerShell-specific examples (e.g., 'ps ping', curl in PowerShell, netsh trace) and references to Windows-centric troubleshooting tools. Windows tools and patterns are mentioned exclusively or before any Linux equivalents, and there is a lack of explicit Linux/macOS command examples for key troubleshooting steps.
Recommendations
- Provide equivalent Linux/macOS troubleshooting commands alongside PowerShell examples (e.g., use 'ping', 'nc', 'tcpdump', 'curl' with Linux flags).
- Mention cross-platform tools (e.g., Wireshark, tcpdump) for packet capture and network tracing.
- Clarify that steps such as rebooting VMs, checking routing tables, and managing NSGs can be performed on any OS, and provide links or brief instructions for Linux/macOS users.
- Avoid assuming PowerShell as the default shell; offer Bash or CLI alternatives where appropriate.
- Balance examples so that Linux/macOS commands are presented with equal prominence to Windows/PowerShell commands.
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 →
Detected Bias Types
Windows First
Windows Heavy
Powershell Heavy
Missing Linux Example
Summary
This documentation page demonstrates a notable Windows bias, especially in the testing and validation sections. While the simulated NVA is an Ubuntu VM and its configuration uses Linux commands, all test VMs in the spokes are Windows Server 2022, and all testing instructions (e.g., verifying NAT gateway and inter-spoke routing) rely on Microsoft Edge and Windows-specific workflows. There are no Linux VM test examples, nor instructions for using Linux tools (e.g., curl, wget, or browser alternatives) to validate connectivity. The PowerShell examples are extensive, with no Bash/CLI equivalents provided. This creates friction for users who prefer or require Linux-based validation and automation.
Recommendations
- Add parallel Linux VM deployment instructions for spoke test VMs, including Ubuntu or other common distributions.
- Provide Linux CLI commands (e.g., curl, wget) for testing outbound NAT and inter-spoke connectivity, alongside Windows/Edge examples.
- Include Azure CLI (az) or Bash script examples in addition to PowerShell for resource creation and management.
- Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both.
- Ensure that validation steps (e.g., checking public IP, web server access) are shown for both OS types.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides step-by-step instructions for the Azure Portal and PowerShell, but omits Azure CLI (az) examples, which are cross-platform and preferred by many Linux/macOS users. All command-line automation is shown exclusively with PowerShell cmdlets, which are traditionally associated with Windows environments, and there is no mention of Bash scripting or native Linux tooling. This creates friction for users on Linux or macOS who may not have PowerShell installed or prefer the Azure CLI.
Recommendations
- Add equivalent Azure CLI (az) command examples for every PowerShell example, ideally in a dedicated tab.
- Explicitly mention that PowerShell Core is cross-platform, but clarify that Azure CLI is often more familiar to Linux/macOS users.
- Where possible, provide Bash script snippets or guidance for Linux-native environments.
- Ensure that references to installing tools (e.g., Azure PowerShell) also include instructions for installing Azure CLI on Linux/macOS.
- Consider listing Azure CLI examples before PowerShell to reduce perceived Windows-first bias.
Nat Gateway
Design virtual networks with Azure NAT Gateway
...s/blob/main/articles/nat-gateway/nat-gateway-design.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references Windows-specific services (Windows Activation and Windows Updates) as examples of workloads requiring outbound connectivity, without mentioning Linux equivalents (such as Linux package updates or activation). There are no command-line examples, but when discussing outbound connectivity requirements, only Windows scenarios are highlighted. No Linux-specific patterns, tools, or examples are provided.
Recommendations
- Include Linux-specific examples of outbound connectivity needs, such as package manager updates (apt, yum, etc.), OS activation, or other common Linux services.
- When listing services that require outbound connectivity, mention both Windows and Linux scenarios to provide parity.
- If providing troubleshooting or monitoring examples, include Linux CLI commands (such as Azure CLI usage on Linux, or log analysis with Linux tools) alongside any PowerShell or Windows-centric instructions.
- Ensure that diagrams and tables use generic terms (e.g., 'VM' or 'compute instance') and clarify that guidance applies to both Windows and Linux virtual machines.
Nat Gateway
Deploy a NAT gateway after moving resources between regions
...b/main/articles/nat-gateway/region-move-nat-gateway.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal UI for NAT gateway deployment and resource movement, which is most commonly accessed from Windows environments. There are no examples or instructions for using cross-platform command-line tools such as Azure CLI or Azure PowerShell, nor are Linux-specific patterns or tools mentioned. This may disadvantage users who prefer or require Linux or command-line automation.
Recommendations
- Add step-by-step instructions for deploying and configuring NAT gateway using Azure CLI, which is cross-platform and widely used on Linux.
- Include equivalent examples for Azure PowerShell, noting its availability on Linux and macOS as well as Windows.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to CLI and PowerShell installation guides for non-Windows platforms.
- Where UI screenshots or references are given, clarify that the Azure portal is accessible from any modern browser on any OS.
Nat Gateway
Design virtual networks with Azure NAT Gateway
...s/blob/main/articles/nat-gateway/nat-gateway-design.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by mentioning Windows-specific services (Windows Activation and Windows Updates) as examples of workloads requiring outbound connectivity, without referencing equivalent Linux scenarios (such as Linux package updates or activation). There are no command-line examples, but where operating system-specific requirements are discussed, only Windows is mentioned. No Linux-specific tools, patterns, or examples are provided.
Recommendations
- Include Linux-specific outbound connectivity scenarios, such as package manager updates (apt, yum, zypper), OS activation (where applicable), or cloud-init operations.
- When listing services that require outbound connectivity, mention both Windows and Linux equivalents to ensure parity.
- If providing examples or troubleshooting steps, include both PowerShell/Windows and Bash/Linux CLI commands.
- Explicitly state that NAT Gateway supports outbound connectivity for both Windows and Linux VMs, and provide links to documentation for configuring outbound access for Linux workloads.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. It specifically mentions Windows Activation and Windows Updates as examples of services requiring outbound connectivity, without referencing Linux equivalents (such as package updates or activation for Linux distributions). Additionally, upgrade instructions for basic resources (e.g., Load Balancer) reference PowerShell, a Windows-centric tool, without mentioning cross-platform alternatives like Azure CLI or ARM templates. No Linux-specific examples, tools, or patterns are provided, and Windows scenarios are mentioned first or exclusively in relevant sections.
Recommendations
- Include Linux-specific examples of services that require outbound connectivity, such as apt/yum package updates, OS activation, or cloud-init operations.
- Provide upgrade instructions for basic resources using Azure CLI and ARM templates alongside PowerShell, ensuring cross-platform parity.
- Explicitly mention that NAT Gateway supports outbound connectivity for both Windows and Linux VMs, with examples for each.
- Add references to Linux administration tools and patterns where relevant, such as using curl/wget for connectivity validation.
- Review and update documentation to ensure that Windows and Linux scenarios are presented with equal prominence and detail.
Nat Gateway
Deploy a NAT gateway after moving resources between regions
...b/main/articles/nat-gateway/region-move-nat-gateway.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes resource deployment and management using the Azure portal UI, which is most commonly accessed from Windows environments. There are no CLI, PowerShell, or Bash examples, nor are Linux-specific tools or workflows mentioned. The absence of Azure CLI or Bash instructions means Linux users do not have parity in guidance for automating or scripting these tasks.
Recommendations
- Add step-by-step instructions using Azure CLI commands for creating and configuring NAT gateways, including resource association and deletion.
- Include Bash script examples for common workflows, such as moving resources and testing NAT gateway functionality.
- Explicitly mention that the Azure portal is accessible from any OS, and provide links or references to cross-platform tools.
- Ensure parity by presenting CLI/Bash examples before or alongside portal instructions, not after.
- Reference PowerShell only if CLI/Bash is also covered, and clarify OS compatibility for each method.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/nat-gateway-design.md
...s/blob/main/articles/nat-gateway/nat-gateway-design.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by mentioning Windows-specific services (Windows Activation and Windows Updates) as examples of workloads requiring outbound connectivity, without referencing equivalent Linux scenarios (such as Linux package updates or activation). There are no command-line examples, but the only concrete OS-specific use case is Windows-centric, and Linux needs are not addressed. No PowerShell, Windows tools, or Windows-first instructions are present, but the documentation does not provide parity in describing Linux requirements for outbound connectivity.
Recommendations
- Include Linux-specific examples, such as the need for outbound connectivity for apt/yum/dnf package updates, OS activation (if applicable), or security patching.
- Explicitly mention that Linux VMs also require outbound connectivity for system updates and other functions, not just Windows VMs.
- If discussing OS-specific scenarios, provide equal coverage for both Windows and Linux, possibly in a table or a dedicated section.
- Consider adding references to Linux documentation or best practices for managing outbound connectivity for Linux workloads.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/region-move-nat-gateway.md
...b/main/articles/nat-gateway/region-move-nat-gateway.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes resource deployment and management using the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no CLI, PowerShell, or Bash examples, nor any mention of Linux-specific tools or workflows. This may disadvantage Linux users or those who prefer command-line automation, as no parity is provided for Azure CLI or Bash scripting approaches.
Recommendations
- Add equivalent Azure CLI examples for all steps, including resource creation, association, and deletion.
- Include Bash script snippets for Linux users to automate NAT gateway deployment and resource association.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows using Azure CLI.
- Provide links to documentation for cross-platform tools (Azure CLI, REST API) alongside portal instructions.
- Ensure that examples and screenshots are not Windows-centric and clarify platform neutrality where possible.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/nat-gateway-design.md
...s/blob/main/articles/nat-gateway/nat-gateway-design.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by specifically mentioning Windows Activation and Windows Updates as services requiring outbound connectivity, without referencing equivalent Linux scenarios (such as package updates or activation for Linux-based workloads). There are no OS-specific examples or CLI commands, but the only explicit outbound connectivity scenario described is for Windows, and Linux equivalents are omitted.
Recommendations
- Include examples of outbound connectivity requirements for Linux VMs, such as package manager updates (apt, yum, etc.), or cloud-init operations.
- Add a general statement that outbound connectivity is required for both Windows and Linux workloads for system updates, package installations, and other OS-level operations.
- Where outbound connectivity is discussed, mention both Windows and Linux operating systems to ensure parity and inclusivity.
- If possible, provide links or references to documentation on configuring outbound connectivity for Linux VMs in Azure.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/nat-overview.md
...re-docs/blob/main/articles/nat-gateway/nat-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific services (Windows Activation and Windows Updates) as requiring outbound connectivity, without mentioning Linux equivalents. Additionally, upgrade instructions for basic resources (Load Balancer, public IP) reference PowerShell and Windows-centric workflows first, with no mention of Linux or cross-platform CLI alternatives. There are no explicit Linux examples or references to Linux-specific outbound connectivity needs.
Recommendations
- Include references to Linux VM outbound connectivity requirements (e.g., package updates, activation of enterprise Linux subscriptions) alongside Windows-specific needs.
- Provide upgrade instructions for basic resources using Azure CLI and/or ARM templates, which are cross-platform, in addition to PowerShell.
- Ensure that examples and guidance do not assume Windows as the default platform; mention both Windows and Linux scenarios where relevant.
- Add links or notes about outbound connectivity for common Linux services (e.g., apt/yum updates, SSH key retrieval) to illustrate NAT Gateway's relevance for Linux workloads.