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 51-75 of 982 flagged pages
Automation Configure data based on STIG for Azure Automation State Configuration ...tomation/automation-dsc-configuration-based-on-stig.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell, referencing Windows PowerShell 5.1 explicitly and providing examples and tooling (PowerSTIG, DSC) that are primarily Windows-centric. There is no mention of Linux equivalents or examples, and the guidance assumes familiarity with Windows tools and patterns. Although there is a brief mention of onboarding Linux machines, no Linux-specific configuration or tooling is discussed.
Recommendations
  • Include examples and instructions for configuring Linux servers using Azure Automation State Configuration.
  • Reference cross-platform DSC implementations (such as PowerShell Core or native Linux DSC support) where applicable.
  • Provide parity in documentation by listing Linux tools, patterns, and community projects that address STIG compliance.
  • Clarify which features and tools are Windows-only and which are available on Linux, and provide links to Linux-specific resources.
GitHub Create Pull Request
Automation Integrate Azure Automation State Configuration with Azure Monitor Logs ...main/articles/automation/automation-dsc-diagnostics.md
High Priority View Details →
Scanned: 2026-01-12 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 setup instructions use PowerShell and Az PowerShell modules, which are native to Windows environments. There are no Bash, CLI, or Linux-native instructions or examples. The prerequisites and troubleshooting steps reference PowerShell modules and tools exclusively, and the only example of continuous deployment uses Chocolatey, a Windows package manager. There is no mention of Linux equivalents or cross-platform alternatives, and Linux support is only referenced in the context of retirement announcements.
Recommendations
  • Provide equivalent instructions and code examples using Azure CLI and Bash, which are cross-platform and commonly used on Linux.
  • Include steps for installing and configuring required modules on Linux systems, or clarify platform limitations.
  • Reference Linux-compatible tools (e.g., Ansible, shell scripts) where appropriate, or explain how Linux users can achieve similar outcomes.
  • Add explicit notes about platform support and limitations, especially in light of Linux retirement announcements, and offer migration guidance for Linux users.
  • Ensure that examples and tooling references are presented in a platform-neutral way, or offer parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
Automation Get started with Azure Automation State Configuration .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Scanned: 2026-01-12 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 exhibits a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature), with no Linux equivalents or cross-platform examples. The prerequisites and instructions focus on creating Windows VMs, and references are primarily to Windows PowerShell DSC documentation. Linux support is only mentioned in passing, and there are no Linux-specific configuration samples, resources, or onboarding steps. The documentation also references Windows-specific tools and patterns before any mention of Linux, and does not provide parity in guidance for Linux users.
Recommendations
  • Add Linux DSC configuration examples, such as using nxFile or nxPackage resources, alongside Windows examples.
  • Include instructions for onboarding Linux VMs to Azure Automation State Configuration, with screenshots and step-by-step guidance.
  • Reference Linux DSC documentation and resources in the prerequisites and next steps sections.
  • Clarify the current support status for Linux (given the retirement announcement), and provide migration or alternative guidance for Linux users.
  • Ensure that cross-platform tools and patterns are presented equally, and avoid presenting Windows-specific tools or examples first.
  • Where PowerShell is referenced, note cross-platform alternatives (e.g., PowerShell Core, or native Linux configuration tools if applicable).
GitHub Create Pull Request
Automation Create configurations from existing servers for Azure Automation State Configuration ...ticles/automation/automation-dsc-config-from-server.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and references centered around Windows PowerShell DSC and related tools. There is no mention of Linux equivalents, and Linux onboarding is only referenced as a link, not described or exemplified. The documentation assumes familiarity with Windows tooling and does not provide guidance for Linux users.
Recommendations
  • Include explicit examples for Linux systems, such as how to extract configurations from Linux servers using cross-platform DSC tools.
  • Mention and describe Linux-compatible DSC resources and modules, if available.
  • Provide step-by-step instructions for onboarding Linux servers, not just a link.
  • Clarify which features or tools are Windows-only and suggest alternatives for Linux where possible.
  • Add references to community or Microsoft-supported DSC solutions for Linux, such as those using PowerShell Core or native Linux configuration management tools.
GitHub Create Pull Request
Automation Work with Azure Desired State Configuration extension version history ...rticles/automation/automation-dsc-extension-history.md
High Priority View Details →
Scanned: 2026-01-12 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 is heavily focused on Windows environments, with all version history, OS support, and examples referencing only Windows Server and Windows Client editions. PowerShell and Windows Management Framework are mentioned exclusively as the tooling for DSC, with no mention of Linux equivalents or support. There are no examples, instructions, or references for Linux DSC extension usage, and the only nod to Linux is an end-of-life announcement, further reinforcing the Windows-centric bias.
Recommendations
  • Add historical context and details about Linux support, including which extension versions supported Linux and when support was retired.
  • Include explicit Linux OS support information (where applicable) in version tables, or clearly state when Linux support was removed.
  • Provide examples or references for Linux DSC extension usage, including configuration and troubleshooting steps for Linux VMs (if still relevant for older versions).
  • Mention Linux equivalents to PowerShell DSC, such as OMI or cross-platform DSC implementations, and link to their documentation.
  • Balance references to Windows Management Framework and PowerShell with information about Linux management tools or frameworks, where applicable.
  • If Linux support is fully retired, add a prominent section summarizing the history and rationale, and direct users to alternative solutions for Linux configuration management.
GitHub Create Pull Request
Automation Enable Azure Automation State Configuration .../main/articles/automation/automation-dsc-onboarding.md
High Priority View Details →
Scanned: 2026-01-12 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 exhibits a strong Windows and PowerShell bias. Most examples and workflows are described using PowerShell cmdlets and Windows tooling, with Linux instructions often appearing after Windows ones or being less detailed. Key onboarding and configuration steps are presented primarily with PowerShell scripts, and Linux-specific workflows are less prominent, sometimes requiring the use of Windows tools to manage Linux nodes. There are also sections where Linux examples are missing or less comprehensive compared to their Windows counterparts.
Recommendations
  • Provide Linux-first or Linux-parity examples for all major workflows, including onboarding, configuration, and troubleshooting.
  • Include native Linux shell (bash) or Python examples for generating and applying metaconfigurations, rather than requiring PowerShell or Windows-based tools for Linux nodes.
  • Ensure that Linux tools and scripts (e.g., Register.py, SetDscLocalConfigurationManager.py) are documented with the same level of detail and step-by-step guidance as PowerShell cmdlets.
  • Clearly separate Windows and Linux instructions, and avoid requiring a Windows machine or PowerShell to manage Linux nodes.
  • Add troubleshooting and status-checking sections specifically for Linux, not just referencing the Windows DSC extension.
  • Where possible, mention Linux tools and workflows before or alongside Windows ones, rather than always after.
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-12 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 heavily on PowerShell DSC, providing more detailed information and examples for Windows (including specific OS versions, tools like WinRM, and proxy configuration via metaconfiguration scripts), and mentioning Windows requirements and features before Linux equivalents. Linux support is referenced but lacks detail, examples, and parity in tooling explanations. The documentation also references Windows-centric tools (e.g., WinRM, WMF 5.1) and does not provide Linux-specific configuration examples or troubleshooting guidance.
Recommendations
  • Provide Linux-specific examples for onboarding, configuration, and troubleshooting, similar to the detail given for Windows.
  • Include explicit lists of supported Linux distributions and versions, not just a link to external documentation.
  • Add Linux equivalents for Windows tools (e.g., explain how DSC for Linux is installed/configured, alternatives to WinRM, and proxy configuration with environment variables).
  • Ensure that Linux instructions and examples are presented alongside Windows, not only as afterthoughts or external links.
  • Add Linux-focused continuous deployment pipeline examples (e.g., using apt/yum instead of Chocolatey).
  • Expand the PowerShell cmdlet reference to include cross-platform usage or note Linux-specific considerations.
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-12 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 workflows. All code examples use Windows PowerShell, with explicit references to Windows file paths (e.g., c:\runbooks). There are no examples or guidance for using Linux or cross-platform tools, such as PowerShell Core on Linux/macOS, nor are there instructions for using Bash, Azure CLI, or other non-Windows environments. Windows terminology and tools are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Add examples for editing and managing runbooks using PowerShell Core on Linux/macOS, including appropriate file paths and environment notes.
  • Include instructions and sample commands for using Azure CLI to export/import runbooks, if supported.
  • Clarify that PowerShell is cross-platform and provide guidance for non-Windows users, including any prerequisites or differences.
  • Avoid using Windows-specific file paths in examples; use generic or platform-agnostic paths, or provide both Windows and Linux/macOS variants.
  • Explicitly mention support and limitations for Linux/macOS environments in Azure Automation documentation.
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-12 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 Windows PowerShell and PowerShell Workflow, with all examples, terminology, and tooling referencing Windows-centric technologies. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The graphical runbook authoring is described exclusively in terms of PowerShell cmdlets and expressions, and references to Windows tools (e.g., System Center Orchestrator, Service Management Automation) are present. No Linux or cross-platform examples, patterns, or considerations are provided.
Recommendations
  • Explicitly state the platform compatibility of graphical runbooks (e.g., clarify if only Windows-based Automation workers are supported, or if Linux workers are available).
  • Add examples or guidance for Linux users, such as how to author runbooks using Bash or Python if supported, or clarify limitations.
  • Reference cross-platform scripting options (e.g., PowerShell Core, Bash, Python) and provide parity in examples where possible.
  • Mention Linux equivalents to Windows tools (e.g., alternatives to System Center Orchestrator) or clarify if none exist.
  • Provide a section on considerations for Linux-based automation accounts, including supported modules, authentication, and limitations.
  • Update terminology to be more inclusive (e.g., 'PowerShell' instead of 'Windows PowerShell' where PowerShell Core is supported).
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-12 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 moderate Windows bias. PowerShell is mentioned as a primary onboarding and management channel, with no equivalent Linux shell examples (e.g., Bash). Windows terminology and tools (such as 'System account', 'PowerShell Workflow', and 'Run As account') are referenced more frequently and in greater detail than their Linux counterparts. Linux is mentioned, but examples, operational details, and troubleshooting guidance are not provided at parity with Windows. The documentation also lists Windows before Linux in several places and does not provide Linux-specific usage patterns or authentication guidance.
Recommendations
  • Add Linux-specific examples for onboarding, management, and troubleshooting, including Bash/CLI commands.
  • Provide parity in operational details for Linux, such as describing the 'nxautomation' account and its permissions, and how to configure authentication for Linux Hybrid Runbook Workers.
  • Include Linux shell (Bash) equivalents for PowerShell cmdlets and workflows.
  • Ensure that references to operating systems are balanced, listing Windows and Linux together or alternating order.
  • Expand documentation on Linux-specific troubleshooting and best practices for Hybrid Runbook Worker deployment and management.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
High Priority View Details →
Scanned: 2026-01-12 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: Windows and PowerShell tools/cmdlets are mentioned and linked more frequently and earlier than Linux equivalents. Backup and export instructions rely on Windows PowerShell cmdlets, with no Linux CLI or scripting alternatives provided. In the data retention section, only Windows PowerShell cmdlets are referenced for resource management. The TLS upgrade section gives a Windows registry link before the Linux OpenSSL guidance, and Linux instructions are less detailed and less integrated. There is a lack of parity in examples and tooling for Linux users.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI, Bash) examples and commands alongside PowerShell instructions for all resource management and backup operations.
  • Include links to Linux-specific documentation and tools (such as az CLI commands) wherever Windows/PowerShell cmdlets are referenced.
  • Ensure Linux guidance is presented with equal prominence and detail as Windows guidance, including step-by-step instructions for common tasks.
  • Add explicit Linux examples for exporting runbooks, DSC configurations, and other assets, using cross-platform tools or scripts.
  • Review tables and lists to ensure Linux is not treated as an afterthought or secondary platform.
GitHub Create Pull Request
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific DSC resources (such as WaitFor resources with a Windows path), linking only to Windows PowerShell documentation, and omitting explicit Linux equivalents or examples. There are no mentions of Linux DSC resources, nor are there examples or guidance tailored for Linux environments, despite Azure Automation supporting both Windows and Linux nodes.
Recommendations
  • Include references and links to Linux DSC resources and documentation, such as those for Linux-based Desired State Configuration.
  • Provide examples or notes on network configuration for Linux nodes, including any differences in resource usage or communication patterns.
  • Ensure parity in documentation by listing both Windows and Linux resource paths and examples when discussing DSC resources.
  • Add clarification on whether the listed network requirements apply identically to Linux nodes, or highlight any platform-specific considerations.
GitHub Create Pull Request
Automation Migrate from Orchestrator to Azure Automation (Beta) ...ticles/automation/automation-orchestrator-migration.md
High Priority View Details →
Scanned: 2026-01-12 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 is heavily focused on Windows-centric technologies, specifically PowerShell and Windows file paths. All examples and tooling references are for Windows environments, with no mention of Linux or cross-platform alternatives. The migration process assumes familiarity with Windows tools and patterns, and does not provide guidance or parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure Automation Python runbooks or Bash scripts where possible.
  • Clarify whether the migration toolkit and Runbook Converter can be used on Linux/macOS, or provide alternatives for non-Windows platforms.
  • Include instructions for Linux users on how to prepare and import runbooks, including file path conventions and environment setup.
  • Mention Azure Automation's support for non-Windows runbook types and how Linux users can leverage these.
  • Add notes or sections explicitly addressing cross-platform considerations and limitations.
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-12 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 bias toward Windows and PowerShell usage. All command-line examples for configuring Azure RBAC and managing role assignments use Azure PowerShell cmdlets, with no mention of Azure CLI or Bash alternatives. The only script-based instructions are PowerShell, and references to 'tabs=windows' in linked content further reinforce the Windows-first approach. There are no Linux-specific instructions, nor are cross-platform tools (such as Azure CLI) presented as alternatives or in parity with PowerShell. This may hinder Linux users or those who prefer Bash/CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, including role assignment, removal, and listing.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI, and provide Bash examples.
  • Where scripts are provided, offer both PowerShell and Bash/CLI versions, and clarify platform compatibility.
  • Review linked content (such as extension-based Hybrid Runbook Worker install) to ensure Linux instructions are present and not relegated to secondary tabs.
  • In introductory sections, list Azure CLI and REST API options before or alongside PowerShell, to avoid Windows-first impression.
  • Include notes or sections for Linux administrators, highlighting any platform-specific considerations or best practices.
GitHub Create Pull Request
Automation Azure Automation Runbook Types ...b/main/articles/automation/automation-runbook-types.md
High Priority View Details →
Scanned: 2026-01-12 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 exhibits a Windows bias by prioritizing PowerShell (a Windows-centric technology) throughout, referencing Windows-specific tools, file paths, and patterns (e.g., C:\modules, .ps1 scripts) without Linux equivalents. Examples and troubleshooting steps almost exclusively use PowerShell and Windows paths, with little to no demonstration of Linux-specific scenarios, especially for PowerShell and graphical runbooks. Python runbooks mention Linux only briefly and do not provide Linux-specific examples or troubleshooting. The documentation often discusses Windows support and limitations before Linux, and Linux support is sometimes described as an exception or afterthought.
Recommendations
  • Provide Linux-specific examples for PowerShell runbooks, including file paths, module management, and troubleshooting steps relevant to Linux Hybrid Runbook Workers.
  • Include explicit guidance and examples for authoring and running runbooks on Linux Hybrid Runbook Workers, especially for PowerShell and Python.
  • Balance the order of presentation so that Linux support and limitations are described alongside Windows, not after or as exceptions.
  • Add troubleshooting sections and sample scripts for common Linux issues (e.g., permissions, file system differences, environment variables) in runbooks.
  • Where Windows-specific tools or patterns are mentioned (e.g., C:\modules, .ps1), provide Linux equivalents (e.g., /opt/modules, .sh or .ps1 usage on Linux) or clarify cross-platform compatibility.
  • Clarify which features are available or limited on Linux Hybrid Runbook Workers for each runbook type, and provide parity where possible.
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-12 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 Windows bias by listing Windows operating systems and PowerShell versions first, focusing heavily on PowerShell (especially Windows PowerShell 5.1), and providing directory path examples only in Windows format (e.g., C:\abc). There are no Linux/macOS-specific examples or instructions, and the use of Windows-centric terminology and tools is prevalent throughout the page.
Recommendations
  • Provide Linux/macOS path examples alongside Windows ones (e.g., /home/user/abc).
  • When listing supported operating systems, alternate or randomize the order, or explicitly state that all are equally supported.
  • Include Linux/macOS-specific instructions or notes where relevant, such as how to install required modules or set directory paths.
  • Balance PowerShell and Python coverage, and clarify any OS-specific limitations or differences.
  • Avoid using only Windows-centric terminology (like 'C:\abc'); use cross-platform language or dual examples.
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-12 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 and PowerShell bias. All examples and workflows center around PowerShell, PowerShell Gallery, and Windows-centric tools. There is minimal mention of Python runbooks, and no Linux-specific examples, tools, or workflows are provided. Windows terminology and patterns (e.g., PowerShell cmdlets, Windows Azure VM) are used exclusively or before any Linux alternatives. The only nod to Linux is in a suggested tag for contributed runbooks, but no practical guidance or examples are given for Linux users.
Recommendations
  • Add explicit Linux-focused examples, such as importing and running Python runbooks for Linux VMs.
  • Include guidance for managing runbooks and modules on Linux Azure VMs, including file copy scenarios and automation tasks.
  • Provide parity in tooling by referencing Bash, CLI, or other Linux-native tools alongside PowerShell.
  • Ensure that documentation sections do not assume PowerShell as the default and offer alternative workflows for Linux users.
  • Highlight any limitations or differences when using Azure Automation with Linux environments.
  • Add links to Linux-specific tutorials and documentation where relevant.
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-12 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-centric error handling patterns. All examples, terminology, and recommended practices are framed around PowerShell and Windows tools, with no mention of Linux, Bash, or cross-platform alternatives. There are no examples or guidance for users running graphical runbooks in Linux environments or using non-PowerShell scripting languages.
Recommendations
  • Include examples using Bash or Python activities for error handling in graphical runbooks, especially for Linux-based automation scenarios.
  • Reference Linux equivalents for cmdlets and error handling patterns, such as using shell exit codes, try/catch in Bash, or error handling in Python.
  • Explicitly state platform compatibility for graphical runbooks and clarify whether Linux Hybrid Workers are supported.
  • Provide parallel documentation sections or examples for Linux users, including how to handle errors in non-Windows environments.
  • Avoid using Windows-centric terminology (e.g., PowerShell errors, cmdlets) as the default; instead, present cross-platform approaches side-by-side.
GitHub Create Pull Request
Automation What's New in Azure Automation .../azure-docs/blob/main/articles/automation/whats-new.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page for Azure Automation updates demonstrates a Windows bias through its heavy focus on PowerShell runbooks, frequent mention of Windows-specific modules and tools (such as AzureRM and Az PowerShell modules), and prioritization of PowerShell and Windows-related features in announcements. While Linux is occasionally referenced (e.g., support for Linux Hybrid Runbook Workers), examples and tooling are almost always PowerShell-centric, and Windows terminology is used first or exclusively in several places. There is a lack of parity in showcasing Linux-specific automation scenarios, tools, or shell examples (e.g., Bash), and the documentation does not provide equivalent Linux-first or cross-platform examples.
Recommendations
  • Include Linux shell (Bash, sh) and cross-platform CLI examples alongside PowerShell in runbook and automation scenarios.
  • Highlight Linux-specific automation use cases and tools, such as native Bash scripts, Ansible, or Python runbooks for Linux environments.
  • Ensure announcements and feature descriptions mention Linux and Windows equivalently, avoiding Windows-first ordering or terminology.
  • Provide migration and troubleshooting guidance for both Windows and Linux users, not just PowerShell/AzureRM/Az module transitions.
  • Add explicit documentation sections or examples for Linux Hybrid Runbook Workers, including installation, configuration, and scripting.
  • Where Visual Studio Code extensions or other tooling are referenced, clarify cross-platform support and provide Linux usage instructions.
GitHub Create Pull Request
Automation Runbook execution in Azure Automation ...in/articles/automation/automation-runbook-execution.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows and PowerShell bias. All code examples are in PowerShell, and references to runbook types and modules focus exclusively on PowerShell and Windows-specific tools (e.g., WinSCP.exe, IIS administration, .NET Framework). There is little to no mention of Linux equivalents, Bash, or Python runbooks, and Windows patterns (such as using C:\temp, UAC, and .exe files) are referenced without Linux alternatives. The documentation does not provide parity for Linux users or those using non-Windows scripting environments.
Recommendations
  • Add examples for Python runbooks and Bash scripts where applicable, especially in sections about error handling, temporary storage, and exception management.
  • Include Linux-specific guidance for Hybrid Runbook Workers, such as how to manage elevation, temporary storage (e.g., /tmp), and third-party software installation on Linux hosts.
  • Mention Linux equivalents for Windows tools (e.g., alternatives to WinSCP.exe, IIS administration, .NET Framework) and clarify module compatibility for Linux environments.
  • Provide explicit documentation on how Azure Automation supports Linux runbooks, including limitations, supported modules, and best practices.
  • Balance references to PowerShell with information about Python and other supported languages, and link to relevant tutorials for Linux users.
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-12 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/PowerShell bias. All examples, code snippets, and tooling references are exclusively for Windows PowerShell, with no mention of Linux-native tools, Bash, or cross-platform scripting alternatives. Windows PowerShell cmdlets and patterns are presented as the default and only option for runbook output and message stream handling. There is no guidance for users running Azure Automation runbooks from Linux environments or using non-PowerShell languages (except a brief note about Python output language support).
Recommendations
  • Add equivalent examples and instructions for Bash, Python, and other supported languages in Azure Automation, especially for output and message stream handling.
  • Explicitly mention cross-platform compatibility for Azure Automation runbooks, clarifying which features and cmdlets are available on Linux and macOS agents.
  • Provide guidance on retrieving runbook output and messages using Azure CLI, REST API, or SDKs, which are platform-agnostic.
  • Include references to Linux shell scripting patterns for error and output handling, such as using stdout/stderr, exit codes, and logging.
  • Clarify any limitations or differences in stream handling between Windows PowerShell and PowerShell Core (pwsh) on Linux/macOS.
  • Where PowerShell is referenced, specify whether instructions apply to Windows PowerShell, PowerShell Core, or both, and note any differences.
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-12 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 exclusively uses PowerShell and Windows-centric tooling for all examples and instructions, including module installation, scripting, and credential management. There are no references to Linux-native tools, Bash, or cross-platform alternatives. All steps assume familiarity with PowerShell and Windows environments, and there is no guidance for users who may prefer or require Linux-based automation approaches.
Recommendations
  • Provide equivalent examples using AWS CLI and Bash scripts for Linux users.
  • Include instructions for installing and using AWS CLI or SDKs in Azure Automation, highlighting cross-platform compatibility.
  • Mention how to author and run Python or Bash runbooks in Azure Automation for AWS VM provisioning.
  • Add notes or sections clarifying platform requirements and offering parity for Linux/macOS users.
  • Ensure that credential management examples include both PowerShell and Linux CLI methods.
GitHub Create Pull Request
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
High Priority View Details →
Scanned: 2026-01-12 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 providing only PowerShell examples for command-line operations and configuration steps, with no equivalent examples for Bash, Azure CLI, or other Linux-native tools. PowerShell is consistently presented as the primary or sole scripting interface, and Windows-centric tools and patterns (such as PowerShell cmdlets) are referenced throughout. REST API examples are included, but there is a lack of parity for Linux users who may prefer Bash or Azure CLI workflows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, including assigning managed identities, configuring Key Vault access policies, and updating encryption settings.
  • Include Bash script snippets for common tasks, especially those relevant to Linux automation environments.
  • Explicitly mention cross-platform support for Azure Automation and clarify that PowerShell is available on Linux, but users may also use Azure CLI or REST API.
  • Reorder sections or provide parallel examples so that Linux-friendly tools (Azure CLI, Bash) are presented before or alongside PowerShell, rather than after.
  • Reference documentation for Azure CLI and Bash where PowerShell modules are mentioned, to guide Linux users to equivalent resources.
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-12 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. All examples and instructions use PowerShell scripts and Windows-style paths (e.g., D:\examplefiles). The only method shown for creating test files is via PowerShell, with no mention of Linux shell equivalents. Folder paths and commands are Windows-centric, and there is no guidance for Linux-based Hybrid Runbook Workers or Bash scripting. The documentation assumes a Windows environment throughout and does not provide Linux parity.
Recommendations
  • Include equivalent Linux/Bash examples for file creation and manipulation (e.g., using 'touch' or 'mkdir' in Bash).
  • Mention how to configure watcher tasks for folders on Linux-based Hybrid Runbook Workers, including example Linux paths (e.g., /home/examplefiles).
  • Provide sample runbooks or scripts written in Bash or Python, or clarify if only PowerShell is supported.
  • Explicitly state platform requirements and limitations (e.g., if watcher tasks only work on Windows Hybrid Runbook Workers).
  • Add troubleshooting notes or guidance for users running Linux Hybrid Runbook Workers.
  • Where possible, use platform-neutral language and examples, or present Windows and Linux instructions side-by-side.
GitHub Create Pull Request
Automation Azure Automation account authentication overview ...in/articles/automation/automation-security-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell cmdlets as the primary automation method and omitting Linux-specific tools or examples. There is no mention of Bash, shell scripts, or Linux authentication patterns, nor are there examples or guidance for Linux users. The documentation implicitly assumes a Windows-centric environment, particularly in the context of Azure Automation and Hybrid Runbook Worker usage.
Recommendations
  • Include examples using Bash or shell scripts alongside PowerShell examples for runbook authentication and automation tasks.
  • Explicitly mention Linux support for Hybrid Runbook Workers and provide guidance for configuring authentication on Linux-based workers.
  • Reference Linux-native tools (e.g., Azure CLI, OpenSSH) in addition to Windows tools like PowerShell.
  • Add a section or callouts for cross-platform considerations, highlighting any differences or additional steps required for Linux environments.
  • Ensure parity in documentation by providing step-by-step instructions for both Windows and Linux users when creating and authenticating Automation accounts.
GitHub Create Pull Request
← Previous Page 3 of 40 Next →