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 376-400 of 613 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias in several ways: Windows-specific guest configuration assignments (e.g., 'WindowsPendingReboot') are referenced without Linux equivalents, and Windows-centric terminology is used. While Azure CLI and PowerShell examples are provided, PowerShell (a Windows-native tool) is always shown, and some queries are only relevant to Windows machines. Linux-specific queries are rare and only appear in one section. There is no parity for Linux guest configuration assignments (e.g., no 'LinuxPendingReboot' example), and the documentation does not clarify Linux support or provide equivalent Linux-focused scenarios.
Recommendations
- Add Linux-specific guest configuration assignment examples (e.g., pending reboot for Linux, installed applications for Linux, compliance status for Linux VMs).
- Clarify which queries and assignments apply to Windows, Linux, or both, and provide equivalent instructions for each platform.
- Include Linux-native command-line tools or shell examples where relevant, or clarify that Azure CLI is cross-platform.
- Balance the documentation by alternating Windows and Linux examples, or grouping them by OS.
- Explicitly mention limitations or differences in guest configuration support between Windows and Linux.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation describes Azure Machine Configuration policies for both Windows and Linux, but the only detailed example provided is for a Windows-specific policy ('Audit Windows machines that are not set to the specified time zone'). No equivalent Linux example is given, and the walkthrough focuses exclusively on Windows. While Linux policies are mentioned in lists and notes, they are not illustrated with step-by-step guidance or screenshots.
Recommendations
- Add a parallel example that demonstrates assigning a Linux-specific built-in Machine Configuration policy, such as auditing Linux password settings or required applications.
- Include screenshots and parameter walkthroughs for Linux policy assignment, mirroring the detail given for Windows.
- Ensure that Linux policies are given equal prominence in examples and are not relegated to notes or lists.
- Consider alternating the order of Windows and Linux examples, or presenting both side-by-side.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell (a Windows-centric tool) always present and often listed after Azure CLI. There is a notable presence of Windows-specific queries (e.g., 'WindowsPendingReboot'), while Linux-specific queries are less frequent and only appear in one section. There are no Bash, shell, or Linux-native tool examples, and PowerShell is highlighted as a primary automation method, which may create friction for Linux/macOS users who prefer Bash or other shells.
Recommendations
- Add Bash/shell script examples for each query, demonstrating how to run az CLI commands in Linux/macOS environments.
- Where queries are Windows-specific (e.g., 'WindowsPendingReboot'), provide equivalent Linux guest configuration queries (e.g., 'LinuxPendingReboot') if supported.
- Clarify cross-platform compatibility for each command, noting any limitations or differences for Linux/macOS users.
- Consider listing CLI examples before PowerShell, or grouping them together, to avoid implicit prioritization of Windows tools.
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
Governance
Protect your resource hierarchy - Azure Governance
...management-groups/how-to/protect-resource-hierarchy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a detailed Azure PowerShell sample for configuring hierarchy settings but does not offer equivalent CLI or scripting examples for Linux/macOS users. The only code sample is in PowerShell, which is natively available on Windows and less commonly used on Linux/macOS. No Bash, Azure CLI, or other cross-platform examples are provided, and the PowerShell section appears before any mention of Linux-compatible alternatives.
Recommendations
- Add Azure CLI examples for all REST API operations shown in PowerShell.
- Provide Bash/curl sample commands for Linux/macOS users to perform the same tasks.
- Explicitly mention that PowerShell Core is available cross-platform, but also offer native Linux/macOS alternatives.
- Ensure code samples for REST API usage are shown in both PowerShell and Bash/Azure CLI, with equal prominence.
Governance
How to test machine configuration package artifacts
...ration/how-to/develop-custom-package/3-test-package.md
Medium Priority
View Details →
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 (SysInternals PSExec) are mentioned by name, while Linux uses the generic 'sudo' command. In command examples, Windows instructions are consistently presented before Linux equivalents. No Linux-native shell or tool examples are provided; all Linux usage is via PowerShell. macOS is explicitly excluded.
Recommendations
- Provide Linux-native shell examples (e.g., Bash scripts) where possible, not just PowerShell.
- Mention Linux-specific troubleshooting or elevation tools (e.g., 'pkexec', 'su') alongside 'sudo'.
- Alternate the order of Windows and Linux examples, or present them side-by-side.
- Clarify whether PowerShell is required on Linux, or if native tools can be used for any steps.
- Add a note about macOS limitations and possible workarounds, if any.
Governance
Quickstart: Create policy assignment with REST API
...n/articles/governance/policy/assign-policy-rest-api.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell-specific syntax and escape characters are featured in all command examples, with explanations tailored to PowerShell users. Linux/Bash alternatives are mentioned only as side notes, and no explicit Bash/Linux command examples are provided. The prerequisites and instructions assume familiarity with Windows tools and patterns, such as Visual Studio Code and PowerShell, while Linux/macOS users are left to infer necessary adjustments.
Recommendations
- Provide explicit Bash/Linux command examples alongside PowerShell examples, especially for az rest commands and file referencing.
- List Linux/macOS prerequisites (e.g., native Bash, Terminal, alternative editors) equally with Windows prerequisites.
- Clarify escape character usage for both PowerShell and Bash in each example, and show the correct syntax for each platform.
- Avoid assuming Visual Studio Code as the default terminal/editor; mention alternatives for Linux/macOS.
- Present examples for both platforms in parallel, or alternate which platform is shown first.
Governance
Planning a change from Desired State Configuration extension to machine configuration
...onfiguration/whats-new/migrating-from-dsc-extension.md
Medium Priority
View Details →
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 Desired State Configuration (DSC), referencing Windows PowerShell versions, Windows-specific extension management, and Windows-centric tools and commands. There are no examples or guidance for Linux or macOS users, nor any mention of how machine configuration or DSC migration applies to non-Windows environments. All code, migration steps, and troubleshooting are presented from a Windows perspective.
Recommendations
- Include explicit guidance for Linux VMs, such as how to check for DSC extension presence and migrate configurations.
- Provide Linux/macOS-specific examples for querying extensions, packaging, and deploying configurations.
- Clarify whether machine configuration supports Linux and, if so, detail any differences in migration or usage.
- Mention and link to equivalent Linux tools or commands where PowerShell is referenced.
- Add a section outlining limitations or considerations for non-Windows platforms.
Governance
How to sign machine configuration packages
...ration/how-to/develop-custom-package/6-sign-package.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents Windows examples and instructions first, with detailed PowerShell scripts and references to Windows certificate stores and tools. Linux instructions are present but less detailed and follow the Windows section. The use of PowerShell as the primary scripting language, even for Linux, and the emphasis on Windows certificate management tools indicate a Windows-centric approach.
Recommendations
- Present Linux and Windows instructions in parallel or alternate order to avoid Windows-first bias.
- Provide Linux-native command examples (e.g., using OpenSSL for certificate management, bash scripts) instead of PowerShell for Linux scenarios.
- Expand Linux sections with more detailed, step-by-step instructions matching the depth of Windows examples.
- Reference Linux-specific documentation and tools for certificate installation and management (e.g., update-ca-certificates, systemd, etc.).
- Clarify cross-platform differences and provide troubleshooting tips for Linux users.
Governance
Understand Azure Machine Configuration
.../articles/governance/machine-configuration/overview.md
Medium Priority
View Details →
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 referenced as the primary validation tool for both Windows and Linux, with Chef InSpec mentioned only for Linux. The open-source nxtools module is described as a PowerShell-centric solution for Linux management. Troubleshooting and log collection examples are provided for both platforms, but the Windows PowerShell example is shown first and is more detailed. References to Azure PowerShell and portal are listed before Azure CLI. There is a lack of Linux-native tooling or examples (e.g., Ansible, native Bash scripts) and the documentation generally assumes PowerShell as the cross-platform solution, which may not align with typical Linux administrator workflows.
Recommendations
- Provide Linux-native examples using common tools such as Bash, Ansible, or native shell commands, especially for configuration management and troubleshooting.
- List Azure CLI instructions before or alongside Azure PowerShell and portal steps to better support Linux/macOS users.
- Expand discussion of Chef InSpec and other Linux-native validation tools, including their usage and integration.
- Clarify that PowerShell DSC on Linux is optional and provide alternatives for users who prefer not to install PowerShell.
- Include more parity in troubleshooting steps, such as using journalctl or syslog for log collection on Linux.
- Highlight Linux-specific considerations and workflows, especially in sections about extensions, managed identities, and policy assignment.
Governance
Tutorial: Add user assign identities to virtual machines
...ce/policy/tutorials/modify-virtual-machine-identity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for the Azure Portal and PowerShell, with all CLI-based automation examples exclusively using Azure PowerShell. There are no examples or guidance for Linux/macOS users using Azure CLI or Bash, and PowerShell is presented as the sole scripting option for command-line automation, which is most commonly used on Windows.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including policy definition creation, assignment, and remediation.
- Explicitly mention that PowerShell commands can be run on Linux/macOS, or provide Bash script alternatives.
- Include a section or note for Linux/macOS users, clarifying cross-platform options and any prerequisites.
- Present CLI examples in parallel (PowerShell and Azure CLI), or alternate which is shown first to avoid Windows-first bias.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI (cross-platform), Azure PowerShell (Windows-centric), and the Azure Portal. While the CLI example is suitable for Linux/macOS, the PowerShell example is Windows-focused and appears before the Portal instructions. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is highlighted as a primary automation tool, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users, especially for scripting scenarios.
- Clarify that Azure CLI commands work on Linux/macOS and provide installation/setup links for those platforms.
- Reorder examples so that cross-platform tools (Azure CLI) are presented before Windows-centric tools (PowerShell).
- Note PowerShell Core is available cross-platform, but provide guidance for Linux users on installation and usage if PowerShell is required.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references the Windows PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning Linux/macOS alternatives (such as Azure CLI or REST authentication flows). This creates friction for non-Windows users, though the main example uses curl, which is cross-platform.
Recommendations
- Add instructions for obtaining an Azure access token using Azure CLI (az account get-access-token) for Linux/macOS users.
- Include a note or example for authenticating with Azure REST API using OAuth flows or other cross-platform tools.
- Reference both PowerShell and CLI methods equally, or present CLI methods first for broader platform coverage.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists PowerShell as a primary method for creating blueprints, and in the 'Next steps' section, PowerShell is mentioned before REST API. There are no explicit Linux/macOS CLI examples or references to cross-platform tools like Azure CLI. The page does not provide Linux-specific guidance or parity 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.
- Reorder the 'Next steps' section to present cross-platform options (e.g., Portal, Azure CLI, REST API) before or alongside PowerShell.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
- Include notes or links for Linux/macOS users on how to perform equivalent tasks using their preferred tools.
Governance
Quickstart: Create a blueprint with REST API
...les/governance/blueprints/create-blueprint-rest-api.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell examples for making REST API calls, with no equivalent Linux/macOS shell (e.g., Bash/cURL) examples. PowerShell is recommended as the primary tool, and Windows-centric cmdlets are used throughout, making it less accessible for Linux/macOS users who may prefer Bash, cURL, or other cross-platform tools.
Recommendations
- Add equivalent Bash/cURL examples for REST API calls, including authentication and request formatting.
- Mention and demonstrate usage of cross-platform tools such as curl, httpie, or Postman alongside PowerShell.
- Reorder examples so that cross-platform solutions (e.g., Bash/cURL) are presented before or alongside PowerShell.
- Explicitly state that the REST API can be accessed from any OS and provide guidance for Linux/macOS users.
Governance
Australian Government ISM PROTECTED blueprint sample controls
...ce/blueprints/samples/ism-protected/control-mapping.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Many controls explicitly reference Windows VMs and Windows-specific audit results, such as auditing the Administrators group or deploying the Microsoft IaaSAntimalware extension. Linux equivalents are either missing or mentioned less frequently and with less detail. Windows examples and tools (e.g., 'Show audit results from Windows VMs', 'Microsoft IaaSAntimalware extension', 'audit Windows web servers') are presented first or exclusively in several sections, while Linux-specific guidance is limited to a few controls (e.g., passwordless accounts on Linux VMs). Endpoint protection and security hardening recommendations are focused on Windows, with no mention of common Linux solutions. This creates friction for Linux users seeking parity in compliance and security controls.
Recommendations
- For every control referencing Windows VMs or Windows-specific tools, provide equivalent Linux VM guidance and examples (e.g., audit sudoers, SSH configuration, Linux antimalware solutions).
- When mentioning endpoint protection, include recommendations for Linux (such as Microsoft Defender for Linux, ClamAV, or other supported solutions).
- Ensure audit and monitoring controls cover both Windows and Linux systems with equal detail, including examples for Linux event logging, privileged access, and secure communication.
- Avoid listing Windows examples first; present Windows and Linux guidance side-by-side or in parallel sections.
- Where VM extensions are referenced, clarify which extensions are available for Linux and provide instructions for their deployment.
Governance
ISO 27001 ASE/SQL workload blueprint sample controls
...s/samples/iso27001-ase-sql-workload/control-mapping.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it covers Azure Policy controls for both Windows and Linux VMs in some areas, Windows-specific examples and audit checks (such as password complexity, password age, and password reuse) are provided in detail, whereas equivalent Linux examples are either missing or less emphasized. Windows VM controls are described explicitly, while Linux VM controls are mentioned only in passing or not at all for some security controls. Additionally, Windows VM password management is covered in depth, but Linux password management is limited to file permissions, with no mention of password complexity or aging policies for Linux VMs.
Recommendations
- Provide equivalent Linux VM audit controls for password complexity, aging, and reuse, similar to those listed for Windows VMs.
- Include explicit examples and descriptions for Linux VM security controls wherever Windows controls are detailed.
- Ensure that Linux tools and management patterns (such as SSH, PAM, or Linux-specific Azure VM extensions) are mentioned alongside Windows tools.
- Where audit results are shown for Windows VMs, add parallel examples for Linux VMs.
- Review all sections for parity and add Linux/macOS-specific guidance where missing.
Governance
Deploy SWIFT CSP-CSCF v2020 blueprint sample
...les/governance/blueprints/samples/swift-2020/deploy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific concepts (such as 'Windows VM Administrators group' and domain join for Windows VMs) are described in detail, while Linux equivalents (e.g., Linux admin groups, domain join) are not mentioned. Windows VM-related parameters and examples appear before Linux ones in the artifact parameters table, and there are more Windows-specific configuration details. Linux VM configuration is present but less detailed and appears later in the table. No PowerShell or CLI examples are given, but the overall pattern and terminology favor Windows.
Recommendations
- Add equivalent Linux admin group configuration details and examples (e.g., specifying sudoers or admin users for Linux VMs).
- Provide parity in artifact parameter descriptions for Linux VMs, such as domain join or security group membership, if applicable.
- Ensure Linux VM-related parameters appear alongside or before Windows ones in tables and lists for balanced visibility.
- Include explicit notes or examples for Linux-specific deployment scenarios, especially where Windows-specific instructions are given.
- Clarify any differences in management or assignment steps for Linux VMs, if they exist.
Governance
ISO 27001 Shared Services blueprint sample controls
.../blueprints/samples/iso27001-shared/control-mapping.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a 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 and examples, while Linux VM password controls are mentioned less frequently and with less detail. Windows-specific audit items are listed before Linux ones, and some controls (e.g., password complexity, password age, password reuse) are only described for Windows VMs, with no Linux equivalents or guidance. There are no PowerShell-heavy examples, but Windows tools and patterns are prioritized in certain areas.
Recommendations
- Add equivalent Linux VM password policy controls and audit definitions, such as minimum password length, password complexity, password age, and password reuse restrictions.
- Provide examples and guidance for enforcing strong password policies on Linux VMs, including references to common Linux tools (e.g., PAM, passwd, chage).
- Ensure audit controls and recommendations are presented in a platform-neutral order, or grouped by OS, rather than listing Windows controls first.
- Where controls are OS-specific, explicitly state this and provide parity or alternatives for Linux/macOS users.
Governance
SWIFT CSP-CSCF v2020 blueprint sample controls
...nance/blueprints/samples/swift-2020/control-mapping.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Several control mappings and policy definitions specifically reference Windows virtual machines and Windows-specific features (e.g., auditing Windows Administrators group membership, password policies, and deploying Microsoft IaaSAntimalware extension for Windows Server). In many sections, Windows VM examples or controls are listed before Linux equivalents, and some controls (e.g., password complexity, domain join status) are only described for Windows VMs with no Linux counterpart provided. However, there are also Linux-specific controls (e.g., auditing passwd file permissions, remote connections without passwords), and many controls are OS-agnostic or have both Windows and Linux options.
Recommendations
- Ensure that every Windows-specific control or example has a Linux equivalent where applicable (e.g., password policies, domain join status, administrator group membership).
- Present Windows and Linux controls/examples in parallel, rather than listing Windows first or exclusively.
- Expand descriptions to clarify how controls apply to Linux/macOS systems, especially for areas like password complexity, administrator group management, and domain join status.
- Include Linux/macOS-specific security tools or extensions where only Windows tools are mentioned (e.g., antimalware solutions).
- Add explicit notes when a control is Windows-only, and suggest alternative approaches for Linux/macOS users.
Governance
Remediation options for machine configuration
.../machine-configuration/concepts/remediation-options.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation references PowerShell DSC methods (Get, Test, Set) and links to PowerShell-specific resources, but does not mention or provide equivalent examples for Linux/macOS platforms or their configuration management tools. There are no explicit Windows-only instructions, but the reliance on PowerShell terminology and links creates friction for Linux users.
Recommendations
- Provide examples or references for Linux/macOS configuration management equivalents (e.g., using Ansible, Chef, or native guest configuration on Linux).
- Clarify whether the machine configuration feature and referenced modules are cross-platform, and if so, how Linux users should interact with them.
- Include links to Linux/macOS documentation or guides for creating and managing machine configuration packages.
- Avoid PowerShell-centric terminology unless explicitly describing Windows-only scenarios; otherwise, offer platform-specific guidance.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides examples for machine configuration assignments using Azure Resource Manager templates, but only demonstrates a Windows-specific built-in configuration ('AzureWindowsBaseline') and does not offer equivalent Linux examples or mention Linux built-in configurations. The link references also default to Azure PowerShell, which is more Windows-centric.
Recommendations
- Include examples of built-in Linux configurations (e.g., 'AzureLinuxBaseline') alongside Windows examples.
- Explicitly mention Linux support and provide guidance for Linux VMs, including any differences in resource types or configuration parameters.
- Add links or references to Linux-focused documentation and tools (such as Azure CLI or Bash examples).
- Present Windows and Linux examples in parallel or alternate their order to avoid implicit prioritization.
Governance
How to develop a custom machine configuration package
...onfiguration/how-to/develop-custom-package/overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by focusing on PowerShell tools and modules (GuestConfiguration), referencing PowerShell DSC, and providing a video guide that uses the GuestConfiguration PowerShell module. There is a lack of Linux-specific examples, tools, or workflows, and macOS is explicitly excluded from testing. While the GuestConfiguration module is mentioned as available on Ubuntu, there are no Linux-centric instructions or parity in examples.
Recommendations
- Add Linux-specific examples for authoring, testing, and deploying machine configuration packages.
- Include instructions or references for using native Linux tools or workflows (e.g., Bash, shell scripts) alongside PowerShell.
- Provide a video or step-by-step guide demonstrating the process on a Linux system.
- Clarify any differences in workflow or requirements for Linux users, especially for distributions other than Ubuntu.
- Explicitly mention alternatives or workarounds for macOS users if possible.
Governance
Azure Policy definitions modify effect
...n/articles/governance/policy/concepts/effect-modify.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation page contains a notable Windows bias in its guidance for listing modifiable policy aliases, referencing only Azure PowerShell and providing a PowerShell-specific command. No equivalent CLI or REST API example is given for Linux/macOS users. The rest of the page is platform-neutral, focusing on JSON policy definitions and Azure concepts.
Recommendations
- Provide equivalent Azure CLI commands for listing modifiable aliases, e.g., using 'az policy alias list' or similar.
- Mention REST API endpoints or provide an example curl command for cross-platform access.
- Clarify that the PowerShell example is one of several options, and link to documentation for other platforms.
- Add a note or table comparing PowerShell, CLI, and REST API approaches for common tasks.
Governance
How to install the machine configuration authoring module
...velop-custom-package/1-set-up-authoring-environment.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily PowerShell-centric, with all examples using PowerShell commands and no mention of Linux-native tools or shell alternatives. Windows is listed first in tables and installation instructions. While Linux is supported, examples and instructions assume PowerShell usage, which may not be native or preferred on Linux systems. There are no bash or Linux-specific workflow examples.
Recommendations
- Provide equivalent bash or shell commands for Linux users where possible.
- Include Linux-native installation and validation steps (e.g., using apt, checking modules via bash).
- Alternate the order of OS presentation, or present Linux instructions first in some sections.
- Clarify any Linux-specific caveats or differences in module usage, especially regarding prerelease versions.
- Add troubleshooting steps or notes for common Linux issues (e.g., permissions, module paths).
Governance
How to create custom machine configuration package artifacts
...tion/how-to/develop-custom-package/2-create-package.md
Medium Priority
View Details →
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 and output are shown first and in greater detail, including explicit file paths and outputs from Windows environments. Linux is mentioned, but Linux-specific examples are minimal and lack parity in detail. There is no demonstration of using native Linux tools or shell commands for packaging, inspecting, or manipulating artifacts, and macOS is explicitly excluded from testing.
Recommendations
- Provide equivalent Linux shell (bash) commands for compiling, packaging, and inspecting configuration artifacts, such as using zip, unzip, and ls.
- Include Linux file system paths and outputs alongside Windows examples to illustrate cross-platform parity.
- Add examples for using PowerShell Core on Linux, clarifying any differences in module installation or usage.
- Explicitly note any platform-specific limitations or alternatives for Linux users, especially where Windows tools (e.g., Expand-Archive, Get-ChildItem) are used.
- Consider including a section for macOS users, even if only to clarify current limitations and possible workarounds.