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 326-350 of 613 flagged pages
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 →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell and Azure CLI as supported interfaces for querying Azure Resource Graph, but consistently lists Azure PowerShell before Azure CLI. There are no explicit Linux or Bash examples or mentions, and the only command-line tools referenced are Azure CLI and Azure PowerShell. While Azure CLI is cross-platform, the documentation does not highlight Linux or Bash usage, nor does it provide parity in example ordering or mention Linux-specific considerations. There is also a section dedicated to Power BI integration, a Windows-centric tool, without mention of Linux alternatives.
Recommendations
  • Ensure that Azure CLI is listed before Azure PowerShell in all lists and examples, as Azure CLI is cross-platform and more commonly used on Linux.
  • Add explicit Bash/Linux shell examples where command-line usage is discussed, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Where Power BI is mentioned, note that it is primarily a Windows tool and suggest alternative reporting or visualization tools available on Linux, if any.
  • Include a brief section or note on using Resource Graph from Linux environments, including any relevant tools or setup steps.
  • Review all quickstart and tutorial links to ensure Linux users are equally supported and that examples are not Windows- or PowerShell-centric.
GitHub Create Pull Request
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 →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for batching queries across subscriptions, referencing PowerShell and Azure CLI as the primary interfaces, and omitting equivalent Linux/bash examples. The use of PowerShell-specific constructs and the absence of bash or cross-platform scripting guidance limits accessibility for Linux users.
Recommendations
  • Provide equivalent bash/Azure CLI script examples for all PowerShell examples, especially for batching queries across subscriptions.
  • When referencing tools, mention both PowerShell and bash/Azure CLI in parallel, not just PowerShell or Windows-first.
  • Clarify that the solutions are cross-platform where possible, and explicitly state if a solution is Windows-specific.
  • Include guidance for Linux/macOS users, such as using Azure CLI with jq or other common Linux tools for scripting.
  • Review all code blocks and ensure parity between Windows and Linux environments.
GitHub Create Pull Request
Governance Overview of Azure Blueprints ...s/blob/main/articles/governance/blueprints/overview.md
Medium Priority View Details →
Scanned: 2026-01-14 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 blueprints, with no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash scripts). PowerShell is traditionally associated with Windows, and its placement before REST API in the 'Next steps' section suggests a Windows-first approach. There are no examples or guidance for Linux/macOS users, nor any mention of cross-platform tooling.
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 on Linux/macOS, or provide Bash script equivalents where possible.
  • Reorder 'Next steps' to present cross-platform options (REST API, Azure CLI) before or alongside PowerShell.
  • Include a note clarifying platform compatibility for each method (Portal, PowerShell, REST API, Azure CLI).
GitHub Create Pull Request
Governance Azure Blueprints functions ...governance/blueprints/reference/blueprint-functions.md
Medium Priority View Details →
Scanned: 2026-01-14 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 OS-specific command examples, but the only tool called out is PowerShell, which is Windows-centric. No Linux/macOS alternatives or parity are discussed.
Recommendations
  • Explicitly mention Azure CLI as a supported tool for managing Blueprints, if applicable.
  • Provide equivalent examples or instructions for using Azure CLI alongside PowerShell.
  • Clarify any platform-specific limitations or differences in managing Blueprints.
  • Ensure references to management tools are inclusive of cross-platform options.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides authentication and REST API invocation examples exclusively using PowerShell, a Windows-centric tool. No Linux/macOS equivalents (e.g., Bash with curl, Azure CLI) are shown, and PowerShell is recommended as the primary tool for beginners. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add authentication and REST API invocation examples using Bash (curl), Azure CLI, or other cross-platform tools.
  • Present examples for both Windows (PowerShell) and Linux/macOS (Bash/curl/Azure CLI), ideally side-by-side.
  • Explicitly mention that PowerShell is available cross-platform, but also provide alternatives for users who prefer native shells.
  • Update tool recommendations to include Azure CLI and curl as beginner-friendly options.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Many control mappings and audit recommendations specifically mention Windows VMs, Windows web servers, and Windows-only extensions (e.g., Microsoft IaaSAntimalware). Windows audit results and prerequisites are referenced repeatedly, while Linux equivalents are only mentioned in a few authentication controls. Endpoint protection and antivirus recommendations focus on Windows, with no explicit Linux guidance. In several cases, audit controls for privileged access, secure communication, and web server configuration are Windows-specific, with Linux coverage either missing or less visible.
Recommendations
  • Provide equivalent Linux examples and audit controls wherever Windows VMs or servers are referenced, especially for privileged access, secure communication, and endpoint protection.
  • Include explicit recommendations and supported extensions/tools for Linux VMs (e.g., supported antimalware solutions, audit prerequisites, secure communication protocols).
  • Ensure that audit and deployment instructions are platform-neutral or offer parallel guidance for both Windows and Linux environments.
  • Where possible, mention Linux controls and tools before or alongside Windows examples to avoid implicit prioritization.
GitHub Create Pull Request
Governance ISO 27001 ASE/SQL workload blueprint sample controls ...s/samples/iso27001-ase-sql-workload/control-mapping.md
Medium Priority View Details →
Scanned: 2026-01-14 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, particularly in the sections related to password management and VM auditing. Windows VM password policies are described in detail, with multiple audit controls and explicit requirements, while Linux VM controls are mentioned but with less specificity and fewer examples. Windows VM password complexity and aging policies are listed, but equivalent Linux controls (e.g., PAM configuration, shadow file settings) are not discussed. Additionally, Windows VM audit results are presented before Linux VM results, and Windows-specific controls (e.g., password re-use, reversible encryption) are included without Linux equivalents.
Recommendations
  • Add equivalent Linux VM password management controls and examples, such as auditing PAM configuration, password aging, and complexity requirements.
  • Provide Linux-specific audit policies for password re-use and encryption, or clarify if these are not applicable.
  • Ensure that Linux VM audit results and controls are presented with equal detail and prominence as Windows VM controls.
  • Include examples or references for managing Linux VM security settings (e.g., passwd/shadow file permissions, password policies) alongside Windows examples.
  • Consider listing Linux and Windows controls together, or alternating their order, to avoid implicit prioritization.
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-14 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 Linux and Windows VMs in the artifact parameters table, but Windows-specific concepts (such as the 'Administrators group' and 'List of users that should be included in Windows VM Administrators group') are described in detail, while equivalent Linux user/group management is not mentioned. Additionally, examples for user/group management are Windows-centric (e.g., 'Administrator; myUser1; myUser2'), and there are no Linux-specific instructions or examples for managing Linux VM users/groups or extensions. The order of presentation in the artifact table lists Windows VM parameters immediately after Linux VM parameters, but the detailed examples are Windows-focused.
Recommendations
  • Add Linux-specific examples for user/group management, such as specifying users/groups for Linux VMs (e.g., 'root; myUser1; myUser2').
  • Include instructions or references for managing Linux VM extensions and user/group assignments, similar to the Windows VM Administrators group.
  • Provide parity in examples and descriptions for both Windows and Linux, ensuring Linux users can follow along without ambiguity.
  • Clarify whether the 'Administrators group' parameter applies to Linux VMs and, if so, provide appropriate Linux terminology and examples.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits moderate Windows bias, particularly in sections related to password management and VM auditing. Windows VM password policies are described in detail, with multiple audit controls specific to Windows, while Linux VM controls are mentioned less frequently and with less detail. Windows examples and tools (such as password complexity, age, and reuse settings) are presented exclusively, with no equivalent Linux guidance or parity in password management controls. Additionally, Windows VM audit results are listed before Linux VM results, and some controls are Windows-only.
Recommendations
  • Add equivalent Linux VM password management controls and examples, such as auditing /etc/login.defs, PAM configuration, or chage settings for password complexity, age, and reuse.
  • Provide Linux-specific audit policies and remediation guidance for password management, not just file permission checks.
  • Ensure that examples and controls for both Windows and Linux are presented with equal detail and prominence.
  • When listing VM-related controls, alternate or group Windows and Linux examples together to avoid implicit prioritization.
  • Review all sections for OS-specific bias and add missing Linux/macOS guidance where applicable.
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-14 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 mild Windows bias. While it mentions both Windows and Linux in the context of Log Analytics agents, the default operating system for the jumpbox VM is set to Windows, and Active Directory Domain Services (a Windows-centric technology) is a core part of the blueprint. There are no explicit Linux/macOS-specific instructions, examples, or parity for non-Windows environments in key sections such as jumpbox configuration or domain services. Windows terminology and technologies (Active Directory, Windows VM, Windows-first defaults) are presented before or instead of Linux equivalents.
Recommendations
  • Provide explicit examples and instructions for deploying Linux-based jumpboxes, including recommended distributions and configuration steps.
  • Clarify how to use non-Windows alternatives for domain services, such as Azure AD-only environments or Linux-based directory services, where possible.
  • Ensure that all artifact parameters and templates that default to Windows (e.g., Jumpbox Operating System) also document Linux options and their implications.
  • Add parity in documentation for Linux/macOS users, including troubleshooting, configuration, and security considerations.
  • Consider reordering examples so that Linux and Windows are presented equally, or Linux is not always secondary.
GitHub Create Pull Request
Governance SWIFT CSP-CSCF v2020 blueprint sample controls ...nance/blueprints/samples/swift-2020/control-mapping.md
Medium Priority View Details →
Scanned: 2026-01-14 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. Several control mappings and policy definitions focus exclusively on Windows virtual machines (VMs), such as auditing Windows Administrators group membership, password policies, and deploying Microsoft IaaSAntimalware extension for Windows Server. In some sections, Windows VM controls are listed before Linux equivalents, and certain controls (e.g., password complexity, domain join status) are only described for Windows, with no Linux or cross-platform alternatives. Linux VM controls are present but less comprehensive, and macOS is not mentioned at all.
Recommendations
  • Ensure that all controls and policy definitions described for Windows VMs have equivalent examples or guidance for Linux VMs, where applicable.
  • Present Linux and Windows examples side-by-side or in parallel lists, rather than listing Windows controls first.
  • Expand coverage of Linux-specific controls, such as password policies, domain membership, and endpoint protection, to match the detail provided for Windows.
  • Include explicit statements about macOS support or limitations, or clarify that the blueprint is not applicable to macOS if that is the case.
  • Where a control is Windows-only due to Azure Policy limitations, clearly state this and suggest alternative approaches for Linux/macOS users.
GitHub Create Pull Request
Governance Deploy SWIFT CSP-CSCF v2020 blueprint sample ...les/governance/blueprints/samples/swift-2020/deploy.md
Medium Priority View Details →
Scanned: 2026-01-14 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. Windows-related artifacts and parameters (such as Windows VM Administrators group and domain join for Windows VMs) are described in detail, while Linux equivalents (such as Linux VM admin group or domain join) are not mentioned. Windows VM examples and parameters appear first in the artifact parameters table, and Windows-specific concepts (like local Administrators group) are referenced without Linux parallels. Linux is only referenced in the context of Log Analytics agent deployment, with no further details or examples.
Recommendations
  • Add equivalent Linux examples for VM administration, such as specifying Linux admin users or groups.
  • Include instructions or parameters for Linux domain join (if supported), or clarify differences.
  • Present Linux and Windows examples in parallel, or alternate their order to avoid Windows-first bias.
  • Expand artifact parameter descriptions to cover Linux-specific configuration options where applicable.
GitHub Create Pull Request
Governance Remediation options for machine configuration .../machine-configuration/concepts/remediation-options.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell DSC methods (Get, Test, Set) and links to PowerShell documentation, without mentioning or providing equivalent Linux/macOS configuration management tools or examples. The terminology and references (such as 'Set' and 'Test' methods) are closely associated with Windows/PowerShell environments. No Linux-specific tools (e.g., Ansible, Chef, or native Linux guest configuration modules) are mentioned, nor are there examples or guidance for Linux users.
Recommendations
  • Include equivalent Linux/macOS examples for configuration management and remediation, such as using Ansible, Chef, or native Linux guest configuration modules.
  • Reference documentation for Linux guest configuration extension and its usage.
  • Clarify whether the described features and methods (e.g., Set/Test) are available and supported on Linux/macOS, and provide links to relevant resources.
  • Add explicit guidance for Linux/macOS users on how to achieve remediation and compliance using Azure Policy and machine configuration.
GitHub Create Pull Request
Governance How to create custom machine configuration policy definitions ...chine-configuration/how-to/create-policy-definition.md
Medium Priority View Details →
Scanned: 2026-01-14 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 is heavily focused on Windows and PowerShell, with all code examples and tooling instructions using PowerShell syntax and Windows-style paths. There are no Linux/macOS shell examples, and references to platform support are generally Windows-first or Windows-only, especially in example configurations and managed identity scenarios. Linux support is mentioned in passing, but not demonstrated.
Recommendations
  • Provide equivalent examples using Bash/Azure CLI for Linux/macOS users, especially for steps involving storage access, GUID generation, and policy creation.
  • Show Linux-style file paths (e.g., /home/user/package.zip) in examples where local paths are referenced.
  • Explicitly document any platform-specific differences or requirements for Linux, including minimum agent versions and supported features.
  • Add a section or callouts for Linux/macOS users, clarifying how to perform each step without PowerShell.
  • Where PowerShell is required, clarify cross-platform installation and usage (e.g., PowerShell Core on Linux/macOS).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes Azure Machine Configuration policies for both Windows and Linux, but the main example provided is exclusively for a Windows policy ('Audit Windows Time Zone'). No Linux-specific example is given, and the walkthrough focuses on Windows settings and parameters. While Linux policies are mentioned, they are not illustrated with step-by-step instructions or screenshots, and the example section is Windows-centric.
Recommendations
  • Add a parallel example that demonstrates assigning a Linux-specific policy (e.g., 'Audit Linux machines that have the specified applications installed'), including screenshots and parameter explanations.
  • Alternate the order of examples or provide both Windows and Linux examples side-by-side to ensure parity.
  • Explicitly mention any differences in parameters or assignment steps for Linux policies.
  • Ensure that CLI and automation examples include Linux policy scenarios, not just generic references.
GitHub Create Pull Request
Governance How to create a machine configuration assignment using an Azure Resource Manager template .../how-to/assign-configuration/azure-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only Windows-specific configuration examples (e.g., AzureWindowsBaseline), omitting Linux equivalents and built-in Linux configuration assignments. Reference links default to Azure PowerShell, a Windows-centric tool, and there is no mention of Linux-specific baselines or how to assign them.
Recommendations
  • Include examples for built-in Linux configurations (e.g., AzureLinuxBaseline) alongside Windows examples.
  • Provide ARM template snippets for Linux VM configuration assignments.
  • Reference both Azure CLI and PowerShell in link definitions and instructions, ensuring parity for Linux/macOS users.
  • Explicitly mention Linux support and any differences in configuration assignment for Linux VMs.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a slight Windows bias by referencing the PowerShell Get-AzAccessToken cmdlet as the method to obtain an Azure access token, without mentioning Linux/macOS alternatives (such as Azure CLI or other cross-platform tools). No Linux-specific example or guidance is provided for authentication, which may create friction for non-Windows users. However, the main example for making the REST API call uses curl, which is cross-platform.
Recommendations
  • Add instructions for obtaining an Azure access token using Azure CLI (az account get-access-token), which works on Linux/macOS/Windows.
  • Explicitly mention that curl is available on Linux/macOS and Windows, and provide any OS-specific notes if needed.
  • Provide links to cross-platform authentication documentation, not just PowerShell.
  • Where PowerShell is referenced, offer an equivalent Azure CLI or REST API example.
GitHub Create Pull Request
Governance Understand The Baseline Settings Parameter Format ...ty-baselines/understand-baseline-settings-parameter.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation presents Windows-specific patterns and examples before Linux equivalents in the Azure Security Baseline (ASB) section. Windows scoping syntax is explained in detail, while Linux is described as 'omitting Windows-specific scoping' without further elaboration. Windows examples use detailed server/role syntax, whereas Linux examples are simpler and less contextual. No PowerShell commands are shown, but the Windows-centric configuration pattern may be unfamiliar to Linux users. The overall structure gives Windows more prominence and detail.
Recommendations
  • Provide equally detailed Linux examples, including any distro-specific or role-based scoping if available.
  • Clarify Linux rule/value patterns and possible variations, not just state that Windows-specific scoping is omitted.
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Explicitly mention how Linux users should interpret or adapt the schema, especially if certain features are Windows-only.
GitHub Create Pull Request
Governance How to install the machine configuration authoring module ...velop-custom-package/1-set-up-authoring-environment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily PowerShell-centric, assuming users on both Windows and Linux will use PowerShell 7.x. Windows installation instructions and examples are presented before Linux equivalents. There is a lack of Linux-native command examples (e.g., Bash), and the guidance for Linux users is limited to PowerShell usage, with no mention of Linux package managers or alternative workflows.
Recommendations
  • Provide Linux-native (Bash) installation and validation examples alongside PowerShell commands.
  • Include instructions for installing PowerShell on Linux using common package managers (apt, yum) directly in the documentation.
  • Clarify whether non-PowerShell workflows are supported or required for Linux users.
  • Present Windows and Linux instructions in parallel, rather than Windows-first.
  • Explicitly address any differences in module versions or functionality between Windows and Linux.
GitHub Create Pull Request
Governance How to create custom machine configuration package artifacts ...tion/how-to/develop-custom-package/2-create-package.md
Medium Priority View Details →
Scanned: 2026-01-14 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 is heavily PowerShell-centric, with all examples and tooling instructions using PowerShell commands and patterns. Windows examples are presented first and in greater detail, including output paths and command outputs that use Windows-style paths. Linux-specific instructions are minimal and refer users to external articles for custom resource creation, rather than providing in-place examples. There is no mention of Linux-native packaging or file inspection tools, and macOS is explicitly excluded from testing.
Recommendations
  • Provide Linux-first or parallel examples, including Linux shell commands for file operations (e.g., using 'mv' instead of 'Rename-Item', 'unzip' instead of 'Expand-Archive').
  • Show Linux output paths and directory structures (e.g., '/home/user/dsc/MyConfig' instead of 'C:\dsc\MyConfig').
  • Include instructions for using PowerShell Core on Linux, and clarify any differences in module installation or usage.
  • Add a Linux-specific example for compiling and packaging, not just referencing external articles.
  • Mention Linux-native alternatives for inspecting and measuring package contents (e.g., 'du -sh', 'ls -lhR').
  • Clarify which steps are identical and which differ between Windows and Linux, especially regarding file paths and permissions.
GitHub Create Pull Request
Governance How to sign machine configuration packages ...ration/how-to/develop-custom-package/6-sign-package.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents Windows examples and PowerShell-based workflows before Linux equivalents, with detailed PowerShell scripts for certificate creation and management. Linux instructions are present but less detailed and use GPG, with less explanation of key management. Windows tools and patterns (certificate stores, PowerShell cmdlets) are mentioned first and more extensively, while Linux instructions are secondary.
Recommendations
  • Present Linux and Windows examples with equal detail and in parallel sections, rather than Windows-first.
  • Provide more explanation and step-by-step instructions for Linux key management, including installation of public keys and integration with system trust stores.
  • Include Linux-native commands for certificate/key management (e.g., openssl, update-ca-certificates) alongside GPG.
  • Add explicit notes about differences in workflows and requirements between platforms.
  • Ensure that references and external links include Linux-relevant resources, not just Windows/PowerShell/Key Vault templates.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by focusing on PowerShell Desired State Configuration (DSC) and the GuestConfiguration PowerShell module, with no Linux-specific examples or equivalent tooling mentioned. The instructional video is PowerShell-centric, and while Linux support is acknowledged, practical Linux authoring/testing steps are missing. MacOS is explicitly unsupported.
Recommendations
  • Add Linux-specific examples for authoring and validating machine configuration packages, using native Linux tools where possible.
  • Include instructions or references for using DSC on Linux, such as with Open Management Infrastructure (OMI) or native shell scripting.
  • Highlight any differences or additional steps required for Linux users in the authoring and testing process.
  • Provide parity in documentation structure, ensuring Linux workflows are described alongside Windows/PowerShell ones.
  • Consider linking to or embedding Linux-focused video tutorials.
GitHub Create Pull Request
Governance View Machine Configuration Compliance Reporting ...rnance/machine-configuration/how-to/view-compliance.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides a generally platform-neutral overview of Azure Machine Configuration compliance reporting, focusing on portal-based workflows and Azure Resource Graph queries. However, in the 'Other Programmatic Access' section, there is a notable bias toward Windows/PowerShell tooling: only the Windows PowerShell cmdlet (Get-AzGuestConfigurationAssignment) is explicitly mentioned, while Linux/macOS equivalents (such as Bash, shell scripting, or cross-platform CLI examples) are absent. This may create friction for Linux/macOS users seeking parity in automation or scripting.
Recommendations
  • Add explicit examples and references for Linux/macOS users, such as Bash or shell scripting with the Azure CLI (az guestconfig, az policy, az graph).
  • Include cross-platform CLI usage examples alongside PowerShell cmdlets in the programmatic access table.
  • Clarify that all CLI tools (az policy, az guestconfig, az graph) are cross-platform and provide sample commands for Linux/macOS environments.
  • Consider reordering or balancing the presentation of PowerShell and CLI tools to avoid implying Windows-first support.
GitHub Create Pull Request
Governance Understand Azure Machine Configuration .../articles/governance/machine-configuration/overview.md
Medium Priority View Details →
Scanned: 2026-01-14 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 demonstrates a moderate Windows bias. PowerShell Desired State Configuration (DSC) is the primary configuration tool mentioned for both Windows and Linux, with Chef InSpec as an additional tool for Linux. Windows-specific tools and concepts (PowerShell, DSC, Windows paths) are referenced frequently and often first. The open-source nxtools module is described as a PowerShell solution for Linux, reinforcing PowerShell as the main cross-platform approach. While Linux is supported and examples are provided, native Linux configuration tools (e.g., Ansible, shell scripts, systemd) are not mentioned, and PowerShell-centric workflows dominate. Windows examples and terminology (paths, modules, troubleshooting) are often presented before or in greater detail than Linux equivalents.
Recommendations
  • Include examples and references for native Linux configuration management tools (e.g., Ansible, shell scripting, systemd unit files) alongside PowerShell DSC.
  • Present Linux examples and troubleshooting steps with equal prominence and detail as Windows examples.
  • Clarify that PowerShell DSC is not the only option for Linux and provide guidance for users who prefer native Linux tools.
  • Add more Linux-first workflows and highlight differences or caveats for Linux users.
  • Avoid presenting Windows paths, tools, and terminology before Linux equivalents in tables and examples.
GitHub Create Pull Request
Governance Troubleshooting Azure Machine Configuration ...onfiguration/overview/04-operations-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is referenced as the primary tool for creating custom policies, and the open-source nxtools module is described as a way to make Linux management easier for PowerShell users, implying a Windows-centric workflow. In several sections, Windows examples and tools are mentioned before their Linux equivalents, such as log file locations and troubleshooting scripts. However, Linux equivalents are generally provided, and Linux-specific policy definitions are listed alongside Windows ones.
Recommendations
  • Provide equivalent Linux-native tooling and examples (e.g., Bash, Python) for creating and managing custom policies, not just PowerShell.
  • Highlight Linux examples and tools with equal prominence and order as Windows ones.
  • Clarify whether the nxtools module is required for Linux management or if native Linux tools can be used.
  • Include references to Linux-native documentation and troubleshooting guides.
  • Avoid language that frames Linux management as an add-on for PowerShell users.
GitHub Create Pull Request
← Previous Page 14 of 25 Next →