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 326-350 of 982 flagged pages
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-manage-send-joblogs-log-analytics.md ...mation/automation-manage-send-joblogs-log-analytics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its references to PowerShell for job log access and error stream handling, and by mentioning Windows-centric tools and patterns before or instead of Linux equivalents. There are no Linux-specific instructions, examples, or references to Linux command-line tools or shell environments. All examples and troubleshooting steps assume use of the Azure portal or PowerShell, with no mention of Bash, CLI, or Linux automation workflows.
Recommendations
  • Add explicit instructions and examples for accessing job logs and streams using Azure CLI (az), Bash, or other Linux-native tools.
  • Include references to Linux automation patterns and troubleshooting steps, such as using shell scripts or cron jobs to interact with Azure Monitor logs.
  • Provide parity in examples by showing how to query logs and configure diagnostic settings from Linux environments, not just via PowerShell or the portal.
  • Mention cross-platform compatibility and clarify that all features are available regardless of OS, or note any limitations.
  • Where PowerShell is referenced, also include equivalent Azure CLI or REST API commands.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-managing-data.md ...b/main/articles/automation/automation-managing-data.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 frequently referencing Windows-specific tools (such as PowerShell cmdlets), listing Windows guidance before Linux, and providing detailed instructions and links for Windows scenarios while Linux guidance is more generic or less detailed. Several backup and retention examples rely solely on Windows PowerShell cmdlets, with no equivalent Linux CLI or automation examples provided.
Recommendations
  • Provide equivalent Linux CLI or shell script examples for backup and retention operations, such as using Azure CLI or REST API.
  • Include Linux-specific instructions and links for managing TLS settings, runbook exports, and DSC configurations, not just generic references to OpenSSL.
  • Balance the order of platform-specific guidance tables and sections so Linux is not always listed after Windows.
  • Reference cross-platform tools (e.g., Azure CLI, Python SDK) alongside PowerShell, and provide usage examples for both.
  • Where PowerShell cmdlets are mentioned, add notes or links to Linux-compatible alternatives.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-orchestrator-migration.md ...ticles/automation/automation-orchestrator-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and PowerShell, with all examples, tools, and migration steps centered around Windows technologies. PowerShell is presented as the default and only scripting language, and all paths and commands use Windows conventions. There is no mention of Linux, Bash, or cross-platform alternatives, nor are Linux-specific considerations or examples provided.
Recommendations
  • Include examples of how converted runbooks or modules could be used or managed on Linux-based Hybrid Runbook Workers.
  • Clarify whether Azure Automation graphical and PowerShell runbooks can be authored or executed from Linux environments, and provide guidance or limitations.
  • Provide Bash or cross-platform scripting examples where possible, especially for asset creation and runbook management.
  • Mention any Linux-compatible tools or modules for migration, or explicitly state if migration is Windows-only.
  • Document any differences or requirements for running converted runbooks on Linux Hybrid Runbook Workers, including module compatibility and execution environment.
  • Add a section addressing cross-platform support and considerations for organizations with mixed Windows and Linux infrastructure.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-output-and-messages.md ...s/automation/automation-runbook-output-and-messages.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, primarily focusing on PowerShell-based runbooks and Windows-centric tooling. All code examples use PowerShell syntax, and references to output/message streams, preference variables, and retrieval of job output are exclusively described in terms of Windows PowerShell cmdlets and patterns. There is no mention of Linux shell scripting, Bash, or cross-platform alternatives, nor are there examples or guidance for non-Windows environments. The documentation also refers to Windows PowerShell features and variables before any mention of Python runbooks, which are only briefly referenced in a note.
Recommendations
  • Include equivalent examples for Bash or Python runbooks, especially for output and error handling.
  • Describe how output and message streams work in non-PowerShell (e.g., Python) runbooks, including any differences in logging or retrieval.
  • Add instructions and examples for retrieving runbook output and messages using Azure CLI or REST API, which are platform-agnostic.
  • Clarify which features or cmdlets are Windows-specific and provide alternatives or limitations for Linux/macOS environments.
  • Reference Linux tools and scripting patterns where applicable, and ensure parity in documentation structure and example order.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-aws-deployment.md ...icles/automation/automation-scenario-aws-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows-centric tooling for all examples and instructions, including module installation, scripting, and credential management. There are no references to Linux-native tools (such as Bash, AWS CLI in Bash, or Python), nor are alternative approaches for Linux users mentioned. The documentation assumes the reader is familiar with PowerShell and Windows environments, and does not provide parity for Linux users.
Recommendations
  • Add equivalent instructions and examples using Bash and the AWS CLI for Linux users.
  • Include steps for installing and using the AWS CLI module in Azure Automation, with sample Bash scripts.
  • Provide guidance for credential management using Linux-native tools and patterns.
  • Ensure that both PowerShell and Bash (or Python) runbook types are covered in the documentation, with examples for each.
  • Mention cross-platform considerations and clarify which steps are Windows-specific and which are platform-agnostic.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-network-configuration.md ...rticles/automation/automation-network-configuration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. It references Windows-specific DSC resources (e.g., WaitFor resources with a Windows documentation link), and does not provide Linux equivalents or examples. The DSC resource documentation link points only to Windows PowerShell DSC resources, and there is no mention of Linux DSC resources or cross-platform configuration scenarios. No Linux-specific tools, patterns, or examples are provided, and Windows terminology appears first or exclusively.
Recommendations
  • Include links and examples for Linux DSC resources, such as those available for Linux nodes.
  • Provide guidance on configuring network requirements for Linux-based Hybrid Runbook Workers and State Configuration, including any differences in agent installation or communication.
  • Reference cross-platform DSC documentation, not just Windows PowerShell DSC resources.
  • Add explicit mention of Linux support and any platform-specific considerations for network configuration.
  • Ensure that examples and documentation are balanced between Windows and Linux, or clarify platform applicability where relevant.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-execution.md ...in/articles/automation/automation-runbook-execution.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and runbook references use PowerShell syntax and cmdlets, with no mention or examples of Bash, Python, or Linux shell scripting. Windows-specific tools and patterns (e.g., WMI, .exe files, C:\temp, UAC, .NET Framework) are referenced exclusively or before any Linux equivalents. There is little to no guidance for Linux users or those wishing to use non-PowerShell runbooks, and Linux-specific considerations are only briefly mentioned in the context of security constraints.
Recommendations
  • Add equivalent examples for Bash and Python runbooks, including error handling and resource management.
  • Include Linux-specific patterns and tools (e.g., using /tmp for temporary storage, systemd for process management, Linux authentication methods).
  • Mention Linux Hybrid Runbook Worker scenarios and provide guidance for installing and managing modules on Linux hosts.
  • Balance references to Windows tools (WMI, .NET, UAC) with Linux alternatives (e.g., psutil, system calls, sudo).
  • Provide links to documentation for Linux runbook types and modules, and clarify OS-specific limitations and best practices.
  • Ensure that introductory and summary sections mention Linux support and provide parity in recommendations.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-graphical-error-handling.md ...omation/automation-runbook-graphical-error-handling.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 concepts, cmdlets, and error handling patterns. All examples use PowerShell syntax and Windows-centric tools (e.g., Write-Warning, Start-AzVM, Get-AutomationVariable), with no mention of Linux equivalents or Bash scripting. The error handling discussion is framed entirely in terms of PowerShell's error types and behaviors, and there are no examples or guidance for Linux-based runbooks or cross-platform scripting.
Recommendations
  • Add equivalent examples using Bash or Python activities to illustrate error handling in graphical runbooks for Linux environments.
  • Discuss error handling concepts in a platform-neutral way, referencing both PowerShell and Linux shell scripting error patterns.
  • Include references to Linux tools (e.g., shell commands, error codes) and how they can be integrated into graphical runbooks.
  • Provide guidance on configuring and handling errors for runbooks that execute on Linux hybrid workers, including differences from Windows/PowerShell.
  • Ensure that documentation sections and examples alternate or balance between Windows and Linux approaches, rather than presenting Windows/PowerShell first and exclusively.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-using-watcher-task.md ...s/automation/automation-scenario-using-watcher-task.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and PowerShell bias. All examples, instructions, and code snippets assume the use of PowerShell and Windows file paths (e.g., D:\examplefiles). There are no references to Linux or cross-platform equivalents, and the only tooling mentioned is PowerShell. The process for creating test files and interacting with the Hybrid Runbook Worker is described exclusively in terms of Windows tools and conventions.
Recommendations
  • Provide equivalent examples and instructions for Linux environments, including bash shell commands (e.g., using 'touch' to create files) and Linux file paths (e.g., /home/user/examplefiles).
  • Clarify whether watcher tasks and runbooks can be executed on Linux-based Hybrid Runbook Workers, and if so, include setup and usage instructions for Linux.
  • Mention and demonstrate how to use cross-platform PowerShell Core (pwsh) if supported, and clarify any platform-specific limitations.
  • Update parameter examples (such as FOLDERPATH) to show both Windows and Linux path formats.
  • Explicitly state any platform restrictions or requirements for watcher tasks and runbooks.
  • Include screenshots or terminal outputs from Linux where applicable to ensure parity.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-secure-asset-encryption.md ...icles/automation/automation-secure-asset-encryption.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 detailed PowerShell-based instructions and examples for all key operations (identity assignment, key vault access policy, encryption configuration), while omitting equivalent examples for Linux-oriented tools such as Azure CLI, Bash, or SDKs. PowerShell is mentioned as the primary method for configuration, with REST API as a secondary option. References to installing the Azure Az PowerShell module further reinforce the Windows-centric approach, and there is no mention of Linux shell commands or cross-platform scripting alternatives.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell code blocks, ensuring Linux users have clear guidance.
  • Mention Azure CLI as an alternative in all procedural sections, and provide links to relevant CLI documentation.
  • Include guidance for cross-platform scripting, such as using Python SDK or Bash scripts, where applicable.
  • Reorder sections so that platform-neutral methods (REST API, CLI) are presented before or alongside PowerShell examples.
  • Explicitly state that all operations can be performed from Linux, macOS, and Windows, and clarify any platform-specific limitations.
  • Reference installation and usage of Azure CLI in the prerequisites, alongside PowerShell.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-send-email.md ...blob/main/articles/automation/automation-send-email.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses PowerShell for all examples, setup, and automation steps, with no mention of Bash, Azure CLI, or Linux-native tooling. Windows/PowerShell tools and patterns are referenced throughout, and all code samples are in PowerShell. There are no Linux or cross-platform alternatives provided, and the instructions assume a PowerShell-centric workflow.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for all major steps, including Key Vault creation, secret management, and role assignments.
  • Include instructions for creating and managing runbooks using Python or other supported languages in Azure Automation.
  • Mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical) and provide links or examples for non-PowerShell options.
  • Present cross-platform tools and commands (e.g., Azure CLI) before or alongside PowerShell examples to avoid Windows-first bias.
  • Clarify any platform-specific requirements and provide guidance for users on Linux or macOS.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-webhooks.md ...s/blob/main/articles/automation/automation-webhooks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 biased towards Windows and PowerShell usage. All code samples and walkthroughs use PowerShell cmdlets and Windows-centric tools (e.g., Az Module, Invoke-WebRequest, file paths with backslashes). There are no examples using Bash, curl, or other Linux-native tools, nor is there guidance for Linux users. Even REST API examples are wrapped in PowerShell scripts. The documentation assumes the user is on Windows or using PowerShell, and does not mention or prioritize Linux equivalents.
Recommendations
  • Provide equivalent examples using Bash and curl for webhook creation, invocation, and management.
  • Show how to use Azure CLI (az) commands for all operations, as Azure CLI is cross-platform.
  • Include Linux file path conventions and note differences in file handling.
  • Add a section or tabs for Linux/macOS users, demonstrating how to perform each step without PowerShell.
  • For REST API calls, show plain HTTP requests (e.g., using curl or httpie) rather than only PowerShell wrappers.
  • Explicitly mention platform compatibility and any differences in behavior or prerequisites for Linux/macOS.
  • Ensure that all code samples and instructions are tested and validated on Linux environments.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md ...e-docs/blob/main/articles/automation/delete-account.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by providing command-line examples exclusively in Azure PowerShell, which is primarily a Windows-centric tool. There are no examples using Bash, Azure CLI, or Linux-native tooling. The structure consistently presents Azure portal (GUI) steps first, followed by PowerShell, with no mention of Linux or cross-platform command-line alternatives. This may disadvantage users on Linux or macOS who prefer or require Bash/Azure CLI workflows.
Recommendations
  • Add Azure CLI examples for all command-line operations, especially for deleting Automation accounts and solutions.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide parity in instructions.
  • Where PowerShell is referenced, clarify its availability on Linux/macOS, or provide Bash equivalents.
  • Include a section or tabs for Linux/macOS users, demonstrating how to perform tasks using native tools or Azure CLI.
  • Review screenshots and UI instructions to ensure they are not Windows-specific, and clarify any OS dependencies.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-overview.md ...in/articles/automation/automation-security-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by referencing PowerShell cmdlets as the primary automation method, omitting equivalent Linux scripting examples (such as Bash or Python). Windows-centric tools and terminology (PowerShell, Azure Resource Manager) are mentioned exclusively or before any Linux alternatives. There is no mention of Linux-native automation tools, nor are Linux-specific authentication scenarios or examples provided.
Recommendations
  • Include Linux-based automation examples (e.g., Bash scripts, Python scripts) alongside PowerShell examples.
  • Explicitly mention how authentication works for runbooks executed on Linux Hybrid Runbook Workers, including any differences or additional steps required.
  • Reference cross-platform tools (such as Azure CLI) and provide examples for both Windows and Linux environments.
  • Clarify whether managed identities and authentication workflows are identical for Linux and Windows runbook workers, and document any platform-specific caveats.
  • Add links to Linux-focused documentation or quickstarts for creating and managing automation accounts and runbooks.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-services.md ...s/blob/main/articles/automation/automation-services.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a notable Windows and PowerShell bias. Azure Automation is repeatedly described in terms of PowerShell runbooks, with extensive references to the PowerShell Gallery and community. Windows-centric tools and concepts (e.g., PowerShell, Active Directory, SQL Server) are mentioned more frequently and in greater detail than Linux equivalents. While Python is occasionally mentioned, Linux-specific automation patterns, tools, or examples are largely absent. The documentation assumes familiarity with Windows administration paradigms and does not provide parity for Linux administrators.
Recommendations
  • Include explicit Linux-focused examples and scenarios for each automation service, such as managing Linux VMs, using Bash scripts, or integrating with Linux-native tools.
  • Balance references to PowerShell with equal coverage of Bash, Python, or other scripting languages commonly used in Linux environments.
  • Highlight Linux-compatible modules, connectors, and best practices for automation, especially in sections discussing configuration management, update management, and hybrid automation.
  • Mention Linux equivalents to Windows-centric tools (e.g., systemd, cron, SSH, Linux package managers) when discussing automation tasks.
  • Ensure that user personas and scenarios reflect both Windows and Linux administrators, with tasks and workflows relevant to each.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md ...g/guidance-migration-log-analytics-monitoring-agent.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily through its reliance on PowerShell for scripting and migration guidance, with prerequisites and instructions centered on PowerShell installation and usage. Windows-specific data types (services, files, registry) are listed before Linux equivalents, and Windows terminology (e.g., MSI installer, Windows registry) is more prominent. There are no Linux shell (bash) script examples or explicit Linux command-line instructions, and Linux migration steps are not shown separately. The guidance for manual migration and alert configuration links to pages with 'windows' as the default tab, further reinforcing Windows-first presentation.
Recommendations
  • Provide equivalent Linux shell (bash) script examples for migration, or clarify how Linux users can perform the migration using native tools.
  • List Linux data types (files, daemons) alongside or before Windows types to balance presentation.
  • Include explicit instructions for Linux environments, such as using Azure CLI or bash, and clarify any Linux-specific prerequisites.
  • Ensure that linked tutorials and configuration guides default to a neutral or Linux-first tab, or highlight Linux steps equally.
  • Mention Linux package manager installation methods for required tools (e.g., PowerShell, Azure CLI) and clarify cross-platform compatibility.
  • Add screenshots or walkthroughs of the migration process on Linux VMs in the Azure portal.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/compose-configurationwithcompositeresources.md ...omation/compose-configurationwithcompositeresources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. It is heavily focused on PowerShell DSC (Desired State Configuration), with terminology, examples, and referenced resources all centered around Windows-centric tools and patterns. The only example of a continuous deployment pipeline uses Chocolatey, a Windows package manager. There are no Linux-specific examples, tools, or patterns provided, and the only mention of Linux is in a retirement announcement, indicating reduced support. All configuration steps and screenshots are tailored to Windows/PowerShell workflows.
Recommendations
  • Add equivalent examples for Linux DSC configurations, including screenshots and step-by-step instructions.
  • Reference and link to Linux DSC resources and modules where applicable.
  • Include examples of using Linux package managers (e.g., apt, yum) in composite resources.
  • Clarify the current support status for Linux nodes and suggest alternatives or migration paths for Linux users.
  • Balance PowerShell references with Bash or other Linux shell examples where possible.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-local-authentication.md ...in/articles/automation/disable-local-authentication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 exclusively providing PowerShell examples and cmdlets for managing the 'Disable local authentication' feature in Azure Automation. There is no mention of Linux-native tools, shell commands, or cross-platform alternatives. The instructions and verification steps rely solely on PowerShell, which is traditionally associated with Windows environments, and do not address how Linux users might perform these tasks.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include REST API usage examples with curl or httpie, showing how to PATCH the disableLocalAuth property from a Linux shell.
  • Clarify that PowerShell Core is available on Linux, but also offer native Linux shell alternatives for users who do not use PowerShell.
  • Add a section or note explicitly addressing Linux/macOS users and guiding them on how to perform these operations without relying on Windows-centric tools.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-managed-identity-for-automation.md .../automation/disable-managed-identity-for-automation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides only PowerShell-based examples for interacting with the REST API, relying on Windows-centric tools and cmdlets. There are no equivalent examples for Linux users (e.g., using Bash, curl, or Azure CLI), and the workflow assumes familiarity with Windows/PowerShell environments. This creates a bias toward Windows users and does not offer parity for Linux or cross-platform scenarios.
Recommendations
  • Add Linux/Bash examples using curl or wget to send the PATCH request.
  • Include Azure CLI examples, which are cross-platform and widely used.
  • Present PowerShell and Linux/Azure CLI examples side-by-side, or clearly label them as platform-specific.
  • Mention prerequisites for both Windows and Linux environments, including authentication methods.
  • Avoid assuming the use of PowerShell as the default automation tool; provide alternatives for other platforms.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enable-managed-identity-for-automation.md ...s/automation/enable-managed-identity-for-automation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and PowerShell bias. Nearly all code examples and procedural steps use PowerShell, with no Bash, CLI, or Linux-native scripting alternatives. Windows tools and paths are referenced first or exclusively, and Linux equivalents are mentioned only briefly or as afterthoughts. There are no examples using Azure CLI, Bash, or Linux shell scripting for key tasks such as enabling managed identity, assigning roles, or authenticating. The REST API and ARM template sections also rely on PowerShell for invocation, further reinforcing the Windows-centric approach.
Recommendations
  • Add Azure CLI examples for all major operations (enabling managed identity, assigning roles, authenticating, etc.).
  • Provide Bash or shell script equivalents for REST API calls and ARM template deployments.
  • Include Linux-native instructions and examples (e.g., using curl, jq, az CLI) alongside PowerShell.
  • Present Linux and Windows instructions in parallel or alternate their order to avoid Windows-first bias.
  • Reference Linux file paths and tools equally when discussing Hybrid Runbook Worker version checks and other operational details.
  • Ensure Python and other cross-platform runbook examples are as detailed as PowerShell ones.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/extension-based-hybrid-runbook-worker-install.md ...ation/extension-based-hybrid-runbook-worker-install.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 several forms of Windows bias. Windows and PowerShell examples are consistently presented first, with detailed PowerShell cmdlets and scripts provided for Windows scenarios. Bicep and ARM template examples are exclusively for Windows VMs, with no Linux equivalents. The use of Windows-specific tools (e.g., Windows PowerShell 5.1, .NET Framework) is emphasized, while Linux requirements are less detailed and lack parity in automation examples. Folder paths and permissions are described only for Windows, with minimal Linux-specific operational guidance. The documentation also lacks Linux-focused CLI, Bicep, and ARM template examples, and troubleshooting notes are Windows-centric.
Recommendations
  • Provide Linux-first or side-by-side examples for all code snippets, especially in PowerShell, Bicep, ARM templates, and CLI sections.
  • Include Linux-specific automation examples in Bicep and ARM templates, showing how to deploy and manage Linux Hybrid Runbook Workers.
  • Expand Linux operational guidance, such as folder permissions, troubleshooting, and extension management, to match the detail given for Windows.
  • Balance the mention of Windows tools with Linux equivalents (e.g., Bash, Python, systemd), and clarify when PowerShell Core is supported on Linux.
  • Ensure all instructions, especially those for proxy, firewall, and extension installation, are equally detailed for Linux environments.
  • Add explicit Linux troubleshooting steps and operational best practices, similar to those provided for Windows (e.g., handling permissions, extension upgrade issues).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/private-link-security.md ...in/articles/automation/how-to/private-link-security.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 only PowerShell examples for configuring public network access, referencing Windows tools and patterns (such as PowerShell DSC and Log Analytics agent for Windows) before or more prominently than their Linux equivalents, and omitting explicit Linux CLI or scripting examples for key configuration steps. While Linux is mentioned as supported (e.g., Log Analytics agent for Windows or Linux, Update Management for Windows and Linux), actionable instructions and code samples are Windows-centric.
Recommendations
  • Provide equivalent CLI or Bash examples for all PowerShell scripts, especially for setting publicNetworkAccess and other resource properties.
  • Include explicit instructions and code samples for Linux environments (e.g., using Azure CLI, Bash, or Python) alongside Windows/PowerShell examples.
  • Mention Linux tools and patterns (such as DSC for Linux, Linux-based Hybrid Runbook Workers) with equal prominence and detail as Windows counterparts.
  • Ensure screenshots and UI walkthroughs do not assume Windows-only environments; clarify cross-platform applicability.
  • Add troubleshooting and configuration notes specific to Linux systems where relevant.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-run-as-account.md ...blob/main/articles/automation/delete-run-as-account.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page focuses on deleting Azure Automation Run As accounts, but all command-line examples and instructions reference PowerShell and the Azure portal, both of which are Windows-centric. There are no examples or guidance for Linux users, such as using Azure CLI or Bash. The mention of PowerShell as the only script-based method and the lack of Linux tool parity indicate a Windows bias.
Recommendations
  • Add equivalent instructions using Azure CLI (az commands) for Linux/macOS users.
  • Include Bash script examples alongside PowerShell examples.
  • Explicitly mention cross-platform tools and clarify which steps can be performed on non-Windows systems.
  • Ensure that portal instructions are not Windows-specific and clarify browser requirements if any.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/graphical-runbook-sdk.md ...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 toward Windows and PowerShell. All examples and SDK usage revolve around PowerShell commands, PowerShell Workflow, and Windows-centric concepts. There is no mention of Linux-compatible scripting, Bash, or cross-platform alternatives. The SDK and runbook activities are described exclusively in terms of PowerShell, with no Linux shell or Python examples. Windows tools and patterns (e.g., .dll assemblies, PowerShell commands) are referenced throughout, and Linux equivalents are absent.
Recommendations
  • Add explicit notes about platform compatibility, clarifying whether the SDK and graphical runbooks can be used on Linux-based Automation accounts.
  • Provide Linux/Bash or Python examples where possible, or state limitations if only Windows/PowerShell is supported.
  • Mention cross-platform alternatives for automation, such as Azure Automation support for Python or Bash runbooks.
  • Include guidance for users working in Linux environments, such as how to author, test, and import runbooks without relying on Windows-specific tools.
  • If the SDK is Windows-only, clearly state this in the prerequisites and introduction.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-sql-server-in-automation.md ...articles/automation/manage-sql-server-in-automation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 using PowerShell cmdlets and examples, referencing Windows-centric tools (e.g., PowerShell, Hybrid Runbook Worker), and omitting any Linux or cross-platform alternatives. All sample code and module installation instructions are PowerShell-based, with no mention of Bash, Azure CLI, or Linux-specific workflows. The documentation assumes the reader is using a Windows environment and does not provide guidance for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for database management tasks.
  • Include instructions for installing and using required modules on Linux systems.
  • Mention cross-platform alternatives to PowerShell, such as Azure CLI or REST API calls.
  • Clarify which steps and tools are platform-agnostic and which are Windows-specific.
  • Provide guidance for running runbooks and Hybrid Workers on Linux machines, including any prerequisites or limitations.
GitHub Create Pull Request
← Previous Page 14 of 40 Next →