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 501-525 of 982 flagged pages
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md
...b/main/articles/automation/automation-runbook-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows and PowerShell-centric bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in the most detail, with numerous examples and troubleshooting sections focused on Windows paths, environment variables, and cmdlets. Many examples and limitations reference Windows-specific file paths (e.g., C:\modules), environment variables, and tools, with little or no equivalent Linux guidance. Python runbooks are discussed, but Linux-specific instructions are minimal and often secondary to Windows explanations. Graphical runbooks and workflows are also tightly coupled to Windows PowerShell, and Linux support is explicitly limited or absent.
Recommendations
- Provide Linux-specific examples and troubleshooting guidance alongside or before Windows examples, especially for file paths, environment variables, and known issues.
- When referencing environment variables or file paths, include both Windows and Linux formats (e.g., C:\modules and /opt/automation/modules).
- Clarify which features and limitations apply to Linux Hybrid Runbook Workers, and offer Linux workarounds where possible.
- For PowerShell runbooks, explicitly document differences in behavior or support between Windows and Linux Hybrid Runbook Workers.
- Expand Python runbook sections to include more Linux-specific details, such as package management, file system paths, and common issues.
- Where graphical runbooks or workflows are Windows-only, suggest alternative approaches for Linux users or clearly state the lack of support.
- Balance the order of presentation so that Linux and cross-platform scenarios are not always secondary to Windows.
Create Pull Request
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-onboarding.md
.../main/articles/automation/automation-dsc-onboarding.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows and PowerShell bias. Most examples, scripts, and workflows are presented using PowerShell and Windows-specific tooling (e.g., WMF 5, PowerShell DSC cmdlets), with Linux instructions often appearing later, being less detailed, or requiring Windows tools to manage Linux nodes. Some Linux-specific steps are present, but they are less comprehensive, and Linux users are frequently directed to use Windows/PowerShell environments for configuration generation and management.
Recommendations
- Provide Linux-first and cross-platform examples alongside Windows/PowerShell examples, especially in sections on generating and applying DSC metaconfigurations.
- Include native Linux command-line examples (e.g., Bash, Python) for all major workflows, such as onboarding, configuration, and status checking.
- Document how to generate and apply DSC metaconfigurations entirely from a Linux environment, without requiring access to Windows or PowerShell.
- List Linux and Windows instructions in parallel, or clearly separate them, rather than always presenting Windows/PowerShell first.
- Expand Linux troubleshooting and operational guidance to match the depth provided for Windows.
- Where PowerShell is required for Linux, clarify if PowerShell Core on Linux is supported, and provide examples accordingly.
- Avoid assuming the user has access to a Windows machine for managing Linux nodes; provide alternatives where possible.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/install-hybrid-worker-extension.md
...omation/quickstarts/install-hybrid-worker-extension.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension names are Windows-specific, with no equivalent guidance or visuals for Linux VMs. Linux is only mentioned in passing, and there are no examples or instructions for Linux users.
Recommendations
- Provide parallel step-by-step instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
- Explicitly mention and show the selection of the Linux Hybrid Worker extension in the Azure portal, including its name and any differences in the installation process.
- Update the prerequisites section to include both Windows and Linux VM requirements.
- Ensure that all references to extension names and configuration steps are clear for both Windows and Linux scenarios.
- Consider alternating the order of Windows and Linux instructions or presenting them side-by-side to avoid a Windows-first impression.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific concepts (such as registry keys and Windows services) are described in greater detail and with more examples than their Linux equivalents. Windows tools, paths, and terminology (e.g., c:\ paths, registry, Windows services) are often mentioned first or exclusively, and alerting examples focus heavily on Windows scenarios. While Linux is supported and mentioned, Linux-specific examples (e.g., for daemons, package tracking, or file paths) are less detailed or absent in some sections. The registry tracking section is entirely Windows-centric, and alerting queries are predominantly Windows-focused, with only one Linux daemon example. Powershell is used as the default CLI context, even for Linux commands.
Recommendations
- Provide equivalent Linux-focused examples alongside Windows examples in all sections, especially for alerting queries and configuration tracking.
- Expand the documentation on Linux-specific features, such as daemon tracking, package inventory, and typical Linux configuration files (e.g., /etc/hosts, /etc/passwd).
- When listing features or examples, alternate the order or present both Windows and Linux scenarios together to avoid 'windows_first' bias.
- Include Linux command-line examples using bash or shell where appropriate, rather than only using PowerShell or Windows-centric CLI.
- Add a section on tracking Linux configuration files and directories, with concrete examples (e.g., monitoring changes in /etc/ssh/sshd_config or /var/log).
- In registry/key tracking sections, clarify that this is Windows-only and provide a parallel discussion of Linux equivalents (e.g., tracking changes in /etc or systemd unit files).
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell environments. Troubleshooting steps, examples, and tooling (such as xDscDiagnostics, PowerShell cmdlets, and references to Windows event logs and WMI) are almost exclusively Windows-centric. Linux is only mentioned in a single scenario, with no equivalent troubleshooting depth, examples, or tooling guidance. Windows tools and patterns are introduced first and often exclusively, with Linux support treated as an afterthought or omitted.
Recommendations
- Provide Linux-specific troubleshooting steps and examples for each scenario where applicable, including log locations, commands, and error investigation techniques relevant to Linux nodes.
- Include Linux equivalents for all PowerShell cmdlets and tools, such as how to collect and analyze DSC logs on Linux, and how to manage certificates or extensions.
- Balance the order of presentation by mentioning Linux approaches alongside Windows, rather than only after or not at all.
- Reference Linux-native tools (e.g., journalctl, systemd, log files in /var/log) and shell commands where appropriate.
- Clarify where features or tools are Windows-only, and provide alternative guidance for Linux users.
- Expand the Linux troubleshooting section to cover common issues, error messages, and resolutions in parity with the Windows content.
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 →
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 scripting examples (e.g., setting public network access flags), and by referencing Windows tools and patterns (such as PowerShell Desired State Configuration) without providing equivalent Linux/Unix command-line or scripting examples. While the text mentions Linux support in some features, practical examples and configuration steps are only shown for Windows/PowerShell environments, leaving Linux users without direct guidance.
Recommendations
- Provide equivalent Azure CLI or Bash examples alongside PowerShell scripts, especially for key configuration steps such as setting the publicNetworkAccess property.
- When referencing configuration management (e.g., DSC), include notes or links about Linux alternatives (such as Chef, Puppet, or native Linux DSC support) and how they interact with Azure Automation.
- Explicitly show Linux command-line examples for agent installation, configuration, and DNS setup, not just mention that Linux is supported.
- Ensure that screenshots and UI walkthroughs do not assume a Windows-centric environment (e.g., referencing Windows file paths or tools only).
- Add a dedicated section or callouts for Linux users, summarizing any differences or additional steps required for parity.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for all steps, including Azure resource management, Key Vault operations, and the runbook itself. There are no references to Bash, Azure CLI, or Linux-based scripting alternatives. All tooling and module references (e.g., Az PowerShell module) are Windows-centric, and the workflow assumes the use of PowerShell as the default and only supported scripting environment.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash script examples for all resource creation, permission assignment, and secret management steps.
- Include a sample runbook written in Python (supported in Azure Automation) or Bash, demonstrating how to retrieve secrets and send emails using SendGrid.
- Mention and link to Linux/macOS-compatible tools and installation instructions, not just PowerShell modules.
- Rephrase instructions to be platform-neutral where possible, or explicitly note that the steps apply to both Windows and Linux environments.
- Add a section or callout for users who prefer or require non-Windows environments, outlining their options for achieving the same automation goals.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell environments. All command-line examples use PowerShell cmdlets, and there are no equivalent instructions or examples for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting). The documentation assumes the use of PowerShell consoles and Windows-specific tools, and there is no mention of how to perform these tasks on Linux or macOS. The only supported runbook type for source control integration is PowerShell 5.1, which is Windows-only, further reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Explicitly state the platform limitations (e.g., that PowerShell 5.1 is Windows-only) and provide guidance for users on other platforms.
- Include Bash or shell script examples for common tasks, such as assigning roles or configuring source control.
- Mention and document any Linux/macOS-compatible alternatives for tasks currently shown only with PowerShell.
- Clarify whether source control integration is possible with Python or other cross-platform runbook types, and if not, explain the roadmap or alternatives.
- Add troubleshooting and encoding guidance relevant to Linux/macOS editors and environments, not just those focused on Windows/PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/shared-resources.md
...n/articles/automation/troubleshoot/shared-resources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All troubleshooting steps, code examples, and references are provided exclusively for PowerShell, with no mention of Linux/Unix equivalents or cross-platform approaches. Windows-specific DLL errors and cmdlets are discussed without Linux context, and there are no Bash, CLI, or Python examples for Linux users.
Recommendations
- Provide equivalent troubleshooting steps and examples using Azure CLI (az) and Bash scripts for Linux users.
- Mention cross-platform modules and tools where possible, and clarify which steps are Windows-specific.
- Include notes or sections on how to perform common tasks (such as module import, authentication, and error resolution) in Linux environments.
- Reference Linux-specific issues or error messages that may arise in Azure Automation, and how to resolve them.
- Balance the order of presentation so that Linux and cross-platform solutions are given equal prominence to Windows/PowerShell solutions.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/modules.md
...b/main/articles/automation/shared-resources/modules.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell modules and workflows, with nearly all examples, instructions, and internal tooling centered on Windows PowerShell and Windows-specific features. Internal cmdlets and modules are explicitly unavailable on Linux Hybrid Runbook Workers, and there are no Linux shell or cross-platform scripting examples. Linux support is mentioned only to note limitations or lack of availability, and there are no Linux-native module management workflows or parity in examples.
Recommendations
- Provide equivalent Linux/bash examples for module management, such as using Azure CLI or bash scripts to import, update, or delete modules.
- Clearly indicate which features are Windows-only and provide alternative workflows or guidance for Linux Hybrid Runbook Workers.
- Include documentation and examples for managing Python modules and runbooks on Linux, not just a link to another page.
- Highlight cross-platform capabilities and limitations in a dedicated section, making it clear what is supported on Linux vs. Windows.
- When listing internal cmdlets or features, suggest Linux-compatible alternatives or workarounds where possible.
- Balance the order of presentation so that Linux and cross-platform options are not always secondary or omitted.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell usage, with all command-line examples and tooling instructions centered around PowerShell cmdlets and Windows-specific patterns. Linux or cross-platform CLI alternatives are not mentioned, and there are no examples using Bash, Azure CLI, or other Linux-native tools. The Python examples are present but limited to the Azure Automation Python SDK, not general Linux workflows. The documentation assumes a Windows/PowerShell environment for automation tasks.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for credential management, which are cross-platform and work natively on Linux.
- Include Bash or shell script examples for retrieving and using credentials in runbooks, especially for Linux Hybrid Runbook Workers.
- Mention and document how Linux users can interact with Azure Automation credentials, including any SDKs or REST API usage.
- Avoid referring to 'Windows PowerShell' exclusively; use 'PowerShell' and clarify cross-platform compatibility where possible.
- List Linux-compatible tools and workflows alongside PowerShell cmdlets, and avoid presenting Windows tools first or exclusively.
- Clarify which features or modules are available on Linux-based Automation workers and provide parity guidance.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows/PowerShell bias. All code examples and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks that use PowerShell cmdlets. Windows-specific tools and patterns (such as PowerShell cmdlets, .NET types, and C# SDK examples) are used exclusively, with no equivalent Bash, Linux shell, or cross-platform CLI examples. The Python section is minimal and lacks parity in detail or examples. There are no references to Linux-native tools, and PowerShell is always presented first and in the most detail.
Recommendations
- Add equivalent examples for starting and managing runbooks using Azure CLI (az), which is cross-platform and widely used on Linux.
- Provide Bash or shell script examples for interacting with Azure Automation via REST API or Azure CLI.
- Expand the Python section to include detailed parameter handling, example scripts, and parity with PowerShell examples.
- Mention and demonstrate how to use Linux/macOS environments for authoring and running runbooks, including any differences or considerations.
- Where PowerShell-specific types or patterns are discussed, note their Linux/Python/CLI equivalents or limitations.
- Ensure that references to tools and workflows are not Windows-first; present Azure CLI or REST API approaches before or alongside PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/tutorial-configure-servers-desired-state.md
...automation/tutorial-configure-servers-desired-state.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows and PowerShell, providing only Windows-centric examples (such as installing IIS), referencing only Windows VMs in prerequisites, and using only PowerShell cmdlets throughout. There are no Linux-specific examples, commands, or guidance, and Linux support is only briefly mentioned in passing. The documentation assumes the use of Windows tools and patterns, with no parity for Linux users.
Recommendations
- Add Linux-specific examples, such as configuring a Linux VM with a DSC configuration (e.g., ensuring nginx or Apache is installed).
- Include Bash/CLI commands or scripts for onboarding and managing Linux nodes, not just PowerShell.
- Update prerequisites to mention Linux VMs and provide links to creating Linux VMs in Azure.
- Clarify the current support status for Linux in Azure Automation State Configuration, especially given the referenced retirement announcement.
- Provide guidance or references for managing Linux nodes, including any differences in onboarding, configuration, or compliance checking.
- Balance the documentation structure so that Linux and Windows scenarios are presented with equal prominence.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows and PowerShell, providing only Windows PowerShell examples and using Windows file paths (e.g., c:\runbooks). There are no examples or guidance for Linux or cross-platform PowerShell Core usage, nor is there mention of Linux-compatible editors or workflows. The use of 'Windows PowerShell' and exclusive reference to Windows tools and conventions demonstrates a clear Windows bias.
Recommendations
- Provide examples using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility with Linux and macOS.
- Include Linux/macOS file path examples (e.g., /home/user/runbooks) alongside Windows paths.
- Mention and demonstrate the use of editors available on Linux/macOS (e.g., VS Code, nano, vim) for editing runbooks.
- Clarify that Az PowerShell module cmdlets can be used from any OS, not just Windows.
- Add a section or notes on how to perform the same tasks from Linux/macOS terminals, including installation instructions for PowerShell Core and Az modules.
- Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when something is Windows-only.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All code samples use PowerShell cmdlets, and there are no examples or guidance for using Linux-based tools or Bash scripting. The instructions for installing modules and running commands assume a PowerShell environment, and there is no mention of cross-platform alternatives or how to perform these tasks on Linux-based Hybrid Runbook Workers. The documentation also refers to Windows concepts (e.g., elevated PowerShell prompt) and does not provide parity for Linux users.
Recommendations
- Provide equivalent Bash/CLI examples for connecting to Azure SQL Database using managed identities (e.g., using Azure CLI and sqlcmd).
- Document how to set up and use Hybrid Runbook Workers on Linux, including module installation and authentication steps.
- Include instructions for installing required modules or tools on Linux (e.g., using pip for Azure CLI, apt/yum for sqlcmd).
- Mention cross-platform compatibility of Azure Automation and clarify which steps or commands are OS-specific.
- Add a section or note explicitly addressing Linux users and linking to relevant resources for Linux-based automation.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/extension-version-details.md
...utomation/change-tracking/extension-version-details.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias: Windows issues and features are consistently listed before Linux equivalents, and some sections provide detailed workarounds or recommendations only for Windows (e.g., use of base64_decode_tostring() for Windows, but not for Linux). There are also references to Windows-specific tools and concepts (Windows Registry, Windows Services) without Linux equivalents being described in similar detail. In some extension versions, Linux changes are marked as 'None' or are less detailed, and Linux-specific issues or workarounds are not elaborated.
Recommendations
- Ensure Linux issues and features are described with equal detail and prominence as Windows.
- Provide Linux-specific workarounds or equivalent commands/tools where Windows-specific ones are mentioned (e.g., if a KQL workaround is given for Windows, note if/how it applies to Linux).
- List Linux and Windows changes/issues in parallel, rather than always listing Windows first.
- Include examples or references for Linux tools and patterns (e.g., mention systemd for Linux daemons, or relevant Linux file/daemon tracking specifics).
- Avoid marking Linux sections as 'None' without further context; if there are no changes, briefly explain why or what users should expect.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/enable-managed-identity.md
...cles/automation/quickstarts/enable-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell runbooks exclusively in the 'Next steps' section, without mentioning Linux or Python runbooks. There are no examples or guidance for Linux users or for using non-Windows scripting environments. The documentation assumes the use of PowerShell as the default automation language, which is more common on Windows.
Recommendations
- Include links to tutorials for creating Python runbooks using managed identity, as Python is commonly used for automation on Linux.
- Explicitly mention that Automation accounts support both PowerShell and Python runbooks, and provide parity in examples and next steps.
- Add a section or note for Linux users, clarifying that the steps apply regardless of OS, and reference relevant Linux-friendly tools or scripts.
- Ensure that future documentation alternates or balances the order of PowerShell and Python/Linux examples, rather than defaulting to Windows-first patterns.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Script-based migration is only described using PowerShell, with no mention of Bash, shell, or native Linux scripting alternatives. Prerequisites and instructions for scripting focus on PowerShell installation and modules, which are more familiar to Windows users. While Linux is mentioned as a supported platform, and Linux-specific data types (like Linux files and daemons) are referenced, the scripting and automation guidance is Windows-centric. The documentation also lists Windows data types before Linux ones and generally presents Windows concepts first.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, or explicitly document how to run the migration using native Linux tools.
- Include Linux-first or Linux-parity instructions and examples, such as using Azure CLI or Bash scripts for migration.
- Clarify any platform-specific differences or limitations in the migration process for Linux VMs.
- List Linux and Windows data types in a neutral or alternating order to avoid implicit prioritization.
- Reference Linux-native tools and patterns (e.g., systemd, cron) where relevant, not just PowerShell and Windows modules.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-packages.md
...-docs/blob/main/articles/automation/python-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing explicit instructions and command-line examples only for Windows environments (e.g., using Windows paths and referencing a Windows 64-bit machine for package download). There are no equivalent instructions or examples for Linux or macOS users, and Windows tools and patterns are mentioned exclusively.
Recommendations
- Provide equivalent Linux (and optionally macOS) instructions for downloading packages and dependencies, such as using the 'pip' command in a Linux shell.
- Include Linux command-line examples alongside Windows examples, using standard Linux paths and conventions.
- Avoid referencing only Windows-specific tools or environments; instead, offer cross-platform guidance or clarify when steps are platform-specific.
- Add a note or section explicitly addressing how users on non-Windows systems can perform the same tasks.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Windows-centric tools and patterns, such as DSC resources and WaitFor resources, with links pointing to Windows PowerShell DSC documentation. There are no Linux-specific examples or references to Linux equivalents of DSC resources, and the documentation does not mention Linux-specific considerations for network configuration or agent communication.
Recommendations
- Include references and links to Linux DSC resources and documentation, such as the Linux DSC resource kit or documentation for Linux OMI-based DSC.
- Provide examples or notes on configuring network requirements for Linux Hybrid Runbook Workers and State Configuration nodes.
- Mention any Linux-specific ports, URLs, or agent behaviors if they differ from Windows.
- Balance references to Windows and Linux in resource links and examples, ensuring Linux users can find relevant information easily.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All examples, terminology, and cmdlets are PowerShell-centric, with no mention of Linux, Bash, or cross-platform scripting. Windows tools and patterns (e.g., PowerShell cmdlets like Start-AzVM, Write-Warning, Get-AutomationVariable) are used exclusively, and there are no Linux or Bash equivalents provided. The error handling concepts are described solely in the context of PowerShell, and the documentation implicitly assumes the reader is operating in a Windows/PowerShell environment.
Recommendations
- Include examples using Bash or Python runbooks, which are supported in Azure Automation, to illustrate error handling in non-Windows environments.
- Mention and demonstrate how error handling works in Linux-based runbooks, including differences in error types and handling patterns.
- Provide parallel examples for common tasks (e.g., starting a VM, sending notifications) using both PowerShell and Bash/Python.
- Clarify in the introduction that the guidance is PowerShell-specific, or restructure the documentation to address both Windows and Linux automation scenarios equally.
- Reference relevant Linux tools or scripting patterns (e.g., try/catch in Bash, error codes, set -e) where appropriate.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-cd-chocolatey.md
...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily focused on Windows environments, exclusively using Windows Server, PowerShell, and Windows-specific tools (Chocolatey, PowerShell DSC, WindowsFeature, xNetworking) in all examples and instructions. Linux is only mentioned in passing, with no equivalent examples or guidance for Linux systems. The workflow, commands, and tooling are all tailored to Windows, with no parity for Linux users.
Recommendations
- Provide equivalent Linux examples using native Linux package managers (e.g., apt, yum) and configuration management tools (e.g., Ansible, Chef, Puppet, or Azure Automation State Configuration for Linux if available).
- Include step-by-step instructions for setting up continuous deployment on Linux VMs, including sample configuration files and automation scripts.
- Mention and demonstrate cross-platform tools or patterns where possible, and clarify any Azure Automation features that are Windows-only or deprecated for Linux.
- Balance the documentation by presenting Linux scenarios alongside Windows, especially in sections describing high-level concepts, workflows, and automation patterns.
- Clearly indicate the current support status for Linux in Azure Automation State Configuration, and provide links or references to Linux-specific guidance if Windows is the only supported platform.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples and instructions use PowerShell, reference Windows-style paths (e.g., D:\examplefiles), and mention only Windows tools and conventions. There are no examples or guidance for Linux-based Hybrid Runbook Workers, nor are Linux shell commands or file path formats provided. The documentation assumes the user is operating in a Windows environment throughout.
Recommendations
- Provide equivalent examples for Linux-based Hybrid Runbook Workers, including bash shell commands for file creation and Linux file path formats (e.g., /home/examplefiles).
- Mention that Azure Automation Hybrid Runbook Workers can run on Linux, and provide any relevant prerequisites or differences.
- Include sample runbooks or scripts that work on Linux, or explain how to adapt the provided PowerShell scripts for Linux environments (e.g., using PowerShell Core on Linux or bash scripts).
- Clarify in the prerequisites and steps where instructions diverge for Windows vs. Linux, and offer both sets of instructions side by side.
- Avoid assuming the use of Windows tools (like PowerShell) exclusively; reference cross-platform tools or provide alternatives.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page for Azure Automation updates demonstrates a Windows and PowerShell bias. Most examples and feature announcements focus on PowerShell runbooks, with PowerShell versions and modules (e.g., AzureRM, Az) being highlighted more frequently and in greater detail than their Linux or cross-platform equivalents. Python support is mentioned, but typically as a secondary note. There is a lack of explicit Linux shell (Bash) or native Linux automation examples, and Windows/PowerShell tools and terminology are often presented first or exclusively.
Recommendations
- Include explicit Bash or native Linux shell script examples and announcements alongside PowerShell updates.
- When announcing new features (e.g., runtime environments, CLI support), provide parity in examples and explanations for both Windows/PowerShell and Linux/Bash users.
- Highlight Linux-specific tools, modules, or best practices where relevant, not just Windows/PowerShell ones.
- Ensure that migration and retirement notices (e.g., for modules or workers) address both Windows and Linux users equally, with clear guidance for each.
- Balance the order of presentation so that Linux and cross-platform options are not always secondary to Windows/PowerShell.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily oriented toward Windows environments, focusing exclusively on PowerShell-based automation, Windows file paths, and Windows-specific tools and patterns. There are no examples or guidance for Linux users, nor any mention of Bash, Linux-compatible modules, or cross-platform considerations. All examples and tool references (such as the Runbook Converter and integration modules) assume a Windows environment.
Recommendations
- Provide examples for Linux users, such as using Bash or Azure CLI where possible.
- Clarify whether the Runbook Converter and integration modules can be used on Linux or only on Windows, and provide alternatives or workarounds if not.
- Include file path examples using Linux conventions (e.g., /home/user/runbooks) alongside Windows paths.
- Mention any cross-platform compatibility or limitations for Azure Automation and related tools.
- If PowerShell Core (pwsh) is supported, specify this and provide examples using it on Linux.
- Add a section or note for Linux users outlining any differences or additional steps required.