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 276-300 of 613 flagged pages
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric queries and terminology (e.g., 'Windows Server', 'kbId', 'updateRollup', 'featurePack', 'servicePack') are used more frequently and are presented before or in greater detail than Linux equivalents. The structure often lists Windows queries before Linux ones, and some queries (such as OS update installation) are split into separate Windows and Linux sections, with Windows appearing first. There is a lack of Linux-specific examples or explanations for several queries, and PowerShell (a Windows-native tool) is given equal prominence to Azure CLI, which is more cross-platform. Windows update classifications are referenced without Linux equivalents or mapping.
Recommendations
- Ensure Linux and Windows queries/examples are presented with equal prominence and detail, alternating order or grouping them together where appropriate.
- Provide Linux-specific terminology and explanations for update classifications, mapping Windows concepts to their Linux equivalents (e.g., security updates, kernel updates, package updates).
- Add more Linux-focused examples, especially for queries that only mention Windows-specific properties or concepts.
- Clarify when queries or properties are OS-agnostic versus OS-specific, and explicitly note differences in resource properties between Windows and Linux VMs.
- Consider including Bash or shell scripting examples alongside PowerShell, or referencing cross-platform scripting approaches.
- Review and balance the use of Windows-centric terms (e.g., 'kbId', 'servicePack') with Linux equivalents (e.g., package version, distribution-specific update types).
Create Pull Request
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
High 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 traditionally Windows-centric, though now available on Linux/macOS) and the absence of Linux-specific shell examples (such as Bash scripts or direct REST API usage) indicate a mild Windows bias. The PowerShell example is given equal prominence to the CLI, and no explicit Linux-native patterns or tools are mentioned.
Recommendations
- Add explicit Bash shell examples using Azure CLI to demonstrate usage on Linux/macOS.
- Clarify that Azure CLI commands work natively on Linux/macOS and Windows.
- Consider including REST API or SDK examples that are platform-agnostic.
- If PowerShell is included, note its cross-platform availability and provide guidance for Linux/macOS users.
- Review tab order and ensure CLI (cross-platform) examples are presented before PowerShell (historically Windows-centric) examples.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/azure-policy.md
...rce-graph/includes/samples-by-category/azure-policy.md
High 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 examples are given equal prominence to Azure CLI, which is cross-platform. There are no explicit Linux shell (bash/zsh) or scripting examples, nor are Linux-specific tools or usage patterns mentioned. The tabs always present Azure CLI first, but PowerShell is given as a primary automation option, which may reinforce Windows bias for automation scenarios. No Linux-specific instructions, troubleshooting, or environment notes are present.
Recommendations
- Add explicit bash/zsh shell script examples for each scenario, demonstrating use on Linux/macOS.
- Clarify that Azure CLI is fully cross-platform and provide installation/use notes for Linux.
- Mention that PowerShell Core is available on Linux/macOS, and provide Linux-specific PowerShell usage notes if relevant.
- Include troubleshooting or environment setup notes for Linux users (e.g., authentication, environment variables, file paths).
- If relevant, reference Linux-native automation tools (e.g., cron, shell scripting) for scheduled queries.
- Consider reordering tabs or adding a note that CLI is recommended for cross-platform use.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/overview.md
...ob/main/articles/governance/resource-graph/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page references Azure PowerShell and Azure CLI as ways to interact with Azure Resource Graph, but PowerShell is mentioned before CLI in most places, and there are no explicit Linux-specific examples or mentions of Linux shell usage (e.g., Bash). The 'Run queries with Power BI connector' section references a Windows-centric tool without mentioning cross-platform alternatives. There is no mention of Linux tools or patterns, nor any explicit parity guidance for Linux users.
Recommendations
- Ensure Azure CLI is mentioned before or alongside PowerShell when listing query methods, as CLI is cross-platform.
- Add explicit examples for running queries from Bash or other Linux shells, including sample commands.
- Mention that Azure CLI works natively on Linux and macOS, and provide links to installation guides for those platforms.
- Reference cross-platform data visualization tools (e.g., Jupyter, Grafana) in addition to Power BI, or clarify Power BI's availability on non-Windows platforms.
- Where possible, include screenshots or walkthroughs from Linux environments to demonstrate parity.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for each query, but omits explicit Linux shell examples (e.g., Bash). PowerShell, a Windows-centric tool, is given equal prominence to Azure CLI, and is listed immediately after CLI in each section. There are no references to Linux-specific tools, shell patterns, or platform considerations, and no guidance for running queries from a Linux environment beyond the CLI. This may unintentionally signal a bias toward Windows users and workflows.
Recommendations
- Add explicit Bash/Linux shell examples for running Azure CLI commands, including any necessary syntax for quoting or escaping.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users (e.g., installation, environment differences).
- Consider including a section or tab for Linux shell usage, or at least mention Linux compatibility in each CLI example.
- If PowerShell is included, note that PowerShell Core is available cross-platform, and provide guidance for Linux/macOS users if relevant.
- Review ordering: consider listing CLI (cross-platform) before PowerShell, and avoid implying PowerShell is the default or preferred method.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/includes/samples-by-category/query/policy-resources-exemption-query.md
...-by-category/query/policy-resources-exemption-query.md
High 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 still most commonly used on Windows) and the absence of Linux-specific shell examples (e.g., Bash scripting, piping, or integration with Linux tools) indicates a bias toward Windows environments. Additionally, PowerShell examples are given equal prominence to CLI, and there is no mention of Linux-native tools or workflows. The references to Azure PowerShell and the lack of explicit Linux shell usage or troubleshooting reinforce a subtle Windows bias.
Recommendations
- Add explicit Bash or Linux shell examples, demonstrating how to use az graph query in typical Linux workflows (e.g., piping to grep, jq, awk).
- Clarify that Azure CLI is cross-platform and provide examples of its use in both Windows and Linux environments.
- Mention Linux-native tools that can be used in conjunction with Azure CLI output, such as jq for JSON parsing.
- If PowerShell is included, note that PowerShell Core is available on Linux and macOS, and provide examples for those platforms where relevant.
- Consider reordering examples to present Azure CLI (cross-platform) before Azure PowerShell, or group them by platform rather than tool.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/resource-graph/troubleshoot/general.md
...cles/governance/resource-graph/troubleshoot/general.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias by providing only PowerShell examples for batch querying subscriptions, referencing PowerShell and Azure CLI as the primary tools, and omitting equivalent Linux shell (bash) or cross-platform SDK examples. The PowerShell solution is presented exclusively, with no mention of how to perform the same task using bash, Python SDK, or REST API directly. This may disadvantage Linux users or those working in non-Windows environments.
Recommendations
- Add equivalent examples using bash (Azure CLI), Python SDK, and REST API for batch querying subscriptions.
- Present cross-platform solutions (e.g., Azure CLI, REST API) before or alongside PowerShell examples.
- Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
- Ensure all troubleshooting steps reference tools and patterns available on both Windows and Linux platforms.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/service-groups/manage-membership.md
...rticles/governance/service-groups/manage-membership.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a clear Windows bias in its automation and scripting guidance. The only provided script for bulk membership management uses PowerShell, a Windows-centric tool, and references Windows-style command lines and output. There are no equivalent examples for Linux or cross-platform tools (such as Azure CLI, Bash, or Python). The script and its usage instructions assume a Windows environment and PowerShell, with no mention of alternatives for Linux or macOS users.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts, which are natively supported on Linux and macOS.
- Include cross-platform automation options, such as Python scripts using the Azure SDK.
- Explicitly mention that PowerShell is available on Linux and macOS, and provide installation instructions or links.
- Add a section comparing automation approaches for Windows and Linux, highlighting any differences and best practices.
- Ensure that output and command examples do not assume a Windows file system or shell (e.g., avoid Windows paths and temp file handling).
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/policy-for-kubernetes.md
...es/governance/policy/concepts/policy-for-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation is largely cross-platform and Kubernetes-focused, but there are subtle signs of Windows bias. Windows-specific domains (e.g., login.windows.net), references to Azure PowerShell, and the use of Azure CLI (which is cross-platform but often associated with Windows environments) are present. The documentation sometimes lists Windows tools (Azure PowerShell) before Linux-native equivalents, and troubleshooting/logging examples do not explicitly address Linux-specific nuances. However, the majority of command-line examples use Azure CLI and kubectl, which are cross-platform, and there is explicit mention that the Azure Policy Add-on for Kubernetes can only be deployed to Linux node pools. There are no overtly missing Linux examples, but the documentation could do more to highlight Linux-native workflows and tools.
Recommendations
- When listing tools or commands, always mention cross-platform or Linux-native options first (e.g., Azure CLI before Azure PowerShell).
- Where Azure PowerShell is referenced, provide equivalent Bash or shell commands for Linux users.
- Clarify that Azure CLI and kubectl commands are cross-platform and provide explicit instructions for both Windows and Linux environments where paths, environment variables, or behaviors differ.
- Avoid using Windows-specific domains or terminology unless strictly necessary; if used, clarify their relevance to all platforms.
- Add troubleshooting/logging sections that address common Linux-specific issues (e.g., permissions, file paths, environment setup).
- Explicitly mention that all examples work on Linux unless otherwise noted, and provide any necessary Linux-specific prerequisites or caveats.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/policy-for-kubernetes.md
...es/governance/policy/concepts/policy-for-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It frequently references Windows-specific domains (e.g., login.windows.net), lists Azure CLI and Azure PowerShell as primary tools (with PowerShell examples included), and refers to the Azure portal UI, which is more familiar to Windows users. While most command-line examples use Azure CLI and kubectl (cross-platform), PowerShell is mentioned as an alternative to Azure CLI, but no explicit Linux shell or bash alternatives are provided for PowerShell commands. Additionally, Windows-specific terminology and endpoints are referenced before or instead of Linux equivalents, and there is a lack of explicit Linux-focused troubleshooting or installation guidance.
Recommendations
- Where PowerShell is mentioned, provide equivalent bash commands for Linux users, or clarify that Azure CLI commands are cross-platform.
- When referencing Azure portal steps, clarify that the portal is web-based and not Windows-specific.
- When listing domains or endpoints (e.g., login.windows.net), clarify their cross-platform nature or provide context for Linux users.
- Include troubleshooting and installation notes specific to Linux environments, especially for common issues (e.g., permissions, networking).
- If referencing Azure CLI, explicitly state its cross-platform compatibility and provide installation links for Linux and macOS.
- Avoid listing Windows tools or endpoints first unless they are required; otherwise, present them in a neutral or platform-agnostic order.
- Add explicit notes or examples for Linux users where behavioral differences may exist (e.g., file paths, environment variables).
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/ism-protected/control-mapping.md
...ce/blueprints/samples/ism-protected/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by repeatedly referencing Windows-specific audit controls, tools, and extensions (such as the Microsoft IaaSAntimalware extension and auditing the Windows Administrators group) without providing equivalent Linux examples or controls. In several sections, only Windows VMs or Windows web servers are mentioned for auditing or security checks, while Linux VMs are either omitted or only referenced in a limited context. Antivirus and endpoint protection recommendations are also Windows-centric, and there is a lack of parity in Linux-specific guidance for several controls.
Recommendations
- For every control or recommendation that references Windows VMs, provide equivalent guidance and Azure Policy mappings for Linux VMs (e.g., audit sudoers or root group membership for Linux).
- When mentioning tools like Microsoft IaaSAntimalware extension (Windows-only), also mention and recommend supported Linux antimalware/endpoint protection solutions.
- Where audit results or prerequisites are listed for Windows (e.g., Administrators group, Security Settings - Account Policies), include parallel examples for Linux (e.g., /etc/passwd, /etc/group, PAM configuration, SSH settings).
- For web server security controls, include Linux-based web servers (Apache, Nginx) in audit recommendations and secure communication protocol checks.
- Ensure that endpoint protection, vulnerability assessment, and backup recommendations explicitly cover both Windows and Linux environments, with clear instructions or links for each.
- Review all sections for Windows-centric language and update to use inclusive phrasing (e.g., 'Windows or Linux VMs') where appropriate.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/swift-2020/control-mapping.md
...nance/blueprints/samples/swift-2020/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Many control mappings and policy definitions specifically reference Windows virtual machines, Windows-specific settings (such as password policies and antimalware extensions), and Windows tools, often without providing equivalent Linux examples or parity. In several sections, Windows controls are listed before Linux ones, and some controls (e.g., password complexity, antimalware) are only described for Windows, with no mention of Linux equivalents or best practices. Linux is referenced in some areas (e.g., auditing accounts without passwords, Log Analytics agent deployment), but coverage is less comprehensive and often appears after Windows content.
Recommendations
- For every Windows-specific policy or example, provide an equivalent Linux policy or example where applicable (e.g., password complexity, antimalware/endpoint protection, auditing domain membership).
- Ensure Linux controls and examples are presented with equal prominence and detail as Windows ones, rather than as secondary or afterthoughts.
- Where a feature is not available for Linux, explicitly state this and, if possible, suggest alternative approaches or workarounds.
- Expand documentation for Linux-specific security practices (e.g., password file permissions, PAM configuration, Linux antimalware solutions) to match the depth of Windows coverage.
- Review the order of presentation to avoid consistently listing Windows controls before Linux ones; alternate or group by OS where appropriate.
- Audit for missing Linux coverage in areas such as password policy enforcement, domain join auditing, and endpoint protection, and add relevant content.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/swift-2020/deploy.md
...les/governance/blueprints/samples/swift-2020/deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-related artifacts and parameters in both descriptions and examples. Windows VM administration and domain join are discussed in detail, while Linux equivalents are mentioned only in passing or as secondary considerations. There are no Linux-specific usage examples, and Windows terminology (e.g., 'Administrators group', 'domain join') is used exclusively where cross-platform alternatives could be provided.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for tasks like VM administration and domain join.
- Balance the artifact parameter table by including Linux-focused parameters and descriptions where applicable (e.g., mention Linux admin groups or domain join alternatives).
- Avoid listing Windows artifacts and parameters before Linux ones unless there is a technical reason; consider alternating or grouping by OS.
- Use neutral, cross-platform terminology where possible (e.g., 'administrator group' instead of 'Windows VM Administrators group').
- Include guidance or links for managing Linux VMs (e.g., joining to a domain, configuring admin users) to achieve parity with the Windows instructions.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/blueprints/samples/iso27001-shared/control-mapping.md
.../blueprints/samples/iso27001-shared/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. While some Linux-specific controls are mentioned (e.g., auditing Linux VM password files and accounts without passwords), Windows examples and controls are prioritized or exclusively detailed in several sections. For example, password management (A.9.4.3) lists only Windows VM policies, with no equivalent Linux password policy controls. Additionally, some controls reference Windows-specific tools or settings without Linux parity, and there is a general lack of Linux-focused examples or guidance in areas where both platforms are relevant.
Recommendations
- For each control that audits or enforces password policies on Windows VMs, provide equivalent controls, examples, or guidance for Linux VMs (e.g., minimum password length, complexity, password age, and reuse policies).
- Where Windows-specific tools or settings are referenced (such as password complexity or audit policies), include Linux equivalents (e.g., PAM configuration, chage, passwd file permissions) and describe how to audit/enforce them via Azure Policy or other supported mechanisms.
- Ensure that for every mention of Windows VM controls, there is a corresponding mention of Linux VM controls where applicable, or explicitly state if such controls are not available.
- Add more Linux-focused examples and recommendations throughout the documentation, especially in sections that currently only mention Windows.
- Review the ordering of examples and controls to avoid always listing Windows first; alternate or group by platform where appropriate.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/overview.md
...onfiguration/how-to/develop-custom-package/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on PowerShell tooling and examples, referencing the GuestConfiguration PowerShell module and providing a video tutorial based on PowerShell. There is no mention of Linux-native tooling, nor are there Linux-specific examples or workflows. The documentation assumes PowerShell as the primary authoring and validation environment, even though Linux support is mentioned.
Recommendations
- Include Linux-native command-line examples (e.g., Bash, shell scripts) for authoring and validating machine configuration packages.
- Provide parity in tooling instructions, such as how to use the GuestConfiguration module or equivalent tools on Linux systems.
- Add a Linux-focused video or walkthrough to complement the PowerShell-based video.
- Clarify any differences or additional steps required for Linux users, especially where PowerShell is not the default shell.
- Explicitly mention and link to Linux documentation or resources where available.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/concepts/assignments.md
...vernance/machine-configuration/concepts/assignments.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias by providing examples and references that are specific to Windows environments, such as the Azure Windows Baseline configuration and exclusive use of PowerShell for management tasks. There are no Linux-specific examples or equivalent command-line instructions, and the documentation does not mention Linux tools or patterns for managing machine configuration assignments.
Recommendations
- Include Linux-specific examples, such as associating a Linux baseline configuration or referencing Linux guest configuration packages.
- Provide equivalent CLI (az CLI), Bash, or REST API examples for managing machine configuration assignments, not just PowerShell.
- Mention and demonstrate how Linux VMs or Arc-enabled machines can be managed with guest configuration assignments.
- Balance the order of examples and references so that Linux and Windows are treated equally, or clarify cross-platform applicability where relevant.
- Reference Linux-relevant documentation or tools where appropriate, such as DSC for Linux or other configuration management solutions.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/develop-custom-package/4-publish-package.md
...ion/how-to/develop-custom-package/4-publish-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell (Az.Storage module) examples for publishing configuration packages to Azure Blob Storage, with no mention of Linux-native tools, Bash, or cross-platform CLI alternatives. All code snippets and workflow steps assume a Windows/PowerShell environment, and there are no references to Linux or macOS workflows.
Recommendations
- Add equivalent examples using Azure CLI (az storage ...) commands, which are cross-platform and work natively on Linux, macOS, and Windows.
- Include Bash shell script examples for uploading files to Azure Blob Storage.
- Mention and provide examples for using tools like azcopy, which is available on all major platforms.
- Explicitly state that the process can be performed from Linux/macOS as well as Windows, and provide guidance for those environments.
- Reorganize the documentation to present cross-platform or CLI-first solutions before PowerShell-specific instructions, or at least present them in parallel.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/machine-configuration/how-to/create-policy-definition.md
...chine-configuration/how-to/create-policy-definition.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples use PowerShell and reference Windows-specific cmdlets and paths. The 'Platform' parameter is always set to 'Windows' in examples, and file paths use Windows conventions (e.g., C:\Local\Path\To\Package). There are no Linux/Bash/CLI examples, and Linux-specific considerations are only mentioned in passing (e.g., minimum agent version). Windows tools and patterns are presented exclusively, with no parity for Linux users.
Recommendations
- Provide equivalent examples using Bash or Azure CLI for Linux users, especially for tasks like setting variables, uploading packages, and creating policies.
- Include at least one example where the 'Platform' parameter is set to 'Linux', and use Linux file path conventions (e.g., /home/user/package.zip) in those examples.
- Mention Linux prerequisites and environment setup steps alongside Windows/PowerShell instructions.
- Reference Linux tools (e.g., az CLI, bash scripting) and show how to accomplish the same tasks without PowerShell.
- Clarify which steps are OS-agnostic and which require OS-specific commands, ideally grouping examples by platform.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/management-groups/how-to/protect-resource-hierarchy.md
...management-groups/how-to/protect-resource-hierarchy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell-only example for interacting with the REST API, with no equivalent example for Linux-native tools such as Bash, curl, or Azure CLI. The only script-based automation guidance is given in PowerShell, which is primarily a Windows tool, and there is no mention of Linux or cross-platform alternatives.
Recommendations
- Add equivalent examples using Bash with curl for REST API calls, which are native to Linux environments.
- Provide Azure CLI (az) command examples where possible, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that the REST API can be called from any platform and provide generic HTTP request examples.
- Ensure that scripting examples are not limited to PowerShell, and offer parity for Linux users.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/management-groups/create-management-group-dotnet.md
...ce/management-groups/create-management-group-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-specific instructions and examples. The execution command uses a Windows-style executable (mgCreate.exe) and PowerShell-style line continuations (`), with no mention of Linux or cross-platform equivalents. There are no Linux/macOS-specific instructions or examples for running the application, and the use of .exe implies a Windows environment. Additionally, the clean-up instructions reference deleting folders in a way that is more familiar to Windows users.
Recommendations
- Provide explicit instructions and examples for running the .NET Core application on Linux and macOS, including using 'dotnet mgCreate.dll' instead of 'mgCreate.exe'.
- Use cross-platform command-line syntax, or provide both Windows (PowerShell/cmd) and Linux/macOS (bash) variants for commands, especially for application execution and directory navigation.
- Avoid Windows-specific line continuation characters (e.g., backtick `) in command examples, or provide bash equivalents (e.g., backslash \) for Linux/macOS.
- Clarify that .NET Core applications are cross-platform and can be run on Windows, Linux, and macOS, and provide any necessary prerequisites or troubleshooting tips for non-Windows environments.
- Update clean-up instructions to include Linux/macOS commands for deleting project folders (e.g., 'rm -rf mgCreate').
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/samples/australia-ism.md
...in/articles/governance/policy/samples/australia-ism.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways. Many policy definitions and compliance controls specifically reference Windows machines, Windows extensions, or Windows-specific tools (such as the Microsoft IaaSAntimalware extension), often without providing equivalent Linux examples or alternatives. In sections where both Windows and Linux are relevant (e.g., guest configuration, privileged access, antivirus), Windows is frequently mentioned first or exclusively, with Linux-specific policies either omitted or only included in select areas. This creates an impression that Windows is the primary or default platform for compliance, while Linux support is secondary or incomplete.
Recommendations
- For every Windows-specific policy or example, provide a Linux equivalent where possible, or explicitly state if one does not exist.
- Ensure Linux guest configuration, extension deployment, and security controls are documented alongside Windows, not as an afterthought.
- Add Linux-focused antivirus and hardening policy examples, or clarify the current limitations for Linux support.
- Review the ordering of examples and policies to avoid always listing Windows first; consider alternating or grouping by OS.
- Where Windows tools or extensions are referenced (e.g., IaaSAntimalware), mention Linux-compatible alternatives or note the lack thereof.
- Include cross-platform guidance and highlight any differences in compliance implementation between Windows and Linux.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/migrate-from-automanage-best-practices.md
...olicy/how-to/migrate-from-automanage-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (such as Windows Admin Center and Microsoft Antimalware for Azure) are highlighted with detailed configuration steps and dedicated sections, while Linux equivalents are either omitted or only briefly mentioned. In several sections, Windows is mentioned before Linux, and some features (like antimalware and Windows Admin Center) are described exclusively for Windows, with no Linux alternatives or guidance provided. Where Linux is mentioned (e.g., Change Tracking and Inventory, Azure Update Manager), the coverage is less detailed than for Windows.
Recommendations
- For every Windows-specific tool or feature (e.g., Windows Admin Center, Microsoft Antimalware), provide Linux equivalents or explicitly state if no equivalent exists.
- Ensure that all example policies, configuration steps, and extension deployments are shown for both Windows and Linux VMs, with equal detail.
- Avoid listing Windows before Linux by default; alternate the order or use neutral phrasing (e.g., 'Windows and Linux VMs').
- Where a feature is Windows-only, clearly state this and, if possible, suggest best practices or alternatives for Linux users.
- Expand sections such as antimalware and admin tools to discuss Linux security and management options (e.g., integration with third-party Linux antimalware, SSH-based management, etc.).
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/samples/canada-federal-pbmm.md
...icles/governance/policy/samples/canada-federal-pbmm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. Windows-specific policies and controls (such as auditing Windows Administrators group membership, password policies, and deployment of Windows Guest Configuration extensions) are listed and described in detail, while equivalent Linux controls are either absent or less comprehensive. In several sections, Windows controls are presented first or exclusively, and there are more granular controls for Windows than for Linux. There are also policies that reference Windows-specific tools and patterns without Linux parity.
Recommendations
- Ensure that for every Windows-specific policy or example (e.g., auditing Administrators group, password complexity, Guest Configuration extension deployment), there is an equivalent Linux policy or example, or clearly state if a Linux equivalent is not available.
- Present Linux and Windows controls in parallel, rather than listing Windows controls first or exclusively, to avoid the perception of prioritizing Windows.
- Expand Linux coverage to include more granular controls, such as auditing Linux sudoers group membership, password complexity, and other common Linux security configurations.
- Where Windows tools or extensions are mentioned (e.g., Windows Guest Configuration extension), ensure Linux equivalents are described with equal detail and prominence.
- If certain controls are not available for Linux, explicitly acknowledge the gap and, if possible, provide guidance or workarounds for Linux users.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/samples/built-in-packages.md
...rticles/governance/policy/samples/built-in-packages.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. The majority of policy definitions and examples are Windows-specific, referencing Windows tools, PowerShell Desired State Configuration (DSC), and Windows-centric modules. Linux is only mentioned in a few entries, and Linux-specific modules or equivalent tooling are not described in detail. The introductory text and table structure focus on PowerShell and Windows, with Linux policies being the exception rather than the norm.
Recommendations
- Add more Linux-specific policy definitions and examples to achieve parity with Windows coverage.
- Include details and links for Linux equivalents of PowerShell DSC modules, or clarify how guest configuration is implemented on Linux.
- Revise introductory text to mention both Windows and Linux approaches equally, rather than focusing on PowerShell and Windows first.
- Where possible, provide side-by-side examples or tables for both Windows and Linux, ensuring Linux is not treated as an afterthought.
- Document any differences in implementation or support between Windows and Linux guest configuration, so users are aware of platform-specific limitations or requirements.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/assign-policy-rest-api.md
...n/articles/governance/policy/assign-policy-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily using PowerShell-specific syntax and escape characters in command examples, mentioning PowerShell and Windows tools before Linux equivalents, and lacking explicit, fully worked Linux/Bash-native examples. While it acknowledges Bash shells like Git Bash, it does not provide clear, parallel Linux command examples or address common Linux environments (e.g., Ubuntu, macOS Terminal) directly.
Recommendations
- Provide explicit, side-by-side command examples for both PowerShell (Windows) and Bash (Linux/macOS), including correct syntax and escape characters for each.
- Mention Linux and macOS terminal environments (e.g., Ubuntu, WSL, macOS Terminal) equally alongside Windows/PowerShell.
- Clarify escape character differences with concrete Bash examples, not just notes about omitting backticks.
- Include installation instructions or links for Bash shells on Linux and macOS, not just Git Bash (which is primarily for Windows).
- Avoid assuming Visual Studio Code as the default terminal; mention alternatives common in Linux/macOS environments.
- Use neutral language when referring to shells and tools, ensuring neither Windows nor PowerShell is presented as the default or primary environment.