Document Details

Dnssec Unsign
Home / Scan #2 / Dnssec Unsign
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 detailed instructions for the Azure Portal, Azure CLI, and PowerShell. While the Azure CLI is cross-platform, the explicit inclusion of PowerShell (which is traditionally associated with Windows environments) and the use of PowerShell-specific cmdlets indicate a bias towards Windows users. Additionally, the PowerShell section is given equal prominence to the CLI, and there are no explicit Linux shell (bash) examples or references to Linux-native tools or workflows. The CLI examples use the Azure CLI, which is available on Linux, but there is no mention of running these commands in a Linux environment or using bash scripting, and the CLI section is labeled with 'azurepowershell-interactive', which may be confusing.
Recommendations
  • Add explicit bash shell examples for the Azure CLI section, showing usage in a Linux/macOS terminal.
  • Clarify that the Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for bash).
  • If PowerShell is included, also include bash equivalents for parity.
  • Avoid labeling CLI code blocks as 'azurepowershell-interactive' when they are standard Azure CLI commands.
  • Mention that PowerShell Core is cross-platform if you intend to support Linux, or clarify that the PowerShell examples are for Windows users.
  • Consider the order of sections: present the Azure CLI (cross-platform) before PowerShell to avoid a 'windows_first' impression.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
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 Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
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 Clean Clean
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

2. Confirm that **(NotFound) DNSSEC is not enabled for DNS zone 'adatum.com'** is displayed after the last command. The zone is now unsigned.

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

1. Use the following commands to remove DNSSEC signing from your zone and view the zone status using PowerShell. Replace the values for subscription ID, resource group, and zone name with your values.