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 76-89 of 89 flagged pages
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 uses Azure Portal (GUI) instructions, which are most commonly accessed from Windows environments. There are no CLI examples (such as Azure CLI or Bash), nor are there PowerShell examples, but the lack of Linux-oriented instructions (such as Bash/CLI commands) means Linux users are underserved. The documentation does not mention Linux tools, patterns, or provide parity for command-line workflows.
Recommendations
- Add Azure CLI examples for each step, showing how to create and configure NAT gateways via command line (Bash).
- Include instructions for using Azure Cloud Shell, which supports both Bash and PowerShell, and clarify cross-platform usage.
- Explicitly mention that the Azure Portal can be accessed from any OS, and provide links to CLI documentation for users preferring non-GUI workflows.
- Ensure future documentation includes both GUI and CLI (Bash and PowerShell) instructions, with CLI examples presented either first or in parallel.
Create Pull Request
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
Medium Priority
View Details →
Detected Bias Types
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.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-ilip-nat.md
...main/articles/nat-gateway/tutorial-migrate-ilip-nat.md
Medium Priority
View Details →
Detected Bias Types
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.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-ilip-nat.md
...main/articles/nat-gateway/tutorial-migrate-ilip-nat.md
Medium Priority
View Details →
Detected Bias Types
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.
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 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.
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
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.
Low Priority
View Details →
Detected Bias Types
Windows Reference
Summary
The documentation is generally platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there is a minor Windows bias in the 'Default outbound access' section, which specifically mentions Windows Activation and Windows Updates as requiring outbound connectivity. No Linux/macOS-specific examples, tools, or patterns are referenced, but the overall guidance applies equally to all OS types. No PowerShell-only examples or Windows-centric tooling is present.
Recommendations
- Add a brief note clarifying that Linux and other OSes may also require outbound connectivity for package updates and activation, not just Windows.
- Where outbound connectivity is discussed, mention common Linux/macOS scenarios (e.g., apt/yum updates, OS activation if relevant) alongside Windows examples.
- Ensure future quickstarts and tutorials include CLI and portal instructions that are OS-agnostic, or provide both PowerShell and Bash/Azure CLI examples where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides parallel instructions for Azure Portal, PowerShell, Azure CLI, and Terraform. However, PowerShell (a Windows-centric tool) is given a dedicated section with detailed, step-by-step examples, and is listed before CLI and Terraform. The PowerShell instructions reference installing Azure PowerShell locally, a pattern most common on Windows. There is no explicit mention of Linux/macOS alternatives for scripting (e.g., Bash), nor are Linux-specific CLI usage patterns highlighted. While CLI and Terraform are cross-platform, the ordering and depth of PowerShell coverage indicate a mild Windows bias.
Recommendations
- List Azure CLI instructions before PowerShell, as CLI is natively cross-platform.
- Explicitly mention that Azure CLI and Terraform work on Linux/macOS and provide links or notes for installing them on those platforms.
- Add Bash scripting examples or notes for Linux users where appropriate.
- In PowerShell sections, clarify that Azure PowerShell can be used in Cloud Shell (browser-based, cross-platform) and on Linux/macOS, not just Windows.
- Ensure parity in troubleshooting and environment setup notes for Linux/macOS users.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-outbound-nat.md
.../articles/nat-gateway/tutorial-migrate-outbound-nat.md
Low Priority
View Details →
Detected Bias Types
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.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-and-azure-services.md
...les/nat-gateway/troubleshoot-nat-and-azure-services.md
Low Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
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.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-outbound-nat.md
.../articles/nat-gateway/tutorial-migrate-outbound-nat.md
Low Priority
View Details →
Detected Bias Types
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.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-outbound-nat.md
.../articles/nat-gateway/tutorial-migrate-outbound-nat.md
Low Priority
View Details →
Detected Bias Types
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.
Nat Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-and-azure-services.md
...les/nat-gateway/troubleshoot-nat-and-azure-services.md
Low Priority
View Details →
Detected Bias Types
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.