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 376-400 of 982 flagged pages
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstart-create-automation-account-template.md ...ation/quickstart-create-automation-account-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 referencing PowerShell and its usage before Azure CLI, providing PowerShell-specific instructions and error messages, and omitting explicit Linux or cross-platform examples. The guidance for running the ARM template prioritizes PowerShell and portal instructions, with Azure CLI mentioned only as an alternative. There are no Linux-specific instructions, screenshots, or troubleshooting notes, and PowerShell is referenced as the default scripting environment for sample runbooks.
Recommendations
  • Provide explicit Linux and macOS instructions and examples, including screenshots if relevant.
  • Ensure Azure CLI examples are given equal prominence to PowerShell, and consider listing CLI before PowerShell to avoid Windows-first ordering.
  • Include troubleshooting notes for Linux environments, such as common issues with shell environments or permissions.
  • Clarify that both PowerShell and Azure CLI are cross-platform, and provide installation links for non-Windows systems.
  • Add sample Bash runbooks or highlight Python runbooks to demonstrate Linux-friendly automation options.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/desired-state-configuration.md ...automation/troubleshoot/desired-state-configuration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell, with nearly all troubleshooting steps, examples, and cmdlets focused on Windows environments. PowerShell DSC tools and commands are referenced throughout, and Windows-specific troubleshooting (such as WMI corruption and certificate management) is detailed. Linux is mentioned only in a few scenarios, often as an afterthought or in a single dedicated section, with minimal guidance or examples for Linux users.
Recommendations
  • Add equivalent Linux troubleshooting steps and examples for each scenario, especially for log collection, agent registration, and extension management.
  • Provide Linux shell commands (e.g., bash, systemctl, journalctl) alongside PowerShell examples for tasks such as certificate management, log inspection, and agent operations.
  • Reference Linux DSC extension documentation and tools where appropriate, and clarify differences in workflow between Windows and Linux nodes.
  • Ensure that Linux scenarios are presented with equal prominence and detail as Windows scenarios, rather than being grouped at the end or in isolated sections.
  • Where PowerShell cmdlets are mentioned, include the Linux method (such as using the OMS agent, DSC extension commands, or relevant configuration files) for parity.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-configuration-based-on-stig.md ...tomation/automation-dsc-configuration-based-on-stig.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, specifically referencing Windows PowerShell 5.1, PowerSTIG (a PowerShell-based tool), and DSC (Desired State Configuration) in a Windows context. There are no Linux-specific examples, tools, or guidance, and all instructions and references are tailored to Windows environments. Linux is only mentioned in passing, with no substantive content or parity in examples.
Recommendations
  • Include equivalent Linux examples and workflows for configuring STIG baselines, such as using Linux DSC agents or other configuration management tools (e.g., Ansible, Chef, or native Linux DSC).
  • Provide explicit instructions or references for onboarding and managing Linux machines with Azure Automation State Configuration.
  • Mention and link to Linux-specific resources, modules, or community projects that help achieve STIG compliance.
  • Clarify in the introduction whether the guidance is Windows-only or provide a parallel section for Linux users.
  • Balance the order of presentation so that Linux and Windows are treated equally, or at least acknowledge the current limitations for Linux.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-connections.md ...lob/main/articles/automation/automation-connections.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows/PowerShell bias. All command-line examples for managing connections (creation, retrieval, etc.) are provided exclusively using PowerShell cmdlets (Az module), with no mention of Bash, Azure CLI, or Linux-native tools. The workflow for creating connections outside the portal is described only for Windows PowerShell, and the internal cmdlets are PowerShell-centric. Python is supported for runbooks, but only within the context of Azure Automation, not for asset management from the command line. There are no examples or guidance for Linux users or those preferring cross-platform CLI tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for creating, retrieving, and managing Automation connections, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell examples work on both Windows and Linux (with PowerShell Core), or clarify any platform-specific limitations.
  • Provide Bash or shell script snippets where appropriate, especially for tasks that can be automated outside of PowerShell.
  • Include a section or note for Linux/macOS users, outlining supported tools and any differences in workflow.
  • Where possible, reference REST API usage for connection management, as this is platform-agnostic.
  • Ensure that all steps and screenshots are not Windows-specific (e.g., avoid referencing Windows-only UI elements or terminology).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-disaster-recovery.md ...in/articles/automation/automation-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or Linux-native alternatives. All automation and migration examples rely on PowerShell, a Windows-centric tool, and installation instructions for Hybrid Runbook Workers default to Windows tabs and links. There is no parity in Linux scripting or tooling, and Linux users are left without guidance for equivalent disaster recovery procedures.
Recommendations
  • Provide Linux-native migration examples using Bash, Python, or Azure CLI, alongside PowerShell.
  • Include explicit instructions and tabs for Linux when describing Hybrid Runbook Worker installation and management.
  • Mention and document Linux tools and patterns (e.g., shell scripts, cron jobs, Azure CLI) where PowerShell is referenced.
  • Ensure that all examples and scripts are cross-platform or offer alternatives for Linux environments.
  • Review and update documentation to present Windows and Linux options in parallel, rather than defaulting to Windows-first approaches.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-edit-textual-runbook.md ...articles/automation/automation-edit-textual-runbook.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 focusing exclusively on PowerShell and Windows PowerShell workflows, providing only Windows-centric examples (e.g., file paths like c:\runbooks), and referencing Windows tools and cmdlets. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting editors. The documentation does not mention or prioritize Linux-compatible workflows or tools.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for Linux/macOS users, including file paths and script management.
  • Clarify that PowerShell Core (pwsh) is cross-platform and provide examples for Linux and macOS environments.
  • Include instructions for editing and importing runbooks from Linux/macOS systems, such as using VS Code or other cross-platform editors.
  • Mention and demonstrate how to use Az module cmdlets in PowerShell Core on non-Windows platforms.
  • Avoid using Windows-specific file paths (e.g., c:\runbooks) and provide platform-agnostic or alternative examples (e.g., ~/runbooks for Linux/macOS).
  • Explicitly state platform compatibility and limitations for each method or tool described.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-role-based-access-control.md ...les/automation/automation-role-based-access-control.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily through exclusive use of PowerShell examples and references to Windows-centric tools and patterns. All command-line instructions for managing Azure RBAC and Automation roles are provided using Azure PowerShell cmdlets, with no mention of equivalent Azure CLI or REST API methods, which are cross-platform and preferred by many Linux users. The only referenced installation guide for Hybrid Runbook Workers is for Windows. There is no guidance or examples for Linux users, nor are Linux tools or shell commands (e.g., Bash, Azure CLI) presented alongside or before Windows/PowerShell instructions.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, including role assignment, listing, and removal.
  • Include REST API examples for RBAC operations to provide platform-neutral guidance.
  • Reference both Windows and Linux installation guides for Hybrid Runbook Workers, or clarify cross-platform support.
  • Ensure that introductory sections mention Azure CLI and REST API as first-class options for managing permissions, not just PowerShell.
  • Where screenshots or UI instructions are given, clarify any OS-specific differences or provide parity for Linux users.
  • Audit linked resources to ensure Linux and cross-platform instructions are present and easy to find.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-getting-started.md .../articles/automation/automation-dsc-getting-started.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and the WindowsFeature resource, with no equivalent Linux examples or resources shown. The prerequisites and step-by-step instructions focus on creating and managing Windows VMs, referencing Windows-specific documentation and tools (e.g., 'Create your first Windows virtual machine', 'Windows PowerShell Desired State Configuration Overview'). Linux support is only mentioned in passing, with no practical guidance or examples. References and links are heavily skewed toward Windows and PowerShell, and there is no mention of Linux DSC resources, onboarding Linux nodes, or managing Linux configurations.
Recommendations
  • Add parallel Linux examples for creating, importing, and compiling DSC configurations, using Linux DSC resources (e.g., nxFile, nxPackage).
  • Include instructions and screenshots for onboarding Linux VMs to Azure Automation State Configuration.
  • Reference Linux-specific documentation and tools, such as onboarding scripts for Linux, and provide links to Linux DSC resource documentation.
  • Clarify the current support status for Linux (especially given the Linux retirement announcement), and provide migration guidance or alternatives for Linux users.
  • Ensure that prerequisites and step-by-step instructions mention both Windows and Linux supported operating systems, and provide links to both Windows and Linux VM creation guides.
  • Balance references to PowerShell with equivalent Bash or shell script examples where possible.
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-08 00:53
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-specific instructions and tools (such as PowerShell cmdlets) are mentioned first and more frequently, with Linux alternatives either missing or less detailed. Examples and guidance for backup and retention rely heavily on Windows PowerShell, and Windows registry/TLS settings are referenced before Linux equivalents. Linux instructions are present but less comprehensive, and Linux-specific tooling or examples (other than a single Python script for TLS) are largely absent.
Recommendations
  • Provide Linux-specific examples and tooling for all major operations, such as data backup/export and resource management, not just TLS configuration.
  • Include Bash/CLI commands and references to Linux-native automation tools (e.g., Azure CLI, shell scripts) alongside or before Windows/PowerShell examples.
  • Ensure parity in guidance detail for both platforms, e.g., how to export runbooks, DSC configurations, and other assets using Linux tools.
  • Reference Linux documentation and best practices as prominently as Windows ones.
  • Where PowerShell cmdlets are mentioned, also provide equivalent Azure CLI or REST API instructions for Linux users.
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-08 00:53
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 and instructions, including setup, resource management, and runbook creation. There are no examples or guidance for using Bash, Azure CLI, or other Linux-native tools. The workflow assumes familiarity with PowerShell and Windows-centric patterns, such as cmdlets and context management, and does not mention or prioritize Linux alternatives. This creates a strong Windows bias and may hinder Linux users from following the guide.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for all major steps, including Key Vault creation, secret management, and role assignment.
  • Include instructions for creating and managing runbooks using the Azure portal and/or REST API, which are platform-agnostic.
  • Provide guidance on how to use Python or other languages supported by Azure Automation for sending emails, especially for Linux-based automation accounts.
  • Explicitly mention Linux compatibility and provide troubleshooting tips for non-Windows environments.
  • Reorganize the documentation to present platform-agnostic methods first, or side-by-side with PowerShell examples.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/context-switching.md ...ocs/blob/main/articles/automation/context-switching.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Az/AzureRM cmdlets for all examples and recommendations, which are Windows-centric tools. There are no Bash, CLI, or Linux-native examples, nor is there mention of cross-platform alternatives. The guidance assumes use of PowerShell, which is more common on Windows, and does not address Linux automation scenarios.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
  • Include Bash script snippets demonstrating context management in Azure Automation.
  • Explicitly mention how context switching issues apply to Linux-based runbooks and how to mitigate them.
  • Clarify whether the recommendations are specific to PowerShell or apply to other scripting environments supported by Azure Automation.
  • Provide links or references to documentation for Linux and cross-platform automation scenarios.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing PowerShell examples and cmdlets (e.g., Get-AzAutomationAccount, Invoke-AzRestMethod) for managing the 'Disable local authentication' feature. There are no CLI, Bash, or Linux-native examples, nor is there mention of cross-platform alternatives. Windows tools and patterns are referenced first and exclusively, which may hinder Linux users or those using non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, demonstrating how to check and set the 'DisableLocalAuth' property using az automation account commands or az rest.
  • Include Bash shell script examples for REST API calls, using curl or similar tools, to illustrate how Linux users can perform the same actions.
  • Explicitly mention that the operations can be performed from any platform (Windows, Linux, macOS) and provide guidance for cross-platform usage.
  • Where possible, link to documentation for Azure CLI and REST API usage, not just PowerShell cmdlets.
  • Reorder examples so that cross-platform methods (CLI, REST API) are presented before or alongside Windows/PowerShell methods.
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-08 00:53
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 oriented toward Windows environments, with exclusive use of PowerShell runbooks, Windows-style file paths (e.g., D:\examplefiles), and instructions that assume the use of PowerShell and Windows file systems. There are no examples or guidance for Linux-based Hybrid Runbook Workers, nor are Linux shell commands or file path conventions mentioned. The only tooling and scripting language referenced is PowerShell, and all examples use Windows-centric patterns.
Recommendations
  • Provide equivalent examples and instructions for Linux-based Hybrid Runbook Workers, including bash shell commands and Linux file path conventions (e.g., /home/examplefiles).
  • Clarify whether watcher tasks and the provided runbooks are compatible with Linux Hybrid Runbook Workers, and if not, state this limitation explicitly.
  • Offer sample runbooks or scripts written in Python or bash for Linux environments, or explain how to adapt the PowerShell logic for Linux.
  • Include Linux-specific troubleshooting tips and expected output examples.
  • When showing how to create test files, provide both PowerShell (Windows) and bash (Linux) command examples side by side.
  • Avoid using only Windows drive letters and backslashes in examples; show Linux paths as well.
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-08 00:53
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 examples and instructions for creating, managing, and invoking webhooks use PowerShell cmdlets and Windows-centric tooling, with no mention of Linux-native tools or cross-platform alternatives. Even REST API examples are shown via PowerShell's Invoke-RestMethod, and there are no bash, curl, or other Linux shell examples. The documentation assumes the user is operating in a Windows/PowerShell environment and does not provide parity for Linux users.
Recommendations
  • Add equivalent examples using bash and curl for invoking webhooks and REST API calls.
  • Show how to use Azure CLI (az) for creating, managing, and deleting webhooks and runbooks.
  • Include instructions and code samples for Linux/macOS environments, such as using curl, jq, and native shell scripting.
  • Explicitly mention cross-platform support and provide guidance for users on non-Windows systems.
  • Where PowerShell is required, clarify if PowerShell Core (pwsh) on Linux/macOS is supported, and provide examples if so.
  • Balance the order of examples so that Linux and cross-platform methods are presented alongside or before Windows/PowerShell methods.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/dsc-configuration.md ...n/articles/automation/quickstarts/dsc-configuration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 relies heavily on PowerShell syntax and tools, references Windows-centric DSC workflows, and mentions Windows server management as the primary use case. Although the example configuration targets a LAMP stack (Linux), all instructions, tooling, and references (such as PowerShell Gallery, DSC configuration files in .ps1 format, and links to PowerShell documentation) are Windows/PowerShell-centric. The retirement of Linux DSC is noted, but no alternative Linux-native configuration management approaches or examples are provided.
Recommendations
  • Provide parity by including Linux-native configuration management alternatives (e.g., Ansible, Chef, Puppet) for Azure VMs.
  • Offer examples and instructions using Linux shell scripts or YAML-based configuration files, not just PowerShell.
  • Reference Linux package managers and service controllers (e.g., apt, systemctl) in examples where appropriate.
  • Include links to Linux documentation and resources alongside PowerShell/Windows links.
  • Clarify the limitations and alternatives for Linux users, especially given the retirement of Linux DSC, and guide them to supported solutions.
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-08 00:53
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 Windows-centric tooling (e.g., Invoke-Sqlcmd, Install-Module, Get-Command) for all automation and database management examples. No Linux shell (bash, Azure CLI) or cross-platform alternatives are provided, and the instructions assume the use of Windows environments (elevated PowerShell prompt, environment variables like $env:computerName). The documentation does not mention or demonstrate how to perform these tasks from Linux or macOS systems, nor does it reference Linux-specific modules or patterns.
Recommendations
  • Add equivalent examples using Azure CLI and bash scripts for Linux users.
  • Document how to install and use required modules (Az.Accounts, SqlServer) on Linux/macOS, including any prerequisites.
  • Provide instructions for running Hybrid Runbook Worker on Linux, if supported, or clarify platform limitations.
  • Reference cross-platform tools (e.g., sqlcmd, Azure CLI) alongside PowerShell, and show usage for database connections and automation.
  • Explicitly state platform requirements and parity, and ensure Linux/macOS users are not excluded from the workflow.
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-08 00:53
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 the exclusive use of PowerShell for configuration examples (specifically for setting public network access flags), and by referencing Windows tools and patterns (e.g., Desired State Configuration, PowerShell DSC) before or more prominently than their Linux equivalents. There are no CLI, Bash, or Linux-specific configuration examples provided, and Linux is only mentioned in passing (e.g., Log Analytics agent compatibility and Update Management support), without concrete usage instructions or examples.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for configuration tasks, such as setting publicNetworkAccess, alongside PowerShell scripts.
  • Include explicit Linux usage scenarios and examples, such as configuring Hybrid Runbook Worker or Update Management on Linux hosts, with step-by-step instructions.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Clarify any differences or additional steps required for Linux environments, especially for DNS configuration and agent setup.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments (e.g., Azure Portal is cross-platform, but command-line examples should show parity).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/source-control-integration.md ...main/articles/automation/source-control-integration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 command-line examples use PowerShell, with no mention of Bash, CLI, or Linux-native tools. The prerequisites and configuration steps assume the use of PowerShell consoles and Azure PowerShell cmdlets. There are no examples or guidance for Linux users, such as using Azure CLI, Bash scripts, or cross-platform automation tools. The documentation also references Windows-centric concepts (e.g., PowerShell 5.1 runbooks) and troubleshooting links that point to PowerShell-specific resources.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for role assignment and source control configuration.
  • Clarify which steps are platform-agnostic and which are Windows-specific; provide guidance for Linux/macOS users.
  • Include references to Linux-compatible editors and troubleshooting resources, not just PowerShell/VSCode.
  • Explicitly state platform requirements and limitations (e.g., if only PowerShell 5.1 runbooks are supported, explain alternatives for Python or Bash runbooks).
  • Where screenshots or instructions reference Windows tools, provide parallel instructions for Linux/macOS environments.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/credentials.md ...in/articles/automation/shared-resources/credentials.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 through its exclusive use of PowerShell cmdlets and examples, which are native to Windows. All CLI examples for credential management are given in PowerShell, with no mention of Linux shell equivalents or cross-platform CLI tools. The documentation refers to Windows-specific tools and patterns (e.g., PSCredential, PowerShell modules) and does not provide guidance for Linux users or those using Bash/Az CLI. The Python examples are present but limited to runbooks, not general credential management. The creation and retrieval of credentials outside the portal are only demonstrated with Windows PowerShell.
Recommendations
  • Add equivalent examples using Azure CLI (az) for credential management, which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash shell examples for creating and retrieving credentials, where possible.
  • Clarify which steps and cmdlets are Windows-specific and provide alternative instructions for Linux/macOS users.
  • Mention any limitations or differences in credential management when using Linux-based hybrid workers or non-Windows environments.
  • Expand Python examples to cover credential creation, not just retrieval, if supported.
  • Consider referencing REST API or SDK methods for credential management, which are platform-agnostic.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runbook-input-parameters.md ...b/main/articles/automation/runbook-input-parameters.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong bias towards Windows and PowerShell environments. Most examples, code snippets, and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). Windows-specific tools and patterns (e.g., PowerShell cmdlets, .NET types, C# SDK usage) are presented exclusively or before mentioning Python as an alternative. There are no examples or guidance for Linux shell scripting, Bash, or cross-platform CLI usage, and no mention of Linux-specific patterns or tools. The Python section is brief and lacks parity in detail and examples compared to PowerShell. The documentation assumes PowerShell as the default automation language and environment, with little consideration for Linux-first or cross-platform users.
Recommendations
  • Add equivalent examples for Bash or Linux shell scripting where PowerShell is used, especially for starting runbooks and passing parameters.
  • Include Azure CLI examples for runbook operations alongside PowerShell cmdlets.
  • Expand the Python section to provide detailed parameter handling, including complex types and real-world scenarios.
  • Mention and demonstrate Linux-specific tools or workflows for interacting with Azure Automation (e.g., using curl for REST API calls, jq for JSON manipulation).
  • Clarify cross-platform compatibility of runbooks and tools, and explicitly state which features are Windows-only or available on Linux.
  • Provide guidance for Linux users on setting up and using Azure Automation, including authentication and environment setup.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/runbooks.md ...blob/main/articles/automation/troubleshoot/runbooks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for troubleshooting Azure Automation runbook issues demonstrates a strong bias towards Windows and PowerShell environments. All code examples and troubleshooting steps are provided exclusively in PowerShell, with no mention or examples of Bash, Linux shell scripting, or cross-platform CLI usage. Windows-specific tools and patterns (such as PowerShell ISE, Windows Management Instrumentation, and Windows Installer service) are referenced, while Linux equivalents are absent. The guidance assumes familiarity with Windows-centric workflows and does not address Linux-specific troubleshooting or hybrid scenarios in detail.
Recommendations
  • Include equivalent troubleshooting steps and code examples for Bash, Azure CLI, and Python runbooks, especially for common scenarios.
  • Explicitly mention Linux and macOS environments where relevant, and provide guidance for running and debugging runbooks from those platforms.
  • Reference cross-platform tools (such as VS Code on Linux/macOS, Azure CLI) alongside Windows tools like PowerShell ISE.
  • Add troubleshooting sections for issues unique to Linux-based Hybrid Runbook Workers (e.g., permissions, environment setup, module installation).
  • Ensure that documentation for module management, authentication, and error handling covers both Windows and Linux patterns.
  • Where PowerShell cmdlets are referenced, provide Azure CLI or REST API equivalents for users who do not use PowerShell.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/whats-new.md .../azure-docs/blob/main/articles/automation/whats-new.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Automation updates demonstrates a notable Windows bias. PowerShell is consistently highlighted as the primary automation language, with frequent announcements about new PowerShell versions and features. Windows terminology and tools (e.g., PowerShell, AzureRM, Az modules) are mentioned more often and earlier than Linux equivalents. Examples and feature descriptions rarely mention or provide parity for Linux-specific tools, patterns, or scripting languages beyond Python. When hybrid worker features are discussed, Windows is typically listed first, and Linux support is only briefly acknowledged. There are few, if any, concrete Linux-centric examples or guidance.
Recommendations
  • Add explicit Linux shell (e.g., Bash) and scripting examples alongside PowerShell in runbook announcements and tutorials.
  • Ensure that Linux support is mentioned with equal prominence and detail as Windows in all hybrid worker and runtime environment updates.
  • Provide guidance and migration resources for Linux users, including troubleshooting and best practices for Bash, Python, and other Linux-native tools.
  • Highlight Linux-compatible modules, tools, and patterns where relevant, and avoid assuming PowerShell as the default.
  • Include sample runbooks and automation scenarios that use Linux tools (e.g., Bash scripts, cron jobs) in addition to PowerShell.
  • When listing supported platforms, alternate the order or explicitly state parity between Windows and Linux to avoid 'Windows first' perception.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/overview-monitoring-agent.md ...utomation/change-tracking/overview-monitoring-agent.md
High Priority View Details →
Scanned: 2025-09-07 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific concepts (registry, services, file paths) are often discussed in more detail or appear first; Windows tools and patterns (registry keys, Windows services, c:\ paths) are highlighted, sometimes without Linux equivalents or with less detail. Powershell/Windows command syntax is used for both OS types in code blocks, and example queries and alerting scenarios are predominantly Windows-centric, with only a few Linux references. Linux-specific features and examples are less detailed or missing.
Recommendations
  • Ensure Linux examples are provided with equal detail and prominence as Windows examples throughout the documentation.
  • When listing supported features or configuration steps, alternate the order between Windows and Linux or present them side-by-side.
  • Provide Linux-specific command-line examples using native Linux shells (e.g., bash), not just az CLI in PowerShell context.
  • Expand Linux daemon/package tracking sections to match the depth of Windows registry/services coverage, including example daemon names, config files, and typical use cases.
  • Include Linux file path examples (e.g., /etc/hosts) in alerting/query scenarios alongside Windows paths.
  • Clarify any Windows-only limitations or features, and explicitly state Linux equivalents or lack thereof.
  • Add more screenshots and walkthroughs for Linux environments, not just Windows.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/overview-monitoring-agent.md ...utomation/change-tracking/overview-monitoring-agent.md
High Priority View Details →
Scanned: 2025-09-06 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation, while claiming support for both Windows and Linux, demonstrates a Windows-first bias in several areas. Windows-specific concepts (such as registry keys, Windows services, and file paths) are described in detail, often without equivalent Linux examples or explanations. Query and alerting examples frequently use Windows file paths and services before mentioning Linux equivalents, and the registry section is entirely Windows-focused. The documentation also references Windows tools and patterns (e.g., PowerShell, Windows registry, Windows services) more prominently and in greater detail than Linux alternatives. Linux coverage is present but less detailed and often secondary.
Recommendations
  • Provide equivalent Linux examples and explanations wherever Windows-specific features (like registry or services) are discussed. For example, explain Linux alternatives to registry tracking (such as configuration file monitoring) and daemon/service management.
  • Balance the order of examples and explanations so that Linux and Windows are treated equally (e.g., alternate which OS is mentioned first in tables, examples, and queries).
  • Expand Linux-specific guidance, such as common file paths, daemon/service management, and package/software tracking, to match the depth given to Windows.
  • Include Linux-specific alerting and query scenarios, such as monitoring /etc/hosts, /etc/passwd, or systemd service changes, alongside Windows examples.
  • Where PowerShell or Windows tools are referenced, provide equivalent Linux command-line or scripting examples (e.g., Bash, systemctl, journalctl).
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/overview-monitoring-agent.md ...utomation/change-tracking/overview-monitoring-agent.md
High Priority View Details →
Scanned: 2025-09-05 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific concepts (e.g., registry keys, Windows services, Windows software, file paths like c:\...) are often discussed in more detail and appear before Linux equivalents. The registry tracking section is exclusively Windows-focused, with no Linux equivalent discussion. Example queries and alerting scenarios use Windows file paths and services first, with Linux examples appearing later or not at all. The use of PowerShell/Windows-centric command syntax is prevalent, and some features (like registry tracking) are only described for Windows, with no mention of Linux alternatives or limitations.
Recommendations
  • Provide Linux-specific examples and explanations alongside Windows examples, especially in sections like alerting, file tracking, and service/daemon monitoring.
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which OS is listed first in tables and examples).
  • For sections that are Windows-only (such as registry tracking), explicitly state the lack of a Linux equivalent and, if possible, suggest analogous Linux features (e.g., tracking changes to /etc or systemd unit files).
  • Include Linux command-line examples (e.g., bash, systemctl) where relevant, not just PowerShell or Windows CLI.
  • Expand the alerting/query examples to include more Linux-centric scenarios (e.g., monitoring /etc/passwd, /etc/ssh/sshd_config, or Linux package changes).
  • Clarify any feature limitations or differences for Linux, and provide guidance or workarounds where possible.
GitHub Create Pull Request
← Previous Page 16 of 40 Next →