Document Details
Subscribe To Resource Notifications Health Resources Events
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
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and the Azure portal. However, the inclusion of Azure PowerShell throughout, with detailed PowerShell command examples, introduces a Windows bias. PowerShell is primarily a Windows-native tool, and its prominence may disadvantage Linux users who are less likely to use PowerShell. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native scripting or tooling. The CLI examples are cross-platform, but the documentation does not clarify this or provide Linux-specific guidance. The PowerShell sections are always present and sometimes precede the CLI sections, reinforcing the Windows-centric approach.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and provide explicit Bash or Linux terminal examples where appropriate.
- De-emphasize PowerShell as a primary automation tool unless specifically targeting Windows users; consider moving PowerShell sections after CLI sections or marking them as Windows-specific.
- Add notes or callouts for Linux/macOS users, such as any differences in CLI usage, environment setup, or authentication.
- If scripting examples are provided, include Bash scripts or references to shell scripting for Linux users.
- Review the order of sections to ensure CLI (cross-platform) instructions come before PowerShell (Windows-centric) instructions.
- Explicitly state that PowerShell examples are optional and primarily for users on Windows or those who have installed PowerShell Core on Linux/macOS.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
 Clean
|
| 2026-01-13 00:00 | #246 | completed |
Clean
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
# [Azure PowerShell](#tab/azure-powershell)
# [Azure PowerShell](#tab/azure-powershell)
If you don't specify `IncludedEventType`, all the event types are included by default. To **filter events** from a specific resource, use the `-SubjectBeginsWith` parameter. The example shows how to subscribe to `AvailabilityStatusChanged` events from resources in a specified resource group.