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 51-75 of 186 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Azure CLI and Azure PowerShell examples side-by-side, but PowerShell examples are always shown, and PowerShell-specific patterns (like ConvertTo-Json, variable assignment, and output review) are explained in detail. The JSON output examples use Windows-centric values (WindowsServer, osType: Windows), and the PowerShell output formatting is discussed more than Linux/macOS shell equivalents. The CLI examples use Unix shell commands (awk, sed, tail, cat), but there is no explicit mention of Linux/macOS or their shell environments, nor any guidance for users on those platforms. Windows/PowerShell patterns are explained before or more thoroughly than Linux equivalents.
Recommendations
- Explicitly mention that Azure CLI examples are cross-platform and provide guidance for Linux/macOS users (e.g., bash/zsh compatibility, alternative commands for Windows CMD).
- Add notes or sections clarifying how PowerShell commands differ on Linux/macOS (e.g., installation, output formatting).
- Balance explanations by including details for CLI output manipulation on Linux/macOS (e.g., jq usage for JSON parsing).
- Include example outputs for Linux/macOS environments, not just Windows-centric values.
- Where PowerShell output formatting is discussed, provide equivalent CLI or shell scripting advice for Linux/macOS users.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for interacting with Azure Resource Graph, but PowerShell (a Windows-centric tool) is featured equally and sometimes first. There are no explicit Linux/macOS shell examples (e.g., Bash, zsh), nor is there mention of platform-specific considerations for Linux/macOS users. The CLI examples are cross-platform, but the heavy inclusion of PowerShell and lack of Linux/macOS-specific guidance creates a subtle Windows bias.
Recommendations
- Clarify that Azure CLI is cross-platform and works natively on Linux/macOS.
- Add explicit Bash/zsh shell usage examples, especially for tasks like parsing or formatting output.
- Note any platform-specific differences in installation or usage for CLI and PowerShell.
- Consider mentioning other SDKs or scripting languages (Python, etc.) that are popular on Linux/macOS.
- If PowerShell is shown, clarify that PowerShell Core is available on Linux/macOS, or provide equivalent Bash commands where relevant.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Specific Resource
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, which are cross-platform tools. However, there is a notable Windows bias in several areas: PowerShell is featured as a primary method (and is traditionally associated with Windows), and some queries and resource names (e.g., 'WindowsPendingReboot') are Windows-specific with no Linux equivalents shown. In most sections, Windows-centric queries or terminology appear before Linux examples, and there is only one explicit Linux-focused example ('installed_application_linux'), which is the exception rather than the rule.
Recommendations
- For queries like 'WindowsPendingReboot', provide equivalent Linux examples (e.g., 'LinuxPendingReboot') if supported.
- Where resource names or queries are Windows-specific, clarify Linux alternatives or explicitly state if none exist.
- Balance example coverage by including Linux/macOS-specific guest configuration assignments and queries where possible.
- When listing command tabs, alternate the order or clarify cross-platform compatibility, rather than defaulting to PowerShell (Windows) first.
- Add notes or links to Linux/macOS documentation for guest configuration policies and compliance reporting.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell example is given equal prominence to the CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS compatibility for the CLI example, nor are there bash-specific notes or troubleshooting for non-Windows platforms. The ordering of tabs (CLI first, then PowerShell) is good, but the PowerShell example uses escaping (`$`) that is specific to Windows/PowerShell, which may confuse Linux users. No Linux-specific issues or alternatives are discussed.
Recommendations
- Explicitly state that the Azure CLI example works on Linux/macOS and Windows.
- Add bash shell examples or notes about escaping (e.g., how to handle `$` and `\` in bash vs PowerShell).
- Include troubleshooting tips for common Linux/macOS issues (e.g., quoting, shell escaping).
- Clarify that PowerShell is primarily for Windows, and direct Linux/macOS users to Azure CLI.
- Consider adding a Linux/macOS tab or section if there are platform-specific considerations.
Governance
Manage Azure Service Group membership at scale
...rticles/governance/service-groups/manage-membership.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides a detailed PowerShell script and example output for bulk membership management using Azure Resource Graph, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform scripting). The only automation example for querying and deploying memberships at scale is Windows-centric, relying on PowerShell and Az modules, with no mention of alternatives or parity for non-Windows environments.
Recommendations
- Provide equivalent examples using Azure CLI and Bash for querying Azure Resource Graph and deploying resources, ensuring Linux/macOS users can follow along.
- Explicitly mention cross-platform options and tools, such as Azure CLI, and link to relevant documentation.
- Add a note clarifying that the PowerShell script is Windows-specific and suggest alternatives for Linux/macOS.
- Include sample scripts or commands for Linux/macOS environments, demonstrating the same workflow.
- Consider reordering examples so that cross-platform solutions are presented before or alongside Windows-specific ones.
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-related parameters and artifacts (e.g., Windows VM Administrators group, Windows VM domain join, Windows VMSS, Windows VMs) are described in detail, with Linux equivalents present but less emphasized. Windows-specific concepts (e.g., Administrators group, domain join) are mentioned without Linux analogs or guidance. Windows artifacts and parameters appear before Linux ones in the artifact table, and there are no examples or instructions for Linux-specific tasks such as joining Linux VMs to a domain or managing Linux administrator groups.
Recommendations
- Provide Linux-specific examples and guidance for tasks such as managing administrator groups and domain join equivalents (e.g., using sudoers, LDAP/SSSD integration).
- Ensure Linux artifacts and parameters are described with equal detail and clarity as Windows ones.
- Reorder artifact tables and examples to alternate or balance Windows and Linux content.
- Add explicit instructions or references for Linux VM management tasks relevant to the blueprint.
- Clarify where Windows-only concepts do not apply to Linux, and offer Linux alternatives.
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 omits any Linux/macOS equivalents. No Linux-specific built-in configuration (such as 'AzureLinuxBaseline') is shown, nor are there examples of Linux configuration parameters or references to Linux tools.
Recommendations
- Include examples of assigning built-in Linux configurations (e.g., 'AzureLinuxBaseline').
- Show configuration parameters relevant to Linux systems.
- Add notes or sections clarifying Linux/macOS support and differences.
- Provide links to Linux-focused documentation or reference materials.
- Ensure parity in example order (e.g., alternate Windows and Linux examples).
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 and instructions for both Windows and Linux focused on running PowerShell. Windows-specific tools (PSExec) are mentioned explicitly, and Windows instructions are consistently presented before Linux equivalents. There is no mention of native Linux shell alternatives or parity for macOS users.
Recommendations
- Provide native Bash or shell script examples for Linux users, not just PowerShell.
- Mention and demonstrate Linux-native tools and patterns where applicable, such as using direct shell commands for privilege elevation and file management.
- Alternate the order of Windows and Linux instructions, or present them side-by-side for parity.
- Clarify the limitations for macOS and suggest any possible workarounds or future support.
- Consider referencing cross-platform scripting approaches or tools that are more common in Linux environments.
Governance
How to access custom machine configuration package artifacts
...tion/how-to/develop-custom-package/5-access-package.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell examples for generating SAS tokens and accessing Azure Storage, which are primarily Windows-centric. There are no equivalent examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API). The use of PowerShell cmdlets and lack of cross-platform instructions may create friction for users on non-Windows systems.
Recommendations
- Add Azure CLI examples for generating SAS tokens and accessing blobs, which work natively on Linux/macOS.
- Include Bash or REST API examples for key operations.
- Explicitly mention cross-platform alternatives and clarify which tools are supported on each OS.
- Reorder examples or provide parallel instructions for both Windows (PowerShell) and Linux/macOS (CLI/Bash).
Governance
Quickstart: Create a management group with .NET Core
...ce/management-groups/create-management-group-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only Windows-style execution examples (using .exe and PowerShell-style line continuations) and omitting explicit Linux/macOS instructions for running the .NET Core application. There is no mention of Linux-specific patterns (such as './mgCreate' or bash line continuations), nor any guidance for Linux/macOS users regarding file permissions or environment differences.
Recommendations
- Include Linux/macOS command examples for running the .NET Core application (e.g., './mgCreate' instead of 'mgCreate.exe').
- Show both Windows (PowerShell) and Linux/macOS (bash/zsh) line continuation styles in command examples.
- Add notes about file permissions and how to make the published binary executable on Linux/macOS (e.g., 'chmod +x mgCreate').
- Clarify that .NET Core is cross-platform and provide platform-specific instructions where relevant.
- Ensure that cleanup instructions mention Linux/macOS file/folder deletion commands as well.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides extensive Azure PowerShell examples and explanations, often with more detail than Azure CLI. PowerShell commands and patterns (such as jobs) are highlighted, and PowerShell is presented before CLI in several sections. There is no mention of Linux/macOS-specific shell usage, nor are there examples using Bash or other common Linux tools. The Azure CLI examples are present but less detailed, and there is no explicit parity check for Linux users.
Recommendations
- Add Bash shell examples for REST API calls using curl, jq, etc., to demonstrate Linux/macOS workflows.
- Ensure Azure CLI examples are as detailed as PowerShell ones, including asynchronous/background execution patterns.
- Explicitly mention that Azure CLI is cross-platform and highlight usage on Linux/macOS, possibly with screenshots or terminal output.
- Where PowerShell jobs are discussed, provide equivalent guidance for backgrounding CLI commands in Linux (e.g., using & or nohup).
- Review ordering so that CLI and REST examples are presented before PowerShell, or in parallel, to avoid Windows-first perception.
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 detailed instructions for using the Azure Portal and PowerShell to assign user managed identities to VMs, but omits equivalent CLI (az), Bash, or Linux/macOS shell examples. The PowerShell workflow is presented as the only scripting/automation option, which may create friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
- Add step-by-step instructions using Azure CLI (az) commands for creating and assigning policy definitions and remediation tasks.
- Include Bash or shell script examples for Linux/macOS users.
- Clarify that PowerShell commands can be run cross-platform (if true), or provide explicit alternatives for non-Windows environments.
- Present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell-only.
- Explicitly mention tool parity and link to relevant Azure CLI documentation.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for Azure Blueprints shows a mild Windows bias. In the 'Next steps' section, PowerShell (a Windows-centric tool) is explicitly listed as a primary method for creating blueprints, while there is no mention of Linux/macOS CLI equivalents (such as Azure CLI or Bash scripting). Additionally, PowerShell is listed before REST API, and there is no example or guidance for Linux-native tools or workflows. Throughout the page, no explicit Windows-only tools are referenced, but the lack of Linux/macOS parity in examples and guidance is notable.
Recommendations
- Add examples and guidance for using Azure CLI (cross-platform) to create and manage blueprints.
- Include Bash scripting or Linux/macOS workflow instructions alongside PowerShell examples.
- In the 'Next steps' section, list Azure CLI and REST API options before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly state that Azure Blueprints can be managed from any OS using cross-platform tools.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references managing Azure Blueprints with Azure PowerShell or REST API, but only explicitly mentions Azure PowerShell—a Windows-centric tool—without mentioning cross-platform alternatives like Azure CLI. There are no command-line examples provided, but the implication is that PowerShell is the primary management tool. No Linux/macOS-specific tools or patterns are mentioned, and no examples are given for those platforms.
Recommendations
- Explicitly mention Azure CLI as a cross-platform alternative to Azure PowerShell for managing Blueprints.
- Provide example commands for both Azure PowerShell and Azure CLI when discussing management tasks.
- Clarify that REST API and Azure CLI are available and supported on Linux/macOS.
- Add a note about platform compatibility for all tools referenced.
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 provides detailed PowerShell examples for authenticating and invoking REST API calls, with no equivalent examples for Linux/macOS users (e.g., Bash, curl, or other cross-platform tools). PowerShell is recommended as the main tool for beginners, and Windows-centric cmdlets are used exclusively in code samples. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
- Add equivalent Bash/curl examples for authenticating and making REST API calls.
- Mention cross-platform tools (e.g., curl, httpie, ARMClient) alongside PowerShell, not just as an aside.
- Present examples for both Windows and Linux/macOS users, or use a neutral tool first (e.g., curl), then show PowerShell as an alternative.
- Clarify that PowerShell Core is available cross-platform, but provide installation instructions or alternatives for users who do not wish to use PowerShell.
Governance
Canada Federal PBMM blueprint sample
...s/governance/blueprints/samples/canada-federal-pbmm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides examples and parameters for both Windows and Linux VM deployments, 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. Windows VM parameters are listed before Linux ones in the artifact table, and there are no examples or guidance for Linux administrator group management or user assignment. The documentation also references Windows-specific terminology and patterns without Linux parity.
Recommendations
- Add explicit instructions or examples for managing Linux administrator groups or sudoers, similar to the Windows Administrators group guidance.
- Ensure Linux VM parameters and examples are presented with equal prominence and detail as Windows ones.
- Provide parity in user/group management examples for Linux VMs, such as specifying users for /etc/sudoers or relevant Linux groups.
- Consider alternating the order of Windows and Linux examples in tables and lists to avoid implicit prioritization.
- Clarify any differences in artifact behavior between Windows and Linux VMs, especially around extension deployment and audit requirements.
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 control mappings and audit recommendations specifically mention Windows VMs, Windows web servers, and Windows-only extensions (e.g., Microsoft IaaSAntimalware). Windows examples and tools are referenced repeatedly, often without equivalent Linux guidance. Linux is only explicitly mentioned in a few authentication controls, and there is a lack of parity in areas such as antivirus, auditing, and secure communication protocols.
Recommendations
- Provide equivalent Linux examples and audit controls where Windows-specific recommendations are given, such as for administrator group audits, secure communication protocols, and antivirus solutions.
- Mention Linux-compatible extensions and tools (e.g., for antimalware, endpoint protection, and auditing) alongside Windows recommendations.
- Ensure that recommendations for VM configuration, patching, and monitoring explicitly address both Windows and Linux environments.
- Where possible, use generic terminology (e.g., 'virtual machines') and clarify when a control applies to all OS types or only to Windows.
- Add notes or links to Linux-specific documentation for controls currently described only for Windows.
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
Missing Linux Example
Windows Tools
Summary
The documentation exhibits moderate Windows bias, especially in sections related to password management and VM auditing. Windows VM password policies are described in detail, with multiple audit controls listed, while Linux equivalents (such as password complexity, aging, and reuse policies) are not mentioned. In other areas, Linux is referenced (e.g., auditing Linux VMs for passwordless accounts and file permissions), but the coverage is less comprehensive than for Windows. No PowerShell-specific examples or Windows command-line tools are present, but Windows VM controls are prioritized and described in greater detail than Linux controls.
Recommendations
- Add equivalent audit controls and documentation for Linux VM password policies, such as minimum password length, complexity, aging, and reuse restrictions.
- Ensure that examples and audit controls for both Windows and Linux are presented with equal detail and prominence.
- Where controls are OS-specific, explicitly state this and provide parity where possible.
- Include references to Linux security tools or configuration patterns (e.g., PAM, passwd/shadow file management) alongside Windows tools.
- Consider adding macOS-specific notes if relevant for Azure VM workloads.
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 page exhibits moderate Windows bias, most notably in the password management section (A.9.4.3), which exclusively audits Windows VM password policies and omits equivalent Linux controls. Windows VM examples and controls are presented without Linux parity, and Windows-specific tools/settings are referenced (e.g., password complexity, password age, password reuse) without mention of Linux equivalents. Other sections do reference Linux VMs (e.g., auditing passwordless accounts, passwd file permissions), but the Windows bias is most pronounced in password management and some cryptographic controls.
Recommendations
- Add equivalent Linux VM password policy audits (e.g., minimum password length, password complexity, password expiry, password reuse) using Linux tools such as PAM, /etc/login.defs, or audit policies.
- Provide examples or references for configuring and auditing password policies on Linux VMs in Azure, similar to the Windows VM controls.
- Ensure cryptographic controls and other security settings are described for both Windows and Linux environments where applicable.
- Present examples for both Windows and Linux VMs in parallel, or clarify OS applicability for each control.
- Where controls are OS-specific, explicitly state so and provide guidance for other platforms.
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 reference Windows-specific features, such as auditing Windows VM Administrators group membership, password policies, and deploying Microsoft IaaSAntimalware extension for Windows Server. In some sections, Windows examples or controls are listed before Linux equivalents, and certain controls (e.g., password complexity, domain join status, antimalware deployment) are only described for Windows, with no Linux counterpart or guidance. However, Linux is addressed in some areas (e.g., auditing Linux VMs for passwordless accounts, passwd file permissions, Log Analytics agent deployment), and some controls are OS-agnostic.
Recommendations
- Ensure that for every Windows-specific control or example, a Linux equivalent is provided (e.g., domain join auditing, password complexity enforcement, antimalware solutions).
- Present Linux and Windows examples in parallel or alternate their order to avoid implicit prioritization.
- Where only Windows tools or extensions are mentioned (e.g., Microsoft IaaSAntimalware), include recommended Linux solutions (such as integration with common Linux antimalware tools or endpoint protection agents).
- Expand sections on password policies and account management to include Linux-specific controls and best practices.
- Audit and document Linux-specific security controls with the same level of detail as Windows controls.
Governance
Remediation options for machine configuration
.../machine-configuration/concepts/remediation-options.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page references PowerShell DSC methods (Get, Test, Set) and links to PowerShell documentation, which are primarily Windows-centric technologies. There are no explicit examples or instructions for Linux/macOS users, nor is there mention of Linux equivalents or cross-platform modules. The documentation assumes familiarity with Windows tooling and patterns, creating friction for Linux users.
Recommendations
- Include examples and references for Linux/macOS environments, such as using cross-platform DSC modules or native Linux configuration tools.
- Clarify whether machine configuration and remediation features work identically on Linux and macOS, and document any differences.
- Provide links to Linux-specific documentation for guest configuration, policy assignment, and remediation.
- Add sample workflows or commands for Linux systems, using Bash or other relevant tools, alongside PowerShell examples.
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 Time Zone). No Linux policy is demonstrated in detail, and the example walkthrough is Windows-centric. While Linux policies are mentioned in lists and notes, their usage is not illustrated, and Linux-specific parameters or considerations are not shown.
Recommendations
- Add a detailed example for a Linux built-in Machine Configuration policy, such as auditing installed applications or enforcing password settings.
- Alternate the order of examples so that Linux and Windows policies are demonstrated with equal prominence.
- Include screenshots and parameter walkthroughs for Linux policy assignments, similar to the Windows example.
- Highlight any Linux-specific prerequisites, parameters, or troubleshooting steps.
- Ensure parity in programmatic examples (CLI, PowerShell, REST) by showing both Windows and Linux policy assignment commands.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for every scenario, and queries reference Windows-specific guest configuration assignments (e.g., 'WindowsPendingReboot'). Linux-specific examples are rare, with only one explicit mention ('installed_application_linux'). The ordering of examples and assignment names generally favors Windows, and there is no discussion of Linux-specific tools or patterns outside Azure CLI/PowerShell. No explicit Linux shell or scripting examples are given, and the documentation does not clarify cross-platform differences or limitations.
Recommendations
- Provide more Linux-focused examples, such as queries for Linux guest configuration assignments (e.g., pending reboot, installed packages, compliance reasons).
- Include Linux shell (bash) or scripting examples where relevant, especially for users who prefer not to use PowerShell.
- Clarify which queries and assignment names are Windows-only and which are Linux-compatible.
- Balance the ordering of examples so Linux scenarios are presented alongside or before Windows ones where appropriate.
- Reference Linux tools or patterns (e.g., using jq, grep, or bash scripting with Azure CLI outputs) to improve parity.
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 page demonstrates a bias towards Windows by referencing the PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning Linux/macOS alternatives. No Linux-specific tools (such as Azure CLI) or authentication methods are provided, and the only authentication example is Windows-centric. The rest of the examples use cURL, which is cross-platform, but the authentication step is a critical blocker for non-Windows users.
Recommendations
- Include instructions for obtaining an Azure access token using Azure CLI (az account get-access-token) for Linux/macOS users.
- Provide authentication examples using platform-agnostic tools or explicitly mention cross-platform alternatives.
- Add a note clarifying that PowerShell is available on Linux/macOS, but also provide native Linux/macOS command examples.
- Ensure all steps required to complete the task are covered for both Windows and Linux/macOS users.
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 and presents Windows examples and tooling first and in greater detail. Linux support is mentioned, but Linux-specific examples and workflows are minimal or deferred to external articles. Output paths and commands use Windows conventions, and there is a lack of parity in Linux-focused guidance, especially for compiling and packaging configurations.
Recommendations
- Provide explicit, step-by-step Linux examples for authoring, compiling, and packaging configurations, including Linux file paths and expected outputs.
- Include Linux/macOS command-line equivalents (e.g., Bash, zip/unzip) for relevant operations like packaging and inspecting artifacts.
- Present Windows and Linux examples side-by-side or clearly separated, rather than Windows-first.
- Clarify any platform-specific requirements or differences directly in the main flow, not just in notes or external links.
- Add a section or appendix for macOS users, even if only to clarify current limitations and possible workarounds.