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 26-50 of 186 flagged pages
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 exhibits a moderate Windows bias. Windows-specific concepts (e.g., 'Windows VM Administrators group', 'Domain Name (FQDN) that Windows VMs should be joined to') are described in detail, while Linux equivalents (such as Linux admin groups or domain join procedures) are not mentioned. Windows VM-related parameters and artifacts are listed before Linux ones in the artifact parameters table. There are no examples or guidance for Linux-specific administrative tasks, and the documentation assumes familiarity with Windows-centric patterns.
Recommendations
- Add equivalent Linux examples and descriptions for administrative group membership and domain join procedures.
- Ensure Linux-related artifacts and parameters are given equal prominence and detail as Windows ones.
- Provide guidance or references for Linux VM management, such as joining Linux VMs to a domain (e.g., using LDAP/SSSD/AD integration) and managing admin users.
- Alternate the order of Windows and Linux examples in tables and lists to avoid implicit prioritization.
- Clarify which steps are OS-agnostic and which require OS-specific actions, with links to relevant Linux documentation.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits moderate Windows bias, particularly in the sections related to password management and complexity enforcement, where only Windows VM policies and audit results are described in detail. Linux VM controls are mentioned in some sections (e.g., passwordless accounts, passwd file permissions), but there is a lack of parity in examples and controls for password complexity and management. Windows-specific audit items are listed explicitly, while equivalent Linux controls are either missing or less detailed.
Recommendations
- Add equivalent Linux VM password complexity and management audit controls and examples, such as enforcing minimum password length, password age, and password reuse policies for Linux VMs.
- Provide Linux-specific examples and policy definitions wherever Windows VM controls are described, ensuring parity in compliance coverage.
- Where audit results or controls are listed for Windows VMs, include corresponding Linux VM controls or clarify if such controls are not available.
- Consider listing Linux controls before or alongside Windows controls to avoid 'windows_first' ordering bias.
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 exhibits a moderate Windows bias. Several control mappings and policy definitions reference Windows-specific concepts, such as auditing Windows VM Administrators group membership, password policies, and deploying Microsoft IaaSAntimalware extension for Windows Server, often without equivalent Linux examples or parity in detail. In some sections, Windows VM audit actions are listed before Linux equivalents, and some controls (e.g., password complexity, antimalware) are only described for Windows. Linux is mentioned in some controls, but not as consistently or thoroughly as Windows.
Recommendations
- Ensure every Windows-specific control or example has a Linux equivalent, especially for password policies, administrator group membership, and antimalware solutions.
- Present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first.
- Include references to common Linux tools or practices (e.g., auditd, fail2ban, ClamAV, Linux password policies) where relevant.
- Clarify which controls are OS-agnostic and which require OS-specific implementation, and provide guidance for both platforms.
- Where only Windows is supported by a policy, explicitly note the limitation and suggest alternative approaches for Linux.
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 Windows-specific configuration names (e.g., 'WindowsPendingReboot') are used without Linux equivalents or explanation. In most sections, Windows/PowerShell is mentioned before Linux, and there are no explicit Linux shell examples (e.g., Bash), nor guidance for Linux-specific guest configuration queries (except for a single 'installed_application_linux' example). This creates friction for Linux/macOS users, who may need to infer or adapt instructions themselves.
Recommendations
- Provide explicit Bash or shell examples for Linux/macOS users alongside PowerShell.
- Where Windows-specific configuration names are used (e.g., 'WindowsPendingReboot'), clarify if Linux equivalents exist and provide those queries.
- Alternate the order of examples so Linux is not always after Windows/PowerShell.
- Add notes or sections explaining differences in guest configuration assignments between Windows and Linux.
- Ensure that all queries and instructions are cross-checked for Linux applicability, not just Windows.
Governance
How to create a machine configuration assignment using Terraform
...configuration/how-to/assign-configuration/terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides examples for assigning configurations to Windows virtual machines using Terraform. All resource references and code samples use azurerm_windows_virtual_machine, with no mention of Linux equivalents (e.g., azurerm_linux_virtual_machine). The built-in configuration example is also Windows-specific (AzureWindowsBaseline), and there are no Linux-focused configurations or instructions. The 'get-started' link references Windows PowerShell, further reinforcing the Windows bias.
Recommendations
- Add equivalent examples for Linux virtual machines using azurerm_linux_virtual_machine.
- Include built-in configuration assignment examples for Linux (e.g., AzureLinuxBaseline).
- Provide guidance on Linux-specific parameters and configuration options.
- Reference Linux/macOS setup guides alongside Windows PowerShell in the 'get-started' section.
Governance
Remediation options for machine configuration
.../machine-configuration/concepts/remediation-options.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references PowerShell DSC methods (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 equivalent Linux configuration management tools or patterns. The documentation assumes familiarity with Windows/PowerShell concepts and omits Linux-specific guidance.
Recommendations
- Add examples and explanations for Linux VM remediation, including how machine configuration works with Linux guest agents.
- Reference Linux equivalents to PowerShell DSC, such as Open Management Infrastructure (OMI) or native configuration management tools (e.g., Ansible, Chef, or native shell scripts).
- Clarify whether the GuestConfiguration module and assignment types are supported and behave identically on Linux/macOS VMs.
- Provide links to Linux/macOS-specific documentation where relevant.
- Include sample policy definitions and remediation flows for Linux VMs.
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
Windows Tools
Summary
The documentation provides examples and built-in configuration assignments that are Windows-centric, specifically referencing 'AzureWindowsBaseline' and password policies typical of Windows environments. There are no examples or references to Linux-specific configurations, nor are Linux built-in baselines mentioned. Additionally, the link to the ARM template tutorial defaults to Azure PowerShell, a Windows-preferred tool.
Recommendations
- Add examples for assigning Linux built-in configurations, such as 'AzureLinuxBaseline', with relevant parameters.
- Include references and links to Linux/macOS-friendly tools (e.g., Azure CLI, Bash) in tutorials.
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Clarify which built-in configurations are available for Linux and how to use them.
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, which is cross-platform but more familiar to Windows users. Windows installation instructions and examples are presented before Linux equivalents, and Linux users are required to use a prerelease version of a key module, while Windows users get a stable release. There are no Linux-native shell (bash) examples or troubleshooting notes for Linux-specific issues, and the documentation assumes PowerShell is the primary interface for all platforms.
Recommendations
- Provide bash or native Linux shell examples for installation and validation steps, where possible.
- Include troubleshooting notes or caveats for Linux users, especially regarding the use of prerelease modules.
- Clarify any limitations or differences in module functionality between Windows and Linux.
- Present Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
- Offer guidance for installing PowerShell on Linux for users who may not have it pre-installed.
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 (including those for Linux) using PowerShell syntax and tools. Windows-specific paths and outputs are shown throughout, and the process for Linux users is less clearly documented, with references to external articles instead of in-place examples. There is a notable lack of native Linux shell (bash) examples, and the workflow assumes a PowerShell environment even for Linux tasks.
Recommendations
- Provide equivalent bash (or other native Linux shell) examples for compiling and packaging configurations on Linux.
- Show Linux file paths and outputs alongside or instead of Windows paths (e.g., use /home/user/ instead of C:\dsc\).
- Clarify if and how the process can be completed using native Linux tools, or explicitly state PowerShell Core is required on Linux.
- Include a full, in-place Linux example for authoring, compiling, and packaging a configuration, rather than referring users to external articles.
- Mention and demonstrate Linux-native tools (e.g., zip, unzip, mv) for packaging and inspecting artifacts.
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 page demonstrates a moderate Windows bias. Windows examples and instructions are presented first, with detailed PowerShell scripts and references to Windows certificate stores and tools. Linux instructions are present but less detailed, and Windows-centric tools (PowerShell, certificate stores) are emphasized throughout, including in certificate export and installation steps. References and example links are also Windows-focused.
Recommendations
- Present Linux and Windows examples in parallel or alternate order to avoid Windows-first bias.
- Expand Linux instructions to include more detail, such as certificate installation commands and verification steps.
- Provide Linux-specific example links and references, such as using Azure Policy to deploy Linux certificates.
- Include non-PowerShell alternatives for Linux users, such as bash scripts or native Linux commands for certificate handling.
- Clarify cross-platform differences in prerequisites and tooling, and link to Linux documentation where appropriate.
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 presented as the primary validation tool for both Windows and Linux, with Chef InSpec only mentioned for Linux. The open-source nxtools module is described as a PowerShell-based solution for Linux management, reinforcing PowerShell as the preferred cross-platform tool. Troubleshooting and log collection examples are provided for both Windows (PowerShell) and Linux (Bash), but the Windows example appears first. References to Azure PowerShell and Windows-specific portal links are frequent, and some policy definitions and troubleshooting steps are more detailed for Windows. Linux alternatives and native tools (like Ansible, shell scripts, or native package managers) are not discussed.
Recommendations
- Provide Linux-native configuration management examples (e.g., Ansible, shell scripts) alongside PowerShell DSC.
- Mention and document Linux-native tools for validation and management, not just PowerShell-based solutions.
- Present Linux and Windows examples in parallel, alternating which comes first.
- Expand troubleshooting and log collection sections to include more Linux-specific tools and approaches.
- Clarify when PowerShell DSC is required on Linux and offer alternatives for environments where PowerShell is not preferred.
- Include links to Linux-specific documentation and community resources.
Governance
Details of the policy definition structure aliases
...vernance/policy/concepts/definition-structure-alias.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows-oriented tools (Visual Studio Code extension and Azure PowerShell) before cross-platform options (Azure CLI and REST API). PowerShell examples are more detailed, including advanced usage notes, while Linux/macOS equivalents (CLI) are less emphasized and lack parity in depth.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Expand Azure CLI section to include advanced usage (e.g., filtering for modifiable aliases), matching the PowerShell note.
- Explicitly mention platform compatibility for each method (e.g., 'Azure CLI is available on Windows, Linux, and macOS').
- Provide links or references to Linux/macOS-specific tooling or workflows where relevant.
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 bias toward Windows by providing only Windows-style execution examples (using .exe and backtick line continuations) and omitting explicit Linux/macOS instructions for running the .NET Core application. There is no mention of Linux-specific patterns, such as using './mgCreate' or handling permissions, nor are there examples for bash or zsh shells.
Recommendations
- Add Linux/macOS command examples for running the .NET Core application (e.g., './mgCreate {tenantId} ...').
- Clarify that the published executable may have a different extension or invocation method on non-Windows platforms.
- Mention any required permissions or execution flags for Linux/macOS (e.g., 'chmod +x mgCreate').
- Present both Windows and Linux/macOS examples side by side, or note platform differences explicitly.
- Avoid using Windows-specific line continuation characters (backticks) in generic examples; use '\' for bash/zsh or show both.
Governance
Troubleshooting Azure Machine Configuration
...onfiguration/overview/04-operations-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
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 solution for Linux management specifically for PowerShell users. In several sections, Windows examples and terminology (such as PowerShell scripts and Windows-specific log locations) are presented before their Linux equivalents. The documentation does provide Linux examples and log paths, but the overall framing and tooling recommendations favor Windows and PowerShell-centric workflows.
Recommendations
- Provide equal emphasis on Linux-native tools (e.g., Bash, shell scripting, native DSC modules) alongside PowerShell.
- Mention Linux examples and log paths before or alongside Windows examples to avoid Windows-first ordering.
- Highlight non-PowerShell options for Linux users, such as Ansible, shell scripts, or native configuration management tools.
- Clarify that nxtools is optional and provide alternatives for Linux users who do not use PowerShell.
- Ensure that all troubleshooting steps and tools are equally documented for both platforms.
Governance
Azure Automation State Configuration to machine configuration migration planning
...iguration/whats-new/migrating-from-azure-automation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with all code examples using PowerShell cmdlets and modules. There is minimal mention of Linux/macOS workflows, and Linux-specific guidance is limited to a brief troubleshooting note. No Linux shell or cross-platform examples are provided, and Windows tools and patterns are presented first and exclusively throughout the migration process.
Recommendations
- Provide equivalent Linux/macOS examples using native shell commands or cross-platform PowerShell Core usage.
- Explicitly document any differences in module management or configuration export/import for Linux environments.
- Add troubleshooting and migration guidance for Linux users, including common issues and workarounds.
- Highlight cross-platform compatibility and clarify which steps are OS-agnostic.
- Include references to Linux DSC documentation and best practices alongside Windows links.
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 First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It centers on PowerShell DSC (a Windows-centric technology), references Windows PowerShell versions and commands, and describes migration steps using PowerShell cmdlets. There are no Linux-specific examples, nor is there guidance for Linux VM scenarios. Windows tools and terminology (e.g., Local Configuration Manager, PowerShell modules, DSC extension for Windows) are used exclusively or first, with no mention of Linux equivalents or considerations.
Recommendations
- Add explicit guidance for Linux VMs, including how to check for DSC extension usage and migrate configurations.
- Provide Linux/macOS-specific examples for commands and configuration packaging, including Bash or CLI alternatives where possible.
- Clarify whether machine configuration supports Linux VMs and how migration differs for non-Windows platforms.
- Mention Linux-compatible modules, configuration formats, and any platform-specific limitations.
- Reorder examples or sections so that Linux and Windows are treated equally, or at least acknowledge platform differences early.
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 exhibits a moderate Windows bias. While it primarily uses Azure CLI (which is cross-platform), command examples and syntax explanations are heavily oriented toward PowerShell and Windows conventions. Escaping and file referencing are described in terms of PowerShell syntax, with only brief, secondary notes about Bash. There are no explicit Linux/macOS command examples, and Windows tools (PowerShell, Visual Studio Code) are mentioned first or exclusively in prerequisites and workflow descriptions.
Recommendations
- Provide explicit Bash/Linux/macOS command examples alongside PowerShell, including correct escaping and file referencing syntax.
- List cross-platform tools (e.g., VS Code, Azure CLI) before Windows-specific ones in prerequisites.
- Add a dedicated section or callouts for Linux/macOS users, clarifying differences in shell syntax and usage.
- Where PowerShell-specific syntax is shown, immediately follow with the Bash equivalent.
- Clarify that Azure CLI works natively on Linux/macOS, and provide links to installation instructions for those platforms.
Governance
Azure Policy definitions modify effect
...n/articles/governance/policy/concepts/effect-modify.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page shows a Windows bias primarily through its exclusive use of Azure PowerShell for listing modifiable aliases, without mentioning or providing equivalent CLI (az) or REST API commands. No Linux/macOS-specific tools or examples are referenced, and the only command-line example is PowerShell-centric. This may create friction for users on Linux or macOS who typically use Bash, Azure CLI, or REST API.
Recommendations
- Provide equivalent Azure CLI (az policy alias list) or REST API examples for listing modifiable aliases.
- Explicitly mention that the PowerShell command is one option, and offer alternatives for users on Linux/macOS.
- Add notes or examples using Bash or Azure CLI where applicable.
- Ensure that all command-line instructions are cross-platform or alternatives are given.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for command-line operations, but PowerShell examples are consistently presented after CLI examples and in greater detail, including advanced usage (background jobs, object inspection). There is a notable emphasis on PowerShell-specific patterns and terminology, which are native to Windows environments. No Linux/macOS-specific shell examples (e.g., Bash) are given, and PowerShell is treated as a primary tool for scripting and automation, which may create friction for Linux/macOS users.
Recommendations
- Add explicit Bash shell examples for REST API calls using curl, especially in sections describing REST usage.
- Clarify that Azure CLI is cross-platform and can be used equally on Linux/macOS/Windows.
- Balance the level of detail between PowerShell and CLI examples, ensuring CLI examples cover advanced scenarios (e.g., asynchronous operations, filtering, background execution) where possible.
- Mention that Azure PowerShell is available cross-platform, but highlight CLI and REST as first-class options for Linux/macOS users.
- Consider reordering examples to present CLI before PowerShell or interleave them to avoid implicit prioritization.
Governance
Programmatically create policies
...es/governance/policy/how-to/programmatically-create.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, ARMClient) are emphasized, with PowerShell examples and instructions presented before Azure CLI and REST API equivalents. Prerequisites and installation instructions often reference Windows first or exclusively. There is little to no mention of Linux/macOS-specific considerations, and ARMClient is a Windows-centric tool. Some commands and installation links are Windows-specific, and PowerShell is used for critical steps without Linux alternatives.
Recommendations
- Provide explicit Linux/macOS installation instructions for Azure CLI and ARMClient, or recommend cross-platform alternatives to ARMClient.
- Include bash or shell script examples alongside PowerShell for policy creation and assignment.
- Clarify which tools and commands are cross-platform, and note any platform-specific limitations.
- Reorder examples so that Azure CLI (cross-platform) is presented before or alongside PowerShell.
- Add troubleshooting notes for Linux/macOS users where tool behavior may differ.
Governance
Azure Automanage Best Practices to Azure Policy migration planning
...olicy/how-to/migrate-from-automanage-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Several sections, such as Microsoft Antimalware and Windows Admin Center, focus exclusively on Windows tools and extensions, with no Linux equivalents or alternatives mentioned. Windows-specific features (e.g., IaaSAntimalware, Windows Admin Center) are described in detail, while Linux management tools are not discussed. In some lists, Windows examples precede Linux ones, and certain features (e.g., antimalware) are only described for Windows. While some services (Change Tracking, Update Manager) acknowledge Linux support, the overall emphasis and example selection favor Windows environments.
Recommendations
- Include Linux-specific examples and tools where relevant, such as antimalware solutions for Linux VMs.
- Provide parity in extension and policy deployment instructions for both Windows and Linux VMs.
- Add references to Linux management tools (e.g., Cockpit, SSH, cloud-init) where Windows Admin Center is mentioned.
- Ensure that lists and examples alternate or equally represent Windows and Linux scenarios.
- Clarify which features are Windows-only and suggest Linux alternatives or workarounds.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias, primarily through the repeated use of Azure PowerShell as the main example for on-demand evaluation scans and policy duplication tasks. No equivalent CLI (az), Bash, or Linux/macOS-specific instructions are provided for these critical operations. PowerShell is mentioned before REST API, and no cross-platform alternatives are shown, which may create friction for Linux/macOS users.
Recommendations
- Add Azure CLI (az) examples alongside or before PowerShell for all tasks, especially for on-demand evaluation scans and policy duplication.
- Include Bash or shell script examples where relevant.
- Explicitly note cross-platform compatibility for SDKs and tools.
- Where PowerShell is referenced, clarify that equivalent functionality is available via Azure CLI or REST API and link to those instructions.
- Ensure that instructions for policy definition duplication and other management tasks are not PowerShell-exclusive.
Governance
Tutorial: Build policies to enforce compliance
...icles/governance/policy/tutorials/create-and-manage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are given in detail and are presented before Azure CLI equivalents. File path examples use Windows-style paths (e.g., 'c:\policies\coolAccessTier.json') without showing Linux/macOS alternatives. There are no explicit Linux/macOS shell examples (e.g., Bash), and instructions for local file usage do not mention Linux paths or considerations. The REST API and Azure CLI sections are cross-platform, but the overall example ordering and details favor Windows/PowerShell users.
Recommendations
- Add Linux/macOS file path examples alongside Windows paths in PowerShell and CLI sections.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide sample Bash usage where relevant.
- Where PowerShell is used, clarify that Azure CLI is available and cross-platform, and consider presenting CLI examples before PowerShell.
- Include notes or sections for Linux/macOS users regarding file locations, shell environments, and any platform-specific considerations.
- Ensure screenshots and UI instructions do not assume Windows-only conventions (e.g., right-click terminology).
Governance
Tutorial: Disallow resource types in your cloud environment
...es/governance/policy/tutorials/disallowed-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial exclusively uses the Azure portal (a web UI) for all steps, which is platform-agnostic, but when discussing exemptions, it mentions Azure CLI, Azure PowerShell, and ARM templates as alternatives. However, there are no concrete command-line examples for Linux/macOS users (e.g., Azure CLI), and PowerShell is mentioned before CLI, suggesting a subtle Windows-first bias. No Linux-specific tools or workflows are described, and no examples are provided for non-Windows environments.
Recommendations
- Add step-by-step examples using Azure CLI for assigning policies, creating exemptions, and cleaning up resources.
- Explicitly mention that Azure CLI is cross-platform and provide sample commands for Linux/macOS users.
- Ensure that PowerShell and CLI examples are presented together, or CLI examples are shown first to avoid Windows-first perception.
- Include notes or links for Linux/macOS users on installing and using Azure CLI.
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-assigned identities to VMs and VMSS. All CLI examples are exclusively in PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
- Add equivalent Azure CLI (az policy definition, az policy assignment, az policy remediation) examples for all PowerShell commands.
- Explicitly mention that PowerShell commands can be run cross-platform, or provide guidance for Linux/macOS users.
- Reorder or parallelize example sections so that CLI examples are not Windows/PowerShell-first.
- Include a note about tool parity and link to Azure CLI documentation.