Automation

123
Total Pages
24
Linux-Friendly Pages
99
Pages with Bias
80.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

982 issues found
Showing 901-925 of 982 flagged pages
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-specific DSC resources (e.g., WaitFor resources in the /powershell/dsc/reference/resources/windows/waitForAllResource link) without mentioning Linux equivalents or providing parity for cross-platform DSC usage. Windows terminology and tooling are mentioned first, and there are no explicit Linux/macOS examples or references to Linux DSC resources.
Recommendations
  • Include references to Linux DSC resources and documentation, such as links to Linux DSC modules and their network requirements.
  • Provide examples or notes for Linux/macOS environments where applicable, especially regarding DSC resource communication and network configuration.
  • Clarify whether the listed URLs, ports, and service tags apply equally to Linux/macOS agents, and explicitly mention any platform-specific differences.
  • Add links to cross-platform DSC documentation and best practices for Linux/macOS users.
GitHub Create Pull Request
Automation Migrate from Orchestrator to Azure Automation (Beta) ...ticles/automation/automation-orchestrator-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and tooling (e.g., Runbook Converter, integration modules) assuming a Windows environment. There are no Linux/macOS-specific instructions, examples, or mentions of cross-platform alternatives. The use of Windows PowerShell cmdlets and Windows-style paths is pervasive, and Linux users are not provided with guidance for equivalent workflows.
Recommendations
  • Provide explicit instructions or notes for Linux/macOS users, including any prerequisites or limitations for running the migration toolkit and PowerShell modules.
  • Include examples using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility of the tools with non-Windows environments.
  • Mention and document any alternative methods for exporting/importing runbooks or assets on Linux/macOS, if available.
  • Use platform-neutral path examples or show both Windows and Linux/macOS path formats.
  • Clarify whether the migration toolkit and Runbook Converter can be run on Linux/macOS, and if not, suggest workarounds or alternatives.
GitHub Create Pull Request
Automation Runbook authoring using VS Code in Azure Automation ...in/articles/automation/automation-runbook-authoring.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and in more detail. Examples and directory paths use Windows-style notation (e.g., C:\abc), and there is a lack of explicit Linux/macOS examples for local directory configuration and usage. Debugging support is focused on PowerShell, with Python debugging relegated to a generic recommendation to use a third-party extension, without further guidance for Linux/macOS users.
Recommendations
  • Provide Linux/macOS-specific examples for directory paths (e.g., /home/user/abc) alongside Windows examples.
  • Clarify how to install and use required PowerShell modules and Python packages on Linux/macOS.
  • Offer parity in debugging instructions for Python runbooks, including recommended extensions and setup steps for Linux/macOS.
  • List supported operating systems in a neutral order or group by OS family.
  • Explicitly mention any OS-specific limitations or differences in feature support.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (PowerShell cmdlets) are referenced for key operations such as unregistering DSC nodes, exporting runbooks, and exporting DSC configurations, with no mention of equivalent Linux commands or tooling. Windows registry settings and PowerShell are discussed in detail, while Linux guidance is limited to a Python script for TLS configuration and a general reference to OpenSSL. In several tables and sections, Windows examples and instructions are presented before Linux equivalents.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell cmdlets mentioned (e.g., unregistering DSC nodes, exporting runbooks/configurations), or clarify if such operations are not supported on Linux.
  • Include CLI or REST API examples for backup/export operations that work cross-platform.
  • Balance tables and guidance by listing Linux and Windows instructions side-by-side, or in parallel sections.
  • Reference Linux-native tools (e.g., Bash scripts, Azure CLI) where appropriate, not just Windows/PowerShell.
  • Clarify any platform limitations explicitly, so Linux/macOS users know what is and isn't possible.
GitHub Create Pull Request
Automation Manage role permissions and security in Azure Automation ...les/automation/automation-role-based-access-control.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed instructions and examples for managing Azure Automation role permissions, but all command-line examples use Azure PowerShell cmdlets. There are no CLI (az) or Bash examples, and PowerShell is presented as the only scripting interface for automation tasks. This creates friction for Linux/macOS users, who may prefer or require Bash or Azure CLI. Additionally, the 'Configure Azure RBAC' section lists PowerShell after the portal, but does not mention or provide parity for Linux-native tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, especially for role assignment, listing, and removal.
  • Explicitly state that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Where scripts are shown, offer both PowerShell and Bash/CLI versions, or note cross-platform alternatives.
  • Clarify that PowerShell Core is available cross-platform, but highlight CLI as the default for Linux/macOS users.
  • Review and update any referenced links to ensure CLI documentation is included alongside PowerShell.
GitHub Create Pull Request
Automation Use Azure Automation runbooks and modules in PowerShell Gallery ...main/articles/automation/automation-runbook-gallery.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric workflows. All examples and references are to PowerShell modules, cmdlets, and the PowerShell Gallery, with no mention of Linux/macOS equivalents or cross-platform scripting approaches. Specific runbooks reference Windows Azure VMs without Linux alternatives. There is minimal coverage of Python runbooks, and no guidance for Linux/macOS users on how to use or contribute runbooks/modules.
Recommendations
  • Add explicit guidance and examples for Linux/macOS users, including how to use Python runbooks and modules.
  • Include examples of importing and running runbooks/modules on Linux-based Azure VMs.
  • Highlight cross-platform tools and scripting approaches, such as Bash or Python, alongside PowerShell.
  • When listing runbooks, ensure parity by including Linux-focused scenarios (e.g., copying files to/from Linux VMs).
  • Clarify which features and modules are supported on PowerShell Core (cross-platform) vs. Windows PowerShell.
  • Provide instructions for validating and running runbooks on Linux/macOS environments.
GitHub Create Pull Request
Automation Azure Automation Runbook Types ...b/main/articles/automation/automation-runbook-types.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell (a Windows-centric technology) is presented first and in greatest detail, with multiple sections and examples focused on Windows PowerShell and Windows file paths (e.g., C:\modules). Many examples and workarounds reference Windows-specific tools, environment variables, and patterns, such as using .ps1 scripts, Windows file paths, and Windows environment variables for Python. Linux support is mentioned but not illustrated with concrete examples, and Linux-specific considerations are often relegated to brief notes or limitations. There are no Linux-specific code samples or walkthroughs, and Windows-centric terminology and tooling dominate the documentation.
Recommendations
  • Add explicit Linux/macOS examples for PowerShell runbooks, such as file paths, environment variables, and module management on Linux Hybrid Runbook Workers.
  • Include Python runbook examples that demonstrate Linux-specific scenarios, such as package installation and environment configuration.
  • Reorder sections or provide parallel examples so that Linux and Windows usage are presented with equal prominence.
  • Clarify limitations and capabilities for both Windows and Linux Hybrid Runbook Workers, especially where features differ.
  • Avoid using Windows file paths (e.g., C:\modules) in generic examples, or provide Linux equivalents (e.g., /usr/src/PSModules).
  • Document Linux-specific troubleshooting steps and known issues, not just Windows ones.
GitHub Create Pull Request
Automation Runbook execution in Azure Automation ...in/articles/automation/automation-runbook-execution.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell runbooks and Windows-centric tools and patterns. All code examples are in PowerShell, and references to modules and execution environments prioritize Windows (e.g., .exe dependencies, IIS administration, WMI, UAC). There is little to no mention of Linux-specific runbook types, modules, or troubleshooting, and no Bash, Python, or Linux shell examples are provided. Windows tools and terminology (e.g., C:\temp, .NET Framework, WMI) are used exclusively or before their Linux equivalents.
Recommendations
  • Add Linux-specific runbook examples, such as Bash or Python runbooks, and demonstrate error handling and process management in those environments.
  • Include references to Linux tools and patterns (e.g., systemd, cron, Linux file paths like /tmp) where applicable.
  • Clarify support for Linux Hybrid Runbook Workers, including OS-specific limitations and configuration steps.
  • Provide parity in module documentation, listing modules and dependencies relevant to Linux environments.
  • Balance examples and terminology so that Linux/macOS users can easily follow along and complete tasks.
GitHub Create Pull Request
Automation Configure runbook output and message streams ...s/automation/automation-runbook-output-and-messages.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows PowerShell, with all code examples and tooling references using PowerShell cmdlets and syntax. There is no mention of Linux/macOS equivalents, Bash, or cross-platform scripting approaches. The retrieval of runbook output outside the Azure portal is only demonstrated using Windows PowerShell tools, and preference variables are described in the context of Windows PowerShell. No Linux-specific guidance or examples are provided, and Windows terminology and tools are used throughout.
Recommendations
  • Add examples using Azure CLI and Bash for retrieving runbook output and messages, especially for cross-platform users.
  • Clarify which features and cmdlets are available in PowerShell Core (cross-platform) versus Windows PowerShell, and note any limitations or differences for Linux/macOS users.
  • Include guidance for Python runbooks and how output streams are handled in non-PowerShell environments.
  • Provide parity in instructions for Linux/macOS users, such as using Azure CLI or REST API to retrieve job output.
  • Explicitly state platform requirements and limitations for PowerShell-based runbooks and retrieval methods.
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are presented before or alongside Windows PowerShell examples.
GitHub Create Pull Request
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented towards Windows environments, with all examples and instructions using PowerShell and Windows file paths (e.g., D:\examplefiles). There are no Linux or macOS equivalents provided for file creation, folder paths, or runbook worker setup. The only tooling mentioned is PowerShell, and the Hybrid Runbook Worker is implicitly assumed to be Windows-based. This creates friction for users operating on Linux/macOS hybrid workers.
Recommendations
  • Provide equivalent Linux/macOS examples for file creation (e.g., using Bash: touch /home/examplefiles/ExampleFile1.txt).
  • Clarify whether Hybrid Runbook Workers can run on Linux, and if so, include setup instructions and examples.
  • Show Linux-style file paths in parameter examples (e.g., /home/examplefiles).
  • Mention and demonstrate how to trigger watcher tasks using Bash or other Linux-native tools if supported.
  • Explicitly state any platform limitations for watcher tasks and runbooks.
GitHub Create Pull Request
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong bias towards Windows and PowerShell. All code examples for configuring Azure Automation encryption use PowerShell cmdlets, with no equivalent examples for Bash, Azure CLI, or cross-platform scripting. PowerShell is mentioned as a prerequisite, and Windows-centric tools and patterns are referenced exclusively or before REST API alternatives. There is no guidance for Linux/macOS users on how to perform these tasks using their native tools.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include Bash script samples for key operations, especially for steps like assigning identities and configuring Key Vault access policies.
  • Explicitly state that all operations can be performed via REST API, and provide curl or httpie examples for Linux/macOS users.
  • Add a section or callout for Linux/macOS users, clarifying tool choices and parity.
  • Reorder examples so that cross-platform options (Azure CLI, REST API) are presented before or alongside PowerShell.
GitHub Create Pull Request
Automation Send an email from an Azure Automation runbook ...blob/main/articles/automation/automation-send-email.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell for all examples and instructions, with no mention of Bash, CLI, or Linux/macOS alternatives. All code samples, module references, and workflow steps are PowerShell-centric, which is most commonly used on Windows. There is no guidance for users who prefer or require Bash, Azure CLI, or other cross-platform tools, nor any indication of how to adapt these steps for Linux/macOS environments.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for each major step, especially for creating Key Vaults, assigning permissions, and sending emails.
  • Explicitly mention that PowerShell Core is available cross-platform and provide instructions for installing and using it on Linux/macOS.
  • Include a note or section on how to perform these tasks from Linux/macOS, including any platform-specific considerations.
  • Reorder or parallelize examples so that Linux/macOS approaches are presented alongside Windows/PowerShell methods, rather than only after or not at all.
GitHub Create Pull Request
Automation Manage your Azure Automation account ...e-docs/blob/main/articles/automation/delete-account.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides Azure PowerShell examples for automation account deletion and solution removal, but does not offer equivalent Azure CLI (cross-platform) commands or Linux/macOS-specific instructions. PowerShell examples are presented as the only command-line option, and are shown before or instead of CLI alternatives, creating friction for users on Linux or macOS who may not use PowerShell.
Recommendations
  • Add Azure CLI examples for all operations currently shown only with PowerShell, such as deleting an Automation account and removing Log Analytics solutions.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, provide REST API examples, or link to REST API documentation for users who prefer scripting outside PowerShell.
  • Ensure that command-line instructions are not Windows-centric and clarify platform compatibility.
  • Present CLI and PowerShell examples side-by-side or in tabs, rather than PowerShell-only.
GitHub Create Pull Request
Automation Disable system-assigned managed identity for Azure Automation account .../automation/disable-managed-identity-for-automation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell-based example for disabling a system-assigned managed identity via REST API, but does not offer equivalent examples for Linux/macOS users (e.g., using Bash, curl, or Azure CLI). The scripting instructions and authentication steps are tailored to Windows/PowerShell environments, creating friction for users on other platforms.
Recommendations
  • Add Linux/macOS-friendly examples using Bash and curl for making REST API requests.
  • Include Azure CLI commands for authentication and API invocation, which are cross-platform.
  • Present examples for both Windows (PowerShell) and Linux/macOS (Bash/curl/Azure CLI) side by side or in separate sections.
  • Explicitly mention that the REST API can be called from any platform and provide generic guidance.
GitHub Create Pull Request
Automation Automation services in Azure - overview ...s/blob/main/articles/automation/automation-services.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias, primarily through heavy emphasis on PowerShell-based automation, frequent references to Windows-centric tools (e.g., registry, Active Directory, SQL Server), and the prioritization of PowerShell in examples and scenarios. While Linux is mentioned as supported in some services (e.g., Azure Automanage), there is a lack of Linux-specific examples, tools, or scripting languages (such as Bash or shell scripts). Windows tools and patterns (PowerShell, registry, etc.) are referenced more often and in greater detail than their Linux equivalents.
Recommendations
  • Add explicit Linux-focused examples, such as using Bash, shell scripts, or Ansible for automation tasks.
  • Include references to Linux-native tools and configuration management systems (e.g., systemd, cron, SSH, SELinux) in relevant scenarios.
  • Balance PowerShell examples with Python or Bash examples, especially in sections about Azure Automation and Azure Functions.
  • Mention Linux equivalents for Windows-specific tools (e.g., registry → configuration files, Active Directory → LDAP/SSSD).
  • Clarify cross-platform support in each service, including any limitations or differences for Linux/macOS users.
  • Provide links to Linux-specific documentation or tutorials where available.
GitHub Create Pull Request
Automation Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent ...g/guidance-migration-log-analytics-monitoring-agent.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides migration guidance for both Windows and Linux VMs, but the only scripting example is a PowerShell script, which is a Windows-centric tool (even though PowerShell Core is cross-platform, its usage is still more familiar to Windows users). The script prerequisites and instructions are PowerShell-specific, and there are no equivalent Bash or Linux-native scripting examples. Additionally, in the migration steps and limitations, Windows terminology (e.g., Windows services, Windows registry) is listed before Linux equivalents (Linux files, Linux daemons), and screenshots and UI flows do not highlight Linux-specific considerations. There is no mention of Linux command-line alternatives or parity for automation.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, or document how to perform the migration using native Linux tools (e.g., Azure CLI, Bash).
  • Explicitly mention Linux-specific steps or considerations in portal flows and screenshots.
  • List Linux and Windows data types in a neutral or alternating order to avoid Windows-first bias.
  • Clarify PowerShell Core cross-platform compatibility and provide installation guidance for Linux/macOS.
  • Add troubleshooting or FAQ sections for common Linux migration issues.
GitHub Create Pull Request
Automation Context switching in Azure Automation ...ocs/blob/main/articles/automation/context-switching.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets and runbook examples, with all code snippets and recommendations tailored to PowerShell workflows. There are no references to Linux/macOS shell environments, cross-platform scripting, or Azure CLI equivalents. This creates friction for users who prefer or require Bash, Python, or other non-Windows automation tools.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for context management and resource access.
  • Include guidance for Bash or Python runbooks, especially for Linux-hosted automation scenarios.
  • Clarify which recommendations apply universally and which are PowerShell-specific.
  • Present cross-platform options first or side-by-side, rather than focusing solely on PowerShell.
  • Reference tools and patterns available on Linux/macOS, such as environment variables or service principals via CLI.
GitHub Create Pull Request
Automation Delete an Azure Automation Run As account ...blob/main/articles/automation/delete-run-as-account.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation focuses exclusively on PowerShell and Azure portal methods for deleting a Run As account, both of which are Windows-centric. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or REST API. The mention of PowerShell as the only scripting method and lack of cross-platform alternatives creates friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for deleting Run As accounts, which work on Linux/macOS.
  • Include REST API instructions for cross-platform automation.
  • Clarify whether PowerShell examples can be run in Azure Cloud Shell (which is cross-platform), or provide explicit instructions for non-Windows environments.
  • Present cross-platform methods before or alongside Windows-specific tools.
GitHub Create Pull Request
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell examples and referencing PowerShell-specific cmdlets (e.g., Invoke-AzRestMethod, Get-AzAutomationAccount) for critical operations. No equivalent examples or instructions are given for Linux/macOS users (e.g., using curl or Azure CLI), and Windows tooling is presented as the default approach. This creates friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent examples using Azure CLI and/or curl for REST API calls, which are cross-platform.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell usage is required, and provide installation guidance.
  • Present cross-platform methods first, or in parallel with PowerShell examples, to avoid Windows-first bias.
  • Add a section clarifying platform compatibility and listing all supported methods for each OS.
GitHub Create Pull Request
Automation Using a system-assigned managed identity for an Azure Automation account ...s/automation/enable-managed-identity-for-automation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong bias toward Windows and PowerShell. All command-line examples use PowerShell, with no Bash, CLI, or Linux-native scripting alternatives. Even REST API and ARM template deployment steps are shown exclusively with PowerShell, and file paths use Windows conventions. Linux is mentioned only in passing for Hybrid Runbook Worker versioning, with no Linux-specific operational examples. This bias makes it difficult for Linux/macOS users to follow the instructions without translating PowerShell commands to their own environments.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell for all major steps, including enabling managed identity, assigning roles, and verifying assignments.
  • Include Bash shell script examples for REST API calls, using curl or httpie, and show how to authenticate and parse results on Linux/macOS.
  • Show ARM template deployment using Azure CLI (az deployment group create) and reference cross-platform tools.
  • When referencing file paths or environment variables, include both Windows and Linux/macOS conventions.
  • Explicitly mention and demonstrate how Linux/macOS users can perform each step, especially for runbook authentication and token retrieval.
  • Add a section or callouts for Linux/macOS users, highlighting any differences or additional requirements.
GitHub Create Pull Request
Automation Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation ...ation/extension-based-hybrid-runbook-worker-install.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage, but there is a notable Windows bias. Windows examples, especially PowerShell-based, are presented first and in greater detail. Many code samples and templates (Bicep, ARM) focus exclusively on Windows VM creation and extension installation, with Linux equivalents either missing or less emphasized. Windows-specific requirements and troubleshooting steps are more thoroughly documented, while Linux instructions are often brief or absent. The use of PowerShell as the primary automation tool further reinforces the Windows-centric approach.
Recommendations
  • Provide Linux-first or side-by-side examples for all code samples, especially in Bicep, ARM templates, and REST API sections.
  • Include explicit Linux VM creation and extension installation steps in Bicep and ARM template examples.
  • Offer Bash or shell script alternatives to PowerShell for Linux users, and clarify when PowerShell Core is required/supported on Linux.
  • Expand Linux-specific troubleshooting, permissions, and configuration guidance to match the depth provided for Windows.
  • Ensure all platform-specific requirements (e.g., CPU quota, hardening, package dependencies) are equally detailed and easy to find.
GitHub Create Pull Request
Automation Manage databases in Azure SQL databases using Azure Automation ...articles/automation/manage-sql-server-in-automation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, such as Az PowerShell cmdlets and instructions for installing modules via PowerShell. All code samples and automation instructions use PowerShell syntax, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. There are no examples or guidance for users who prefer or require Linux-native tools, and the documentation implicitly assumes a Windows environment (e.g., references to elevated PowerShell prompts, Windows environment variables, and module installation patterns).
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for connecting and managing Azure SQL databases.
  • Include instructions for installing required modules or packages on Linux/macOS environments.
  • Clarify which steps are OS-agnostic and which require adaptation for non-Windows platforms.
  • Provide guidance for running runbooks on Linux-based Hybrid Runbook Workers, including environment setup and troubleshooting.
  • List Linux/macOS prerequisites and highlight any platform-specific limitations or considerations.
GitHub Create Pull Request
Automation Manage Runtime Environment and Associated Runbooks in Azure Automation ...main/articles/automation/manage-runtime-environment.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, primarily through its heavy emphasis on PowerShell examples, repeated references to Windows-specific tools (such as PowerShell Gallery and .zip modules), and the prioritization of PowerShell scenarios over Python/Linux equivalents. Linux-specific details, such as package formats and runtime nuances, are mentioned only briefly and lack parity in examples and guidance. There are no concrete Linux/macOS shell or CLI examples, and the documentation assumes familiarity with Windows-centric workflows.
Recommendations
  • Provide equivalent examples for Python runbooks, including REST API payloads and portal workflows.
  • Include Linux/macOS-specific guidance, such as how to prepare and upload Python packages (.whl files), and clarify supported OS environments for Python runbooks.
  • Offer examples using Azure CLI or Bash where applicable, not just PowerShell.
  • Balance screenshots and walkthroughs to show both PowerShell and Python scenarios.
  • Clarify any platform-specific limitations or behaviors for Linux/macOS users.
GitHub Create Pull Request
Automation Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation ...g-agent-based-hybrid-worker-to-extension-based-workers.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Most code examples (Bicep, ARM template, PowerShell) focus exclusively on Windows VMs, with parameters and resource types hardcoded for Windows (e.g., 'HybridWorkerForWindows'). PowerShell is emphasized as the primary automation tool, with Windows-specific prerequisites and folder paths detailed, while Linux equivalents are either missing or less detailed. Linux-specific instructions, examples, and extension types (e.g., 'HybridWorkerForLinux') are not provided in the main migration and deployment sections, making it harder for Linux users to follow along.
Recommendations
  • Add parallel Linux-focused examples for Bicep, ARM templates, REST API, Azure CLI, and PowerShell, including use of 'HybridWorkerForLinux' extension type.
  • Include Linux VM creation and onboarding steps in all code samples, not just Windows.
  • Document Linux-specific prerequisites, folder paths, and permissions with the same level of detail as Windows.
  • Ensure that CLI and PowerShell examples show both Windows and Linux usage, or provide tabs for each.
  • Clarify any differences in extension installation or management between Windows and Linux.
  • Review and update references to Windows-only tools (e.g., PowerShell 5.1) and provide Linux alternatives (e.g., PowerShell Core, Bash).
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily focused on PowerShell-based automation, with all code samples, migration steps, and graphical runbook instructions using PowerShell cmdlets and patterns. There are no examples or guidance for Linux/macOS users, such as using Python, Bash, or cross-platform SDKs. Windows-centric tools and workflows (PowerShell, AzureRM/Az modules) are mentioned exclusively and first, with no parity for Linux-native automation approaches.
Recommendations
  • Add equivalent sample scripts using Azure CLI (az), which is cross-platform and commonly used on Linux/macOS.
  • Provide examples using Python SDK (azure-identity, azure-mgmt-resource) for runbooks, as Python is supported in Azure Automation and widely used on Linux.
  • Explicitly mention that PowerShell Core is available cross-platform, but clarify any limitations or differences for Linux/macOS users.
  • Include troubleshooting and migration steps for runbooks written in Bash or Python, not just PowerShell.
  • Add notes or links to documentation for Linux/macOS users on how to authenticate with managed identities outside of PowerShell.
GitHub Create Pull Request
← Previous Page 37 of 40 Next →