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 551-575 of 613 flagged pages
Governance
Manage your Azure subscriptions at scale with management groups - Azure Governance
...b/main/articles/governance/management-groups/manage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents Azure PowerShell examples before Azure CLI examples in each section, and PowerShell command output is shown with Windows-style prompts (e.g., PS C:\>). While both PowerShell and CLI are covered, the ordering and example formatting reflect a subtle Windows bias. No Linux/macOS-specific tools or patterns are mentioned, but CLI parity is maintained throughout.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid implicit prioritization.
- Use neutral shell prompts (e.g., $ or >) in example outputs instead of Windows-specific PS C:\>.
- Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and provide links or notes for installing/running them on Linux/macOS.
- Include a brief note or section on using these commands in Bash/zsh or other popular Linux/macOS shells.
- Ensure screenshots and example outputs do not reinforce Windows-only usage.
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
Windows First
Summary
The documentation page is largely platform-neutral, focusing on JSON structure and Azure concepts. However, there is a subtle Windows bias in the 'strongType' section, where the only tool mentioned for resource type validation is PowerShell's Get-AzResourceProvider, with no mention of equivalent Azure CLI or REST API commands. This places Windows/PowerShell tooling first and may create friction for Linux/macOS users who prefer Azure CLI or REST API.
Recommendations
- Include Azure CLI and REST API equivalents alongside PowerShell commands, e.g., show how to list resource providers using 'az resource provider list' or via REST.
- When referencing tooling, avoid assuming PowerShell is the default; present cross-platform options equally.
- Add explicit notes or links for Linux/macOS users to ensure parity in examples and tooling references.
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 mentions exporting policy and initiative definitions via PowerShell, CLI, or Azure Resource Graph, listing PowerShell first and not providing explicit Linux/macOS shell examples. There is a subtle preference for Windows-centric tools and workflows, such as PowerShell and Azure Pipelines, without equivalent emphasis or examples for Linux-native tools or Bash scripting. No explicit Linux/macOS command-line examples are given, and there is no mention of platform-specific considerations for non-Windows users.
Recommendations
- Provide explicit Bash or Azure CLI examples for Linux/macOS users alongside PowerShell examples.
- When listing tools or methods, alternate or balance the order (e.g., 'CLI, PowerShell, or Azure Resource Graph') to avoid Windows-first bias.
- Mention cross-platform compatibility for recommended tools like Azure Pipelines and GitHub workflows.
- Include notes or links about running Azure CLI and SDKs on Linux/macOS, and clarify any platform-specific setup steps.
- Add sample scripts or workflow steps using Bash or other Linux-native tools where automation is discussed.
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 demonstrates a mild Windows bias, primarily by referencing Azure portal (which is most accessible on Windows) before CLI in several workflows, listing Windows-specific domains (login.windows.net, store.policy.core.windows.net), and including Azure PowerShell examples alongside Azure CLI, but never showing Linux-specific shell or tool alternatives. However, all critical operational steps (installation, validation, troubleshooting, removal) are shown using Azure CLI and kubectl, which are cross-platform. There are no sections that require Windows or PowerShell exclusively, and Linux is explicitly mentioned as the only supported node pool OS for the add-on.
Recommendations
- Add explicit notes or examples for Linux/macOS users, such as shell commands for installing Azure CLI or setting up kubectl.
- Clarify that Azure CLI and kubectl commands work on Linux/macOS and provide links to installation guides for those platforms.
- If mentioning Azure PowerShell, also mention Bash or other Linux-native scripting options for parity.
- When listing portal-based steps, note that the Azure portal is accessible from any OS/browser.
- Consider listing CLI examples before portal steps to emphasize cross-platform compatibility.
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. Azure PowerShell is listed explicitly alongside Azure CLI, and both are referenced before REST API. There are no Linux/macOS-specific examples, and PowerShell is a Windows-centric tool, though it is available cross-platform. No Linux-specific tools (e.g., bash, shell scripting) or explicit Linux/macOS instructions are provided, but the CLI and REST API are cross-platform.
Recommendations
- Add explicit Linux/macOS examples for policy assignment, such as using Azure CLI in bash or zsh.
- Clarify that Azure CLI is cross-platform and provide example commands for Linux/macOS terminals.
- Mention that Azure PowerShell is available on Linux/macOS, or provide alternative shell scripting examples.
- Ensure that examples do not imply Windows-first usage by listing CLI before PowerShell, or by grouping cross-platform tools together.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources, but PowerShell (a Windows-centric tool) is given its own dedicated section and example. The CLI example is presented first, which is positive for Linux parity, but the PowerShell section is equally prominent and detailed. No Linux/macOS-specific tools or shell examples (e.g., bash scripting, jq usage) are provided, nor is there discussion of platform-specific considerations. The Resource Graph export is described as a portal feature, which is cross-platform.
Recommendations
- Add explicit Linux/macOS shell examples, such as using Azure CLI output piped to jq for JSON manipulation.
- Clarify that Azure CLI works natively on Linux/macOS and provide installation links for those platforms.
- Mention that PowerShell Core is cross-platform, or provide bash alternatives for tasks like converting JSON.
- Ensure parity in detail and guidance between CLI and PowerShell sections, possibly merging them or providing side-by-side examples.
- Include troubleshooting notes for platform-specific issues (e.g., file encoding, path separators).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Azure portal, PowerShell, and Azure CLI as ways to assign policies, listing PowerShell before Azure CLI. There are no explicit Linux/macOS-specific instructions or examples, and PowerShell is mentioned as a primary tool, which is traditionally associated with Windows. No Linux-specific tools or shell examples (e.g., Bash) are provided, and the documentation does not clarify cross-platform usage for command-line tools.
Recommendations
- Explicitly state that Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users where relevant.
- Include Bash or shell script examples for common tasks, especially for policy assignment and management.
- When listing tools, alternate or randomize the order (e.g., sometimes list Azure CLI before PowerShell) to avoid Windows-first perception.
- Add a section or note about using Azure Policy tools on Linux/macOS, including installation and usage tips.
- Reference documentation or quickstarts specifically for Linux/macOS users where available.
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 aliases, but lists Azure PowerShell after Azure CLI and includes explicit PowerShell cmdlet usage. No Linux/macOS-specific tools or shell examples are given, but Azure CLI is cross-platform and shown first. There is no exclusive use of Windows tools, but PowerShell is mentioned and exampled, which may be less familiar to Linux/macOS users. The rest of the tutorial is platform-neutral, focusing on JSON and Azure portal usage.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
- Add bash/zsh shell examples for Azure CLI usage, if relevant.
- Clarify that Azure PowerShell is available cross-platform, or link to installation instructions for Linux/macOS.
- Consider mentioning or linking to REST API usage for fully platform-agnostic automation.
- Ensure that any references to 'Cloud Shell' note its availability in browser regardless of OS.
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 as a primary example and the explicit labeling of 'Azure PowerShell' (which is often associated with Windows environments) indicates a slight Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, and there is no mention of Linux/macOS-specific considerations or shell environments. However, the presence of Azure CLI (which is cross-platform) and the portal option means Linux/macOS users can complete the task without major friction.
Recommendations
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- If relevant, provide Bash or shell scripting examples alongside PowerShell, or note any OS-specific differences.
- Indicate that Azure PowerShell is available cross-platform, or clarify when a command is Windows-only.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, with the PowerShell example given its own dedicated section. The PowerShell example may be perceived as Windows-centric, and the ordering of tabs (CLI, then PowerShell, then Portal) puts PowerShell before the more platform-neutral Portal option. However, the CLI example is cross-platform and presented first. No Linux-specific tools or shell examples are missing, but the presence of a PowerShell tab and lack of explicit Linux/macOS shell examples may create minor friction for non-Windows users.
Recommendations
- Clarify that the Azure CLI example works on Windows, Linux, and macOS.
- Consider adding a Bash shell example (even if it simply invokes az graph query) to explicitly show Linux/macOS parity.
- Add a note that PowerShell Core is available cross-platform, or clarify if the PowerShell example is Windows-only.
- If possible, provide parity in depth and detail between CLI and PowerShell sections.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each scenario, with PowerShell (a Windows-centric tool) always given its own tab and mentioned alongside CLI. There are no Linux- or macOS-specific command-line examples or notes, and PowerShell is presented as a primary automation option, which may signal a Windows-first or PowerShell-heavy bias. However, the Azure CLI examples are cross-platform and appear before PowerShell in each section.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
- Add a note clarifying that Azure PowerShell is also available cross-platform (via PowerShell Core), or provide installation/use guidance for Linux/macOS users.
- Consider including Bash shell scripting examples or notes for Linux/macOS users, especially where output parsing or scripting is relevant.
- If possible, provide links to documentation about using Azure CLI and PowerShell on different platforms.
- Ensure that any references to PowerShell do not imply it is required or preferred for all users.
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 highlighted as a primary method, which is Windows-centric. The PowerShell example is given its own tab, and there is no mention of Linux/macOS-specific considerations or alternative shells. The CLI example is cross-platform, but PowerShell's prominence may imply Windows preference.
Recommendations
- Clarify that Azure CLI works on Linux/macOS and is the recommended cross-platform tool.
- Add a note that PowerShell Core is available on Linux/macOS, or clarify if the example requires Windows PowerShell.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform parity.
- Explicitly mention that all examples (except PowerShell) are suitable for Linux/macOS users.
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. No explicit Linux/macOS command-line alternatives (e.g., Bash scripts) are given, and PowerShell is presented as an equal alternative to Azure CLI, despite CLI being more cross-platform. The order of examples (CLI, then PowerShell, then Portal) is reasonable, but the inclusion of PowerShell may signal a slight Windows bias.
Recommendations
- Clarify that Azure CLI works natively on Linux/macOS and is the recommended cross-platform tool.
- Add explicit notes or examples for running Azure CLI in Bash or zsh shells.
- Indicate that PowerShell Core is available cross-platform, if relevant, or clarify if the example is for Windows PowerShell only.
- Consider adding a section or note about Linux/macOS usage, especially if there are any differences or prerequisites.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure CLI (cross-platform), Azure PowerShell (primarily Windows-centric), and the Azure Portal (web-based). While Azure CLI is cross-platform, the inclusion of Azure PowerShell as a primary example introduces a mild Windows bias, as PowerShell is traditionally associated with Windows environments, and Linux users may not have it installed by default. No Linux/macOS-specific shell examples (e.g., Bash) or explicit mention of platform differences are provided.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, demonstrating the same query using Azure CLI.
- Clarify that Azure CLI works on all platforms and highlight installation instructions for Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but provide guidance for Linux users if needed.
- Consider ordering examples so that cross-platform tools (Azure CLI) appear before Windows-centric tools (PowerShell).
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. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric) and the absence of Linux/macOS-specific shell examples (e.g., Bash) or explicit mention of cross-platform compatibility for PowerShell introduces a mild Windows bias. Additionally, PowerShell is presented as a primary tab, which may suggest Windows-first thinking.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Clarify whether Azure PowerShell examples are compatible with PowerShell Core on Linux/macOS.
- Add a Bash shell example using Azure CLI to demonstrate usage on Linux/macOS.
- Consider reordering tabs so that cross-platform tools (Azure CLI) are shown before Windows-centric tools (PowerShell).
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 PowerShell is given its own tab and is mentioned before Linux-native shell alternatives. There are no Linux-specific shell examples (e.g., Bash), nor is there guidance for Linux/macOS users beyond the Azure CLI, which is cross-platform. The PowerShell example may imply a Windows-centric workflow.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider listing Azure CLI (cross-platform) before PowerShell in tab order.
- Note any OS-specific requirements for running the CLI or PowerShell.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, with PowerShell given its own tab and shown immediately after CLI. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (primarily used on Windows) as a first-class example may signal a Windows bias. No explicit Linux/macOS examples or shell-specific instructions are provided, and PowerShell is mentioned before any Linux-specific alternatives.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit shell examples (e.g., bash/zsh) if command syntax or environment setup differs.
- Add a note about Azure PowerShell's cross-platform support, or provide equivalent bash examples if relevant.
- Ensure that CLI examples are shown before PowerShell, or group them together with clear platform guidance.
- Consider adding troubleshooting or environment setup notes for Linux/macOS users if any steps differ.
Governance
Run Azure Resource Graph query using REST API
...cles/governance/resource-graph/first-query-rest-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias by listing PowerShell and Windows-centric tools (Visual Studio Code, Git Bash) in the prerequisites before Bash, and by providing PowerShell-specific instructions and examples before Bash equivalents. The use of Visual Studio Code and Git Bash as default shell environments further centers Windows workflows. However, Linux/Bash instructions are present and parity is generally maintained for the main task.
Recommendations
- List Bash and Linux-native shells (e.g., Ubuntu Terminal, macOS Terminal) equally or before PowerShell in prerequisites.
- Provide examples using native Linux/macOS terminals, not just Git Bash (which is a Windows workaround).
- Clarify that Visual Studio Code is optional and suggest alternatives for Linux/macOS users.
- Ensure that Bash examples are shown first or side-by-side with PowerShell, not after.
- Explicitly mention Linux/macOS compatibility and provide troubleshooting notes for those platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page is mostly neutral and cross-platform, but there is mild Windows bias in the 'Escape characters' section, where PowerShell and cmd are mentioned before Bash, and PowerShell examples are provided. There are no explicit Linux/macOS command-line examples for interacting with Resource Graph, and Windows shells are referenced more prominently. However, the core content (KQL queries, REST API usage) is platform-agnostic.
Recommendations
- Present Bash/Linux examples before or alongside Windows/PowerShell examples in sections discussing shell-specific syntax.
- Include sample usage of Resource Graph queries via Azure CLI or Bash scripts to demonstrate Linux/macOS parity.
- Clarify that REST API and KQL queries are platform-independent, and provide links or examples for common Linux/macOS tools (e.g., curl, jq) where relevant.
- Avoid listing Windows shells first unless there is a technical reason.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, as well as portal links. However, PowerShell (a Windows-centric tool) is always given equal prominence to Azure CLI, and in some cases, the PowerShell tab appears before the CLI tab. There are several queries and explanations that reference Windows Server or Windows-specific concepts (e.g., KB IDs, Windows patching), while Linux-specific queries are less frequent and less detailed. The documentation does not provide any Linux shell (bash) or scripting examples, nor does it mention Linux-native tools or patterns outside of Azure CLI. In sections about OS updates, Windows is often the default or first example, with Linux-specific queries appearing later or as exceptions.
Recommendations
- Ensure that Azure CLI (cross-platform) examples are always listed before PowerShell, or at least given equal prominence.
- Add Linux shell (bash) scripting examples where appropriate, especially for automation scenarios.
- When referencing OS updates or patching, provide parallel and equally detailed examples for both Windows and Linux, including explanations of Linux-specific fields (e.g., package versions, classifications).
- Avoid using Windows-specific terminology (like KB IDs) without also explaining or providing Linux equivalents.
- Where possible, mention Linux-native tools or patterns (e.g., jq for JSON parsing, grep/awk for filtering) in addition to Azure CLI.
- Audit for sections where only Windows or PowerShell is mentioned, and add Linux alternatives or clarify cross-platform applicability.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, with the PowerShell example given its own dedicated section. While Azure CLI is cross-platform and shown first, the inclusion of a PowerShell example (which is traditionally Windows-centric, though now available cross-platform) may still signal a Windows bias. No Linux/macOS-specific shell or tooling is mentioned, but there are no critical missing Linux examples since Azure CLI is supported everywhere.
Recommendations
- Clarify that Azure CLI commands work identically on Windows, Linux, and macOS.
- Consider adding a Bash shell example (even if it simply invokes the Azure CLI) to reinforce Linux parity.
- Explicitly mention PowerShell Core compatibility on Linux/macOS if including PowerShell examples.
- If possible, provide a table or note summarizing cross-platform support for each method.
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 Windows-centric, and its inclusion as a primary example may indicate a mild Windows bias. Additionally, PowerShell is listed immediately after Azure CLI, which is a common pattern in Microsoft documentation that can subtly prioritize Windows workflows. No Linux-specific tools or shell examples (e.g., Bash) 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 a Bash shell example to demonstrate usage in a native Linux environment (even if it simply wraps the Azure CLI command).
- Clarify that PowerShell Core is cross-platform if recommending PowerShell, or provide links to installation instructions for Linux/macOS.
- Consider listing CLI examples before PowerShell to reinforce cross-platform parity.
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. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is most commonly used on Windows) and the lack of Linux/macOS-specific shell examples (such as Bash or scripting with jq) indicate a mild Windows bias. Additionally, PowerShell is listed as a primary tab, and there are no explicit Linux/macOS command-line examples or notes about cross-platform usage.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, demonstrating the same query using Azure CLI in a typical Linux environment.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any platform-specific caveats if applicable.
- Consider providing example output or troubleshooting notes for Linux/macOS users.
- If PowerShell is required for advanced scenarios, note how to install and use PowerShell Core on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
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-only. PowerShell is primarily a Windows tool, and its inclusion alongside cross-platform CLI may suggest a Windows bias. The CLI example uses Azure CLI, which is cross-platform, but PowerShell is listed immediately after, reinforcing the Windows-centric approach. No explicit Linux/macOS examples or notes are provided.
Recommendations
- Clearly indicate that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, confirming that Azure CLI commands work on those platforms.
- Consider listing the Azure CLI example before PowerShell, or grouping platform-specific instructions together.
- Provide troubleshooting or installation guidance for Azure CLI on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources. However, Azure PowerShell (primarily used on Windows) is given a dedicated section and detailed example, while Linux/macOS-specific considerations are not discussed. The CLI example is presented first, but the PowerShell section is equally prominent and assumes familiarity with Windows tooling. There is no mention of Linux/macOS shell alternatives or guidance for users on those platforms.
Recommendations
- Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and highlight its parity.
- Add examples using Bash or other Linux/macOS shells for exporting and manipulating JSON output.
- Clarify that Azure PowerShell can be installed on Linux/macOS, or provide installation links and notes.
- Consider adding a table comparing CLI and PowerShell usage across platforms.
- Ensure that Linux/macOS users are not left out by including troubleshooting or usage notes relevant to their environments.