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 251-275 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-runbook-execution.md
...n//articles/automation/automation-runbook-execution.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples use PowerShell syntax, and the only scripting environments discussed in detail are PowerShell, PowerShell Workflow, and graphical runbooks (which are Windows-centric). Windows tools and concepts (such as WMI, .NET Framework, UAC, and Windows file paths like C:\temp) are referenced exclusively or before any Linux equivalents. There are no examples or explicit guidance for Linux shell scripting, Bash, or Python runbooks, and Linux-specific operational patterns are not discussed. The documentation assumes a Windows-centric perspective throughout.
Recommendations
- Add examples and guidance for Python runbooks, which are supported in Azure Automation and are more cross-platform.
- Include Linux/Bash scripting examples where relevant, especially in sections on error handling, temporary storage, and process execution.
- When discussing file paths (e.g., C:\temp), also mention Linux equivalents (e.g., /tmp) and clarify OS-specific differences.
- Reference Linux tools and APIs (such as /proc, systemd, or Linux performance counters) alongside Windows tools like WMI.
- In module and environment discussions, clarify which modules and features are available or behave differently on Linux Hybrid Runbook Workers.
- Provide parity in troubleshooting and operational guidance for both Windows and Linux environments.
- Explicitly mention Linux support and limitations in each relevant section, not just in security or monitoring contexts.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-runbook-gallery.md
...ain//articles/automation/automation-runbook-gallery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with all examples and workflows centered around PowerShell Gallery, PowerShell scripts, and modules. There is little to no mention of Linux-specific tools, workflows, or examples, and the only reference to Linux is in a tag suggestion. The documentation assumes familiarity with Windows/PowerShell paradigms and does not provide parity for Linux users or Bash/Python-first workflows.
Recommendations
- Include explicit examples and workflows for Linux users, such as using Bash scripts or Python runbooks, and how to import and manage them in Azure Automation.
- Mention and demonstrate how to use Linux-based automation modules or scripts, and reference Linux package repositories or community sources where relevant.
- Provide parity in documentation structure: when introducing PowerShell Gallery, also mention alternatives or equivalents for Linux users (e.g., PyPI for Python runbooks).
- Add sample runbooks and modules that target Linux automation scenarios, such as managing Linux VMs, using SSH, or handling Linux-specific tasks.
- Balance the order of presentation so that Linux and Windows/PowerShell approaches are introduced together, or alternate which comes first.
- Clarify in notes or introductory sections that Azure Automation supports both Windows and Linux runbooks, and link to relevant Linux-focused documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-use-copilot-generate-image-definition-file.md
...x/how-to-use-copilot-generate-image-definition-file.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing only Windows-specific tools (WinGet, PowerShell, UAC), omitting Linux equivalents or examples. All example prompts and workflows assume a Windows environment, and there is no mention of Linux package managers, shells, or validation steps. The documentation positions Windows tools and patterns as the default or only supported option, without clarifying cross-platform support or providing parity for Linux users.
Recommendations
- Explicitly state whether Dev Box customizations and the agentic workflow support Linux-based Dev Boxes or only Windows.
- If Linux is supported, provide equivalent examples using Linux package managers (e.g., apt, yum) and shell scripts (e.g., bash) alongside WinGet and PowerShell.
- Include sample natural language prompts for configuring Linux development environments (e.g., installing build-essential, Python, Docker, etc.).
- Clarify in the prerequisites and supported scenarios whether the workflow is Windows-only or cross-platform.
- If only Windows is supported, make this limitation clear at the top of the documentation to set user expectations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-runbook-graphical-error-handling.md
...omation/automation-runbook-graphical-error-handling.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All error handling concepts and examples are presented exclusively in the context of PowerShell cmdlets and Windows-centric tools, with no mention of Linux, Bash, or cross-platform scripting. The terminology, examples, and recommended practices assume the use of PowerShell and Windows-based automation, omitting Linux-native equivalents or guidance for users running graphical runbooks with Linux hybrid workers.
Recommendations
- Include examples and explanations for error handling in graphical runbooks that use Linux hybrid workers, such as using Bash or Python script activities.
- Mention that Azure Automation supports Linux runbooks and clarify any differences in error handling or activity configuration between Windows and Linux environments.
- Provide parallel examples using Bash or Python activities, showing how to handle errors and configure error links in non-PowerShell contexts.
- Avoid assuming PowerShell as the default or only scripting language; use more neutral language or explicitly address both Windows and Linux scenarios.
- Reference Linux tools and error handling patterns (e.g., exit codes, stderr handling) alongside PowerShell cmdlets.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/enable-change-tracking-at-scale-policy.md
...nge-tracking/enable-change-tracking-at-scale-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation claims to support both Windows and Linux VMs, but it exhibits subtle Windows bias. Windows-specific features (Registry, Files, Software) are listed explicitly, while Linux equivalents are less detailed. The policy breakdown lists 'Configure ChangeTracking Extension for Windows virtual machines' before the Linux equivalent, and there are no Linux-specific examples, screenshots, or tool mentions. The documentation also references Windows concepts (like Registry) without Linux parallels, and omits any command-line or shell examples for Linux users.
Recommendations
- Provide explicit Linux examples and screenshots, especially for Linux file and software tracking.
- List Linux and Windows options in parallel, or alternate which is mentioned first.
- Include Linux-specific details (e.g., tracked file types, package managers, configuration files) alongside Windows Registry and Software.
- Add command-line examples for both PowerShell (Windows) and Bash (Linux) where relevant.
- Clarify Linux support by mentioning any limitations or differences in feature parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-scenario-aws-deployment.md
...icles/automation/automation-scenario-aws-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (PowerShell Gallery, PowerShell ISE) for all examples and instructions. There are no references to Linux-based automation, Bash, AWS CLI (outside PowerShell), or cross-platform scripting options. All steps assume a Windows/PowerShell environment, and Linux users are not provided with equivalent guidance.
Recommendations
- Provide equivalent examples using AWS CLI and Bash scripts for Linux/macOS users.
- Mention and demonstrate how to use Azure Automation with Python runbooks, which are cross-platform.
- Include instructions for installing and using the AWS CLI in Azure Automation, not just the PowerShell module.
- Add notes or sections clarifying how Linux users can author, test, and deploy runbooks (e.g., using Cloud Shell, VS Code, or other cross-platform tools).
- Balance references to PowerShell Gallery with links to AWS CLI documentation and PyPI (for Python modules) where appropriate.
- Avoid assuming the use of PowerShell ISE or other Windows-only tools; suggest VS Code or other cross-platform editors.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-secure-asset-encryption.md
...icles/automation/automation-secure-asset-encryption.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for all command-line operations, referencing Windows-centric tools (Azure Az PowerShell module), and omitting equivalent instructions for Linux users (e.g., Azure CLI, Bash, or cross-platform scripting). REST API examples are present, but when it comes to scripting, only PowerShell is covered. There are no Linux shell or Azure CLI examples, and PowerShell is always presented first and exclusively.
Recommendations
- Add Azure CLI (az) examples alongside all PowerShell examples for each operation (assigning identities, setting access policies, rotating keys, etc.), as Azure CLI is cross-platform and widely used on Linux.
- Include Bash script snippets where appropriate to demonstrate automation for Linux users.
- Explicitly mention that the PowerShell examples can be run on PowerShell Core on Linux/macOS, or clarify platform requirements.
- Reorder or parallelize example sections so that PowerShell and CLI/Bash examples are presented together, not with PowerShell always first.
- Reference and link to Azure CLI documentation as prominently as PowerShell documentation.
- Consider including a table comparing PowerShell and CLI commands for common tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-scenario-using-watcher-task.md
...s/automation/automation-scenario-using-watcher-task.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, using PowerShell exclusively for scripting and examples, referencing Windows-style paths (e.g., D:\examplefiles), and omitting any mention of Linux or cross-platform alternatives. There are no Bash or Linux shell examples, and the instructions assume the use of Windows tools and conventions throughout.
Recommendations
- Provide equivalent Bash or shell script examples for Linux-based Hybrid Runbook Workers.
- Include instructions and screenshots that use Linux file paths (e.g., /home/examplefiles) alongside Windows examples.
- Clarify that Azure Automation Hybrid Runbook Workers can run on Linux, if supported, and describe any differences in setup or usage.
- Mention and demonstrate how to create test files and run watcher tasks using Linux command-line tools (e.g., touch ExampleFile1.txt).
- Ensure terminology and instructions are inclusive of both Windows and Linux users, or explicitly state if only Windows is supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-security-guidelines.md
.../articles/automation/automation-security-guidelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific installation instructions and tools (such as the Hybrid Runbook Worker VM extension with '?tabs=windows'), without mentioning or linking to Linux equivalents. All examples and guidance for Hybrid Runbook Worker installation, management, and unregistration are given with Windows as the default or only context. There is no mention of Linux-based Hybrid Runbook Workers, their installation, or security considerations, and no Linux-specific examples or links are provided.
Recommendations
- Include parallel instructions and links for Linux-based Hybrid Runbook Worker installation, management, and unregistration wherever Windows-specific guidance is given.
- When referencing documentation links with '?tabs=windows', also provide or mention the '?tabs=linux' equivalent.
- Explicitly state that Hybrid Runbook Workers can be installed on both Windows and Linux, and provide security best practices for both platforms.
- Add Linux-specific considerations or examples for authentication, permissions, and network isolation where relevant.
- Review the document for any other implicit assumptions of a Windows environment and ensure Linux parity in all sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-manage-send-joblogs-log-analytics.md
...mation/automation-manage-send-joblogs-log-analytics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the example tool for accessing job logs outside the portal, mentioning PowerShell error streams, and omitting any mention of Linux tools or command-line equivalents. There are no examples or guidance for users working from Linux environments or using cross-platform tools like Azure CLI. The documentation assumes familiarity with Windows-centric patterns and does not provide parity for Linux users.
Recommendations
- Include examples using Azure CLI (az) for querying and managing Automation job logs, alongside or instead of PowerShell.
- Explicitly mention that job logs and streams can be accessed from both Windows and Linux environments, and provide instructions for both.
- When discussing error streams or debugging, clarify how these concepts map to both PowerShell and other scripting languages (e.g., Python, Bash) that can be used in Azure Automation.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
- Avoid language that assumes PowerShell is the only or primary interface for automation, and ensure screenshots and walkthroughs are platform-neutral where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-security-overview.md
...n//articles/automation/automation-security-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the default automation interface, omitting Linux/Unix shell or CLI examples, and not mentioning Linux-native tools or patterns. The language and examples assume a Windows-centric environment, with no guidance for users operating from Linux systems or using Bash/CLI tools. This may hinder Linux users from effectively leveraging Azure Automation.
Recommendations
- Include equivalent Bash or Azure CLI examples alongside PowerShell cmdlets for authentication and automation tasks.
- Explicitly mention that Azure Automation supports both Windows and Linux Hybrid Runbook Workers, and provide examples for each.
- Reference Linux-native tools and authentication patterns (such as using managed identities with Bash scripts or Python on Linux).
- Clarify that runbooks can be authored in multiple languages (PowerShell, Python, etc.) and provide cross-platform code samples.
- Add a section or callout for Linux users, outlining any differences or additional steps required for authentication and automation from Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/rollback-on-error.md
.../azure-resource-manager/templates/rollback-on-error.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents PowerShell examples before Azure CLI, and the PowerShell examples use Windows-style file paths (e.g., c:\MyTemplates\azuredeploy.json). There are no explicit Linux shell or Bash examples, and the use of PowerShell as the first example and Windows file paths may signal a Windows-centric approach.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI (cross-platform) examples first to avoid the impression of Windows-first bias.
- In PowerShell examples, use environment-agnostic file paths or provide both Windows and Linux path examples.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and consider adding Bash shell examples or notes for Linux users.
- Where appropriate, add notes or examples for Linux-specific considerations (such as file path formats or shell syntax differences).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-use-azure-ad.md
...b/main//articles/automation/automation-use-azure-ad.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell environments. All examples and instructions are provided exclusively for Windows PowerShell, with explicit requirements for Windows-specific tools (e.g., Windows Management Framework, .NET Framework, Microsoft Online Services Sign-In Assistant). There are no references to Linux, macOS, or cross-platform PowerShell Core usage, nor are there any CLI or Bash examples. The documentation assumes the user is on Windows and does not mention or support alternative platforms.
Recommendations
- Add equivalent instructions and examples for Linux and macOS environments, including installation steps for PowerShell Core (pwsh) and Az modules on those platforms.
- Provide Azure CLI (az) command examples for authentication and credential management, as Azure CLI is cross-platform.
- Clarify which steps are Windows-specific and offer alternative guidance for non-Windows users.
- Mention and support PowerShell Core (7+) as a cross-platform option, and note any differences or limitations compared to Windows PowerShell.
- Avoid requiring Windows-only tools (e.g., Microsoft Online Services Sign-In Assistant) where possible, or provide alternatives for Linux/macOS.
- Reorder sections or provide parallel instructions so that Linux/macOS users are not treated as an afterthought.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/enable-change-tracking-at-scale-machines-blade.md
...king/enable-change-tracking-at-scale-machines-blade.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page, while stating applicability to both Windows and Linux VMs, demonstrates subtle Windows bias. Windows-specific features (Registry, Files, Software) are listed explicitly, while Linux equivalents are less detailed. There are no Linux-specific examples or terminology (e.g., Linux package inventory, configuration files), and the mention of Windows artifacts precedes Linux ones. No Linux command-line or tool references are present, and screenshots focus on generic or Windows-centric UI elements.
Recommendations
- Explicitly mention Linux-specific tracked items (e.g., package managers, configuration files) alongside Windows artifacts.
- Provide examples or screenshots that show Linux VMs and their inventory/change tracking features.
- Balance the order of mention: alternate or group Windows and Linux features together, rather than listing Windows first.
- Include references to Linux tools or concepts where relevant (e.g., tracked files in /etc, package inventory via apt/yum/rpm).
- Ensure that any advanced or troubleshooting steps include both Windows and Linux command-line examples if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/change-tracking-data-collection-rule-creation.md
...cking/change-tracking-data-collection-rule-creation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed Windows registry settings, file paths, and a dedicated note with Windows file path examples, while Linux-specific configuration is less detailed and lacks equivalent example sections. Windows tools and patterns (such as registry keys and drive letter paths) are heavily referenced, and Windows settings are listed before Linux settings throughout.
Recommendations
- Add a dedicated example section for Linux file settings, similar to the Windows file settings note, using typical Linux paths and options.
- Provide more detailed Linux-specific configuration examples, such as monitoring /etc, /var/log, or other relevant directories, and explain Linux-specific options.
- Ensure Linux and Windows configuration blocks are presented with equal prominence and detail, possibly in parallel sections.
- Include Linux-specific tools or patterns (e.g., systemd services, package managers) where appropriate, to match the Windows registry and file path focus.
- Review the ordering of examples and settings to avoid always listing Windows first; consider alternating or presenting both together.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/extension-version-details.md
...utomation/change-tracking/extension-version-details.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently lists Windows-specific issues, features, and workarounds before Linux equivalents, and in some cases omits Linux-specific details or solutions. Windows tools and patterns (such as registry, environment variables, and base64_decode_tostring() for Windows service descriptions) are mentioned explicitly, while Linux-specific tools or equivalent guidance are missing or less detailed. Linux issues are sometimes marked as 'None' or described in less detail, suggesting a lack of parity in troubleshooting and feature documentation.
Recommendations
- Provide Linux-specific examples and troubleshooting steps wherever Windows-specific guidance is given (e.g., if there is a workaround for Windows, check and document if a similar workaround is needed for Linux).
- List Linux and Windows issues/features in parallel, giving equal detail and prominence to both platforms.
- Include Linux equivalents for Windows tools and patterns (e.g., if referencing Windows Registry or environment variables, mention relevant Linux configuration files or environment handling).
- Avoid listing Windows issues or features first by default; alternate or group by platform for clarity.
- Ensure that Linux known issues and fixes are described with the same level of detail as Windows, rather than using 'None' as a placeholder.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-send-email.md
...lob/main//articles/automation/automation-send-email.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell for all examples and instructions, assumes the use of PowerShell-based Az modules, and does not provide any Linux shell (Bash/CLI) or cross-platform alternatives. All automation and scripting steps are presented in PowerShell, which is traditionally associated with Windows environments, and there is no mention of Azure CLI or Bash scripting, which are more common on Linux systems. The documentation also refers to installing the Azure Az PowerShell module on 'your machine' without clarifying cross-platform support.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash script examples alongside PowerShell for all major steps, including authentication, Key Vault management, and sending email via SendGrid.
- Explicitly mention that PowerShell Core is cross-platform, or clarify if the instructions are Windows-specific.
- Include a section or callout for Linux/macOS users, outlining any differences or prerequisites for running the scripts on non-Windows platforms.
- Reference and link to Azure CLI documentation where appropriate, and suggest it as an alternative to PowerShell for users on Linux.
- Ensure that all tooling and module installation instructions are cross-platform or provide platform-specific guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md
...g/guidance-migration-log-analytics-monitoring-agent.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation shows a moderate Windows bias, particularly in the scripting and automation sections. The only provided script-based migration method is a PowerShell script, which, while PowerShell is cross-platform, is still more familiar and accessible to Windows users. The prerequisites and instructions for scripting focus on PowerShell installation and modules, and do not mention Bash, shell scripts, or native Linux automation alternatives. Additionally, in the migration steps, Windows-specific data types (services, files, registry) are listed before Linux equivalents, and Windows terminology (such as 'services' and 'registry') is more prominent. There are no Linux shell script examples or explicit Linux-first instructions.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, or explicitly state if PowerShell Core is required and supported on Linux.
- Include Linux-native automation guidance, such as using Azure CLI or Bash scripts, for migration tasks.
- Balance the order of examples and terminology by alternating or grouping Windows and Linux instructions, rather than listing Windows first.
- Clarify in the prerequisites that PowerShell Core is cross-platform and provide Linux-specific installation and usage notes.
- Where possible, reference both Windows and Linux tools or patterns (e.g., mention systemd for Linux daemons alongside Windows services).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/overview-monitoring-agent.md
...utomation/change-tracking/overview-monitoring-agent.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific concepts (such as registry keys, Windows services, and file paths) are described in greater detail and often appear before their Linux equivalents. The registry section is exclusively Windows-focused, with no Linux configuration file or daemon tracking examples. Example queries and alerting scenarios prioritize Windows file paths and services, with Linux examples being fewer and less detailed. The documentation also references Windows tools and patterns (e.g., registry, c:\ paths, Windows services) more frequently and in more depth than Linux equivalents. While Linux is mentioned and supported, parity in examples and depth is lacking.
Recommendations
- Add equivalent Linux-focused sections where Windows registry keys are discussed, such as tracking changes to important Linux configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config) or daemon/service definitions.
- Ensure that for every Windows example (e.g., file paths, services, registry), a Linux example is provided with equal detail and explanation.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which OS is discussed first in tables and examples).
- Expand the alerting/query examples to include more Linux scenarios, such as tracking changes to systemd services, package installations, or critical config files.
- Where Windows-specific tools or concepts are introduced (e.g., registry, explorer.exe), provide a Linux equivalent or explicitly state the Linux alternative or lack thereof.
- Include screenshots and UI instructions that show both Windows and Linux contexts where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/enable-vms-monitoring-agent.md
...omation/change-tracking/enable-vms-monitoring-agent.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. Windows terminology and resources are mentioned first or exclusively in several places: the prerequisites link only to Windows VM creation, and Windows-specific features (like Windows Registry and Software) are highlighted. While both Windows and Linux are referenced in the scope and some CLI examples, Linux-specific instructions or parity in examples are often missing or appear after Windows. There is also a lack of Linux-focused screenshots and portal navigation, and no Linux VM creation link in prerequisites.
Recommendations
- Add a link to Linux VM creation in the prerequisites section alongside the Windows VM link.
- Ensure that all examples (especially CLI and portal workflows) show both Windows and Linux variants side by side, or alternate which comes first.
- Include Linux-focused screenshots and portal navigation where appropriate.
- Explicitly mention Linux file, package, and configuration tracking features in the introduction and throughout the documentation.
- Review all sections for parity in detail and clarity between Windows and Linux instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/disable-managed-identity-for-automation.md
.../automation/disable-managed-identity-for-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only PowerShell-based examples and instructions for disabling a system-assigned managed identity via the REST API, assuming the use of Windows tools and workflows. There are no examples or guidance for performing the same task using Linux-native tools (such as curl, az CLI, or bash scripting), and the PowerShell approach is presented as the default method. This creates a bias towards Windows environments and users.
Recommendations
- Add equivalent examples using Azure CLI (az rest) and/or curl for sending the PATCH request, with sample bash scripts.
- Include instructions for authenticating and obtaining an access token on Linux/macOS (e.g., using az account get-access-token).
- Present both PowerShell and Linux-native (bash/CLI) examples side by side, or clearly indicate that multiple platforms are supported.
- Avoid assuming the use of PowerShell or Windows-specific cmdlets as the only method for interacting with Azure REST APIs.
- Explicitly mention that the steps can be performed from any OS, and provide parity in tooling and instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/enable-managed-identity-for-automation.md
...s/automation/enable-managed-identity-for-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily biased towards Windows and PowerShell usage. All command-line examples are provided exclusively in PowerShell, with no Bash, CLI, or Linux-native scripting equivalents. Windows-specific tools and paths are mentioned first or exclusively in several sections. While there are brief mentions of Linux Hybrid Runbook Worker, there are no Linux shell (bash) examples, and the workflow assumes a Windows/PowerShell environment throughout.
Recommendations
- Provide equivalent Azure CLI (az) and Bash examples alongside PowerShell for all operations, including enabling managed identity, assigning roles, and obtaining tokens.
- Include Linux-native file paths and commands (e.g., using cat instead of vi for version checks, curl for REST API calls) wherever Windows paths or tools are mentioned.
- When describing prerequisites or steps, list Linux and Windows options equally, not always with Windows first.
- Add examples for using managed identity in Bash and Python (beyond the single Python example), especially for token acquisition and resource access.
- Reference Linux automation environments and tools (such as cloud-init, systemd, or shell scripts) where appropriate.
- Ensure that all code samples are available in both PowerShell and Bash/CLI formats to support cross-platform users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/quickstarts/enable-managed-identity.md
...cles/automation/quickstarts/enable-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on enabling managed identities via the Azure portal and, in its 'Next steps' section, directs users only to a PowerShell runbook tutorial. There are no examples or references to Linux-based automation (such as Python or Bash runbooks), nor are there links to equivalent Linux/Unix guidance. The PowerShell focus and lack of Linux parity suggest a Windows-first, PowerShell-heavy bias.
Recommendations
- Include links to tutorials for creating and using managed identities with Python and Bash runbooks, not just PowerShell.
- In the 'Next steps' section, provide parallel guidance for Linux/Unix users (e.g., 'Tutorial: Create Automation Python runbook using managed identity').
- Where possible, mention that managed identities can be used with multiple runbook types (PowerShell, Python, etc.) and provide cross-platform examples.
- Ensure that any referenced tools or scripts are available and documented for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/disable-local-authentication.md
...n//articles/automation/disable-local-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (Get-AzAutomationAccount, Set-AzAutomationAccount) for checking and configuring local authentication, with no equivalent CLI, Bash, or Linux-native examples. The use of PowerShell is assumed throughout, and there is no mention of Azure CLI or REST API usage from Linux environments. Windows tools and patterns are presented as the default or only method, and Linux alternatives are not discussed.
Recommendations
- Provide Azure CLI examples (az automation account show/update) for checking and setting the DisableLocalAuth property, alongside PowerShell.
- Include REST API curl examples that can be run from Linux/macOS terminals.
- Explicitly mention that these operations can be performed from any platform, not just Windows.
- Balance the order of examples so that Linux-friendly tools (CLI, REST) are presented before or alongside PowerShell.
- Clarify any platform-specific limitations or considerations, if present.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/delete-account.md
...-docs/blob/main//articles/automation/delete-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively using Azure PowerShell, with no equivalent Azure CLI or Bash examples. The PowerShell examples are presented as the only scripting/automation option, and there is no mention of Linux-native tools or shell environments. Additionally, the order of presentation often places PowerShell before any mention of cross-platform tools, and there are no explicit Linux instructions or screenshots.
Recommendations
- Add Azure CLI examples (az commands) alongside or before PowerShell examples for all automation and deletion tasks.
- Include Bash shell command examples where relevant, especially for users on Linux or macOS.
- Clearly indicate which instructions are cross-platform and which are Windows-specific.
- Add a tabbed interface for code samples, allowing users to select between PowerShell, Azure CLI, and possibly REST API or ARM template options.
- Ensure screenshots and UI instructions are not Windows-centric, or clarify when they are platform-agnostic.
- Mention and link to Linux/macOS documentation or tools where appropriate.