Governance
496
Total Pages
410
Linux-Friendly Pages
86
Pages with Bias
17.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
186 issues found
Showing 126-150 of 186 flagged pages
Governance
Details of the Azure Policy attestation structure
...es/governance/policy/concepts/attestation-structure.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation mentions PowerShell as a primary management tool for attestations, listing it before Azure CLI and ARM API. There is an implicit bias toward Windows tooling (PowerShell) and no explicit Linux/macOS shell examples or guidance. While Azure CLI is mentioned, no examples are provided for either CLI or PowerShell, and the order of mention places PowerShell before CLI, subtly prioritizing Windows-centric workflows.
Recommendations
- Provide explicit Azure CLI examples for attestation management alongside any PowerShell examples.
- Mention cross-platform compatibility of Azure CLI and ARM API, and clarify that PowerShell is available on Linux/macOS.
- If PowerShell examples are added, ensure Bash or shell equivalents are also included and shown first or equally.
- Add a note or section highlighting Linux/macOS usage patterns for attestations.
Create Pull Request
Governance
Details of the initiative definition structure
...nce/policy/concepts/initiative-definition-structure.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation page is largely platform-neutral, focusing on JSON structures and Azure concepts. However, there is a subtle Windows bias in the 'strongType' section, where the only tool mentioned for validating resource types is 'Get-AzResourceProvider', a PowerShell cmdlet. No Linux/macOS equivalent (such as Azure CLI or REST API) is referenced, which may create friction for non-Windows users.
Recommendations
- When referencing tools for resource discovery or validation, include Azure CLI equivalents (e.g., 'az provider list') and/or REST API examples alongside PowerShell cmdlets.
- Explicitly state that all JSON examples and Azure Policy concepts are platform-agnostic and can be used from any OS.
- Where possible, provide links to cross-platform documentation or tooling.
- Add a note clarifying that PowerShell is available on Linux/macOS, but users may prefer Azure CLI or REST API for native experience.
Governance
Design Azure Policy as Code workflows
.../articles/governance/policy/concepts/policy-as-code.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references exporting policy and initiative definitions via PowerShell, CLI, or Azure Resource Graph, listing PowerShell first. There are no explicit Linux/macOS shell examples, nor is there mention of bash, shell scripting, or Linux-specific tools. The workflow and automation recommendations (GitHub workflows, Azure Pipelines) are cross-platform, but the lack of Linux/macOS command examples and the ordering of PowerShell before CLI suggest a subtle Windows bias.
Recommendations
- Provide explicit bash or shell examples for exporting and managing policy definitions, alongside PowerShell.
- When listing tools or commands, alternate or randomize the order (e.g., CLI before PowerShell) to avoid implicit prioritization.
- Include references to Linux/macOS environments and any platform-specific considerations for Azure Policy as Code workflows.
- Clarify that all recommended automation tools (GitHub workflows, Azure Pipelines) are cross-platform and provide links to Linux/macOS setup guides where relevant.
Governance
Learn Azure Policy for Kubernetes
...es/governance/policy/concepts/policy-for-kubernetes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and instructions for using Azure Policy for Kubernetes clusters frequently reference Windows-centric tools and patterns, such as the Azure portal and Azure PowerShell, often before or alongside Azure CLI. The domain and port requirements all reference *.windows.net endpoints. However, Linux parity is generally maintained through the use of Azure CLI and kubectl examples, and explicit mention that the add-on only works on Linux node pools. There are no critical sections that are Windows-only, but Windows tools and terminology are presented first or alongside Linux equivalents, and PowerShell is given as an option for resource provider registration.
Recommendations
- Present Azure CLI and kubectl examples before Azure PowerShell or portal instructions, as these are cross-platform.
- Clearly indicate that all CLI and kubectl commands work on Linux/macOS as well as Windows.
- Where PowerShell is mentioned, always provide an equivalent Azure CLI example and note platform compatibility.
- Clarify that *.windows.net endpoints are required regardless of OS, and that the add-on is Linux-only.
- Consider adding a short section or callout for Linux/macOS users confirming full support and parity.
- Remove unnecessary references to Windows-specific tools unless there is no cross-platform alternative.
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 assigning policy parameters, listing Azure CLI first and Azure PowerShell second. There are no explicit PowerShell-heavy examples, nor are Windows-only tools or patterns described. Linux parity is generally maintained, but the ordering may subtly reinforce Windows-first expectations.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for scripting on Linux/macOS.
- Provide example commands for both Azure CLI and Azure PowerShell, and clarify their platform compatibility.
- Consider listing Azure CLI before PowerShell to reinforce cross-platform usage.
- Add a note or section highlighting Linux/macOS usage, if relevant.
Governance
Tutorial: Create a custom policy definition
...ce/policy/tutorials/create-custom-policy-definition.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for discovering resource property aliases, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux/macOS alternatives for PowerShell. The 'Export template' and portal-based instructions are platform-neutral, but the inclusion of PowerShell commands may suggest a slight Windows bias, especially since PowerShell is more commonly associated with Windows environments. The order of presentation (CLI before PowerShell) slightly mitigates this bias, but the lack of explicit Linux/macOS guidance for PowerShell could create friction for non-Windows users.
Recommendations
- Clarify that Azure PowerShell is cross-platform and provide installation/use instructions for Linux/macOS.
- Explicitly state that Azure CLI works natively on Linux/macOS and is recommended for those platforms.
- Consider providing bash or shell script examples where appropriate.
- Add notes or links for Linux/macOS users on how to perform equivalent actions if any step is platform-specific.
- If referencing VS Code, mention that it is available on all major platforms.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell is a Windows-centric tool and is given equal prominence to the cross-platform CLI. There are no explicit Linux/macOS-specific instructions or notes, and PowerShell is presented as a primary method, which may create friction for non-Windows users. However, the Azure CLI example is present and fully cross-platform, so Linux/macOS users can complete the task.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is primarily for Windows, and suggest using Azure CLI on Linux/macOS.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform compatibility.
- If there are any Linux/macOS-specific considerations (e.g., installation, authentication), mention them.
Governance
Tutorial: Self-enforce MFA through Azure Policy
...rticles/governance/policy/tutorials/mfa-enforcement.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is primarily focused on the Azure portal (web UI), which is cross-platform, but when command-line examples are given, Azure CLI is shown first, followed by Azure PowerShell. PowerShell is a Windows-centric tool, though it is available on Linux/macOS. There are no examples using Bash, shell scripting, or Linux-native tools, nor is there explicit mention of Linux/macOS-specific instructions or screenshots. The ordering of examples (CLI, then PowerShell) slightly favors Windows users.
Recommendations
- Add explicit notes that Azure CLI and PowerShell are available on Linux/macOS, with installation links.
- Include Bash or shell scripting examples for common tasks, especially for audit log queries.
- Provide screenshots or instructions for Linux/macOS environments where relevant (e.g., terminal output, installation steps).
- Clarify that all portal-based steps are platform-agnostic.
- Consider listing CLI examples before PowerShell, or alternating the order.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for running queries, but PowerShell (a Windows-centric tool) is consistently presented alongside or immediately after CLI, and is referenced in prerequisites and notes. There is a slight preference for Windows/PowerShell tooling, with no explicit mention of Linux/macOS shell alternatives or guidance for non-Windows environments. However, the Azure CLI is cross-platform and is given equal coverage in examples.
Recommendations
- Explicitly state that Azure CLI works on Linux/macOS and provide shell-specific notes if needed.
- Add guidance or troubleshooting notes for running Azure CLI on Linux/macOS (e.g., installation, authentication differences).
- Consider mentioning Bash or other shell environments in introductory sections to reinforce cross-platform support.
- Clarify that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows users.
- If possible, add example commands using Bash scripting or other popular Linux/macOS tools for interacting with Azure Resource Graph.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is mostly platform-neutral, focusing on the Azure Resource Graph query language and KQL. However, in the 'Escape characters' section, PowerShell is mentioned and given an explicit example before Bash and cmd, and the PowerShell-specific escape character is described in detail. Bash is included, but the ordering and example emphasis slightly favor Windows/PowerShell. No Linux-specific tools or patterns are missing, but the example ordering and detail show minor Windows-first bias.
Recommendations
- List Bash examples before PowerShell in the 'Escape characters' section to avoid implicit Windows-first ordering.
- Provide parity in example detail for Bash, cmd, and PowerShell (e.g., show explicit cmd example, not just a statement).
- Add a note clarifying that all examples work equally on Linux/macOS and Windows, except for shell-specific escape characters.
- Consider including a table summarizing escape character usage across all major shells (Bash, Zsh, PowerShell, cmd) for clarity.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is given equal prominence as CLI, and is included in every example. There are no Linux-specific shell examples (e.g., Bash), nor is there any mention of Linux/macOS terminal usage or alternative tools. The ordering of examples is Azure CLI first, then PowerShell, which is a minor 'windows_first' bias. However, since Azure CLI is cross-platform and the queries themselves are platform-neutral, Linux/macOS users are not blocked, but may feel the documentation is slightly Windows-centric due to the consistent inclusion of PowerShell.
Recommendations
- Explicitly state that Azure CLI works on Linux/macOS and provide installation/use links.
- Add Bash or shell script examples where relevant, or clarify that CLI commands are intended for all platforms.
- Consider mentioning that PowerShell Core is available cross-platform, or clarify if examples are for Windows PowerShell only.
- Add a note about platform compatibility for both CLI and PowerShell.
- If possible, include troubleshooting or environment notes for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell is a Windows-centric tool, and its inclusion as a primary example alongside Azure CLI (which is cross-platform) introduces a mild Windows bias. The PowerShell examples are given equal prominence to CLI, and there is no mention of Linux/macOS-specific shell usage (e.g., Bash, zsh), nor are there any examples showing Linux-specific patterns or troubleshooting. The documentation does not explicitly state platform compatibility for the CLI or PowerShell tools, and PowerShell is traditionally associated with Windows environments.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide installation or usage notes for those platforms.
- Add example commands using Bash/zsh or highlight CLI usage in Linux/macOS terminals.
- Indicate platform compatibility for Azure PowerShell (e.g., note that PowerShell Core is available cross-platform, but some users may still associate it with Windows).
- Consider reordering examples to show CLI (cross-platform) first, followed by PowerShell, to reduce perceived Windows-first bias.
- Add troubleshooting notes or links for Linux/macOS users if there are any known issues or differences.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell example is given equal prominence and is not clearly marked as Windows-specific. PowerShell is primarily a Windows tool, and its inclusion alongside cross-platform CLI without clarification may suggest Windows bias. The CLI example is cross-platform, but the PowerShell tab may confuse Linux/macOS users who do not use PowerShell. The ordering of tabs (CLI, then PowerShell, then Portal) is reasonable, but the PowerShell example could be misinterpreted as universally applicable.
Recommendations
- Clearly label the Azure PowerShell example as Windows-specific or note its limited support on Linux/macOS.
- Add a note clarifying that Azure CLI is recommended for Linux/macOS users.
- Consider providing bash or shell script examples for Linux users if relevant.
- Ensure that PowerShell examples are not presented as the default or primary method for cross-platform tasks.
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, but PowerShell (a Windows-centric tool) is always listed after Azure CLI. There are no Linux-specific examples or notes, but Azure CLI is cross-platform and listed first. No Windows-only tools or patterns are present, and the examples are generally platform-neutral.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
- Consider including bash shell script examples or usage notes for Linux users, if relevant.
- Ensure parity in troubleshooting or environment setup instructions for Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is given equal prominence as CLI, despite being primarily a Windows tool. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is not marked as cross-platform. The ordering of tabs consistently puts Azure CLI first, which is positive for Linux parity, but the inclusion of PowerShell as a primary method may suggest a slight Windows bias.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or provide Bash examples where appropriate.
- Add notes or examples for running Azure CLI commands in Bash or other Linux shells.
- Consider mentioning that Azure CLI is the recommended tool for Linux/macOS users.
- If PowerShell is shown, note its cross-platform availability explicitly to avoid implying Windows exclusivity.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is a Windows-centric tool and is presented as a primary tab alongside CLI. There are no Linux/macOS-specific shell examples (e.g., Bash, zsh), nor are there notes about cross-platform usage for PowerShell. The presence of PowerShell as a first-class example and lack of explicit Linux/macOS guidance introduces a mild Windows bias.
Recommendations
- Add explicit notes that Azure CLI commands work natively on Linux/macOS and Windows.
- Clarify that PowerShell Core is cross-platform, and provide instructions for installing and running PowerShell on Linux/macOS if relevant.
- Consider including Bash or zsh shell examples for Azure CLI usage, showing how to use the CLI in typical Linux/macOS environments.
- If PowerShell is shown, clarify which commands require Windows PowerShell vs. PowerShell Core, and highlight cross-platform compatibility.
- Reorder tabs so Azure CLI (cross-platform) appears before PowerShell, or add a note explaining the parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but lists PowerShell (a Windows-centric tool) before the Portal tab and after CLI. There is no explicit Linux bias, but PowerShell is traditionally associated with Windows, and its inclusion may suggest a Windows-first approach. However, Azure CLI is cross-platform and listed first, mitigating the bias. No Windows-only tools or patterns are present, and Linux users can complete all tasks using Azure CLI or Portal.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly mention platform compatibility for each tool (e.g., 'Azure CLI: Windows, Linux, macOS; PowerShell: Windows, Linux, macOS').
- Consider listing Azure CLI and Portal before PowerShell to reinforce cross-platform parity.
- Add a note for Linux/macOS users recommending Azure CLI as the primary automation tool.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific terminology (e.g., 'Windows Server', 'kbId') is used in several queries, and Windows update queries are presented before Linux equivalents. PowerShell examples are provided for every query, and the documentation references Windows concepts and tools more frequently than Linux ones. Linux-specific queries are present but less prominent and sometimes grouped separately, rather than integrated with Windows examples. There are no Linux/macOS-specific CLI or shell examples beyond Azure CLI, which is cross-platform, but PowerShell is a Windows-centric tool. No critical Linux functionality is missing, but the ordering and terminology favor Windows users.
Recommendations
- Present Linux and Windows queries/examples together for parity, rather than in separate sections.
- Use neutral terminology where possible (e.g., 'OS update installation' instead of 'Windows Server OS update installation').
- Add bash/shell script examples for Linux/macOS users where relevant, especially for automation.
- Ensure Linux queries are given equal prominence and ordering as Windows queries.
- Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
- Avoid using Windows-specific identifiers (like 'kbId') without Linux equivalents or explanation.
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, the inclusion of Azure PowerShell (which is historically Windows-centric, though now available cross-platform) and the ordering of examples (CLI first, then PowerShell, then Portal) shows a slight Windows-first bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS-specific considerations. The PowerShell example may reinforce a Windows-centric approach for users unfamiliar with its cross-platform capabilities.
Recommendations
- Explicitly state that Azure CLI and Azure PowerShell are available on Linux/macOS, and provide installation links.
- Add a Bash shell example using Azure CLI to demonstrate usage in a typical Linux environment.
- Clarify that PowerShell Core is available cross-platform, and link to relevant documentation.
- Consider reordering examples or grouping CLI and PowerShell together as cross-platform tools.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but lists PowerShell as a primary tab, which is a Windows-centric tool. There is no explicit Linux/macOS example or mention of platform-specific considerations, and PowerShell is presented alongside CLI without clarifying cross-platform compatibility. The CLI example is cross-platform, but the presence and prominence of PowerShell may create a perception of Windows bias.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux/macOS/Windows.
- Add explicit notes or examples for Linux/macOS users, such as running Azure CLI in Bash.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
- If PowerShell is shown, mention that PowerShell Core is available on Linux/macOS, or provide a Bash shell example.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell is a Windows-centric tool and is presented as a primary tab. There is no explicit Linux shell example (e.g., Bash), and the order of examples places PowerShell before the portal, which may suggest a Windows-first approach. However, the Azure CLI example is cross-platform and shown first.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add explicit Bash or shell examples to demonstrate usage on Linux/macOS.
- Consider reordering tabs to show CLI (cross-platform) and Bash examples before PowerShell.
- Note any platform-specific differences in command usage, if applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure CLI and Azure PowerShell examples side-by-side, but lists Azure CLI first (which is cross-platform) and then Azure PowerShell (which is Windows-centric). There is no explicit Linux/macOS bias, but the inclusion of PowerShell as a primary example may suggest a slight Windows orientation. No Windows-only tools or patterns are present, and all command-line examples use cross-platform tools.
Recommendations
- Clarify that Azure CLI works on Linux/macOS/Windows, and PowerShell is primarily Windows-focused (though PowerShell Core is cross-platform).
- Consider adding Bash shell examples for Linux users, if relevant.
- Explicitly mention platform compatibility for each example.
- If PowerShell is not required for the task, emphasize Azure CLI as the default cross-platform solution.
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, but consistently lists Azure PowerShell examples immediately after Azure CLI and before the Azure Portal. The introductory metadata and instructions reference Azure PowerShell and Azure CLI as the supported shells, but do not mention Bash, Linux, or macOS specifically. There are no examples or notes about Linux-specific usage, shell differences, or platform-specific caveats. However, since Azure CLI is cross-platform and all examples are CLI-based (not Windows-only tools), Linux/macOS users can follow the instructions without issue.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS, not just Windows.
- Add a note clarifying that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- Consider listing Azure CLI examples before PowerShell, or alternating the order to avoid implicit Windows-first bias.
- If there are any platform-specific caveats (e.g., quoting, escaping), mention them.
- Add a short section or FAQ for Linux/macOS users to confirm parity and highlight any differences.
Governance
Details of the Azure Policy attestation structure
...es/governance/policy/concepts/attestation-structure.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation mentions PowerShell as a primary management tool for Azure Policy attestations and lists it before Azure CLI, which may indicate a Windows-first bias. No explicit Linux/macOS examples or platform-specific guidance are provided, but Azure CLI is referenced, which is cross-platform.
Recommendations
- Provide explicit Linux/macOS usage examples, especially for Azure CLI.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Avoid listing PowerShell before CLI unless there is a technical reason; consider ordering tools alphabetically or by platform neutrality.
- Add links or guidance for installing and using Azure CLI on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references both PowerShell and Azure CLI for policy assignment, but PowerShell is mentioned first in several places. There are no explicit Linux/macOS-specific examples, and the documentation does not clarify cross-platform usage or highlight Linux parity. The mention of 'PowerShell' without specifying cross-platform compatibility may lead Linux/macOS users to assume a Windows bias.
Recommendations
- Explicitly state that Azure CLI and PowerShell are both cross-platform, and clarify usage on Linux/macOS.
- Provide Linux/macOS-specific example commands or workflows where relevant.
- Alternate the order of example links so Azure CLI is sometimes listed before PowerShell.
- Add a note or section on platform compatibility for management tools.