Governance

496
Total Pages
410
Linux-Friendly Pages
86
Pages with Bias
17.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

186 issues found
Showing 1-25 of 186 flagged pages
Governance How to create custom machine configuration policy definitions ...chine-configuration/how-to/create-policy-definition.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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 syntax and Windows-centric paths (e.g., C:\Local\Path\To\Package), with no Linux/macOS shell or path examples. The 'Platform' parameter is always set to 'Windows' in examples, and Windows services are referenced in parameter examples. There is no guidance or code for Linux-specific scenarios, tools, or file paths, despite the product supporting Linux. Windows tools and patterns are mentioned exclusively and first throughout.
Recommendations
  • Provide equivalent Linux/macOS examples using Bash, Azure CLI, or cross-platform PowerShell, including Linux file paths (e.g., /home/user/package.zip).
  • Show usage of the 'Platform' parameter set to 'Linux' in example code blocks.
  • Include Linux service auditing examples (e.g., systemd services) in parameter definitions.
  • Clarify any OS-specific requirements or differences in the workflow, especially for package paths and managed identity usage.
  • Reference Linux/macOS setup instructions and tools where appropriate.
GitHub Create Pull Request
Governance How to create custom machine configuration policy definitions ...chine-configuration/how-to/create-policy-definition.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell-based workflows and Windows-centric examples. All code samples use PowerShell syntax, and file paths are Windows-style (e.g., C:\Local\Path\To\Package). The 'Platform' parameter is always set to 'Windows' in examples, with no Linux-specific examples or file paths. Windows services are referenced in parameter examples, and there is no mention of Linux equivalents (e.g., systemd services). The documentation does not provide Linux/macOS shell alternatives or clarify cross-platform differences, making it challenging for non-Windows users to follow the instructions.
Recommendations
  • Provide Linux/macOS-specific examples alongside Windows, including bash/CLI equivalents for all PowerShell commands.
  • Show how to set up the authoring environment and required modules on Linux/macOS, including installation steps and file path conventions.
  • Include examples where the 'Platform' parameter is set to 'Linux', and demonstrate policy definitions for Linux services (e.g., systemd units).
  • Clarify any differences in managed identity usage, file paths, and package handling between Windows and Linux.
  • Reference Linux tools and patterns where relevant, such as az CLI, and provide links to cross-platform documentation.
GitHub Create Pull Request
Governance Learn Azure Policy for Kubernetes ...es/governance/policy/concepts/policy-for-kubernetes.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Azure portal, Azure CLI, Azure PowerShell) are referenced throughout, with Azure portal instructions often presented first. Azure PowerShell is mentioned as an alternative to Azure CLI for resource provider registration, but no Linux-specific shell or package manager instructions (e.g., apt, yum, Homebrew) are provided for installing Azure CLI. The documentation does not provide explicit Linux/macOS installation or troubleshooting guidance, nor does it mention platform-specific differences for commands or prerequisites. However, most operational commands (kubectl, helm) are cross-platform, and the add-on itself only supports Linux node pools, which is clearly stated.
Recommendations
  • Add explicit instructions for installing Azure CLI on Linux and macOS, including package manager commands (apt, yum, Homebrew).
  • When listing command-line instructions, clarify platform compatibility and provide any necessary platform-specific notes (e.g., path differences, shell syntax).
  • When presenting Azure portal instructions, alternate or parallelize with CLI instructions, and clarify that both are cross-platform.
  • If Azure PowerShell is mentioned, also mention Bash or other Linux-native shells where appropriate.
  • Include troubleshooting steps or notes for Linux/macOS users, especially for common issues like permissions, networking, or environment setup.
  • Make clear that all kubectl and helm commands are cross-platform and provide any platform-specific caveats if relevant.
GitHub Create Pull Request
Governance Planning a change from Desired State Configuration extension to machine configuration ...onfiguration/whats-new/migrating-from-dsc-extension.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It focuses almost exclusively on PowerShell DSC (Desired State Configuration), references Windows PowerShell versions, and provides examples and migration steps that assume Windows-centric tooling and workflows. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for users managing Linux VMs with DSC or machine configuration. The use of PowerShell cmdlets and references to Windows-specific services (like Local Configuration Manager) further reinforce the bias.
Recommendations
  • Add explicit guidance and examples for Linux VMs, including how to check for DSC extension presence and migrate configurations.
  • Clarify whether machine configuration supports Linux and, if so, provide Linux-specific migration steps and tooling.
  • Include references to Linux DSC resources and modules, and describe any differences in workflow or compatibility.
  • Provide sample commands or scripts for Linux environments (e.g., Bash, Azure CLI) where appropriate.
  • Mention any limitations or considerations for non-Windows platforms in the migration process.
GitHub Create Pull Request
Governance Details of the initiative definition structure ...nce/policy/concepts/initiative-definition-structure.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is largely platform-neutral, focusing on JSON structure and Azure concepts. However, there is a notable Windows bias in the 'strongType' section, where the only tool mentioned for resource type validation is 'Get-AzResourceProvider', a PowerShell cmdlet. No Linux/macOS equivalent (such as Azure CLI) is referenced, and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
  • Include Azure CLI equivalents (e.g., 'az provider show' or 'az provider list') alongside PowerShell examples for resource type validation.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these tasks, and provide sample commands for each.
  • Where possible, link to cross-platform documentation or note platform compatibility for tools.
  • Avoid listing Windows-specific tools first; present cross-platform options equally.
GitHub Create Pull Request
Governance Get policy compliance data ...ticles/governance/policy/how-to/get-compliance-data.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, REST API, Azure PowerShell, Visual Studio Code extension, and GitHub Actions. However, Azure PowerShell examples are given equal or greater prominence than Azure CLI, and PowerShell-specific features (like jobs) are described in detail. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples for Bash, zsh, or other common Linux/macOS environments. The documentation assumes familiarity with PowerShell and Windows-centric tooling, and does not clarify cross-platform compatibility for PowerShell commands or provide Linux/macOS-specific guidance.
Recommendations
  • Add explicit Bash/zsh examples for command-line operations, especially for REST API calls using curl or similar tools.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
  • Add a section or note about running Azure PowerShell on Linux/macOS, including installation and usage differences.
  • Balance the order of examples, presenting Azure CLI before PowerShell, or interleave them to avoid Windows-first perception.
  • Mention and demonstrate use of native Linux/macOS tools (e.g., curl, jq) for REST API interactions.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment setup).
GitHub Create Pull Request
Governance Deploy ISO 27001 Shared Services blueprint sample ...overnance/blueprints/samples/iso27001-shared/deploy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it does mention Linux in some artifact parameters (e.g., deploying Log Analytics Agent for Linux VMs), Windows is often the default or only example given (e.g., Jumpbox Operating System defaults to Windows, Active Directory Domain Services is Windows-centric, and no Linux/macOS equivalents or instructions are provided for those components). There are no Linux/macOS-specific deployment instructions, and Windows terminology (Active Directory, domain admin, etc.) is used exclusively for identity and management tasks.
Recommendations
  • Provide explicit Linux/macOS deployment examples or instructions for jumpboxes and identity management (e.g., using Linux-based bastion hosts, LDAP, or Azure AD-only scenarios).
  • Include Linux/macOS equivalents for Windows-centric artifacts, such as alternatives to Active Directory Domain Services.
  • When listing artifact parameters, avoid defaulting to Windows unless necessary; offer parity by showing both Windows and Linux options.
  • Clarify which steps or artifacts are platform-agnostic and which are Windows-specific, and provide guidance for Linux/macOS users where appropriate.
GitHub Create Pull Request
Governance How to develop a custom machine configuration package ...onfiguration/how-to/develop-custom-package/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by centering PowerShell and its GuestConfiguration module as the primary tooling for authoring and validating machine configuration packages. The only example video is PowerShell-based, and there are no Linux-specific command-line examples or references to Linux-native tools or workflows. While Linux is mentioned as a supported platform, practical guidance and examples for Linux users are missing.
Recommendations
  • Include Linux-specific examples using Bash, shell scripts, or native Linux tools for authoring and validating machine configuration packages.
  • Provide a parallel video or walkthrough demonstrating the process on a Linux system.
  • Clarify any differences in workflow or tooling for Linux users, especially where PowerShell is not the default shell.
  • Explicitly mention how Linux users can install and use the GuestConfiguration module, including any prerequisites or alternative approaches.
  • Add notes or sections for macOS users, even if only to clarify current limitations.
GitHub Create Pull Request
Governance How to access custom machine configuration package artifacts ...tion/how-to/develop-custom-package/5-access-package.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell examples for generating SAS tokens and interacting with Azure Storage, which are Windows-centric. There are no equivalent examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API). The use of PowerShell-specific cmdlets and lack of cross-platform instructions may create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for generating SAS tokens and accessing blob storage, which work natively on Linux/macOS.
  • Include Bash or REST API snippets for key operations, ensuring platform neutrality.
  • Explicitly state that PowerShell examples can be run cross-platform using PowerShell Core, or clarify any limitations.
  • Reorder examples or provide parallel instructions for both Windows and Linux/macOS users.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using the Azure Rest API ...-configuration/how-to/assign-configuration/rest-api.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page shows a mild Windows bias by referencing the Windows PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning equivalent Linux/macOS CLI alternatives. While the main example uses curl (cross-platform), the authentication step is Windows-centric, potentially creating friction for non-Windows users.
Recommendations
  • Include instructions for obtaining an Azure access token using Azure CLI (az account get-access-token), which works on Linux/macOS as well as Windows.
  • Add explicit notes or examples for Linux/macOS users, especially for authentication steps.
  • Reference cross-platform tools first (e.g., Azure CLI) before platform-specific ones like PowerShell.
  • Clarify that curl examples are cross-platform and provide any necessary OS-specific usage notes.
GitHub Create Pull Request
Governance Discover And Assign Built In Machine Configuration Policies ...chine-configuration/how-to/assign-built-in-policies.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Example Heavy Missing Linux Example
Summary
The documentation describes Azure Machine Configuration policies for both Windows and Linux, but the main example provided is exclusively for Windows ('Audit Windows Time Zone'). No Linux-specific example is given, and the step-by-step assignment walkthrough is Windows-centric. While Linux policies are mentioned in lists and notes, they are not illustrated in detail, which may create friction for Linux users seeking parity in guidance.
Recommendations
  • Add a parallel example for a Linux built-in policy (e.g., 'Audit Linux machines that have the specified applications installed'), including step-by-step assignment instructions and screenshots.
  • Alternate the order of examples or provide both Windows and Linux examples side-by-side to avoid Windows-first bias.
  • Ensure that references to prerequisites, parameters, and compliance reporting include Linux-specific details and screenshots.
  • Explicitly mention any differences in assignment or parameterization for Linux policies.
GitHub Create Pull Request
Governance How to test machine configuration package artifacts ...ration/how-to/develop-custom-package/3-test-package.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily PowerShell-centric, with all examples using PowerShell cmdlets. Windows-specific tools (PSExec) are mentioned explicitly, and Windows instructions are consistently presented before Linux equivalents. While Linux is supported, macOS is explicitly excluded, and no Linux-native shell or tool examples are provided.
Recommendations
  • Provide Linux-native shell examples (e.g., Bash scripts) where possible, not just PowerShell via pwsh.
  • Present Linux instructions before or alongside Windows instructions, rather than always after.
  • Mention Linux-native tools for privilege elevation (e.g., 'su', 'pkexec') in addition to 'sudo'.
  • Clarify PowerShell requirements for Linux users, and suggest installation steps or alternatives.
  • Explicitly state limitations for macOS and offer guidance or workarounds if possible.
GitHub Create Pull Request
Governance Protect your resource hierarchy - Azure Governance ...management-groups/how-to/protect-resource-hierarchy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed Azure PowerShell sample for interacting with the REST API, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, curl, or Azure CLI). The only command-line example is in PowerShell, which is primarily a Windows tool, and there is no mention of Linux-native tools or patterns.
Recommendations
  • Add equivalent Bash/curl and Azure CLI examples for REST API calls to ensure Linux/macOS users have clear guidance.
  • Explicitly mention that PowerShell Core is cross-platform, but also provide native Linux/macOS command samples.
  • Reorder or parallelize command-line examples so Linux/macOS and Windows users are equally represented.
GitHub Create Pull Request
Governance Details of the policy definition structure parameters ...nce/policy/concepts/definition-structure-parameters.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references the Windows PowerShell cmdlet Get-AzResourceProvider as the method to determine valid resource types for the strongType property, without mentioning an equivalent Azure CLI or REST API approach. No Linux/macOS-friendly command-line examples are provided, and the only tooling guidance is Windows-centric.
Recommendations
  • Add Azure CLI examples (e.g., 'az provider list') alongside PowerShell for determining resource provider types.
  • Mention REST API alternatives for cross-platform compatibility.
  • Present CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly state that PowerShell commands can be run on Linux/macOS if applicable, or provide installation guidance.
GitHub Create Pull Request
Governance Remediate non-compliant resources ...ticles/governance/policy/how-to/remediate-resources.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given in detail and appear before Azure CLI examples in most sections. The PowerShell instructions use Windows-centric terminology and commands, while Azure CLI examples (which are cross-platform) are present but less detailed and sometimes referenced as links rather than shown inline. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of platform-specific considerations for Linux/macOS users. The use of PowerShell as a primary scripting language may create friction for users on non-Windows platforms.
Recommendations
  • Provide Bash shell examples alongside PowerShell, especially for Azure CLI commands.
  • Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples.
  • Explicitly mention that Azure CLI works cross-platform and highlight any platform-specific considerations.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
  • Add notes or sections for Linux/macOS users, clarifying any differences in workflow or prerequisites.
GitHub Create Pull Request
Governance List of built-in packages for guest configuration ...rticles/governance/policy/samples/built-in-packages.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. The introductory text and table focus heavily on Windows policies, PowerShell DSC modules, and Windows-specific tooling. Windows policies and modules are listed first and in greater quantity, with only a few Linux-related entries (often marked as 'Preview'). The guidance for understanding configurations refers users to PowerShell scripts, which are not natively applicable to Linux. There is a lack of parity in examples, explanations, and tooling for Linux guest configuration.
Recommendations
  • Add equivalent Linux examples and modules for each Windows policy where possible.
  • Provide clear guidance on how Linux guest configuration is implemented, including references to Linux-native tools and scripts.
  • Balance the documentation by listing Linux and Windows policies together, or in alternating order, rather than Windows-first.
  • Clarify which modules and configurations are cross-platform and which are Windows-only.
  • Include explanations or links for Linux-specific configuration mechanisms (e.g., shell scripts, Ansible, or other Linux-native DSC equivalents).
GitHub Create Pull Request
Governance Run Azure Resource Graph query using REST API ...cles/governance/resource-graph/first-query-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows a moderate Windows bias: PowerShell is mentioned first in prerequisites and examples, and Visual Studio Code is recommended as the terminal environment. While Bash examples are provided, Windows tools and patterns (PowerShell, VS Code, Git Bash) are emphasized or listed before Linux-native equivalents. No Linux-specific shell or editor is recommended, and the overall flow assumes a Windows-centric workflow.
Recommendations
  • List Bash and Linux-native shells (e.g., GNOME Terminal, xterm) equally or before PowerShell in prerequisites.
  • Recommend Linux-native editors (e.g., Vim, Nano, Gedit) alongside Visual Studio Code.
  • Provide explicit instructions for running commands in standard Linux/macOS terminal environments, not just Git Bash (which is primarily for Windows).
  • Ensure example tabs alternate or start with Bash/Linux, not always PowerShell first.
  • Clarify that Azure CLI and REST API usage is cross-platform and provide links to Linux/macOS installation guides.
GitHub Create Pull Request
Governance Troubleshoot common errors for Azure Resource Graph ...cles/governance/resource-graph/troubleshoot/general.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell script for batching subscription queries, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI or REST API usage). The only concrete code sample is in PowerShell, and the solution section refers specifically to using the Subscription parameter in PowerShell, omitting guidance for non-Windows platforms. This creates friction for users on Linux or macOS who may not use PowerShell.
Recommendations
  • Add equivalent Azure CLI examples for batching subscription queries.
  • Provide REST API sample requests for the same scenario.
  • Explicitly mention cross-platform alternatives and tools for each scenario.
  • Ensure code samples are balanced between PowerShell and CLI/REST, or presented together.
GitHub Create Pull Request
Governance Quickstart: Create a blueprint with REST API ...les/governance/blueprints/create-blueprint-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides interactive PowerShell examples and recommends PowerShell as the primary tool for making REST API calls, without offering equivalent examples or guidance for Linux/macOS users (e.g., Bash, curl, or other cross-platform tools). Windows-centric tools and patterns are mentioned first and exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent examples using Bash and curl for authentication and REST API calls.
  • Mention cross-platform tools (e.g., Azure CLI, curl, httpie, Postman) alongside PowerShell.
  • Reorder or parallelize example sections so Linux/macOS and Windows users see relevant instructions simultaneously.
  • Clarify which steps are platform-agnostic and which require OS-specific tooling.
GitHub Create Pull Request
Governance Overview of Azure Blueprints ...s/blob/main/articles/governance/blueprints/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page lists PowerShell as a primary method for creating Azure Blueprints, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash). The 'Next steps' section presents PowerShell before REST API, and does not reference cross-platform tools or provide Linux/macOS-specific guidance. There are no explicit Windows-only tools, but the example ordering and lack of Linux parity create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for blueprint creation and management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available cross-platform, or clarify any Windows-specific requirements.
  • Reorder 'Next steps' to present cross-platform options (Portal, Azure CLI, REST API) before PowerShell.
  • Include notes or links for Bash scripting or automation on Linux/macOS.
  • Ensure future documentation sections provide parity in examples for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Governance Canada Federal PBMM blueprint sample ...s/governance/blueprints/samples/canada-federal-pbmm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples and parameters for both Windows and Linux VM deployments, but Windows-specific concepts (such as the Administrators group and user lists for Windows VMs) are described in more detail, with explicit examples. The artifact parameters table lists Windows VM parameters before Linux VM parameters in some cases, and Windows-centric administrative patterns are referenced without Linux equivalents. There are no Linux/macOS-specific command-line or administrative group examples, and the documentation does not mention Linux/macOS tools or patterns for managing blueprints.
Recommendations
  • Provide equivalent Linux administrative group/user examples (e.g., referencing sudoers or wheel group) where Windows Administrators group is discussed.
  • Ensure Linux VM examples are presented with equal detail and prominence as Windows VM examples.
  • Include Linux/macOS command-line or automation options for blueprint management, if available.
  • Alternate the order of Windows and Linux examples in tables and descriptions to avoid Windows-first bias.
  • Reference Linux/macOS-specific documentation or tools where relevant.
GitHub Create Pull Request
Governance Deploy Australian Government ISM PROTECTED blueprint sample .../governance/blueprints/samples/ism-protected/deploy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral in its instructions for deploying the ISM PROTECTED blueprint sample, focusing on Azure portal UI steps. However, there is a notable Windows bias in the artifact parameters table, which includes several parameters specific to Windows VM administration (e.g., users included/excluded from Windows VM Administrators group, Microsoft IaaSAntimalware extension for Windows servers, password policy parameters that match Windows conventions). These Windows-specific parameters are listed before or alongside Linux equivalents, but there are more Windows-specific controls and examples than Linux ones. No PowerShell or CLI examples are given, so the bias is moderate and mostly in the context of VM management and security controls.
Recommendations
  • Add equivalent Linux-focused parameters and controls where possible, such as Linux admin group management, Linux-specific antimalware or endpoint protection extensions, and Linux password policy controls.
  • Ensure that Linux VM management examples and parameters are presented with equal prominence and detail as Windows ones.
  • Where password or admin group controls are described, clarify whether they apply to Windows, Linux, or both, and provide Linux-specific guidance if relevant.
  • Consider including CLI or script-based deployment examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments to improve parity.
GitHub Create Pull Request
Governance Azure Blueprints functions ...governance/blueprints/reference/blueprint-functions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure PowerShell as a management tool for Blueprints, but does not mention or provide examples for Azure CLI or other cross-platform tools. There are no explicit Linux/macOS examples or guidance, and the only tooling mentioned is PowerShell, which is traditionally associated with Windows (though now available cross-platform). This may create friction for Linux/macOS users who prefer Azure CLI or REST API directly.
Recommendations
  • Explicitly mention Azure CLI as a supported tool for managing Blueprints, alongside PowerShell.
  • Provide example commands for both Azure PowerShell and Azure CLI where management actions are described.
  • Clarify that REST API and PowerShell are both cross-platform, and link to relevant Azure CLI documentation.
  • Add a note or section about managing Blueprints from Linux/macOS environments, including setup instructions if needed.
GitHub Create Pull Request
Governance Australian Government ISM PROTECTED blueprint sample controls ...ce/blueprints/samples/ism-protected/control-mapping.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Many control mappings and audit recommendations explicitly reference Windows VMs, Windows web servers, and Windows-specific extensions (e.g., Microsoft IaaSAntimalware). Linux equivalents are only mentioned in a few authentication-related controls, and there are no Linux-specific examples or guidance for several critical areas such as antivirus, application allow-listing, or secure communication protocols. Windows tools and terminology are used exclusively in several sections, and Windows examples are presented first or solely.
Recommendations
  • Provide equivalent Linux guidance and examples for all controls that currently mention only Windows (e.g., auditing privileged access, antivirus deployment, secure communication protocols).
  • Include references to Linux-compatible security solutions (e.g., antimalware, endpoint protection, allow-listing) alongside Windows tools.
  • Where audit results or prerequisites are described for Windows VMs, add parallel instructions for Linux VMs (e.g., how to audit sudoers, SSH configuration, Linux group memberships).
  • Ensure that recommendations and policy mappings for VM extensions, endpoint protection, and logging include both Windows and Linux options.
  • Avoid presenting Windows examples or tools first unless there is a clear technical reason; strive for parity in ordering and detail.
GitHub Create Pull Request
Governance ISO 27001 Shared Services blueprint sample controls .../blueprints/samples/iso27001-shared/control-mapping.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, especially in sections related to password management and VM auditing. Windows VM password policies are detailed with multiple audit controls, while Linux VM password and authentication controls are mentioned less frequently and with less detail. Windows examples (e.g., password complexity, password age, password reuse) are given explicitly, whereas Linux controls are referenced more generically (e.g., password file permissions, accounts without passwords) and lack parity in depth and coverage. No PowerShell-specific instructions or tools are mentioned, but Windows VM controls are consistently listed before or in greater detail than Linux equivalents.
Recommendations
  • Add equivalent detailed audit controls for Linux VMs, such as password complexity, password age, password reuse, and other authentication settings.
  • Ensure that examples and policy definitions for Linux are as comprehensive and explicit as those for Windows.
  • Where VM controls are listed, present Linux and Windows examples together or in parallel, rather than focusing on Windows first.
  • Include references to Linux-specific tools or configuration methods (e.g., PAM, shadow file settings) where relevant.
  • Review all sections for parity in coverage between Windows and Linux, especially for security and compliance controls.
GitHub Create Pull Request
← Previous Page 1 of 8 Next →