Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1376-1400 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/samples/ism-protected/control-mapping.md
...ce/blueprints/samples/ism-protected/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows-specific audit results, tools, and extensions (such as the Microsoft IaaSAntimalware extension and auditing of Windows VMs) without providing equivalent Linux examples or mentioning Linux tools. In several controls, only Windows VMs or Windows web servers are mentioned for auditing or compliance, while Linux systems are addressed less frequently and with less detail. Endpoint protection and antivirus guidance is Windows-centric, and there is a lack of parity in examples or recommendations for Linux environments.
Recommendations
- For every control or recommendation that references Windows VMs, provide equivalent guidance and examples for Linux VMs (e.g., auditing sudoers or root group membership, using Linux-compatible antimalware solutions).
- When mentioning deployment of prerequisites or audit results for Windows, include parallel instructions or references for Linux (e.g., using Azure's Log Analytics Agent on Linux, or Linux security extensions).
- List Linux and Windows examples together, or alternate which platform is mentioned first, to avoid the impression of Windows being the default or primary platform.
- For antivirus and endpoint protection, specify recommended solutions for Linux VMs and virtual machine scale sets, not just Windows.
- Where possible, generalize recommendations to cover both Windows and Linux, or explicitly state when a control is applicable to one OS only.
- Ensure that all Azure Policy definitions and compliance checks referenced are available and documented for both Windows and Linux environments.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/troubleshoot-performance-issues.md
.../articles/frontdoor/troubleshoot-performance-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific network troubleshooting tools (tracert, pathping) and linking to their Windows documentation, without mentioning or providing equivalent Linux tools (such as traceroute, mtr). The only command-line example provided is with curl in Bash, which is cross-platform, but all network path diagnostics are described using Windows terminology and tools, with no Linux or macOS equivalents or examples.
Recommendations
- Include Linux/macOS equivalents for network path diagnostics, such as 'traceroute' and 'mtr', alongside 'tracert' and 'pathping'.
- Provide example commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/terminal) when discussing network troubleshooting steps.
- Link to documentation for Linux/macOS tools (e.g., man pages for traceroute/mtr) in addition to Windows command references.
- Use neutral language when referring to tools (e.g., 'use a tool such as traceroute (Linux/macOS) or tracert (Windows)') rather than defaulting to Windows-first phrasing.
- Where possible, provide screenshots or output samples from both Windows and Linux tools to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/reference/blueprint-functions.md
...governance/blueprints/reference/blueprint-functions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references Azure PowerShell as a primary management tool for Blueprints artifacts, with no mention of Azure CLI or cross-platform alternatives. There are no Linux-specific examples or guidance, and the only tool mentioned for managing Blueprints-as-code is Azure PowerShell, which is historically Windows-centric (though now cross-platform). This suggests a bias toward Windows tooling and omits Linux-first or CLI-based workflows.
Recommendations
- Include Azure CLI examples alongside or instead of Azure PowerShell for managing Blueprints, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide Bash shell examples where appropriate.
- Reference REST API usage with curl or similar Linux-native tools, not just PowerShell.
- Ensure that all code snippets and management instructions are platform-agnostic or provide parallel instructions for both Windows and Linux environments.
- Add a section or note about managing Blueprints from Linux environments, including setup and usage tips.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/overview.md
.../blob/main//articles/governance/blueprints/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for Azure Blueprints does not provide explicit command-line examples, but in the 'Next steps' section, it lists 'Create a blueprint - PowerShell' before mentioning REST API, and does not mention Azure CLI or Bash/Linux-based workflows. This ordering and omission suggest a Windows-first and PowerShell-heavy bias, with missing Linux/CLI examples.
Recommendations
- Add Azure CLI examples and documentation links alongside or before PowerShell examples to ensure Linux and cross-platform parity.
- In the 'Next steps' section, include 'Create a blueprint - Azure CLI' (if supported) or provide Bash scripting guidance for Linux users.
- Review all example sections and ensure that both Windows (PowerShell) and Linux (CLI/Bash) workflows are equally represented and easy to find.
- Avoid listing Windows-specific tools (like PowerShell) before cross-platform or Linux-friendly tools unless there is a technical reason.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/samples/iso27001-shared/control-mapping.md
.../blueprints/samples/iso27001-shared/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias, particularly in sections related to password management and VM auditing. Windows VM password policies are detailed with multiple audit points, while Linux VM password and authentication controls are mentioned less frequently and with less detail. There are no Linux-specific examples or parity in the depth of controls described for Linux systems. Windows terminology and tools are referenced without equivalent Linux alternatives or examples.
Recommendations
- Provide equivalent Linux VM password policy audits (e.g., minimum password length, complexity, password age, reuse restrictions) alongside Windows examples.
- Include Linux-specific examples and guidance for controls, especially where only Windows VMs are mentioned (such as password management and complexity).
- Ensure that for every Windows VM control or audit, a corresponding Linux VM control is described if available, or explicitly state if not applicable.
- Reference Linux-native tools and configuration patterns (such as PAM, passwd, chage, or auditd) where relevant, not just Windows Group Policy or settings.
- Structure lists and descriptions so that Linux and Windows are given equal prominence, rather than listing Windows first or exclusively.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/samples/ism-protected/deploy.md
.../governance/blueprints/samples/ism-protected/deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While it covers both Windows and Linux in the artifact parameters table, Windows terminology and patterns (e.g., 'Administrators group', 'Microsoft IaaSAntimalware extension for Windows servers') are more prominent and detailed. Windows-specific parameters are listed before Linux equivalents in several places, and there are no explicit Linux command-line or management examples. The documentation assumes a GUI-based workflow, which is more common for Windows users, and does not provide CLI or automation guidance that would be familiar to Linux users.
Recommendations
- Provide equivalent Linux examples and explanations wherever Windows-specific terms or parameters are used (e.g., explain Linux admin group management alongside Windows Administrators group).
- Ensure Linux-related parameters and artifacts are given equal prominence and detail as Windows ones in tables and descriptions.
- Include CLI-based deployment instructions (using Azure CLI, Bash, or PowerShell Core cross-platform) in addition to GUI steps, to support Linux-first and automation-focused users.
- Where Windows tools or extensions are mentioned (e.g., Microsoft IaaSAntimalware), mention Linux alternatives or clarify if there is no equivalent.
- Review the order of presentation in tables and lists to avoid consistently listing Windows before Linux, which can reinforce a Windows-first perception.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/samples/iso27001-ase-sql-workload/control-mapping.md
...s/samples/iso27001-ase-sql-workload/control-mapping.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows a moderate Windows bias. While it does mention Linux VMs in some audit policies, Windows-specific controls (such as password complexity, password age, and password history) are described in detail, with no equivalent Linux examples or controls provided. The section on password management focuses exclusively on Windows VMs, and there are no Linux command-line or configuration examples. Windows tools and policies are mentioned explicitly, while Linux is only referenced in passing or in a limited context.
Recommendations
- Provide equivalent Linux VM password policy audit controls and examples, such as auditing /etc/login.defs or PAM configuration for password complexity and aging.
- Include Linux-specific examples or references wherever Windows-specific policies are described, especially in password management and complexity sections.
- When listing audit results or controls, ensure Linux and Windows are treated equally (e.g., 'Show audit results from Linux and Windows VMs that do not enforce password complexity').
- Where possible, add sample Azure Policy definitions or remediation steps for both Windows and Linux platforms.
- Avoid listing Windows controls first or exclusively; present both platforms in parallel for each relevant control.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/samples/swift-2020/deploy.md
...les/governance/blueprints/samples/swift-2020/deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows-specific artifacts and parameters (such as 'Windows VM Administrators group' and 'Domain Name (FQDN) that the Windows VMs should be joined to') are described in detail, while Linux equivalents (such as Linux VM user/group management or domain join) are not mentioned. Windows-related parameters and artifacts are listed before Linux ones in the artifact parameters table. There are no command-line examples, but the focus on Windows management patterns and lack of Linux-specific operational guidance shows a preference for Windows environments.
Recommendations
- Add Linux-specific artifact parameters and descriptions, such as guidance for managing Linux VM users/groups or joining Linux VMs to a domain (e.g., using Azure AD or LDAP).
- Ensure Linux-related artifacts and parameters are listed alongside or before Windows ones to avoid the impression of Windows-first ordering.
- Provide parity in operational guidance for both Windows and Linux VMs, including any relevant configuration or security considerations.
- Include explicit examples or notes for Linux VM scenarios where only Windows scenarios are currently described (e.g., group membership, domain join).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/develop-custom-package/3-test-package.md
...ration/how-to/develop-custom-package/3-test-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific instructions and tools (such as PSExec) are mentioned before their Linux equivalents, and the overall workflow is centered around PowerShell, which is more native to Windows. While Linux examples are present, the documentation assumes familiarity with Windows patterns and tools, and PowerShell is required on both platforms, which may not align with typical Linux workflows.
Recommendations
- Alternate the order of Windows and Linux instructions/examples to avoid always listing Windows first.
- Provide native Linux shell (bash) alternatives where possible, or clarify if PowerShell is a strict requirement for all platforms.
- Mention and link to Linux-native privilege escalation tools (e.g., 'su', 'sudo') before or alongside Windows tools like PSExec.
- Clarify the rationale for using PowerShell on Linux, and provide guidance for users who may not have it installed by default.
- Where possible, use neutral language that does not assume Windows as the primary environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/create-blueprint-rest-api.md
...les/governance/blueprints/create-blueprint-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples for making REST API calls, with no equivalent Linux or cross-platform command-line examples (such as curl or Bash). PowerShell is recommended as the tool for REST API interaction, and no mention is made of Linux-native tools or workflows. This may disadvantage users on Linux or macOS systems, or those preferring non-PowerShell environments.
Recommendations
- Add equivalent examples using curl (or httpie) in Bash to demonstrate REST API calls, including how to acquire Azure access tokens using the Azure CLI (az account get-access-token).
- Explicitly mention that REST API calls can be made from any platform and provide guidance for both Windows and Linux/macOS users.
- Rephrase recommendations to not assume PowerShell as the default tool, and instead present both PowerShell and Bash/curl as options.
- Where PowerShell cmdlets are referenced for parsing JSON (e.g., ConvertFrom-Json), provide Linux alternatives such as jq.
- Consider including a table or section comparing common REST API invocation methods across platforms (PowerShell, Bash/curl, Postman, etc.).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/concepts/assignments.md
...vernance/machine-configuration/concepts/assignments.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing examples and references that are Windows-centric. The primary configuration example uses the 'AzureWindowsBaseline', and the only command-line example for deleting assignments is given in Azure PowerShell, with no equivalent Bash, CLI, or Linux-native example. There are no explicit Linux configuration examples or references to Linux baseline configurations, and the documentation does not mention Linux-specific tools or patterns.
Recommendations
- Include examples using Linux baseline configurations (e.g., 'AzureLinuxBaseline') alongside or before Windows examples.
- Provide command-line examples using Azure CLI (az) and/or Bash scripts for managing machine configuration assignments, not just Azure PowerShell.
- Mention Linux-specific considerations or tools where relevant, such as differences in configuration package structure or assignment behavior.
- Ensure that property descriptions and examples are not Windows-specific and clarify cross-platform applicability.
- Where possible, alternate the order of Windows and Linux examples to avoid implicit prioritization.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/concepts/remediation-options.md
.../machine-configuration/concepts/remediation-options.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell DSC methods (Get/Test/Set) without mentioning Linux equivalents, linking to PowerShell documentation, and omitting any Linux-specific examples or tools. The terminology and references assume familiarity with Windows-centric configuration management, with no mention of how these concepts apply to Linux VMs or what tools/mechanisms are used there.
Recommendations
- Include explicit examples or references for Linux VM configuration management, such as how machine configuration interacts with Linux systems.
- Mention Linux equivalents to PowerShell DSC methods, such as how the GuestConfiguration agent applies configurations on Linux (e.g., via shell scripts, OMI, or other mechanisms).
- Provide links to Linux-specific documentation or clarify cross-platform support where PowerShell/DSC is referenced.
- Add a section or examples that demonstrate remediation and assignment types on Linux, highlighting any differences or additional requirements.
- Balance references to PowerShell with equivalent Linux tools or commands, ensuring parity in guidance for both platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/assign-configuration/terraform.md
...configuration/how-to/assign-configuration/terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides examples for Windows virtual machines, referencing only azurerm_windows_virtual_machine resources. There are no examples or guidance for Linux virtual machines or their configuration assignments. Additionally, the 'get-started' link points specifically to a Windows PowerShell guide, further reinforcing a Windows-centric approach.
Recommendations
- Add parallel examples for Linux virtual machines using azurerm_linux_virtual_machine resources.
- Include built-in configuration assignment examples relevant to Linux (e.g., CIS Linux Baseline).
- Update or supplement the 'get-started' link to include Linux and cross-platform guides, not just Windows PowerShell.
- Explicitly mention support for both Windows and Linux, and provide guidance on any differences in configuration assignment between the two platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/assign-configuration/azure-resource-manager.md
.../how-to/assign-configuration/azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only a Windows-specific built-in configuration example ('AzureWindowsBaseline') and omitting any Linux equivalent. The parameter names and values are tailored to Windows security policies (e.g., password length and age), and there are no examples or references for Linux configurations. Additionally, the referenced tutorial link defaults to Azure PowerShell, a tool more commonly used on Windows.
Recommendations
- Include an example of assigning a built-in Linux configuration (such as 'AzureLinuxBaseline') with relevant Linux parameters.
- Provide guidance or links for both Windows and Linux built-in configurations, clarifying which are available for each OS.
- Ensure that referenced tutorials and links offer parity for both Azure PowerShell and Azure CLI, with explicit Linux instructions where applicable.
- Add a section or note explaining how to adapt the template for Linux VMs, including any differences in configuration names or parameters.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/develop-custom-package/2-create-package.md
...tion/how-to/develop-custom-package/2-create-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily PowerShell-centric, with all command-line examples and tooling instructions provided in PowerShell syntax. Windows-specific paths and outputs are shown by default, and the workflow assumes use of Windows tools (e.g., Expand-Archive, Get-ChildItem) even when discussing Linux configurations. While Linux is mentioned, Linux-specific command-line examples and equivalent native tooling are missing, and Windows examples are consistently presented first or exclusively.
Recommendations
- Provide Linux-native command-line examples (e.g., using bash, unzip, ls, du) alongside or in place of PowerShell commands when discussing Linux configurations.
- Show Linux file paths and outputs (e.g., /home/user/dsc/MyConfig) in relevant examples, not just Windows paths.
- When introducing tools or commands, present Linux equivalents either first or in parallel with Windows (e.g., 'On Windows, use Expand-Archive; on Linux, use unzip').
- Include a full Linux workflow for authoring, compiling, and packaging configurations, not just a Windows-centric one.
- Clarify any platform-specific requirements or differences in the main flow, not just in notes.
- Ensure that all steps (such as renaming files, checking package size, etc.) have Linux-native command alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/develop-custom-package/1-set-up-authoring-environment.md
...velop-custom-package/1-set-up-authoring-environment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation is heavily PowerShell-centric, requiring PowerShell for both Windows and Linux users. Windows is consistently mentioned first in tables and instructions. All examples and tooling are PowerShell-based, with no mention of native Linux tools or workflows, and Linux users are required to install and use PowerShell rather than being offered alternatives.
Recommendations
- Provide native Bash or shell-based alternatives for Linux users where possible, especially for tasks like validation, package management, and scripting.
- Alternate the order of OS presentation, or present Linux and Windows instructions in parallel to avoid always listing Windows first.
- Clarify if PowerShell is a strict requirement for all workflows, or if some steps can be performed using native Linux tools.
- Include Linux-specific troubleshooting tips and considerations, especially around module compatibility and differences in PowerShell behavior on Linux.
- Explicitly state the rationale for requiring PowerShell on Linux, and link to resources for users less familiar with PowerShell in Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/includes/policy/azure-policy-guest-configuration.md
...ce/includes/policy/azure-policy-guest-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows some evidence of Windows bias. In particular, the 'List machines and status of pending reboot' section only references 'WindowsPendingReboot', with no mention of a Linux equivalent or how to check pending reboots on Linux machines. Additionally, the documentation frequently uses Windows-centric resource names and examples (e.g., 'WindowsPendingReboot') and does not provide parity for Linux scenarios in those sections. While there is one explicit Linux example ('installed_application_linux'), the overall structure and example selection tend to favor Windows, and there are missing Linux equivalents for some queries.
Recommendations
- For each scenario that references a Windows-specific resource (such as 'WindowsPendingReboot'), provide the equivalent Linux resource or clarify if one does not exist.
- Add examples that explicitly show how to query for Linux-specific guest configuration assignments, such as pending reboots or compliance checks for Linux machines.
- Where possible, use neutral or parallel examples (e.g., both 'WindowsPendingReboot' and 'LinuxPendingReboot' if available) to demonstrate parity.
- Document any limitations or differences in guest configuration support between Windows and Linux to inform users of potential gaps.
- Review all sections for implicit Windows-first ordering and ensure Linux scenarios are given equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/develop-custom-package/overview.md
...onfiguration/how-to/develop-custom-package/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on PowerShell Desired State Configuration (PSDSC) and the GuestConfiguration PowerShell module, with no Linux-specific examples or tooling mentioned. The only video tutorial provided is based on PowerShell, and there is no equivalent guidance or walkthrough for Linux users. While there is a brief mention of Linux support, the documentation assumes familiarity with Windows/PowerShell workflows and does not provide parity for Linux users.
Recommendations
- Include Linux-specific examples and workflows, such as authoring and testing machine configuration packages using native Linux tools or shell scripts.
- Provide a parallel video or written walkthrough demonstrating the process on a Linux system.
- List Linux prerequisites and environment setup steps alongside Windows instructions.
- Reference Linux DSC resources and modules, and clarify any differences in usage or support.
- Ensure that all steps (authoring, testing, publishing, signing) have Linux-specific guidance where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/whats-new/migrating-from-azure-automation.md
...iguration/whats-new/migrating-from-azure-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on PowerShell-based workflows and tools, with all code examples using PowerShell commands and modules. Windows-centric terminology and tools (such as PowerShell 7, Windows PowerShell, and Windows-specific DSC resources) are used throughout, with little to no mention of Linux equivalents or workflows. Linux is only referenced in passing, and there are no Linux-specific examples or guidance for users managing Linux systems.
Recommendations
- Provide equivalent Linux/Bash/CLI examples for each PowerShell workflow, especially for exporting configurations and managing modules.
- Include explicit instructions and examples for managing DSC configurations on Linux systems, referencing relevant Linux tools and patterns.
- Mention and demonstrate how to use cross-platform tools (such as pwsh on Linux/macOS) and clarify any differences in behavior or requirements.
- Highlight any Linux-specific considerations or limitations in the migration process, and provide troubleshooting steps for common Linux issues.
- Balance the order of presentation so that Linux and Windows are treated equally, rather than defaulting to Windows-first explanations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/develop-custom-package/5-access-package.md
...tion/how-to/develop-custom-package/5-access-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides PowerShell examples and references Azure PowerShell cmdlets for generating SAS tokens, with no equivalent examples for Linux environments (e.g., using Azure CLI, Bash, or cross-platform tools). There is no mention of Linux-native tooling or command-line patterns, and the only code sample assumes a Windows/PowerShell context.
Recommendations
- Add equivalent Azure CLI (az) command examples for generating SAS tokens and managing storage access, which are cross-platform and commonly used on Linux.
- Include Bash shell script examples for common operations, or at least mention how Linux users can perform the same tasks.
- Explicitly state that the PowerShell example is just one way to accomplish the task and provide links or references to Linux-compatible documentation.
- Where possible, use neutral language and tooling (e.g., Azure CLI) in primary examples, and provide PowerShell as an alternative for Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/management-groups/how-to/protect-resource-hierarchy.md
...management-groups/how-to/protect-resource-hierarchy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a detailed Azure PowerShell example for configuring hierarchy settings but does not include equivalent examples for Linux-native tools such as Azure CLI, Bash, or curl. The only command-line automation example is in PowerShell, which is primarily a Windows tool, and there is no mention of Linux or cross-platform alternatives. This may make it less accessible for users on Linux or macOS systems.
Recommendations
- Add equivalent Azure CLI and Bash/curl examples for all REST API operations shown in PowerShell.
- Explicitly mention that the REST API can be called from any platform and provide cross-platform command-line examples.
- Where possible, present Azure CLI or REST/curl examples before or alongside PowerShell to ensure parity.
- Clarify in the documentation that PowerShell is available cross-platform, but also provide native Linux/macOS command examples for user preference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/develop-custom-package/4-publish-package.md
...ion/how-to/develop-custom-package/4-publish-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell examples and cmdlets (e.g., New-AzResourceGroup, New-AzStorageAccount), which are most familiar to Windows users. There are no equivalent examples for Linux users, such as using Azure CLI (az) commands or cross-platform scripting. The workflow and tooling are presented from a Windows-centric perspective, with no mention of Bash, Linux shell, or alternative upload methods outside of PowerShell.
Recommendations
- Add equivalent Azure CLI (az) command examples for each PowerShell example, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include notes or sections specifically addressing Linux/macOS users, highlighting any differences or additional steps required.
- Show how to upload files to Azure Blob Storage using common Linux tools (e.g., az storage blob upload, curl, or Python scripts).
- Present both PowerShell and CLI examples side-by-side or allow users to select their preferred environment.
- Avoid assuming the user is running commands in a Windows environment or Cloud Shell; clarify when steps are platform-agnostic.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/create-policy-definition.md
...chine-configuration/how-to/create-policy-definition.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All code examples use PowerShell, and Windows-specific tools and paths are referenced exclusively. Even when the documentation mentions Linux support, no Linux-specific examples, shell commands, or file paths are provided. Windows is always listed first in parameters and examples, and the only example of a managed identity scenario uses a Windows file path.
Recommendations
- Provide equivalent Linux/Bash examples alongside PowerShell, especially for steps involving package creation, uploading, and policy definition.
- Include Linux file path examples (e.g., /home/user/package.zip) where Windows paths (e.g., C:\Local\Path\To\Package) are shown.
- Demonstrate use of Azure CLI for relevant steps, not just PowerShell, to ensure cross-platform usability.
- Explicitly mention and show how to set up the authoring environment on Linux, including required dependencies and commands.
- When referencing parameters like Platform, alternate the order (Windows/Linux) or show both in examples.
- Clarify any differences or limitations for Linux users, and provide troubleshooting tips specific to Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/overview.md
.../articles/governance/machine-configuration/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell Desired State Configuration (DSC) is emphasized as the primary validation tool for both Windows and Linux, with Chef InSpec only mentioned as an additional tool for Linux. The open-source nxtools module is described as a way to make Linux management easier for PowerShell users, reinforcing a Windows-centric approach. In troubleshooting, the PowerShell example is presented before the Bash example. There are no Linux-native configuration management tools (such as Ansible, Puppet, or native shell scripting) mentioned as alternatives or complements. Most examples and references assume familiarity with Windows/PowerShell tools, and Linux guidance is often presented as an adaptation of Windows patterns.
Recommendations
- Provide Linux-native configuration management options (e.g., Ansible, Puppet, or shell scripting) alongside or as alternatives to PowerShell DSC for Linux.
- Include Linux-first or Linux-parity examples in troubleshooting and operational guidance, not just PowerShell/Bash adaptations.
- Clarify when PowerShell DSC is required on Linux versus when Chef InSpec or other tools are used, and provide guidance for users who prefer not to use PowerShell on Linux.
- Highlight Linux-specific best practices and tools, rather than positioning Linux management as an extension of Windows/PowerShell paradigms.
- Consider including links or references to Linux community resources or documentation for configuration management.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/assign-policy-azurecli.md
...//articles/governance/policy/assign-policy-azurecli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by recommending Visual Studio Code (a Microsoft tool commonly associated with Windows) as the terminal environment, and by not mentioning or providing examples for Linux/macOS terminal usage. The prerequisites and instructions assume a Windows-centric workflow, with no explicit guidance for Linux users. There are no references to Linux-specific tools, shells, or line continuation conventions, and no mention of alternative editors or environments. The documentation does not address potential differences in command syntax or environment setup for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide links to platform-specific installation instructions.
- In the prerequisites, suggest alternative terminal environments and editors (e.g., GNOME Terminal, Terminal.app, nano, vim) alongside Visual Studio Code.
- Note that line continuation with backslash (\) works in Bash (Linux/macOS) but not in Windows CMD; clarify for PowerShell users if needed.
- Add a section or callout for Linux/macOS users, highlighting any differences in command usage or environment setup.
- Ensure that all instructions and examples are tested and applicable on Linux/macOS, and explicitly state this in the documentation.