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 526-550 of 613 flagged pages
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/azure-security-benchmark-foundation/deploy.md
.../samples/azure-security-benchmark-foundation/deploy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell-specific command (`Get-AzLocation | Where-Object Providers -like 'Microsoft.OperationalInsights' | Select DisplayName`) as the only example for listing available Log Analytics workspace regions. No equivalent CLI or Bash/Linux example is given, and there is no mention of cross-platform tools or instructions. The rest of the documentation is GUI-focused and does not reference platform-specific tools, but the only command-line example is Windows-centric.
Recommendations
- Provide equivalent Azure CLI (az) commands for tasks such as listing available Log Analytics workspace regions, e.g., `az account list-locations --query "[?metadata.resourceType=='Microsoft.OperationalInsights/workspaces'].displayName"`.
- When giving command-line examples, always include both PowerShell and Bash/Azure CLI versions, or clearly indicate cross-platform options.
- Review documentation for any other PowerShell-specific guidance and ensure Linux/macOS users are equally supported.
- Consider adding a note that all tasks can be performed using Azure CLI or Cloud Shell, which are cross-platform.
Create Pull Request
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/ism-protected/deploy.md
.../governance/blueprints/samples/ism-protected/deploy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits a mild Windows bias. While it covers both Windows and Linux in the artifact parameters table, Windows terminology and concepts (such as 'Windows VM Administrators group', 'Microsoft IaaSAntimalware extension', and password policies typical of Windows environments) are mentioned explicitly and in detail. There are no Linux-specific administrative group examples or equivalent Linux user/group management parameters. Additionally, the documentation references Windows VM settings before or more frequently than Linux equivalents in several places, and the only user/group management examples are for Windows. However, there are parameters for both Windows and Linux Log Analytics agents, and Linux is not entirely omitted.
Recommendations
- Add Linux-specific examples for user/group management, such as parameters for configuring sudoers or root access exclusions/inclusions on Linux VMs.
- Where user/group management is discussed for Windows (e.g., Administrators group), provide equivalent Linux examples (e.g., sudo or wheel group).
- Ensure that for every Windows-specific extension or policy (like IaaSAntimalware), the Linux equivalent (such as the OMS agent or Linux security extensions) is also mentioned and described.
- Review the order of presentation in the artifact parameters table and documentation text to ensure Linux and Windows are given equal prominence, alternating or grouping them together where possible.
- Where password policies are described, clarify which apply to Windows, Linux, or both, and provide Linux-specific guidance if relevant.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/assign-configuration/rest-api.md
...-configuration/how-to/assign-configuration/rest-api.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the Windows PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning or providing Linux/CLI alternatives. No Linux-specific tools or authentication workflows are described, and there is no parity in example commands for Linux users.
Recommendations
- Include instructions and examples for obtaining an Azure access token using the Azure CLI (az account get-access-token) on Linux/macOS.
- Mention cross-platform alternatives to PowerShell, such as Bash scripts or REST client tools available on Linux.
- Provide equivalent authentication and request examples using Linux-native tools and workflows.
- Ensure that all referenced tools and commands are available and documented for both Windows and Linux environments.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/initiative-definition-structure.md
...nce/policy/concepts/initiative-definition-structure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page contains a reference to a Windows-specific tool (Get-AzResourceProvider from PowerShell) when describing how to determine valid strongType resource types. There are no equivalent Linux/CLI commands or examples provided, and no mention of cross-platform alternatives. No explicit Windows-first ordering is present, but the only tool mentioned is Windows-centric.
Recommendations
- Add Azure CLI equivalents (e.g., 'az provider show' or 'az provider list') alongside or in place of PowerShell commands to ensure Linux and macOS users are supported.
- Wherever a PowerShell cmdlet is referenced, provide the corresponding Azure CLI command and example output.
- Consider a short note or table summarizing cross-platform methods for discovering resource types, making it clear that both Windows and Linux/macOS users are supported.
- Review other documentation sections for similar tool references and ensure parity in examples and instructions.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/remediate-resources.md
...ticles/governance/policy/how-to/remediate-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by consistently presenting PowerShell examples before Azure CLI examples in all code sections. The PowerShell sections are more detailed, with richer example scripts and explanations, while Azure CLI sections are more succinct and sometimes refer to external documentation for examples. There is no mention of Linux-specific tools, shells, or workflows, and the documentation implicitly assumes familiarity with PowerShell, which is more common on Windows.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI examples first in some sections to avoid reinforcing a Windows-first perspective.
- Ensure that Azure CLI examples are as detailed and comprehensive as the PowerShell examples, including full command sequences and explanations.
- Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, to encourage non-Windows users.
- Where appropriate, add Bash shell examples or notes for Linux/macOS users (e.g., variable syntax differences, login methods).
- Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported equally.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/concepts/guidance-for-throttled-requests.md
...urce-graph/concepts/guidance-for-throttled-requests.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only C# code examples, which are most commonly associated with Windows development environments. There are no examples using Linux-native tools, shell scripts, or cross-platform command-line utilities (such as Azure CLI or REST API via curl). This may make it less accessible or immediately useful for Linux users or those working outside of the Windows/.NET ecosystem.
Recommendations
- Add equivalent examples using Azure CLI commands, which are cross-platform and commonly used on Linux.
- Include REST API examples using curl or similar tools to demonstrate how to interact with Azure Resource Graph from any platform.
- If PowerShell is relevant, provide both Windows PowerShell and cross-platform PowerShell Core examples, and clarify their compatibility.
- Explicitly mention that the SDK and APIs are usable from Linux and provide links or notes on how to set up the environment on Linux.
- Consider including bash or Python SDK examples, which are popular in Linux environments.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/insight-resources-monitor-data-collection-rules.md
...ery/insight-resources-monitor-data-collection-rules.md
Medium 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 to the cross-platform CLI, and there is no explicit mention of Linux-specific usage or shell environments. The PowerShell tab may imply a Windows-centric approach, especially since no Bash or Linux shell examples are provided or discussed.
Recommendations
- Explicitly mention that the Azure CLI example works cross-platform, including on Linux and macOS.
- Add a Bash shell example or clarify that the Azure CLI command can be run in Bash, zsh, or other Linux shells.
- Consider reordering tabs to present the Azure CLI (cross-platform) example before PowerShell, or clarify that PowerShell Core is available on Linux.
- Add a note about any differences or prerequisites for running these commands on Linux versus Windows, if applicable.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/management-groups.md
...raph/includes/samples-by-category/management-groups.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each scenario. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now cross-platform) in every example, and the explicit labeling of 'Azure PowerShell' as a primary tab, demonstrates a Windows-centric approach. Additionally, PowerShell examples are always presented alongside or immediately after CLI examples, reinforcing a 'Windows-first' mindset. There are no Linux-specific shell (e.g., Bash) or scripting examples, nor are there references to Linux-native tools or patterns.
Recommendations
- Add explicit Bash or shell script examples where applicable, especially for users on Linux or macOS.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if differences exist.
- Consider reordering tabs to present Azure CLI (the most cross-platform tool) first, or provide a note about cross-platform compatibility.
- If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, and provide installation or usage notes for those platforms.
- Where possible, include references to Linux-native scripting or automation approaches, such as using jq or other common Unix tools in conjunction with Azure CLI output.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/iot-defender.md
...rce-graph/includes/samples-by-category/iot-defender.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure CLI and Azure PowerShell examples side by side, but always lists Azure PowerShell (a Windows-centric tool) as a primary method alongside CLI. There are no explicit Linux shell or scripting examples, and PowerShell is given equal prominence to the cross-platform CLI, which may suggest a Windows-centric bias.
Recommendations
- Add explicit Bash or Linux shell examples where relevant, especially for scripting scenarios.
- Clarify that Azure CLI is fully cross-platform and highlight its use on Linux/macOS.
- Consider listing Azure CLI examples before PowerShell, or note that PowerShell Core is cross-platform if that is intended.
- Include notes or links for Linux/macOS users about installing and using the Azure CLI.
- If PowerShell examples are included, specify whether they are compatible with PowerShell Core on Linux/macOS.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/tutorials/disallowed-resources.md
...es/governance/policy/tutorials/disallowed-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure Portal (web UI) for all tasks and only mentions Azure CLI, Azure PowerShell, and ARM templates in a single note about creating resources in exempted scopes. There are no command-line examples for either Windows or Linux, but the mention of Azure PowerShell and the lack of explicit Linux CLI (bash) examples or references to Linux tooling suggest a subtle Windows-first bias. The documentation does not provide parity for Linux users who may prefer bash or cross-platform CLI workflows.
Recommendations
- Add explicit Azure CLI (bash) command examples for all major tasks (assigning policy, creating exemptions, cleaning up resources), ensuring commands are cross-platform.
- Where Azure PowerShell is mentioned, also mention Azure CLI and provide equivalent examples.
- Include a section or callout for Linux/macOS users, clarifying that all tasks can be performed via CLI and providing links to relevant documentation.
- Avoid implying that Azure PowerShell is the primary or only non-portal automation option; always present CLI and PowerShell together.
- Consider adding screenshots or terminal output from both Windows and Linux environments where appropriate.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-monitor.md
...ce-graph/includes/samples-by-category/azure-monitor.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each scenario. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally associated with Windows, though now available cross-platform) and the explicit labeling of 'Azure PowerShell' examples before any mention of Linux-native tools or shell environments introduces a subtle Windows bias. There are no Linux shell (bash, zsh) or scripting examples, nor is there any mention of Linux-specific usage patterns. The ordering of examples (CLI, then PowerShell, then Portal) also places Windows-oriented tooling before Linux-native alternatives.
Recommendations
- Add explicit bash/zsh shell examples using Azure CLI to demonstrate usage in Linux environments (e.g., with jq for parsing).
- Clarify that Azure CLI commands are cross-platform and can be used in both Windows and Linux environments.
- Consider including example scripts or usage patterns for Linux automation (e.g., bash scripts, cron integration).
- If PowerShell is included, note that PowerShell Core is available on Linux and macOS, and provide a Linux PowerShell example if relevant.
- Review the ordering of examples to avoid always placing Windows-oriented tools (PowerShell) before Linux-native or cross-platform tools.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/samples/swift-csp-cscf-2021.md
...icles/governance/policy/samples/swift-csp-cscf-2021.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a comprehensive mapping of Azure Policy definitions to SWIFT CSP-CSCF v2021 controls, with coverage for both Windows and Linux platforms. However, there is a subtle Windows bias: in several cases, Windows-specific policies or tools are mentioned before their Linux equivalents, and some monitoring or security features (such as antimalware) are described only for Windows. Additionally, certain policy descriptions reference Windows-specific mechanisms (e.g., registry paths, Windows Update) without parallel Linux details.
Recommendations
- Ensure that for every Windows-specific policy or tool mentioned, the Linux equivalent is presented with equal prominence and detail, ideally side-by-side.
- Where policies are platform-specific (e.g., antimalware for Windows), clarify whether an equivalent exists for Linux or explicitly state the gap.
- Avoid listing Windows policies before Linux ones by default; consider alternating or grouping by platform.
- In descriptions referencing Windows-specific mechanisms (such as registry paths or Windows Update), provide analogous Linux mechanisms (such as package manager updates, file permissions) where applicable.
- Add more Linux-specific examples or guidance where currently only Windows details are provided, especially for monitoring, security updates, and malware protection.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-arc.md
...source-graph/includes/samples-by-category/azure-arc.md
Medium 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 to CLI, despite PowerShell being primarily a Windows-centric tool (even though cross-platform support exists). There are no Linux- or bash-specific examples or notes, and PowerShell is presented as a first-class option alongside CLI, which may not reflect the typical Linux user experience. No explicit Windows-only tools are used, but the lack of Linux shell or scripting context may disadvantage Linux users.
Recommendations
- Add bash shell examples using Azure CLI to demonstrate usage in typical Linux environments (e.g., piping, jq for output parsing).
- Clarify that Azure CLI commands work cross-platform and highlight any OS-specific considerations.
- If PowerShell is included, note its cross-platform availability but clarify that many Linux users may prefer bash.
- Consider providing example output or troubleshooting notes for both Windows and Linux shells.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/microsoft-defender.md
...aph/includes/samples-by-category/microsoft-defender.md
Medium 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 to Azure CLI, despite PowerShell being a Windows-centric tool (even though cross-platform support exists, it is still most familiar to Windows users). No Linux- or Unix-specific shell examples (e.g., Bash, shell scripting, or piping output to jq) are provided. The ordering of examples (CLI first, then PowerShell) is acceptable, but the consistent inclusion of PowerShell examples without any Linux-native shell context may signal a bias toward Windows users.
Recommendations
- Add explicit Bash/shell examples for Linux users, demonstrating how to run the Azure CLI commands in a typical Linux shell environment.
- Include examples of parsing or formatting output using Linux tools (e.g., piping az graph query output to jq or grep).
- Clarify in the documentation that Azure CLI is fully cross-platform and can be used natively on Linux, macOS, and Windows.
- Consider including a 'Bash' or 'Linux shell' tab alongside the CLI and PowerShell tabs, or at least provide a note or example for Linux users.
- If PowerShell is included for its cross-platform nature, explicitly mention that it is available on Linux and macOS, and provide installation links or references.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-virtual-machines.md
...includes/samples-by-category/azure-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally presents queries and examples in a platform-neutral way, using Azure CLI, Azure PowerShell, and Portal tabs for each scenario. However, there is a subtle Windows bias: in sections about OS update installation, the general (non-Linux/Windows-specific) queries and explanations implicitly focus on Windows, with Linux-specific queries only appearing later and in a separate section. There is no equivalent 'general' query for Linux, and the Linux example is not presented alongside the Windows one, but rather after several Windows-centric queries. This ordering and separation can make Linux users feel like an afterthought.
Recommendations
- When presenting OS update installation queries, provide both Windows and Linux examples side by side, or clearly indicate which queries apply to which OS.
- In sections where a 'general' query is given (e.g., 'Count of OS update installation done'), clarify whether it applies to both Windows and Linux, or provide equivalent queries for each.
- Avoid grouping all Windows-related queries before Linux ones; instead, interleave or pair them to show parity.
- Explicitly state OS applicability in headings and descriptions, so Linux users can quickly find relevant content.
- Consider adding a summary table or section at the top that links to both Windows and Linux scenarios for common tasks.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/iot-defender.md
...rce-graph/includes/samples-by-category/iot-defender.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure PowerShell examples alongside Azure CLI and Portal, with PowerShell being a Windows-centric tool. There is no explicit mention of Linux-specific shells or command-line environments, and PowerShell is given equal prominence to the cross-platform Azure CLI. The ordering of examples sometimes places PowerShell before or on par with CLI, which may imply Windows as a primary platform.
Recommendations
- Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though cross-platform PowerShell Core exists).
- Consider placing Azure CLI examples before PowerShell to reinforce cross-platform parity.
- Add notes or examples for running queries in Bash or other common Linux shells, especially if there are any differences in quoting or command syntax.
- Clarify in the documentation that all shown queries are platform-agnostic when using Azure CLI.
- If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, and provide installation links if relevant.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-assignments-key-properties.md
...uthorization-resources-role-assignments-key-properties.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, but lists Azure PowerShell (a Windows-centric tool) as a primary tab alongside Azure CLI, and does not clarify cross-platform compatibility. There is no explicit mention of Linux or macOS environments, nor are there Linux-specific notes or examples. The PowerShell example may imply a Windows-first approach.
Recommendations
- Clearly state that Azure CLI is fully cross-platform and works on Linux, macOS, and Windows.
- Add a note clarifying that Azure PowerShell is available on all platforms via PowerShell Core, or provide a Linux/macOS-specific PowerShell example if differences exist.
- Consider listing Azure CLI before PowerShell, as it is the most universally available tool.
- Explicitly mention Linux/macOS compatibility in the introductory text or in tool descriptions.
- If there are any platform-specific caveats (e.g., authentication differences), call them out in the documentation.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-key-properties.md
...uthorization-resources-role-definitions-key-properties.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but includes a dedicated PowerShell section, which is primarily a Windows tool. The PowerShell example is given equal prominence to the Azure CLI, but there is no explicit mention of Linux shell (bash) or cross-platform scripting, and PowerShell is still more closely associated with Windows environments. The ordering of examples (CLI first, then PowerShell) is good, but the presence of a PowerShell-specific tab without a corresponding Linux shell/bash example may indicate a slight Windows bias.
Recommendations
- Add a bash or Linux shell example to demonstrate parity for Linux users.
- Clarify that Azure CLI commands work identically on Windows, Linux, and macOS.
- Consider mentioning cross-platform PowerShell Core if PowerShell examples are included, to highlight Linux/macOS support.
- Explicitly state platform compatibility for each example to reassure non-Windows users.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-actions-list.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/authorization-resources-role-definitions-actions-list.md
Medium 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 traditionally associated with Windows, though now available cross-platform) and its placement immediately after the CLI example may suggest a slight Windows bias. There are no explicit Linux shell (bash) examples, nor are Linux-specific tools or workflows mentioned. The documentation does not provide a bash or shell script example, nor does it clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
Recommendations
- Add a dedicated Bash/shell example or explicitly note that the Azure CLI example works on Linux/macOS as well as Windows.
- Clarify that Azure PowerShell is available cross-platform, or provide a note about its usage on Linux/macOS.
- Consider reordering examples so that the most cross-platform tool (Azure CLI) is presented first, and PowerShell is clearly marked as optional or secondary.
- If relevant, mention any Linux-specific considerations or troubleshooting tips.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/insight-resources-monitor-data-collection-rules.md
...ery/insight-resources-monitor-data-collection-rules.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux-specific usage or shell environments. The use of PowerShell as a primary example can be seen as Windows-centric, especially since PowerShell is traditionally associated with Windows, even though it is now cross-platform. There are no Linux shell (bash) specific examples or notes about running the CLI on Linux.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example usage in a bash shell.
- Add a Linux/macOS terminal example (e.g., bash prompt) to demonstrate parity and clarify cross-platform support.
- Clarify that PowerShell is available cross-platform, or provide guidance for Linux users who may not use PowerShell.
- Consider ordering the examples with Azure CLI (which is more cross-platform) before PowerShell, or provide a clear note about cross-platform compatibility.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/virtual-machine-scale-sets-computeresources-uniform-orchestration.md
...hine-scale-sets-computeresources-uniform-orchestration.md
Medium 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 its own dedicated tab, which can be interpreted as giving it equal or higher prominence compared to the cross-platform Azure CLI. There are no explicit Linux-specific examples or notes, and the PowerShell example may suggest a Windows-centric workflow, especially for users unfamiliar with cross-platform capabilities of Azure CLI.
Recommendations
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
- Consider listing the Azure CLI tab first, as it is the most cross-platform tool.
- Add a note clarifying that PowerShell Core is available on Linux and macOS, or provide a Bash shell example to further demonstrate Linux parity.
- Ensure that documentation does not imply PowerShell is the default or preferred method unless justified.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/virtual-machine-scale-sets-resources-flexible-orchestration.md
...al-machine-scale-sets-resources-flexible-orchestration.md
Medium 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 to the CLI example, which can indicate a slight Windows bias. There is no explicit Linux shell example (such as Bash), and PowerShell is a Windows-centric tool, though it is now cross-platform. The ordering of examples (CLI first, then PowerShell) is good, but the lack of a native Bash or Linux shell example may disadvantage Linux users.
Recommendations
- Add a Bash shell example using az CLI to explicitly demonstrate Linux compatibility.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider including a note that PowerShell Core is cross-platform, but traditional PowerShell is Windows-only.
- If possible, provide OS-specific instructions or notes for any differences in command usage or output.
Governance
Deploy Australian Government ISM PROTECTED blueprint sample
.../governance/blueprints/samples/ism-protected/deploy.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation shows a mild Windows bias, primarily in the artifact parameters table, where parameters related to Windows VM Administrator group management and Windows-specific extensions (e.g., Microsoft IaaSAntimalware extension) are present. Windows VM examples (e.g., lists of users for Administrators group) are described in detail, while Linux equivalents (such as sudoers or admin group management) are not mentioned. However, Linux VM and VMSS artifacts are included, and there are parameters for both Windows and Linux VM images and Log Analytics workspaces. No PowerShell-specific instructions or Windows-only deployment steps are present, and the UI-based instructions are platform-neutral.
Recommendations
- Add equivalent Linux admin group management parameters and documentation (e.g., managing sudoers or admin group membership for Linux VMs).
- Provide examples or notes for Linux VM security controls where only Windows controls are described (e.g., password complexity, admin group membership).
- Ensure parity in extension deployment descriptions (e.g., mention Linux antimalware or endpoint protection extensions if available).
- Clarify in the documentation which controls apply to Windows, Linux, or both, and provide links to Linux-specific guidance where relevant.
Governance
Azure Machine Configuration prerequisites
...chine-configuration/overview/02-setup-prerequisites.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows mild Windows bias, with Windows examples and tools (PowerShell DSC) mentioned before Linux equivalents, and links to Windows-specific configuration guides. While Linux is supported and referenced (including Chef InSpec and PowerShell DSC v3 for Linux), Windows tools and patterns are often listed first, and some links (e.g., managed identity configuration) point to Windows VM-specific instructions without clear Linux alternatives.
Recommendations
- Ensure Linux and macOS instructions are presented alongside or before Windows examples, especially for common tasks like managed identity configuration.
- Provide explicit links and examples for configuring managed identities and extensions on Linux VMs, not just Windows VMs.
- Clarify the use of validation tools for Linux, including PowerShell DSC v3 and Chef InSpec, with step-by-step Linux-specific setup instructions.
- Where possible, avoid listing Windows tools first in tables or sections; alternate or group by OS.
- Add references to macOS support or limitations if relevant.
Governance
Azure machine configuration agent release notes
...es/governance/machine-configuration/whats-new/agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux by providing separate release notes and features for each platform. However, there is a mild bias in the order of presentation (Windows extension release notes are listed before Linux), and in one section, PowerShell is used as the first example for updating the Linux extension, with the Azure CLI example following. There are no critical omissions of Linux information or exclusive use of Windows tools for Linux tasks.
Recommendations
- Alternate the order of Windows and Linux sections or present them in parallel to avoid implicit prioritization.
- When providing command examples for cross-platform tasks (such as updating extensions), present Azure CLI examples first or equally with PowerShell, as CLI is more universally available on Linux/macOS.
- Explicitly mention platform-appropriate tools and workflows for both Windows and Linux in all relevant sections.
- Ensure that any references to environment variables, file paths, or configuration steps are clearly distinguished for each platform.