Document Details

Quickstart Create Nat Gateway
Home / Scan #41 / Quickstart Create Nat Gateway
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
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.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-23 00:00 #290 failed Clean Clean
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Clean Clean
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Clean Clean
2026-01-08 00:53 #231 completed Clean Clean
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Biased Biased
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

    ### PowerShell

    
### PowerShell


### PowerShell

1. Get the Azure resource group name.

    
1. Run [Get-AzNatGateway](/powershell/module/az.network/get-aznatgateway) to display the details about the NAT gateway.

    
## Clean up resources

### [Portal](#tab/portal)

[!INCLUDE [portal-clean-up.md](~/reusable-content/ce-skilling/azure/includes/portal-clean-up.md)]

### [PowerShell](#tab/powershell)

If you're not going to continue to use this application, delete the virtual network, virtual machine, and NAT gateway with the following command:


### [ARM](#tab/arm)

When no longer needed, you can use the [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) command to remove the resource group and all resources contained within.