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 151-175 of 982 flagged pages
Automation Get started with Azure Automation State Configuration .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. All configuration examples use Windows PowerShell syntax and Windows-specific DSC resources (e.g., WindowsFeature). The only VM creation instructions link to Windows VM guides, and there are no Linux configuration examples or references to Linux DSC resources. The documentation repeatedly refers to Windows PowerShell DSC and Windows tools, with no parity for Linux users. Although Linux support is mentioned as retired, the documentation does not provide historical Linux examples or guidance for users migrating from Linux.
Recommendations
  • Add historical Linux DSC configuration examples to illustrate how Linux nodes were managed prior to retirement.
  • Clearly indicate the current support status for Linux, and provide migration guidance for users previously using Linux DSC.
  • Include references to Linux DSC resources and tools, even if only for archival or migration purposes.
  • Balance the documentation by mentioning Linux equivalents where relevant, such as Linux VM creation guides, and explicitly state the lack of support if applicable.
  • Provide links to community or alternative solutions for Linux configuration management in Azure.
GitHub Create Pull Request
Automation Enable Azure Automation State Configuration .../main/articles/automation/automation-dsc-onboarding.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows and PowerShell bias. Most examples, scripts, and workflows are presented first (or exclusively) for Windows, with PowerShell as the primary tool. Linux support is mentioned, but Linux-specific instructions are often secondary, less detailed, or require the use of Windows tools (e.g., generating metaconfigurations on Windows with PowerShell before applying them to Linux). Some Linux steps are less explicit or rely on referencing Windows-centric processes.
Recommendations
  • Provide Linux-first or parallel Linux examples for all major workflows, especially for onboarding, metaconfiguration generation, and registration.
  • Include native Linux command-line examples (e.g., Bash, Python) for generating and applying DSC metaconfigurations, without requiring a Windows/PowerShell environment.
  • Document Linux-specific tooling and workflows (such as Register.py, SetDscLocalConfigurationManager.py) in equal detail to their Windows/PowerShell counterparts.
  • Avoid requiring Windows or PowerShell as an intermediary for Linux onboarding; describe a fully Linux-native onboarding path.
  • Where possible, use cross-platform tools or clarify when a step is Windows-only, and provide equivalent Linux alternatives.
  • Ensure that Linux instructions are as detailed and explicit as Windows instructions, including troubleshooting and status-checking steps.
GitHub Create Pull Request
Automation Remediate noncompliant Azure Automation State Configuration servers ...b/main/articles/automation/automation-dsc-remediate.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias by presenting Windows remediation steps first, providing detailed PowerShell examples, and referencing Windows-specific tools (PowerShell, Update-DscConfiguration) with direct links. Linux remediation is described in less detail, lacks concrete script examples, and is presented as less capable (no Run Command support, only re-registration or external Python scripts). Windows tools and patterns are emphasized, while Linux equivalents are either missing or referenced indirectly.
Recommendations
  • Provide Linux remediation steps with concrete script examples, similar to the PowerShell example for Windows.
  • Include direct links to Linux-specific documentation and tools, such as Python scripts or shell commands for DSC operations.
  • Present Windows and Linux remediation steps in parallel sections with equal detail and visibility.
  • Clarify any feature parity gaps (e.g., Run Command support) and suggest alternative Linux workflows.
  • Reference cross-platform tools or approaches where possible, and avoid presenting Windows solutions first by default.
GitHub Create Pull Request
Automation Forward Azure Automation job data to Azure Monitor logs ...mation/automation-manage-send-joblogs-log-analytics.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily through its references to PowerShell and Windows-centric patterns. PowerShell is mentioned as the tool for viewing job logs, and error handling is described in terms of PowerShell error streams. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. The documentation does not mention or provide parity for Linux tools or workflows, nor does it clarify how Linux users can perform equivalent tasks.
Recommendations
  • Add explicit examples using Azure CLI and Bash for querying logs and managing automation jobs.
  • Clarify that Azure Automation and Azure Monitor are cross-platform and provide guidance for Linux users.
  • When mentioning PowerShell, also mention Azure CLI and provide equivalent commands or workflows.
  • Include troubleshooting and monitoring steps relevant to Linux environments.
  • Avoid describing error handling solely in terms of PowerShell streams; explain how errors are surfaced in Bash or other shells.
  • Ensure screenshots and UI instructions are not Windows-specific, or note any differences for Linux users.
GitHub Create Pull Request
Automation Azure Automation State Configuration overview ...ob/main/articles/automation/automation-dsc-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing primarily on PowerShell DSC, listing Windows operating systems and tools first, providing more detail for Windows prerequisites, and referencing Windows-specific tools (e.g., WinRM, WMF). Linux support is mentioned but less detailed, with no Linux-specific examples or tools highlighted, and no Linux-first guidance or parity in examples.
Recommendations
  • Include Linux-specific examples and walkthroughs, such as onboarding a Linux node and compiling/applying DSC configurations on Linux.
  • Provide parity in detail for Linux prerequisites, including supported distributions and required packages.
  • Reference Linux-native tools and patterns (e.g., systemd, OpenSSH, native DSC agent usage) alongside Windows tools.
  • Balance the order of presentation so that Linux and Windows are treated equally, rather than listing Windows first.
  • Add links to Linux documentation and troubleshooting guides similar to those provided for Windows.
  • Show example metaconfiguration scripts for Linux, not just Windows.
  • Clarify any feature differences or limitations for Linux nodes up front.
GitHub Create Pull Request
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell and Windows-specific workflows. All command-line examples use Windows PowerShell, with explicit references to Windows paths (e.g., c:\runbooks) and no mention of Linux, macOS, or cross-platform alternatives. There are no Bash or Azure CLI examples, and the use of Windows PowerShell is assumed throughout. The documentation does not address how users on Linux or macOS can interact with Azure Automation runbooks, nor does it mention cross-platform editors or tools.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for Linux/macOS users.
  • Clarify that PowerShell Core (pwsh) is cross-platform and provide examples for non-Windows environments.
  • Replace or supplement Windows-specific file paths (e.g., c:\runbooks) with platform-neutral or Linux/macOS paths (e.g., /home/user/runbooks).
  • Explicitly mention support for editing runbooks from Linux/macOS and provide guidance or links for those platforms.
  • Ensure that references to editors and tools include cross-platform options (e.g., VS Code, nano, vim) and not just Windows-centric ones.
GitHub Create Pull Request
Automation Author graphical runbooks in Azure Automation ...les/automation/automation-graphical-authoring-intro.md
High Priority View Details →
Scanned: 2026-01-11 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 for authoring graphical runbooks in Azure Automation exhibits a strong Windows bias. All examples, activities, and scripting references are exclusively based on Windows PowerShell and PowerShell Workflow. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows-centric tools and patterns (e.g., cmdlets, System Center Orchestrator, Service Management Automation), and does not provide Linux equivalents or guidance for users on non-Windows platforms.
Recommendations
  • Clarify whether graphical runbooks support cross-platform execution, and if not, explicitly state the Windows-only limitation.
  • If Linux support is possible, provide examples using Bash, Python, or other Linux-compatible scripting languages.
  • Mention Azure Automation Hybrid Workers for Linux and provide guidance on authoring runbooks for Linux environments.
  • Include references to Linux tools and patterns where applicable, such as shell scripts, cron jobs, or Linux authentication mechanisms.
  • Add a section comparing Windows PowerShell and Linux scripting approaches in Azure Automation, with links to relevant documentation.
  • Ensure that introductory and tutorial links include Linux-focused content or alternatives.
GitHub Create Pull Request
Automation Azure Automation Hybrid Runbook Worker Overview ...rticles/automation/automation-hybrid-runbook-worker.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias in several ways: PowerShell cmdlets are listed as a primary onboarding method before mentioning Azure CLI, Bicep, and REST API; references to authentication and permissions link to Windows-specific guides; examples and operational details (such as job execution under the 'System' account) are described for Windows first, with Linux mentioned secondarily or generically. There are no Linux-specific examples, troubleshooting steps, or references to Linux-native tools or patterns. The documentation assumes familiarity with Windows concepts and tools, and does not provide parity for Linux users.
Recommendations
  • Provide Linux-specific examples and walkthroughs for installation, configuration, and troubleshooting, including shell commands and references to Linux-native tools.
  • Ensure that onboarding and management methods (Azure CLI, REST API, Bicep) are listed before or alongside PowerShell, not after.
  • Add explicit references and links to Linux authentication and permissions guides, including details on the 'nxautomation' account and how to manage credentials on Linux.
  • Include troubleshooting steps and operational details specific to Linux environments.
  • Balance references to Windows and Linux throughout the documentation, ensuring that both platforms are equally represented in examples, diagrams, and instructions.
GitHub Create Pull Request
Automation Manage role permissions and security in Azure Automation ...les/automation/automation-role-based-access-control.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through exclusive use of PowerShell examples for command-line operations, with no mention of Azure CLI or Bash alternatives. The 'Configure Azure RBAC' section provides detailed PowerShell cmdlets and scripts, but does not offer equivalent instructions for Linux/macOS users who may prefer Azure CLI or Bash. The documentation references 'devx-track-azurepowershell' and links to PowerShell-specific resources, further reinforcing the Windows-centric approach. There are no Linux-specific tools, patterns, or examples provided.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets and scripts, including role assignment, listing, and removal.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for managing Azure RBAC, and provide links to relevant documentation.
  • Where scripts are provided, offer both PowerShell and Bash/Azure CLI versions side-by-side.
  • Review references to Windows-specific tabs or instructions (e.g., in Hybrid Worker documentation) and ensure Linux parity is addressed.
  • Update 'Next steps' and related links to include Azure CLI documentation and Linux/macOS usage guides.
GitHub Create Pull Request
Automation Runbook execution in Azure Automation ...in/articles/automation/automation-runbook-execution.md
High Priority View Details →
Scanned: 2026-01-11 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 exhibits a strong bias toward Windows and PowerShell environments. All code examples and technical references use PowerShell syntax, cmdlets, and concepts. Windows-specific tools and patterns (e.g., WMI, WinSCP.exe, IIS, .NET Framework versions, UAC) are mentioned exclusively or before any Linux equivalents. There are no Bash, Python, or Linux shell examples, nor references to Linux-specific modules or tools. The documentation assumes familiarity with Windows paradigms and does not provide guidance for Linux users or parity in examples.
Recommendations
  • Add equivalent examples for Bash, Python, or other Linux-supported runbook types where applicable.
  • Include references to Linux tools and patterns (e.g., systemd, cron, Linux file paths, Linux authentication methods) alongside Windows-specific ones.
  • Explicitly mention Linux support and limitations in relevant sections, such as Hybrid Runbook Worker environments.
  • Provide guidance for handling Linux-specific scenarios, such as monitoring files/folders, installing modules, and handling elevation (sudo).
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence.
  • Expand module documentation to include Linux-compatible modules and clarify any OS-specific requirements.
GitHub Create Pull Request
Automation Handle errors in Azure Automation graphical runbooks ...omation/automation-runbook-graphical-error-handling.md
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias by exclusively referencing PowerShell, Windows cmdlets, and Windows error handling patterns. All examples and terminology are PowerShell-centric, with no mention of Linux-native tools, Bash, or cross-platform scripting approaches. The documentation assumes the reader is using Windows environments and does not provide Linux or cross-platform alternatives.
Recommendations
  • Include equivalent examples using Bash or Python for error handling in graphical runbooks.
  • Mention how graphical runbooks interact with Linux VMs and provide error handling patterns for Linux environments.
  • Reference cross-platform modules and tools (e.g., Azure CLI, Bash scripts) alongside PowerShell cmdlets.
  • Clarify which features or settings are available or behave differently on Linux vs. Windows targets.
  • Add a section on best practices for error handling in runbooks targeting Linux resources.
GitHub Create Pull Request
Automation Azure Automation Runbook Types ...b/main/articles/automation/automation-runbook-types.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias by prioritizing Windows PowerShell and PowerShell Workflow runbooks, frequently referencing Windows-specific paths, tools, and patterns (e.g., C:\modules, .ps1 scripts, environment variables for Windows Python installations). PowerShell examples and limitations dominate the content, with Linux support mentioned only as an afterthought or in limitations. There are no Linux-specific code examples, troubleshooting steps, or parity in tooling guidance. Python runbooks mention Linux only in passing, and graphical runbooks cannot run on Linux Hybrid Workers.
Recommendations
  • Add Linux-specific examples for PowerShell and Python runbooks, including code samples and troubleshooting steps relevant to Linux Hybrid Runbook Workers.
  • Clearly indicate cross-platform compatibility for each runbook type and provide guidance for Linux users where features differ or are unavailable.
  • Avoid referencing Windows paths (e.g., C:\modules) exclusively; include Linux equivalents (e.g., /opt/modules) or abstract file path usage.
  • Provide parity in documentation for Linux tools, environment variables, and module/package management, especially for Python runbooks.
  • Include explicit limitations and workarounds for Linux environments alongside Windows ones, rather than only listing what is unsupported.
  • Balance the ordering and emphasis of Windows and Linux content, ensuring Linux is not always mentioned second or only in limitations.
GitHub Create Pull Request
Automation Runbook authoring using VS Code in Azure Automation ...in/articles/automation/automation-runbook-authoring.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows and PowerShell bias. PowerShell is the only shell language mentioned for local debugging, and all directory path examples use Windows-style paths (e.g., C:\abc). Windows operating systems are listed first in the supported OS matrix, and Windows PowerShell 5.1 is specifically called out, with no equivalent focus on Bash or Linux-native tools. There are no Linux or macOS-specific examples or instructions, and Python debugging is not supported or documented, further emphasizing PowerShell and Windows environments.
Recommendations
  • Provide equivalent Linux/macOS examples for directory paths (e.g., /home/user/abc) alongside Windows examples.
  • Include instructions or notes for using Bash or other Linux-native shells for runbook authoring and debugging.
  • List supported operating systems in a neutral or rotating order, or group by platform type (Windows, Linux, macOS).
  • Offer parity in debugging support and documentation for Python runbooks, including recommended debugger extensions for Linux/macOS.
  • Explicitly mention any Linux/macOS-specific considerations or limitations, and provide troubleshooting steps for those platforms.
  • Avoid using only Windows-centric terminology (e.g., 'Manage icon in the activity bar' is fine, but avoid only referencing Windows shortcuts like Ctrl+Shift+P; include Cmd+Shift+P for macOS).
GitHub Create Pull Request
Automation Use Azure Automation runbooks and modules in PowerShell Gallery ...main/articles/automation/automation-runbook-gallery.md
High Priority View Details →
Scanned: 2026-01-11 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 strong bias toward Windows and PowerShell environments. All examples and tooling references are centered on PowerShell, with no Linux shell (Bash, CLI) or cross-platform scripting examples. The listed runbooks and modules are PowerShell-centric, and specific scenarios (such as copying files to/from Azure VMs) mention only Windows VMs. There is no guidance or parity for Linux users, nor are Linux tools or patterns referenced.
Recommendations
  • Include equivalent examples for Linux environments, such as Bash or Azure CLI runbooks.
  • List or link to runbooks and modules that target Linux VMs and common Linux automation scenarios.
  • Explicitly mention Linux compatibility and limitations for runbooks and modules.
  • Provide guidance on using Python runbooks in Linux contexts, with examples.
  • Ensure that documentation does not assume PowerShell as the default or only automation language.
  • Add references to Linux-specific documentation and best practices for Azure Automation.
GitHub Create Pull Request
Automation Configure runbook output and message streams ...s/automation/automation-runbook-output-and-messages.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively using Windows PowerShell cmdlets and scripting patterns throughout. All code examples are in PowerShell, with no mention or examples for Linux-native tools, Bash, or Python (except a brief note about Python runbooks). Windows PowerShell concepts, variables, and cmdlets are referenced as the default or only approach, and retrieval of runbook output is described solely via Windows PowerShell tools. There is no guidance for Linux users or parity in examples for non-Windows environments.
Recommendations
  • Include equivalent examples using Bash, Azure CLI, or Python where applicable, especially for retrieving runbook output and handling streams.
  • Explicitly mention support and usage patterns for Linux Hybrid Workers and cross-platform scenarios.
  • Provide guidance and examples for authoring and managing runbooks in Linux environments, including differences in stream handling and output retrieval.
  • Reference Azure CLI commands and REST API methods alongside PowerShell cmdlets for managing runbooks and retrieving output.
  • Clarify which features and cmdlets are Windows-specific and which are available cross-platform, and link to Linux-focused documentation where possible.
GitHub Create Pull Request
Automation Deploy an Amazon Web Services VM with an Azure Automation runbook ...icles/automation/automation-scenario-aws-deployment.md
High Priority View Details →
Scanned: 2026-01-11 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 PowerShell for all automation examples and instructions, including module installation, scripting, and credential management. There are no references to Linux-native tools, Bash, or cross-platform alternatives. The workflow assumes familiarity with Windows-centric tools (PowerShell ISE, PowerShell Gallery) and does not mention or provide parity for Linux users or those using Bash/AWS CLI directly. Windows/PowerShell approaches are presented first and exclusively.
Recommendations
  • Provide equivalent examples using Bash and the AWS CLI, which are native to Linux and cross-platform environments.
  • Include instructions for importing and using AWS CLI modules in Azure Automation, and authoring runbooks in Python or Bash where supported.
  • Mention Linux-compatible editors and environments (e.g., VS Code, Cloud Shell) alongside PowerShell ISE.
  • Clarify that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, Bash) and link to documentation for each.
  • Add notes or sections specifically for Linux users, outlining any differences in credential management, module installation, and scripting.
  • Ensure that references to PowerShell are balanced with references to Bash/AWS CLI, and avoid assuming a Windows-first workflow.
GitHub Create Pull Request
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias. All examples and instructions rely exclusively on PowerShell, with commands and file paths (e.g., D:\examplefiles) that are specific to Windows environments. There are no references to Linux equivalents, such as Bash commands, Linux file paths, or cross-platform scripting approaches. The documentation assumes the use of Windows tools and patterns throughout, without acknowledging or providing guidance for Linux users running Hybrid Runbook Workers.
Recommendations
  • Provide equivalent examples using Bash or other Linux shell commands for file creation and manipulation.
  • Include instructions and screenshots for Linux environments, such as using /home/examplefiles as a folder path.
  • Clarify that Hybrid Runbook Workers can run on Linux, and provide guidance for Linux setup and usage.
  • Mention and link to cross-platform scripting options, such as PowerShell Core, and note any differences in usage or compatibility.
  • Add a section comparing Windows and Linux approaches, highlighting any platform-specific considerations.
GitHub Create Pull Request
Automation Automation services in Azure - overview ...s/blob/main/articles/automation/automation-services.md
High Priority View Details →
Scanned: 2026-01-11 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 heavy emphasis on PowerShell scripting and modules, frequent references to Windows-centric tools (e.g., Active Directory, SQL Server), and a lack of Linux-specific examples or tooling. PowerShell is repeatedly highlighted as the primary automation language, with only brief mentions of Python as an alternative. Windows tools and scenarios (such as registry changes, ServiceNow integration, and Active Directory management) are described in detail, while Linux equivalents (such as systemd, cron, or Linux configuration management tools) are not mentioned. Although Azure Automanage claims Linux and Windows support, practical Linux-focused automation scenarios, examples, or best practices are missing throughout the document.
Recommendations
  • Add Linux-specific automation examples, such as using Bash, Python, or Ansible scripts for common tasks.
  • Include references to Linux tools and patterns (e.g., systemd, cron jobs, SSH, configuration management with Ansible or Chef) alongside or before Windows tools.
  • Provide sample runbooks or workflows that target Linux VMs, demonstrating tasks like package updates, log rotation, or service management.
  • Balance PowerShell examples with equivalent Bash or Python scripts for cross-platform parity.
  • Explicitly mention Linux-specific challenges and solutions in Azure Automation, such as handling SELinux, managing systemd services, or integrating with Linux monitoring tools.
  • Ensure that documentation sections discussing configuration management, update management, and event response include Linux-focused scenarios and terminology.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a strong Windows bias by exclusively using PowerShell for all examples and instructions, referencing Windows-specific modules and cmdlets, and omitting any mention of Linux or cross-platform alternatives. There are no Bash, CLI, or Python examples, nor is there guidance for users operating on Linux or macOS. Windows tools and patterns (such as PSCredential, Get-Credential, and Windows PowerShell modules) are presented as the default or only option.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for credential management and runbook automation.
  • Explicitly mention cross-platform support for Azure Automation and Microsoft Entra ID, including how Linux/macOS users can authenticate and manage credentials.
  • Reference Python SDK or REST API methods for authentication and automation tasks.
  • Clarify which steps are Windows-specific and provide alternative instructions for Linux/macOS environments.
  • Include links to cross-platform documentation and tools where available.
GitHub Create Pull Request
Automation Compose DSC configurations ...omation/compose-configurationwithcompositeresources.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily oriented towards Windows and PowerShell, with all examples and references using PowerShell DSC concepts, cmdlets, and Windows-centric tools (e.g., PSExecutionPolicy, Chocolatey). There is no mention of Linux-specific DSC resources, nor are there examples or guidance for Linux nodes. The retirement announcement for Linux DSC is included, but the documentation does not provide alternatives or parity for Linux users.
Recommendations
  • Add examples and workflows for Linux nodes, including how to compose configurations for Linux DSC resources (if still supported elsewhere).
  • Include references to Linux equivalents for tools and patterns (e.g., alternatives to Chocolatey, Linux credential management).
  • If Linux DSC is deprecated, provide guidance or migration paths for Linux users, and clearly indicate Windows-only applicability in the documentation.
  • Balance PowerShell examples with cross-platform scripting or configuration approaches where possible.
  • Explicitly state platform limitations and provide links to Linux configuration management alternatives (e.g., Ansible, Chef, Puppet) for Azure Automation users.
GitHub Create Pull Request
Automation Context switching in Azure Automation ...ocs/blob/main/articles/automation/context-switching.md
High Priority View Details →
Scanned: 2026-01-11 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 PowerShell and Az/AzureRM cmdlets for all examples and recommendations, which are primarily Windows-centric tools. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform scripting approaches. All code samples and troubleshooting steps assume a Windows/PowerShell environment, potentially excluding Linux users or those using other shells.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
  • Include Bash or shell script snippets demonstrating context management in Azure Automation.
  • Clarify which recommendations apply to PowerShell only, and provide guidance for Linux users or those using non-PowerShell runbooks.
  • Mention the availability of Azure Automation Hybrid Worker for Linux and how context switching is handled there.
  • Ensure troubleshooting steps and error messages include references to Azure CLI and Linux environments where applicable.
GitHub Create Pull Request
Automation Start an Azure Automation Runbook from a Webhook ...s/blob/main/articles/automation/automation-webhooks.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias. All code examples and automation instructions use PowerShell, which is primarily a Windows tool (despite cross-platform support, most Linux users prefer Bash or Python). There are no Bash, curl, or Linux-native examples for creating or invoking webhooks. The REST API section also uses PowerShell's Invoke-RestMethod, not curl or other Linux tools. The documentation refers to PowerShell modules and cmdlets exclusively, and does not mention Linux equivalents or alternative workflows. The ARM template section also provides only PowerShell deployment instructions. There is no guidance for Linux users or those using Bash, curl, or Python.
Recommendations
  • Add equivalent examples using Bash and curl for creating and invoking webhooks.
  • Provide Python code samples for REST API interactions, as Python is widely used on Linux.
  • Include instructions for using Azure CLI (az) commands to create and manage webhooks, as Azure CLI is cross-platform.
  • Clearly indicate which steps or tools are Windows-specific and provide Linux alternatives where possible.
  • Add a section or callouts for Linux/macOS users, highlighting platform-agnostic approaches.
  • Where PowerShell is used, note that it is available on Linux, but also suggest alternatives for those who prefer native Linux tools.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing migration scripting guidance exclusively via PowerShell, a tool most commonly associated with Windows, even though PowerShell Core is cross-platform. The prerequisites and instructions for scripting focus on PowerShell installation and modules, with no mention of Bash, shell scripts, or Linux-native automation tools. Examples and screenshots throughout the page are generic but do not provide Linux-specific UI or CLI guidance. Data types listed in the script migration section prioritize Windows services, files, and registry before Linux equivalents. There are no Linux shell script examples or parity in automation tooling, and the migration steps are described in a way that assumes familiarity with Windows-centric patterns.
Recommendations
  • Provide equivalent migration scripts and automation examples using Bash or other Linux-native tools, or clarify PowerShell Core usage on Linux with explicit Linux installation and usage instructions.
  • Include Linux-specific screenshots or step-by-step UI guidance for onboarding and migration, highlighting any differences in the Linux experience.
  • List Linux data types (e.g., daemons, files) before or alongside Windows types to avoid Windows-first ordering.
  • Add troubleshooting and limitations sections specific to Linux environments, such as agent removal nuances or workspace configuration differences.
  • Ensure all referenced tutorials and links include Linux tabs/examples, not just Windows or PowerShell.
GitHub Create Pull Request
Automation Use the Azure Automation graphical runbook SDK (preview) ...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority View Details →
Scanned: 2026-01-11 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-centric technologies, specifically PowerShell and PowerShell Workflow, without mentioning or providing examples for Linux or cross-platform equivalents. All code and SDK references assume a Windows environment, and there is no guidance for Linux users or alternatives for non-Windows platforms.
Recommendations
  • Explicitly state platform requirements and limitations at the start of the documentation.
  • Provide information on whether graphical runbooks and the SDK can be used or authored from Linux or macOS environments.
  • If Linux support is unavailable, suggest alternative approaches for Linux users (e.g., using text-based runbooks, Python, or Bash in Azure Automation).
  • Include examples or notes for cross-platform scripting languages supported by Azure Automation, such as Python or Bash.
  • Mention any plans for future cross-platform support, if applicable.
  • Clarify whether the SDK and .dll package are usable on non-Windows platforms (e.g., via .NET Core/6+), and provide installation instructions for Linux if supported.
GitHub Create Pull Request
Automation Manage your Azure Automation account ...e-docs/blob/main/articles/automation/delete-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no Azure CLI (bash or cross-platform) examples. The PowerShell examples are presented before any mention of other automation methods, and there is no guidance for Linux users or those working in bash or other shells. The documentation assumes familiarity with PowerShell and Windows-centric workflows, omitting equivalent instructions for Linux environments.
Recommendations
  • Add Azure CLI examples (bash syntax) alongside PowerShell commands for all automation tasks, including deleting accounts and solutions.
  • Explicitly mention that Azure CLI is cross-platform and provide usage instructions for Linux/macOS users.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is accessible from any OS.
  • Include a section or tab for Linux shell users, demonstrating how to perform the same operations using Azure CLI.
  • Review terminology and instructions to avoid assuming a Windows/PowerShell environment as the default.
GitHub Create Pull Request
← Previous Page 7 of 40 Next →