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 76-100 of 613 flagged pages
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways. Most queries and examples are generic, but the only OS-specific example provided is for Windows ('WindowsPendingReboot'), with no equivalent Linux example (e.g., 'LinuxPendingReboot'). Additionally, the use of Azure PowerShell is highlighted alongside Azure CLI, but there is no mention of Linux-native scripting or shell environments (such as Bash), nor are Linux-specific tools or patterns referenced. The ordering of examples and the focus on Windows-specific guest configuration assignments further reinforce the bias.
Recommendations
- Add equivalent Linux examples for OS-specific queries, such as pending reboot status for Linux machines (e.g., 'LinuxPendingReboot').
- Include Linux-native command-line usage patterns (e.g., Bash scripts, shell pipelines) where appropriate, alongside Azure CLI and PowerShell.
- Explicitly mention Linux guest configuration assignments and provide example queries for common Linux scenarios.
- Ensure parity in documentation by listing both Windows and Linux examples when discussing OS-specific features.
- Consider adding notes or sections about cross-platform compatibility and limitations for each query or tool.
Create Pull Request
Governance
SWIFT CSP-CSCF v2020 blueprint sample controls
...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 page demonstrates a moderate Windows bias. Controls and audit actions for Windows virtual machines (VMs) are frequently mentioned before their Linux equivalents, and some controls are exclusively described for Windows (e.g., password policies, antimalware deployment). Several audit and deployment examples focus solely on Windows VMs, with Linux coverage present but less detailed or sometimes omitted. Windows-specific tools and settings (such as Microsoft IaaSAntimalware extension, password complexity, and domain join status) are referenced without Linux alternatives or parity in explanation.
Recommendations
- Ensure every Windows-specific control or example has a Linux equivalent, especially for password policies, domain join status, and antimalware solutions.
- Present Linux and Windows examples in parallel, rather than listing Windows first or exclusively.
- Include references to Linux-native tools (e.g., ClamAV, auditd, password complexity enforcement via PAM) where applicable.
- Expand explanations for Linux controls to match the detail given for Windows (e.g., describe how to audit password policies and enforce minimum password length on Linux VMs).
- Review all audit and deployment actions to ensure Linux systems are equally covered, and add missing Linux examples where only Windows is mentioned.
Governance
How to create custom machine configuration package artifacts
...tion/how-to/develop-custom-package/2-create-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by relying exclusively on PowerShell for all examples and tooling, presenting Windows-specific instructions and outputs first, and omitting native Linux command-line alternatives. The packaging and inspection steps use Windows-centric paths and PowerShell cmdlets, with no mention of Linux-native tools or workflows. Linux examples are present but still require PowerShell, and there is no parity for using bash, shell scripts, or Linux-native utilities.
Recommendations
- Provide equivalent Linux-native examples using bash, shell scripts, or common Linux utilities (e.g., zip/unzip, mv, ls) for compiling, packaging, and inspecting configuration artifacts.
- Include Linux file system paths and outputs alongside Windows examples to illustrate cross-platform usage.
- Clarify when PowerShell is required on Linux and offer guidance for users who prefer native Linux tools.
- Present Linux examples before or alongside Windows examples to avoid 'windows_first' bias.
- Document any platform-specific limitations or differences in workflows explicitly, and suggest best practices for Linux environments.
Governance
Protect your resource hierarchy - Azure Governance
...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 detailed Azure PowerShell example for interacting with the REST API but does not offer equivalent examples for Linux-native tools such as Bash, curl, or Azure CLI. The only command-line sample is in PowerShell, which is primarily a Windows tool, and there is no mention of Linux or cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux users from easily following the instructions.
Recommendations
- Add equivalent examples using Bash with curl for REST API calls.
- Provide Azure CLI examples for the same operations, as Azure CLI is cross-platform.
- Explicitly mention that the REST API can be accessed from any OS and provide guidance for Linux/macOS users.
- Ensure that PowerShell examples are not the only command-line samples, and present Linux-friendly options either before or alongside PowerShell.
Governance
How to access custom machine configuration package artifacts
...tion/how-to/develop-custom-package/5-access-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell examples for generating SAS tokens and interacting with Azure Storage. There are no equivalent examples for Linux environments (such as Bash/CLI), nor are cross-platform tools or commands mentioned. The use of PowerShell and Azure PowerShell modules is a Windows-centric approach, and Linux users are not given guidance or parity in the instructions.
Recommendations
- Include equivalent Azure CLI (az) examples for generating SAS tokens and accessing blob storage, which are natively supported on Linux and macOS.
- Add Bash shell script snippets for common operations, ensuring Linux users can follow along without needing PowerShell.
- Explicitly mention cross-platform tools and clarify which commands work on Windows, Linux, and macOS.
- Consider adding a section that discusses platform differences and provides guidance for both Windows and Linux users.
- Review and update documentation to ensure that Linux-first or Linux-parity examples are present wherever possible.
Governance
Details of the Azure Policy attestation structure
...es/governance/policy/concepts/attestation-structure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions PowerShell as a primary management tool for Azure Policy attestations and lists it before Azure CLI, which is cross-platform. There are no Linux-specific examples or references to Linux-native tools or shell usage, and the documentation does not provide parity in examples for Linux users.
Recommendations
- Provide explicit examples using Azure CLI commands, as CLI is cross-platform and preferred by many Linux users.
- Avoid listing PowerShell before Azure CLI unless there is a technical reason; consider listing CLI first or both together.
- Add notes or sections clarifying that all operations can be performed from Linux, macOS, and Windows using Azure CLI.
- Include sample commands for attestation management using Bash or other Linux shells.
- Mention that PowerShell Core is available on Linux, if relevant, but do not assume Windows-only usage.
Governance
Tutorial: Add user assign identities to virtual machines
...ce/policy/tutorials/modify-virtual-machine-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions for using the Azure Portal and Azure PowerShell to add user assigned identities to virtual machines, but does not offer equivalent examples for Linux users, such as Azure CLI or Bash scripts. PowerShell is emphasized as the primary automation tool, which is typically associated with Windows environments. No mention is made of cross-platform alternatives or Linux-native tooling.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, showing how to author, assign, and remediate policy definitions using az policy commands.
- Include Bash script snippets for Linux users where appropriate.
- Explicitly state that both PowerShell and Azure CLI can be used on Windows, macOS, and Linux, and provide links to installation guides for both tools.
- Where possible, present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Review and update the 'Prerequisites' and 'Next steps' sections to reference cross-platform tooling and documentation.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell examples are provided for every query, often with additional explanatory notes specific to PowerShell (such as ConvertTo-Json and depth settings). The sample resource data consistently uses Windows-centric values (e.g., WindowsServer images, osType: Windows, windowsConfiguration), and the workflow patterns (variable assignment, output review) are described in PowerShell terms. While Azure CLI examples are present and some shell scripting is shown, there are no explicit Linux shell examples (e.g., bash, zsh, or other Linux-native tools), nor is there parity in explaining Linux-specific VM properties or images. Windows terminology and tools are mentioned first or exclusively in several places.
Recommendations
- Add explicit Linux shell examples (e.g., bash scripts, use of jq for JSON parsing, etc.) alongside Azure CLI commands.
- Include sample resource data for Linux VMs (e.g., imageReference for Ubuntu or CentOS, osType: Linux, linuxConfiguration properties).
- Balance explanatory notes between PowerShell and Linux shell environments (e.g., discuss output formatting with jq or other Linux tools).
- When describing workflows, provide both PowerShell and bash/zsh variable assignment and output review patterns.
- Avoid using Windows-centric terminology or examples exclusively; alternate or combine with Linux equivalents.
- Ensure that any advanced samples or linked resources also include Linux-focused scenarios.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments and is presented alongside CLI in every example. There are no explicit Linux shell (bash, sh) or scripting examples, nor are there references to Linux-specific tools or usage patterns. The ordering of examples does not explicitly favor Windows, but the inclusion of PowerShell in parity with CLI may reinforce a Windows-centric perspective, especially for users seeking Linux-native workflows.
Recommendations
- Add explicit bash/sh examples for running Azure CLI commands on Linux/macOS, including sample shell scripts or command-line usage.
- Clarify that Azure CLI is cross-platform and can be used natively on Linux/macOS, possibly with installation or usage notes for those platforms.
- Consider including links or references to Linux-specific documentation or troubleshooting guides.
- If PowerShell is included, note that PowerShell Core is available cross-platform, but provide guidance for users who prefer native Linux shells.
- Review example ordering to ensure CLI (cross-platform) is presented before PowerShell (Windows-centric) to avoid implicit Windows-first bias.
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 (e.g., Bash with REST API or jq) or references to Linux-native tools suggests a mild Windows bias. Additionally, PowerShell is presented as a primary tab, reinforcing its prominence. There are no explicit Linux examples or instructions, and no mention of Linux-specific usage patterns.
Recommendations
- Add explicit Bash shell examples using az CLI and/or REST API calls, demonstrating usage in Linux environments.
- Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users, such as installation steps or environment notes.
- Consider including examples using Linux-native tools (e.g., curl, jq) for querying the Azure Resource Graph API.
- Balance tab order or presentation so that PowerShell is not always shown before Linux-friendly options.
- Mention PowerShell Core's cross-platform support if PowerShell is included, to reduce perception of Windows-only bias.
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 explicit mention of PowerShell-specific parameters (e.g., -UseTenantScope) indicate a Windows bias. Additionally, the reference to 'Azure PowerShell' is given equal prominence to Azure CLI, and there are no examples using Linux-native shells or tools (e.g., bash scripting, piping, jq). The documentation does not mention or demonstrate Linux-specific patterns, nor does it clarify cross-platform compatibility for PowerShell.
Recommendations
- Add explicit notes clarifying that Azure CLI commands work identically on Linux, macOS, and Windows.
- Provide Linux shell (bash) examples where relevant, such as using environment variables, piping, or text processing.
- Clarify whether Azure PowerShell commands are fully supported on Linux/macOS and provide installation or usage notes if so.
- Consider including examples using other cross-platform scripting languages (e.g., Python with Azure SDK) for broader parity.
- Avoid presenting PowerShell as the default or primary scripting option unless cross-platform support is clearly stated.
Governance
Manage Azure Service Group membership at scale
...rticles/governance/service-groups/manage-membership.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias in its automation and scripting examples. The only provided script for bulk membership management uses PowerShell, which is native to Windows and not universally available or preferred on Linux. There are no Bash, Azure CLI, or cross-platform scripting examples. The walkthrough and sample outputs are all PowerShell-centric, and there is no mention of Linux-specific tools or guidance for users on non-Windows platforms.
Recommendations
- Add equivalent Bash or Azure CLI examples for bulk membership management, especially for scenarios currently covered only with PowerShell.
- Include guidance on running the automation from Linux/macOS environments, such as using Azure CLI, REST API calls via curl, or Python scripts.
- Explicitly state cross-platform options and limitations for each automation scenario.
- Where PowerShell is used, note that PowerShell Core is available on Linux/macOS and provide installation instructions or alternatives.
- Ensure that sample outputs and walkthroughs include examples from Linux shells (e.g., Bash) and Azure CLI, not just PowerShell.
Governance
Overview of Azure Resource Graph
...ob/main/articles/governance/resource-graph/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Azure PowerShell before or alongside Azure CLI, referencing Power BI (a Windows-centric tool), and lacking explicit Linux-specific examples or tooling. While Azure CLI is referenced, there is no mention of Linux shell usage, nor are Linux-specific patterns or tools highlighted. REST API is presented neutrally, but the overall pattern privileges Windows/PowerShell workflows and tools.
Recommendations
- Add explicit Linux shell (bash/zsh) examples for running Resource Graph queries using Azure CLI.
- Mention and link to Linux-native tools or workflows (e.g., jq for parsing REST API output, shell scripting for automation).
- Ensure Azure CLI examples are presented before or alongside PowerShell to avoid Windows-first ordering.
- Reference cross-platform data visualization alternatives to Power BI, such as Grafana, and provide integration examples.
- Include a section or note clarifying that all CLI and REST API instructions work on Linux, macOS, and Windows equally.
Governance
Understand the deployment sequence order
...les/governance/blueprints/concepts/sequencing-order.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing PowerShell as the primary CLI tool for creating blueprint artifacts, and mentioning it before REST API alternatives. No Linux-specific tools (such as Azure CLI or Bash) are referenced, and all command-line guidance is focused on PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add equivalent Azure CLI (az blueprint) examples for artifact creation and management, alongside PowerShell.
- Explicitly mention that REST API and Azure CLI can be used from any platform, including Linux and macOS.
- Provide Bash script examples for common blueprint operations to improve accessibility for Linux users.
- Reorder references to command-line tools so that cross-platform options (Azure CLI, REST API) are mentioned before or alongside PowerShell.
- Include a note clarifying that all operations can be performed from Linux, macOS, and Windows, and link to platform-specific setup guides.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for Azure Blueprints shows evidence of Windows bias. In the 'Next steps' section, PowerShell (a Windows-centric tool) is listed as the only command-line example, with no mention of Bash, Azure CLI, or Linux shell equivalents. The ordering also places PowerShell before REST API, and there are no Linux-specific or cross-platform command-line examples provided. Throughout the page, there is no reference to Linux tooling or patterns, and the only scripting example is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add Azure CLI examples for blueprint creation and management, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash shell examples where applicable, especially for scripting or automation tasks.
- Reorder the 'Next steps' section to list cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
- Explicitly mention that Azure Blueprints can be managed from Linux, macOS, and Windows environments, and provide links to relevant documentation.
- Ensure parity in examples and instructions for both Windows and Linux users throughout the documentation.
Governance
Canada Federal PBMM blueprint sample
...s/governance/blueprints/samples/canada-federal-pbmm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides examples and parameters for both Windows and Linux VMs, but Windows-specific concepts (such as the 'Administrators group' and 'List of users that should be included in Windows VM Administrators group') are mentioned explicitly, while equivalent Linux concepts (such as sudoers or admin groups) are not. Additionally, the artifact parameters table lists Windows VM-related parameters before Linux VM parameters in some cases, and only Windows administrator group membership is described with examples. There are no Linux-specific user/group management examples or references to Linux admin patterns/tools.
Recommendations
- Add equivalent Linux user/group management parameters and examples, such as specifying sudoers or admin groups for Linux VMs.
- Provide Linux-specific examples alongside Windows examples, especially for administrative access and configuration.
- Ensure that Linux and Windows examples are presented with equal prominence and detail.
- Reference Linux tools and patterns (e.g., /etc/sudoers, groupadd, usermod) where relevant.
- Consider listing Linux and Windows parameters together or alternating their order to avoid implicit prioritization.
Governance
Quickstart: Create a blueprint with REST API
...les/governance/blueprints/create-blueprint-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for making REST API calls, recommending PowerShell as the primary tool, and omitting equivalent Linux or cross-platform command-line examples (such as curl or bash). Windows tools and patterns are mentioned first and exclusively, with no guidance for users on Linux or macOS systems.
Recommendations
- Add equivalent Linux/macOS examples using curl, httpie, or bash scripts for REST API calls.
- Mention cross-platform tools (e.g., Azure CLI, ARMClient, curl) before or alongside PowerShell.
- Provide authentication instructions for REST API calls using Azure CLI or other cross-platform methods.
- Clarify that PowerShell is one option among several, and link to resources for Linux/macOS users.
- Ensure all code samples are available in both PowerShell and bash/curl formats.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Blueprints functions demonstrates Windows bias primarily through its references to Azure PowerShell and REST API as the main management interfaces for Blueprints-as-code. There is no mention of Azure CLI or Linux-native tooling, and PowerShell is referenced before REST API. No Linux-specific examples or parity guidance is provided, and the only management example is PowerShell-centric.
Recommendations
- Add explicit examples and instructions for managing Azure Blueprints using Azure CLI, which is cross-platform and widely used on Linux.
- Mention Azure CLI alongside PowerShell and REST API wherever management interfaces are discussed, including in the Blueprints-as-code section.
- Provide sample commands for both PowerShell and Azure CLI when demonstrating artifact management, assignment, or querying.
- Review and update terminology to avoid implying PowerShell is the default or preferred tool, and clarify that all major Azure management interfaces are supported on Windows, Linux, and macOS.
- Include troubleshooting and lifecycle guidance that covers both PowerShell and CLI workflows.
Governance
Australian Government ISM PROTECTED blueprint sample controls
...ce/blueprints/samples/ism-protected/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas. Many audit and security controls are described only for Windows VMs (e.g., auditing Administrators group membership, security settings, and secure communication protocols), with no equivalent examples or instructions for Linux VMs. Windows-specific tools and extensions, such as the Microsoft IaaSAntimalware extension, are mentioned without Linux alternatives. In sections where both Windows and Linux could be relevant, Windows is often listed first or exclusively, while Linux coverage is limited or absent.
Recommendations
- Provide Linux-specific examples and controls wherever Windows VM controls are described, such as auditing sudoers or privileged groups, password policies, and secure communication protocols.
- Mention and document Linux-compatible antimalware and endpoint protection solutions alongside Windows tools.
- Ensure that audit prerequisites and instructions are available for both Windows and Linux VMs, including guidance for common Linux distributions.
- Where controls reference Windows-specific configuration (e.g., 'Security Settings - Account Policies'), add equivalent Linux configuration guidance (e.g., PAM, passwd, sudoers).
- Review ordering and presentation to avoid listing Windows controls first or exclusively when both platforms are supported.
Governance
ISO 27001 Shared Services blueprint sample controls
.../blueprints/samples/iso27001-shared/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows VM password policies are described in detail, with multiple audit controls and explicit settings listed, while Linux VM password and authentication controls are mentioned only briefly and lack equivalent detail. Windows-specific audit examples are provided (e.g., password complexity, password age, password history), but Linux equivalents (such as password aging, complexity, and shadow file permissions) are not covered. Additionally, Windows VM controls are presented before Linux VM controls in relevant sections, and Windows terminology/tools are referenced without Linux parity.
Recommendations
- Add equivalent Linux VM password management audit controls, such as checks for password complexity, aging, and history (e.g., /etc/login.defs, PAM configuration).
- Provide explicit Linux examples for password and authentication controls, similar to the Windows examples (e.g., minimum password length, password reuse restrictions).
- Ensure that both Windows and Linux VM controls are presented with equal detail and prominence in all relevant sections.
- Reference Linux tools and configuration patterns (e.g., passwd, chage, PAM modules) alongside Windows tools.
- Where audit controls are OS-specific, clearly label them and provide parity for both platforms.
Governance
Deploy Australian Government ISM PROTECTED blueprint sample
.../governance/blueprints/samples/ism-protected/deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. Windows-specific concepts (such as 'Windows VM Administrators group', 'Microsoft IaaSAntimalware extension', and password complexity requirements tailored to Windows) are mentioned explicitly, while their Linux equivalents are either absent or less detailed. Windows-related parameters and examples are listed before Linux ones in several places. There are no examples or guidance for Linux-specific administrative groups or security extensions, and no PowerShell or CLI examples are provided for either platform.
Recommendations
- Add equivalent Linux administrative group parameters and examples (e.g., guidance on managing sudoers or root group membership).
- Provide parity in security extension deployment (e.g., mention and link to Linux antimalware or endpoint protection solutions if available).
- Ensure that Linux-related parameters and examples are presented alongside Windows ones, not after or omitted.
- Clarify password policy applicability for Linux VMs, or note differences in enforcement and configuration.
- Where Windows-specific tooling or terminology is used, add Linux equivalents or note platform differences.
- Consider including CLI examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) for blueprint deployment and assignment steps.
Governance
ISO 27001 ASE/SQL workload blueprint sample controls
...s/samples/iso27001-ase-sql-workload/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Windows VM password policies are audited in detail, with multiple controls and explicit requirements listed, while Linux VM password policies are only briefly mentioned and lack equivalent detail. Windows-specific audit controls (e.g., password complexity, password age, password history) are present, but there are no corresponding Linux examples or controls for these settings. Additionally, Windows VM audit results are listed before Linux VM audit results, and Windows tools/patterns (such as password management) are referenced without Linux equivalents.
Recommendations
- Add equivalent audit controls and examples for Linux VM password policies (e.g., minimum password length, password complexity, password age, password history).
- Provide parity in documentation by listing Linux VM controls and examples alongside Windows VM controls, not only after or less prominently.
- Reference Linux tools and configuration patterns (such as PAM, /etc/login.defs, chage, passwd) where appropriate for password management and auditing.
- Ensure that audit results and policy definitions for Linux VMs are as detailed and comprehensive as those for Windows VMs.
- Consider including cross-platform examples and guidance for all relevant controls, not just Windows-centric ones.
Governance
Deploy ISO 27001 Shared Services blueprint sample
...overnance/blueprints/samples/iso27001-shared/deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas. Windows operating systems and related artifacts (e.g., Windows VM, Windows VMSS, Active Directory Domain Services) are mentioned before or more prominently than Linux equivalents. The default value for the jumpbox operating system is set to Windows, and there is a strong focus on Windows-centric infrastructure components (Active Directory, domain admin accounts, etc.). While some Linux-specific artifacts are present (e.g., Log Analytics Agent for Linux VMs), there are no Linux-first examples or guidance, and Linux options are generally presented as secondary or optional.
Recommendations
- Provide Linux-first examples and guidance where applicable, such as setting the default jumpbox OS to Linux or offering parallel instructions for Linux-based deployments.
- Ensure that Linux VM and VMSS artifacts are described with equal detail and prominence as their Windows counterparts.
- Include explicit instructions or examples for configuring Linux authentication and management (e.g., SSH keys, Linux domain join alternatives) alongside Windows/Active Directory guidance.
- Review parameter tables and deployment steps to avoid defaulting to Windows unless required by the blueprint's compliance needs.
- Where Active Directory is referenced, mention alternatives for Linux environments (e.g., Azure AD, LDAP, or other identity solutions) if possible.
Governance
Deploy SWIFT CSP-CSCF v2020 blueprint sample
...les/governance/blueprints/samples/swift-2020/deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-related artifacts and parameters (e.g., Windows VM Administrators group, domain join for Windows VMs) are described in detail, while Linux equivalents are less prominent or missing. Windows VM examples and terminology appear before Linux ones in the artifact parameters table. There are no Linux-specific administrative examples (e.g., Linux user/group management, domain join) provided, and no CLI or shell examples for Linux users. Windows tools and patterns (such as domain join and Administrators group) are mentioned exclusively, with no Linux alternatives or parity.
Recommendations
- Add equivalent Linux administrative parameters and examples, such as specifying Linux users/groups or domain join options for Linux VMs.
- Ensure Linux-related artifacts and instructions are presented with equal prominence and detail as Windows ones.
- Provide Linux CLI or shell examples for blueprint deployment and management, alongside any PowerShell or Windows GUI instructions.
- Clarify when instructions or parameters are Windows-specific and offer Linux alternatives where possible.
- Review the artifact parameters table to ensure Linux artifacts are described as thoroughly as Windows ones, and consider listing Linux options before or alongside Windows options to avoid ordering bias.
Governance
Discover And Assign Built In Machine Configuration Policies
...chine-configuration/how-to/assign-built-in-policies.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page presents both Windows and Linux support in its introduction and policy discovery steps, but the only detailed assignment example is for a Windows-specific policy ('Audit Windows Time Zone'). No Linux policy assignment example is provided. The programmatic section lists PowerShell and CLI options, but the CLI examples are not explicitly Linux-focused, and PowerShell (a Windows-centric tool) is mentioned prominently. This creates a subtle bias toward Windows usage and scenarios.
Recommendations
- Add a step-by-step example for assigning a Linux-specific Machine Configuration policy (e.g., 'Audit Linux machines that have the specified applications installed'), including screenshots and parameter details.
- Ensure parity in example depth and clarity for both Windows and Linux policies.
- Highlight Azure CLI usage for Linux scenarios, possibly with explicit Linux shell command examples.
- Mention Linux-native tools or automation patterns (such as Bash scripts or Ansible) where relevant.
- Balance PowerShell references with Linux-friendly alternatives, clarifying cross-platform support.