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.

Bias Analysis

Bias Types:
⚠️ windows_first
⚠️ powershell_heavy
⚠️ windows_tools
Summary:
The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing PowerShell as a primary automation tool, and linking to Windows-centric resources (such as .NET TimeZoneInfo documentation). There are no Linux- or Bash-specific examples, and the CLI section is presented after PowerShell, which is traditionally associated with Windows environments.
Recommendations:
  • Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
  • Include Bash shell script examples for common tasks, especially for automation scenarios.
  • Reference Linux-compatible tools and documentation (e.g., link to IANA time zone database or cross-platform time zone docs, not just .NET/Windows).
  • Explicitly state that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide guidance for users on different platforms.
  • Where screenshots or UI references are given, clarify that the Azure portal experience is the same across platforms.
GitHub Create pull request

Scan History

Date Scan ID Status Bias Status
2025-07-12 23:44 #41 in_progress ❌ Biased
2025-07-12 00:58 #8 cancelled ✅ Clean
2025-07-10 05:06 #7 processing ✅ Clean

Flagged Code Snippets

1. Create a maintenance configuration using the `New-AzMaintenanceConfiguration` cmdlet. - The `-Duration` must be a minimum of a five hour window. - The `-RecurEvery` is per day. - For TimeZone options, see [Time Zones](/dotnet/api/system.timezoneinfo).
1. Save the maintenance configuration as a variable named `$config`.
1. Save the service resource as a variable named `$serviceResource`. 1. Create the maintenance configuration assignment using the `New-AzConfigurationAssignment` cmdlet. The maintenance policy is applied to the resource within 24 hours.
1. To remove a configuration assignment: - A configuration assignment is removed automatically if the configuration or the resource is deleted. - If you want to manually remove a configuration assignment from the maintenance configuration to a resource, use the `Remove-AzConfigurationAssignment` cmdlet.
1. Create a maintenance configuration using the `az maintenance configuration create` command. - Sets the `--location` to specify the Azure region for the maintenance configuration. - Sets the `--maintenance-scope` to `Resource`. - Sets the extension property to `maintenanceSubScope=NetworkSecurity` using `--extension-properties`. - Sets the `--maintenance-window-duration` to specify the maintenance window length (must be at least five hours, format: HH:mm). - Sets the `--maintenance-window-start-date-time` to specify when the maintenance window begins (format: YYYY-MM-DD HH:MM). - Sets the `--maintenance-window-expiration-date-time` to specify when the maintenance window expires (format: YYYY-MM-DD HH:MM). - Sets the `--maintenance-window-recur-every` to `Day` for daily recurrence. - Sets the `--maintenance-window-time-zone` to specify the time zone for the schedule. For available time zones, see [Time Zones](/dotnet/api/system.timezoneinfo). - Sets the `--namespace` to `Microsoft.Maintenance`. - Sets the `--visibility` to `Custom`. - Sets the `--resource-group` to specify the resource group. - Sets the `--resource-name` to specify the name of the maintenance configuration.