Governance
305
Total Pages
190
Linux-Friendly Pages
115
Pages with Bias
37.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
613 issues found
Showing 601-613 of 613 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Minor Linux Segregation
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, with the Portal as a third option. However, PowerShell (a Windows-centric tool) is always given equal prominence to Azure CLI, and in some cases, the PowerShell tab appears before CLI in the tab order. There are also separate queries for Windows and Linux OS update installations, but the Windows example appears before the Linux one, and the Linux example is segregated rather than integrated. There are no Linux/macOS-specific command-line examples (e.g., bash scripts), and no mention of Linux-native tools or shell environments. The documentation assumes parity between CLI and PowerShell, but the prominence of PowerShell and the ordering of Windows/Windows Server examples before Linux ones indicate a subtle Windows bias.
Recommendations
- Ensure Azure CLI examples are always listed before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Where possible, add bash or shell script examples for Linux/macOS users, especially for common automation scenarios.
- When presenting OS-specific queries (e.g., update installation), present Linux and Windows examples together, or alternate their order to avoid always prioritizing Windows.
- Explicitly mention that Azure CLI works on all platforms and highlight its use for Linux/macOS users.
- Consider adding a 'Linux/macOS' tab for any platform-specific guidance or troubleshooting.
- Review tab order and documentation structure to avoid implicit prioritization of Windows tools or workflows.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell always listed after Azure CLI. While Azure CLI is cross-platform, the inclusion of PowerShell (which is historically Windows-centric, though now available cross-platform) may suggest a slight Windows bias. However, no examples are missing for Linux/macOS users, and no Windows-only tools or patterns are used. There are also no shell-specific instructions or notes that would disadvantage Linux/macOS users.
Recommendations
- Continue to provide Azure CLI examples first, as it is the most cross-platform-friendly.
- Explicitly note that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
- Consider adding Bash or shell scripting examples where relevant, especially if quoting/escaping is required.
- If PowerShell is included, clarify that it is available cross-platform to avoid the impression of Windows exclusivity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, with PowerShell (a Windows-centric tool) given its own tab and parity with CLI. The ordering places Azure CLI first, which is cross-platform, but the inclusion of PowerShell as a primary method may signal a slight Windows bias. No Linux-specific tools or shell examples (e.g., bash, zsh) are provided, but the CLI example is sufficient for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Add example usage in bash/zsh (e.g., piping, output formatting) to demonstrate Linux workflows.
- Clarify that PowerShell Core is cross-platform, or note if the example is Windows PowerShell only.
- Consider listing CLI and PowerShell examples side-by-side, or note platform compatibility in tabs.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, with PowerShell (a Windows-centric tool) given its own tab and shown immediately after CLI. There is no explicit Linux shell example (e.g., Bash), nor is there any mention of Linux-specific considerations. However, the Azure CLI example is cross-platform and shown first, which mitigates the bias somewhat.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
- Add a Bash shell example or clarify that the CLI example is suitable for Bash/zsh/fish shells.
- Note any differences in installation or usage for Linux/macOS users, if applicable.
- Consider reordering tabs to show CLI (cross-platform) first and PowerShell second, or clarify platform applicability in tab labels.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks, as well as portal instructions. However, Azure PowerShell is a Windows-centric tool and its inclusion alongside Azure CLI (which is cross-platform) may create a slight Windows bias. There are no Linux-specific examples or notes, but the CLI examples use POSIX shell syntax, which is compatible with Linux/macOS. No critical functionality is Windows-only, and the order of examples does not prioritize Windows tools.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Clarify that Azure PowerShell is available on Linux/macOS via PowerShell Core, or provide installation links for non-Windows platforms.
- Add a note or section on running these queries in Bash or other Linux shells, if any differences exist.
- Consider including example outputs or troubleshooting tips for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is traditionally associated with Windows environments. The PowerShell example is given equal prominence to the CLI, and there is no explicit mention of Linux/macOS-specific considerations or examples. The ordering of examples (CLI, then PowerShell, then Portal) is typical, but the inclusion of PowerShell may suggest a slight Windows bias, especially if Linux users are not informed about cross-platform PowerShell availability.
Recommendations
- Explicitly note that Azure CLI works on Linux/macOS and Windows.
- Clarify that PowerShell Core is available cross-platform, or provide Bash shell examples for Linux users.
- Add a note or section highlighting any platform-specific differences or installation instructions for Linux/macOS users.
- Consider providing Bash or shell script examples where appropriate.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for running Resource Graph queries, but PowerShell examples are given equal prominence and are presented immediately after CLI examples. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples for Bash, shell scripting, or alternative Linux-native tools. However, since Azure CLI is fully cross-platform and shown first, the bias is minor.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
- Add a note clarifying that PowerShell examples are for users who prefer PowerShell, typically on Windows, but PowerShell Core is also available cross-platform.
- Consider including example shell scripts or usage notes for Linux/macOS environments, such as running Azure CLI in Bash.
- If there are any platform-specific caveats (e.g., escaping characters), document them for Linux/macOS users.
Governance
Author policies for array properties on resources
...governance/policy/how-to/author-policies-for-arrays.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias in the section 'Pass values to a parameter array during assignment.' It lists Azure CLI, Azure PowerShell, and REST API as methods for passing array parameters, but mentions Azure PowerShell (a Windows-centric tool) before REST API and does not mention Linux-specific tools or shell patterns. There are no Linux shell (bash) examples, nor is there any mention of Linux-specific usage or considerations. The rest of the page is platform-neutral and focuses on Azure Policy JSON definitions and logic.
Recommendations
- Add explicit examples for Linux users, such as using Azure CLI from bash/zsh, including sample commands and parameter formatting.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- If mentioning Azure PowerShell, also mention PowerShell Core (pwsh), which is cross-platform, and clarify usage on Linux.
- Consider including a table or section comparing parameter passing in Azure CLI (bash), Azure PowerShell (Windows/pwsh), and REST API, highlighting any platform-specific differences.
- Ensure that command-line examples are provided for both Windows and Linux environments where applicable.
Governance
Author policies for array properties on resources
...governance/policy/how-to/author-policies-for-arrays.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure CLI, Azure PowerShell, and REST API as methods for passing array parameters during policy assignment. However, Azure PowerShell is listed before REST API, and there are no explicit Linux-specific examples or references to Linux-native tools or shell environments. The only command-line examples provided are generic and do not show Linux shell usage (e.g., Bash), nor do they address Linux-specific concerns such as quoting, escaping, or environment differences. There is a subtle Windows bias in the ordering and absence of Linux/Bash examples.
Recommendations
- Add explicit Bash/Linux shell examples for passing array parameters using Azure CLI.
- Clarify that Azure CLI works cross-platform and provide sample commands for both Windows (PowerShell/CMD) and Linux (Bash).
- When listing tools, alternate the order or explicitly state that Azure CLI is cross-platform and often preferred on Linux.
- Include notes or examples for Linux-specific usage, such as handling JSON files, environment variables, or shell quoting.
- Consider adding a table or section comparing usage in PowerShell vs Bash to highlight parity.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/author-policies-for-arrays.md
...governance/policy/how-to/author-policies-for-arrays.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents cross-platform Azure Policy concepts and examples, but in the section 'Pass values to a parameter array during assignment', it lists Azure CLI, Azure PowerShell, and REST API as the three methods for assignment. Azure PowerShell is mentioned explicitly and before REST API, and no Linux-specific shell or tool (such as Bash, shell scripting, or Linux-native tools) is referenced. There are no PowerShell-heavy examples, but the ordering and explicit mention of PowerShell may suggest a slight Windows-first bias. No Linux-specific examples or tools are provided, and the CLI example is generic without shell context.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide example commands in both Windows (PowerShell) and Linux (Bash) shell formats.
- Include Linux/Bash-specific usage notes, such as how to pass JSON parameters using Bash (e.g., using single quotes, escaping, etc.).
- Add a note clarifying that Azure PowerShell is available on Linux, or link to cross-platform installation guides.
- Consider reordering the assignment methods to list Azure CLI first, then REST API, then Azure PowerShell, or clarify that all are cross-platform.
- Provide example commands for both PowerShell and Bash where relevant, especially in sections discussing command-line usage.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/author-policies-for-arrays.md
...governance/policy/how-to/author-policies-for-arrays.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for passing array parameters during policy assignment using Azure CLI, Azure PowerShell, and REST API. The order of presentation lists Azure CLI first, followed by Azure PowerShell, and then REST API. There are no explicit Linux-specific examples or references to Linux-native tools (such as bash scripting or Linux shell usage). However, Azure CLI is cross-platform and can be used on both Windows and Linux, while Azure PowerShell is primarily associated with Windows environments. The documentation does not provide Linux-specific command-line examples or highlight Linux usage patterns.
Recommendations
- Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide Linux shell (bash) examples for passing parameters, such as using az policy assignment create from a bash script.
- Include notes or examples for using REST API with curl or other Linux-native tools.
- Avoid listing Windows-centric tools (PowerShell) before cross-platform or Linux-native options, or alternate the order to avoid perceived bias.
- Where possible, add examples that show both Windows (PowerShell) and Linux (bash/curl) usage for common tasks.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/definition-structure-basics.md
...ernance/policy/concepts/definition-structure-basics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page contains a subtle Windows bias in the section discussing the 'mode' property. It mentions PowerShell before Azure CLI when describing how to specify the 'mode' parameter, and provides default behavior for both, but lists Azure PowerShell first. No explicit Windows-only tools, PowerShell-heavy examples, or missing Linux examples are present, but the ordering suggests a slight preference for Windows-centric tooling.
Recommendations
- When referencing cross-platform tools such as PowerShell and Azure CLI, alternate the order in which they are mentioned or explicitly state that both are supported equally.
- Provide example commands for both Azure PowerShell and Azure CLI when discussing actions that can be performed with either tool.
- Consider including a note that both Azure CLI and PowerShell are cross-platform and available on Windows, Linux, and macOS.
- Review documentation for other subtle ordering or phrasing that may imply a preference for Windows tools, and adjust for neutrality.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/concepts/deployment-stages.md
...es/governance/blueprints/concepts/deployment-stages.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Azure management tools in the order: Portal, Azure CLI, Azure PowerShell, REST API, and ARM template. Azure PowerShell is mentioned before REST API and ARM template, which can be interpreted as a subtle 'windows_first' bias. However, there are no explicit PowerShell-only examples, nor are Windows-specific tools or patterns promoted exclusively. Azure CLI is mentioned, which is cross-platform, and no examples are given that are specific to Windows or Linux.
Recommendations
- When listing management tools or methods, alternate the order or explicitly state that all methods are cross-platform where applicable.
- Provide explicit command examples for both Azure CLI and Azure PowerShell, ensuring parity, or clarify that both are supported equally.
- If possible, add a note that Azure CLI is available on Windows, Linux, and macOS to reinforce cross-platform support.
- Avoid consistently listing PowerShell before CLI or REST unless there is a technical reason.