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 1-25 of 89 flagged pages
Nat Gateway
Manage a Standard V2 NAT Gateway
...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page provides detailed instructions and code samples exclusively for Azure PowerShell, a Windows-centric tool, with no examples for Azure CLI, Bash, or Linux-native workflows. All command-line automation is shown using PowerShell, and there is no mention of Linux shell equivalents or cross-platform scripting. The structure and examples prioritize Windows tooling and patterns, making it difficult for Linux users to follow or replicate the steps without adaptation.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command sequences, using Bash syntax where appropriate.
- Include explicit instructions and code samples for Linux/macOS users, such as using Azure CLI in Bash or Cloud Shell.
- Mention cross-platform compatibility of Azure tools and clarify which steps can be performed identically on Linux, macOS, and Windows.
- Reorder or parallelize example sections so that Azure CLI/Bash and PowerShell are presented side-by-side, rather than PowerShell-only.
- Avoid exclusive reliance on Windows-specific tools (e.g., PowerShell modules) and reference platform-agnostic alternatives where possible.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It specifically mentions Windows Activation and Windows Updates as requiring outbound connectivity, without referencing equivalent Linux scenarios (such as package updates or activation for Linux-based VMs). Additionally, upgrade instructions for basic resources (like Load Balancer) reference PowerShell, a Windows-centric tool, without mentioning Azure CLI or other cross-platform alternatives. There are no explicit Linux examples or references to Linux-specific outbound connectivity needs.
Recommendations
- Include Linux VM scenarios that require outbound connectivity, such as OS package updates (apt, yum, etc.), and reference these alongside Windows Activation/Updates.
- When providing upgrade instructions (e.g., upgrading Load Balancer or public IP), offer Azure CLI examples in addition to PowerShell, and present them together or with CLI first.
- Add explicit statements clarifying that NAT Gateway supports outbound connectivity for both Windows and Linux VMs, and mention typical Linux use cases.
- Ensure that all examples and tutorials include both PowerShell and Azure CLI (or REST API) steps to improve cross-platform parity.
Nat Gateway
Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates
...-gateway/quickstart-create-nat-gateway-v2-templates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell usage. The ARM template deployment section exclusively provides Azure PowerShell instructions, with no Azure CLI or Bash example for Linux/macOS users. PowerShell is presented first and in greater detail, while CLI instructions are only available for Bicep deployments. There is no mention of Linux-native tools or workflows for ARM template deployment, and the initial deployment workflow assumes familiarity with PowerShell, which is primarily a Windows tool.
Recommendations
- Add Azure CLI (az) examples for ARM template deployment alongside PowerShell, especially in the ARM template tab.
- Present CLI and PowerShell instructions in parallel or allow users to select their preferred environment, rather than defaulting to PowerShell.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash/CLI instructions for Linux/macOS users.
- Ensure that Linux/macOS users are not required to use PowerShell for deployment tasks, and clarify cross-platform options.
- Review the order of presentation so that CLI and PowerShell are given equal prominence, or allow users to select their OS/workflow first.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page shows evidence of Windows bias primarily through extensive PowerShell examples, detailed guidance on using Azure PowerShell and Cloud Shell (which is often associated with Windows users), and instructions for installing/updating Azure PowerShell locally. The PowerShell tab is presented before the CLI tab, and PowerShell-specific tooling is described in greater detail than CLI or Linux-native alternatives. While Linux is referenced (e.g., Ubuntu VM deployment, bash commands), the documentation favors Windows-centric tools and patterns, especially in the prerequisites and example sections.
Recommendations
- Provide equal detail for Azure CLI usage, including local installation and environment setup for Linux/macOS users.
- Add explicit instructions for running CLI commands on Linux/macOS, including shell environment notes and troubleshooting tips.
- Include references to Linux-native automation tools (e.g., shell scripts) where PowerShell scripts are shown.
- Reorder tabs so that CLI examples are presented before or alongside PowerShell, reflecting cross-platform parity.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
- Avoid describing PowerShell as the default or primary method; use neutral language when introducing deployment options.
Nat Gateway
Create a Standard V2 Azure NAT Gateway
...ticles/nat-gateway/quickstart-create-nat-gateway-v2.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and instructions are given equal prominence to Azure CLI, but PowerShell is mentioned before CLI in prerequisites and throughout the document. Instructions for running Azure CLI locally mention Windows and macOS specifically, with Linux only implied. There is a strong focus on Azure PowerShell, a Windows-centric tool, and references to Windows patterns (e.g., Get-Credential) are present. However, CLI examples are provided for all steps, and Linux is the default OS for the VM example, which helps mitigate bias.
Recommendations
- Explicitly mention Linux as a supported platform for Azure CLI in the prerequisites, and provide Linux-specific instructions where appropriate (e.g., SSH key handling, file paths).
- Present CLI examples before PowerShell examples, or alternate their order, to avoid Windows-first perception.
- Add notes or links for Linux users regarding installation and usage of Azure CLI and Cloud Shell.
- Where PowerShell-specific patterns (like Get-Credential) are used, provide equivalent Linux/CLI guidance (e.g., using environment variables or files for credentials).
- Ensure that all references to running commands locally include Linux as a first-class option, not just Windows/macOS.
- Consider adding a short section or callout for Linux users, especially in areas where Windows tools or workflows are referenced.
Nat Gateway
Troubleshoot Azure NAT Gateway connectivity
.../articles/nat-gateway/troubleshoot-nat-connectivity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Troubleshooting steps and examples reference Windows-centric tools (e.g., PowerShell, netsh, PsPing) without providing Linux equivalents. When discussing connection testing and state flushing, PowerShell and Windows reboot instructions are given, but Linux commands and workflows are omitted. The documentation mentions browser and curl usage in PowerShell, but does not show how to test or flush connections on Linux. Overall, the guidance assumes a Windows environment for VM management and troubleshooting, with little consideration for Linux users.
Recommendations
- Provide Linux equivalents for all troubleshooting commands (e.g., use tcpdump, ss, ip, ping, nc, lsof, netstat for network diagnostics and connection state).
- Include examples for connection testing and state flushing on Linux VMs (e.g., how to restart networking, flush connections, or reboot on Linux).
- When referencing tools like PsPing and netsh, also mention and give examples for Linux-native tools.
- Ensure that instructions for validating outbound connectivity, managing connections, and troubleshooting are platform-neutral or include both Windows and Linux workflows.
- Explicitly state when a step or tool is Windows-specific, and provide a Linux alternative in parallel.
- Add troubleshooting scenarios and best practices relevant to common Linux distributions used in Azure (Ubuntu, CentOS, etc.).
Nat Gateway
Troubleshoot Azure NAT Gateway
...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools (PsPing, PowerShell Invoke-WebRequest) are presented alongside Linux tools, but Windows examples are more detailed and PowerShell is used for troubleshooting steps without equivalent Linux CLI or Azure CLI examples. In troubleshooting failed network interfaces, only PowerShell and Azure Resource Explorer (browser-based, with a Microsoft Edge recommendation) are provided, omitting Linux/Azure CLI alternatives. The order of presentation often lists Windows tools before Linux, and some steps are Windows-centric.
Recommendations
- Add equivalent Azure CLI or REST API commands for all PowerShell-based troubleshooting steps, ensuring Linux users have parity.
- Provide Linux-specific examples (e.g., using curl, nc, or Azure CLI) wherever Windows tools or PowerShell are referenced.
- When listing tools or commands, alternate or group by OS, and avoid consistently listing Windows tools first.
- Remove browser recommendations that are Windows-specific (e.g., Microsoft Edge) or provide alternatives for Linux/macOS users.
- Explicitly mention cross-platform tools and approaches to troubleshooting, and ensure all steps can be performed from Linux or macOS environments.
Nat Gateway
Tutorial: Use a NAT gateway with a hub and spoke network
...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by using Windows Server virtual machines for all test scenarios, providing only Windows-specific tools (e.g., Microsoft Edge, IIS, PowerShell) for verification and configuration, and omitting equivalent Linux-based examples for test VMs and web servers. The PowerShell examples are extensive, while Linux CLI or Bash alternatives are not provided for resource creation or configuration. The workflow for testing NAT gateway and inter-spoke routing is exclusively Windows-centric.
Recommendations
- Add equivalent Linux VM test scenarios (e.g., Ubuntu or other Linux distributions) in the spokes, with instructions for deploying, configuring, and testing using Linux tools (e.g., curl, wget, Apache/Nginx web server).
- Provide Bash/Azure CLI examples alongside PowerShell for all resource creation and configuration steps.
- Include instructions for testing outbound NAT and inter-spoke routing from Linux VMs, such as using curl to check public IP (e.g., curl ifconfig.me) and accessing web servers.
- Mention Linux tools and browsers (e.g., Firefox, Chromium) for verification steps, not just Microsoft Edge.
- Ensure parity in portal instructions by referencing both Windows and Linux VM images and configuration options.
- Add cleanup instructions for Linux-based resources if any are created.
Nat Gateway
Integrate NAT Gateway with Azure Firewall in Hub and Spoke Network
...rticles/nat-gateway/tutorial-hub-spoke-nat-firewall.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation provides step-by-step instructions for integrating NAT Gateway with Azure Firewall, offering examples via the Azure Portal and PowerShell. There is a strong bias toward Windows-centric tooling: all command-line examples use PowerShell, with no Bash/Azure CLI equivalents provided. PowerShell is presented as the only scripting option, and Windows tools/patterns (e.g., Get-Credential, PowerShell modules) are referenced exclusively. The structure consistently lists Portal and PowerShell tabs, omitting Azure CLI/Bash, which are preferred by Linux users. This results in missing Linux parity and a Windows-first experience.
Recommendations
- Add Azure CLI (bash) examples for every PowerShell example, ensuring Linux users have direct, native instructions.
- Include a CLI tab alongside Portal and PowerShell in all code sections.
- Reference Azure CLI documentation and installation instructions in prerequisites, not just PowerShell.
- Where authentication or credential management is discussed, provide Linux-native alternatives (e.g., SSH key generation, az login).
- Review terminology and tool references to ensure cross-platform neutrality (e.g., avoid assuming Get-Credential or PowerShell modules are default).
- Explicitly state that both PowerShell and Azure CLI are supported, and link to both sets of docs.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is given a dedicated section with extensive, step-by-step examples for every operation, often with more detailed context and variable usage than the Azure CLI equivalents. The PowerShell section is always listed before the Azure CLI section, and the prerequisites for PowerShell include instructions for local installation and module management, which are Windows-centric. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux users (such as using Bash scripts or Linux-native tools). The CLI examples are generic and do not clarify cross-platform usage, and the documentation does not address differences in experience between Windows and Linux environments.
Recommendations
- Add explicit Bash shell examples for Azure CLI usage, including variable assignment and command chaining, to demonstrate parity for Linux users.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide guidance for installing and using Azure CLI on Linux systems.
- Balance the order of sections by alternating or randomizing the presentation of PowerShell and CLI examples, or by listing CLI before PowerShell in some cases.
- Include notes or callouts for Linux/macOS users regarding environment setup, such as using Azure CLI in native shells or Cloud Shell.
- Reduce the emphasis on PowerShell-specific prerequisites and provide equivalent detail for CLI usage on Linux.
- Consider adding troubleshooting tips or environment-specific notes for Linux users, such as file permissions or shell differences.
Nat Gateway
Troubleshoot Azure NAT Gateway connectivity
.../articles/nat-gateway/troubleshoot-nat-connectivity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: troubleshooting steps and examples reference PowerShell (e.g., 'curl in PowerShell', 'ps ping', 'netsh trace'), and Windows-specific tools are mentioned without Linux equivalents. No Linux shell commands (such as curl in bash, tcpdump, or iptables) are provided, and examples are framed in a Windows-first context. This may make the guidance less accessible to users operating Linux-based Azure VMs.
Recommendations
- Provide Linux shell equivalents for all command-line examples (e.g., show how to use curl in bash, use tcpdump for packet capture, etc.).
- Mention Linux troubleshooting tools (such as netstat, ss, ip, tcpdump, lsof) alongside Windows tools like netsh.
- When referencing PowerShell, also include Bash or other Linux shell syntax/examples.
- Avoid assuming the reader is using Windows; clarify that instructions apply to both Windows and Linux, or specify OS where relevant.
- Add explicit Linux-focused troubleshooting steps and examples, especially for network diagnostics and connection state management.
Nat Gateway
Manage a Standard V2 NAT Gateway
...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page provides detailed instructions and code samples exclusively for Azure PowerShell, which is primarily a Windows-centric tool, with no examples for Azure CLI, Bash, or Linux-native workflows. All command-line automation is shown using PowerShell syntax, and prerequisites focus on PowerShell installation and usage. There is no mention of Linux shell equivalents or cross-platform command-line tools, and PowerShell examples are presented before any mention of alternatives.
Recommendations
- Add equivalent Azure CLI examples for all operations (create, associate, remove, add/remove IPs/prefixes) alongside PowerShell, using Bash syntax where appropriate.
- Include instructions for installing and using Azure CLI on Linux and macOS in the prerequisites section.
- Clearly indicate which tools are cross-platform and provide guidance for users on Linux and macOS.
- Ensure parity in detail and completeness between PowerShell and CLI examples, so Linux users have equal access to automation workflows.
- Consider adding a tabbed interface for 'Azure CLI' and 'Bash' alongside 'Azure PowerShell', mirroring the structure used for the portal and PowerShell.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell (a Windows-centric tool) is featured prominently and with extensive example coverage, often before Azure CLI. The prerequisites and example sections for PowerShell are more detailed than those for CLI, including module installation, version checks, and authentication steps. There is no mention of Linux-specific shell environments (e.g., bash) or native Linux tools, and the CLI examples are generic, not tailored to Linux workflows. The documentation assumes familiarity with PowerShell and Windows patterns, and does not provide parity for Linux users beyond the basic Azure CLI commands.
Recommendations
- Add explicit Linux shell (bash/zsh) examples and instructions, especially for Azure CLI usage, including environment setup and authentication steps.
- Balance the depth of prerequisites and troubleshooting guidance between PowerShell and CLI sections, ensuring Linux users are equally supported.
- Mention and link to Azure CLI installation and usage on Linux, including package manager commands (apt, yum, etc.), not just generic CLI requirements.
- Where PowerShell-specific troubleshooting or module management is discussed, provide equivalent guidance for CLI on Linux (e.g., updating CLI, managing credentials).
- Consider reordering sections so that platform-neutral or Linux-friendly tools (Azure CLI, Bicep) are presented before PowerShell, or at least in parallel.
- Explicitly state that Azure CLI commands are cross-platform and provide notes or tips for Linux users (e.g., differences in quoting, environment variables).
Nat Gateway
Create a Standard V2 Azure NAT Gateway
...ticles/nat-gateway/quickstart-create-nat-gateway-v2.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation method alongside the Azure portal, with detailed instructions and explanations for PowerShell usage. Windows-specific tools and patterns (PowerShell, Cloud Shell, local PowerShell installation) are mentioned before or with more detail than their Linux equivalents. While Azure CLI examples are provided (which work cross-platform), the introductory and prerequisite sections emphasize PowerShell and Windows-centric workflows. There is little explicit mention of Linux-specific environments or shell usage, and the CLI section suggests Docker for macOS/Windows but does not mention native Linux usage.
Recommendations
- Explicitly mention that Azure CLI works natively on Linux and provide guidance for Linux users in the prerequisites.
- Add examples or notes for running Azure CLI commands in common Linux shells (bash, zsh), including installation and authentication steps.
- Balance introductory content to present CLI and PowerShell equally, or consider listing CLI before PowerShell to avoid Windows-first ordering.
- Where PowerShell-specific instructions are given (e.g., credential handling), provide equivalent Linux/CLI workflows (such as SSH key generation and management).
- Include references to Linux documentation or troubleshooting for common issues encountered by Linux users.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide links or instructions for both.
Nat Gateway
Integrate NAT Gateway with Azure Firewall in Hub and Spoke Network
...rticles/nat-gateway/tutorial-hub-spoke-nat-firewall.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Windows Tools
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 is a strong bias toward Windows-centric tooling: all command-line examples use PowerShell, with no Bash, Azure CLI, or Linux-native shell examples. PowerShell is presented as the only scriptable option, and Windows/PowerShell instructions are given equal or greater prominence than the Portal. There is no mention of Linux equivalents or cross-platform CLI usage, and the prerequisites and setup steps assume PowerShell as the default automation tool.
Recommendations
- Add Azure CLI (az) examples for each step alongside PowerShell, using Bash syntax to ensure Linux parity.
- Explicitly mention that Azure CLI is cross-platform and can be used from Linux, macOS, and Windows.
- Where PowerShell is referenced, clarify that it is available on Linux and macOS, but provide CLI alternatives for users who prefer Bash.
- Include notes or sections for Linux users, such as how to install and authenticate with Azure CLI.
- Ensure that any references to local scripting or automation do not assume a Windows environment.
- Consider reordering examples so that cross-platform CLI instructions are presented before or alongside PowerShell.
Nat Gateway
Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates
...-gateway/quickstart-create-nat-gateway-v2-templates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing PowerShell examples first and in greater detail, especially in the ARM template deployment section. The initial deployment instructions use Azure PowerShell in Cloud Shell, with no equivalent Azure CLI (Linux-friendly) example for ARM template deployment. The Bicep section does offer both CLI and PowerShell, but PowerShell is still presented as an option. There is an absence of explicit Linux shell (bash) instructions for ARM template deployment, and Windows/PowerShell terminology appears before Linux/CLI alternatives. The SSH key note references Linux paths, but overall, deployment guidance is Windows/PowerShell-centric.
Recommendations
- Add Azure CLI (bash) examples for ARM template deployment alongside PowerShell, especially in the ARM template section.
- Present CLI (Linux-friendly) instructions before or alongside PowerShell instructions to avoid Windows-first ordering.
- Explicitly mention that Azure Cloud Shell supports both bash and PowerShell, and provide instructions for both.
- Ensure all steps (copy/paste, resource deletion, etc.) have CLI equivalents, not just PowerShell.
- Consider adding a table or tabs that let users choose their preferred environment (CLI/bash, PowerShell, etc.) for all deployment and management tasks.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides full parity between Azure Portal, Azure CLI, PowerShell, and Terraform for creating a NAT Gateway. However, the PowerShell section is notably detailed and uses Windows-centric tooling (PowerShell), which is traditionally associated with Windows environments. The PowerShell tab appears before the CLI tab, and PowerShell-specific instructions (such as installing/updating Azure PowerShell) are given more prominence than equivalent Linux shell instructions. There is no explicit Linux shell example (e.g., Bash scripts outside of Azure CLI), and PowerShell is presented as a primary automation method, which may suggest a Windows bias.
Recommendations
- Ensure CLI (az) examples are given equal or greater prominence than PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Add explicit Bash shell script examples for resource creation and cleanup, demonstrating usage outside of the Azure CLI tool.
- Clarify that Azure PowerShell is available cross-platform and provide installation instructions for Linux/macOS alongside Windows.
- Consider reordering tabs so that CLI or Portal appears before PowerShell, reducing the perception of Windows-first bias.
- Where possible, reference Linux-native tools (e.g., Bash, SSH) in verification and troubleshooting steps, not just PowerShell.
- Highlight that all steps can be performed on Linux, macOS, and Windows, and link to platform-specific setup guides.
Nat Gateway
Troubleshoot Azure NAT Gateway
...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. In troubleshooting steps, Windows tools (PowerShell, PsPing) are mentioned explicitly, with detailed instructions and links, while Linux equivalents are either omitted or referenced generically. For example, PowerShell commands are provided for resolving network interface issues, but no Linux CLI or Azure CLI alternatives are given. In connectivity validation, Windows tools are listed with links and specific commands, whereas Linux tools are referenced without detail or links. This prioritization and lack of Linux parity may hinder Linux users' troubleshooting experience.
Recommendations
- Add equivalent Linux/Azure CLI commands for all PowerShell-based troubleshooting steps, especially for managing network interfaces and NAT gateway resources.
- Provide detailed Linux tool usage examples (e.g., using nc, curl, ip, az CLI) with command syntax and links to documentation, matching the detail given for Windows tools.
- Ensure that tables and lists of troubleshooting tools and steps present Linux and Windows options with equal prominence and detail.
- Where Azure Resource Explorer is recommended, clarify that it is browser-based and platform-agnostic, and avoid browser recommendations that imply Windows-only usage.
- Review all troubleshooting workflows to ensure Linux users can follow each step without needing to translate Windows-specific instructions.
Nat Gateway
Tutorial: Use a NAT gateway with a hub and spoke network
...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows Server is used exclusively for test VMs in both spokes, with no Linux alternative provided; IIS (a Windows-only web server) is used for connectivity tests; all test and verification steps rely on Windows tools (Microsoft Edge, IIS); PowerShell is the only CLI scripting option shown, with no Bash/Azure CLI equivalents; and Windows VM creation and configuration steps are detailed before any mention of Linux options. While the NVA is simulated with Ubuntu, all user-facing test and validation steps are Windows-centric.
Recommendations
- Provide parallel Linux-based examples for spoke VMs, such as deploying Ubuntu or other Linux distributions.
- Include instructions for installing and testing with Apache or Nginx on Linux VMs, alongside IIS on Windows.
- Offer Azure CLI (Bash) scripting examples in addition to PowerShell for all resource creation and management steps.
- Demonstrate connectivity and NAT gateway verification using Linux tools (e.g., curl, wget, or browser access from Linux desktop environments).
- Ensure that both Windows and Linux test VM options are presented equally, and avoid defaulting to Windows-only tools for verification steps.
- Add notes or sections explaining how to adapt the tutorial for Linux-only environments.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway-v2.md
...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page provides detailed instructions for managing a Standard V2 NAT Gateway using the Azure portal and Azure PowerShell, with all CLI examples exclusively in PowerShell. There are no examples using Azure CLI (bash), nor any mention of Linux-native tools or shell environments. The PowerShell instructions are extensive and appear before any mention of Azure CLI, which is only referenced in metadata. This creates a bias toward Windows and PowerShell users, making it less accessible for Linux or cross-platform users who rely on Azure CLI.
Recommendations
- Add equivalent Azure CLI (bash) examples for all PowerShell command sections, ensuring parity in functionality and clarity.
- Explicitly mention that Azure CLI can be used from Linux, macOS, and Windows, and provide installation instructions or links.
- Reorganize code example tabs so that Azure CLI appears before or alongside PowerShell, not after.
- Where possible, use generic terminology (e.g., 'command line') rather than 'PowerShell' when referring to cross-platform operations.
- Include notes or guidance for Linux/macOS users, such as how to run Azure CLI commands in their environments.
- Audit future documentation to ensure both PowerShell and Azure CLI examples are provided for all resource management tasks.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway.md
...s/blob/main/articles/nat-gateway/manage-nat-gateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently and in detail, with extensive, step-by-step examples and explanations, often before or in parallel with Azure CLI. The prerequisites and instructions for PowerShell assume local installation, which is most common on Windows, and reference Windows-specific tools and patterns (e.g., PowerShell modules, cmdlets). Azure CLI is provided, but PowerShell examples are more verbose and detailed. There is little explicit mention of Linux-specific considerations, and no Bash or shell scripting examples are given. The overall structure and depth of PowerShell coverage suggest a Windows-centric approach.
Recommendations
- Add explicit Bash shell scripting examples for Azure CLI commands, showing usage in Linux/macOS terminals.
- Clarify that Azure CLI is cross-platform and provide Linux/macOS installation instructions or links.
- Balance the depth of PowerShell and CLI examples, ensuring CLI coverage is as detailed as PowerShell.
- Mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select the shell.
- Where PowerShell prerequisites are listed, add equivalent notes for Bash/CLI on Linux/macOS (e.g., how to authenticate, check CLI version).
- Avoid assuming local PowerShell installation; highlight cross-platform options equally.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure NAT Gateway shows evidence of Windows bias. It specifically mentions Windows Activation and Windows Updates as examples of services requiring outbound connectivity, without mentioning Linux equivalents (such as package updates or activation for Linux-based workloads). Additionally, upgrade instructions for basic resources reference PowerShell (a Windows-centric tool) without providing parity for Linux CLI or Bash. There are no explicit Linux or cross-platform examples or references, and Windows scenarios are mentioned first and exclusively in relevant sections.
Recommendations
- Include Linux-specific examples and scenarios, such as outbound connectivity for apt/yum updates, cloud-init, or SSH key retrieval.
- When referencing upgrade instructions, provide Azure CLI (cross-platform) and Bash examples alongside PowerShell.
- Mention Linux workloads and their outbound connectivity needs in parity with Windows Activation/Updates.
- Ensure that all tooling references (e.g., PowerShell) are accompanied by equivalent instructions for Azure CLI or other cross-platform tools.
- Add explicit notes or examples for Linux VM outbound connectivity, especially in sections discussing private subnets and NAT Gateway requirements.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway-v2-templates.md
...-gateway/quickstart-create-nat-gateway-v2-templates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. The ARM template deployment section exclusively provides a PowerShell example, with no Azure CLI or Bash equivalent, which may disadvantage Linux/macOS users. PowerShell is presented first and most prominently throughout, and instructions for copying/pasting scripts reference Windows-centric UI patterns (right-click, paste). Although the Bicep section includes both CLI and PowerShell, the ARM template section does not. There are no explicit Linux shell examples for ARM template deployment, and the initial deployment workflow assumes familiarity with PowerShell and Windows conventions.
Recommendations
- Add Azure CLI and Bash examples for ARM template deployment alongside PowerShell, ensuring Linux/macOS users have clear, native instructions.
- Present CLI (cross-platform) and PowerShell examples side-by-side or in tabs, rather than PowerShell-first, to avoid implicit prioritization of Windows tooling.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
- Revise UI instructions (e.g., copy/paste) to be platform-neutral, mentioning keyboard shortcuts for Windows, macOS, and Linux.
- Ensure all resource management (deployment, deletion) examples are available in both CLI and PowerShell formats.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway-v2.md
...ticles/nat-gateway/quickstart-create-nat-gateway-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides examples for Azure Portal, PowerShell, and Azure CLI, but PowerShell is given prominent attention throughout, including detailed prerequisites and installation instructions. PowerShell is a Windows-centric tool, and its usage is described in more detail than the Azure CLI, which is cross-platform. In several sections, PowerShell instructions and references appear before CLI, and there is a notable emphasis on Azure Cloud Shell and local PowerShell installation, both of which are more familiar to Windows users. There is also mention of Docker for CLI on Windows/macOS, but no explicit Linux-first or Linux-specific guidance. The documentation does not provide Linux-specific troubleshooting, nor does it mention Linux-native tools or patterns beyond the CLI.
Recommendations
- Give Azure CLI equal or greater prominence than PowerShell, as it is cross-platform and preferred by many Linux users.
- Add explicit instructions or notes for running Azure CLI on Linux, including installation and authentication steps.
- Where PowerShell is mentioned, clarify that Azure CLI is fully supported and often preferred on Linux.
- Include troubleshooting tips or common patterns for Linux environments, such as SSH key management, file permissions, and shell usage.
- Avoid assuming Cloud Shell or PowerShell as the default; present CLI as the primary automation tool for cross-platform parity.
- If mentioning Docker for CLI, also provide direct Linux installation instructions and highlight native package managers (apt, yum, etc.).
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md
...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. Windows tools and PowerShell commands are mentioned explicitly and sometimes exclusively, with Linux alternatives either missing or less detailed. Windows examples (PsPing, PowerShell Invoke-WebRequest) are provided for connectivity testing, while Linux examples are limited and less descriptive. Troubleshooting steps for network interfaces in a failed state focus on PowerShell and Azure Resource Explorer (browser-based), with no Linux CLI or Azure CLI alternatives. This prioritization and omission can hinder Linux users seeking parity in troubleshooting guidance.
Recommendations
- Provide equivalent Linux/Unix command-line examples (e.g., Azure CLI, Bash) wherever PowerShell is used.
- Include Linux-specific troubleshooting steps for network interfaces, such as using az network nic commands.
- Expand Linux tool recommendations for connectivity testing (e.g., ss, telnet, nmap for TCP/UDP tests).
- Ensure that both Windows and Linux procedures are presented side-by-side, or in parallel sections, to avoid Windows-first ordering.
- Reference cross-platform tools and scripts where possible, and clarify when a tool is Windows-only.