Automation
232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
365 issues found
Showing 351-365 of 365 flagged pages
Automation
Archive for What's new in Azure Automation
...ocs/blob/main/articles/automation/whats-new-archive.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and covers both Windows and Linux platforms for Azure Automation features. However, there is some evidence of Windows bias: Windows tools/scripts are named and referenced explicitly (e.g., 'Create Automation Windows HybridWorker'), and Windows support is sometimes mentioned before Linux equivalents (e.g., Hybrid Runbook Worker support for Windows Server 2008 R2 is highlighted separately). References to PowerShell modules (Az modules) and the PowerShell Gallery are present, but Linux equivalents (such as bash scripts or Linux-native tooling) are not described in detail. Most features and updates do mention Linux support where relevant, and Linux distributions are listed for compatibility, but examples and tooling references tend to favor Windows.
Recommendations
- Where Windows scripts/tools are named, ensure Linux equivalents are equally described and linked.
- Provide example commands or scripts for Linux alongside PowerShell/Windows examples.
- When referencing tools (e.g., Az modules), clarify Linux compatibility and usage, or offer Linux-native alternatives.
- Avoid listing Windows support before Linux unless there is a technical reason; present both platforms in parallel.
- Include more explicit Linux/macOS usage scenarios and troubleshooting tips.
Create Pull Request
Automation
Quickstart: Use Terraform to create an Azure Automation account
...ickstarts/create-azure-automation-account-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is featured equally and referenced in the next steps, which may indicate a slight Windows bias. The next step tutorial specifically highlights PowerShell runbooks, reinforcing a Windows-centric approach. However, the core Terraform workflow is platform-agnostic and does not use Windows-only tools.
Recommendations
- Include Bash or shell script examples for Linux/macOS users alongside PowerShell.
- Provide parity in next steps by linking to tutorials for Python or graphical runbooks, not just PowerShell.
- Clarify that Azure CLI commands work cross-platform and highlight platform-neutral options first.
- Consider listing Azure CLI before PowerShell in verification steps to reduce perceived Windows-first bias.
Automation
Archive for What's new in Azure Automation
...ocs/blob/main/articles/automation/whats-new-archive.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page provides updates and release notes for Azure Automation, mentioning both Windows and Linux support in several places. However, there is a slight Windows bias: Windows tools/scripts are named and referenced explicitly (e.g., 'Create Automation Windows HybridWorker'), and Windows Server support is called out in dedicated sections before or alongside Linux equivalents. PowerShell modules (Az modules) are referenced for onboarding scripts, which are primarily Windows-centric. Linux support is present and growing, but Windows examples/tools tend to be mentioned first or more prominently.
Recommendations
- Ensure Linux scripts and tools are named and referenced with equal prominence as Windows equivalents.
- When listing new features or supported platforms, alternate the order or group Windows and Linux together to avoid implicit prioritization.
- Provide explicit examples, links, and documentation for Linux/macOS users where Windows/PowerShell tools are mentioned.
- Reference cross-platform tools (e.g., Azure CLI, Python scripts) wherever possible, and clarify when features are available for Linux/macOS.
Automation
Azure Automation Hybrid Runbook Worker Overview
...rticles/automation/automation-hybrid-runbook-worker.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. While it mentions support for both Windows and Linux Hybrid Runbook Workers, Windows terminology (such as PowerShell, System account, and Run As accounts) is referenced more frequently and often appears before Linux equivalents. The onboarding channels list PowerShell cmdlets before other options, and the description of job execution and permissions is more detailed for Windows (System account, PowerShell Workflow checkpoints) than for Linux (nxautomation account, no workflow checkpoint details). There are no explicit Linux shell or scripting examples, and references to Windows tools and patterns (PowerShell, Run As account) are more prominent.
Recommendations
- Provide Linux-specific examples and details, such as shell scripting, authentication mechanisms, and job restart behavior for Linux.
- List onboarding channels in a neutral order (e.g., Azure CLI, REST API, PowerShell, Bicep, ARM templates, Azure portal) or group them by platform.
- Clarify Linux equivalents for concepts like Run As accounts and workflow checkpoints.
- Include explicit Linux troubleshooting and operational guidance where Windows-specific details are given.
- Ensure parity in technical depth for both Windows and Linux throughout the documentation.
Automation
Forward Azure Automation job data to Azure Monitor logs
...mation/automation-manage-send-joblogs-log-analytics.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily through references to PowerShell for job log access and error stream handling. PowerShell is mentioned as the tool for viewing individual job logs, and error stream behavior is described in terms of PowerShell output. No Linux/macOS-specific CLI tools (such as Azure CLI or Bash) are referenced, and examples do not clarify cross-platform usage. However, most instructions are based on the Azure portal and Kusto queries, which are platform-agnostic.
Recommendations
- Add explicit instructions and examples for accessing job logs and streams using Azure CLI or Bash, especially for Linux/macOS users.
- Clarify that Kusto queries and portal steps are platform-independent.
- When discussing error streams and debugging, mention how non-PowerShell runbooks (Python, etc.) behave and how to access their logs on Linux/macOS.
- Avoid language that implies PowerShell is the only or primary method for log access; provide parity for other platforms.
- Include a brief section or note on cross-platform compatibility for all steps.
Automation
Enforce job execution on Azure Automation Hybrid Runbook Worker
...cles/automation/enforce-job-execution-hybrid-worker.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and assigning Azure Policy definitions, but PowerShell examples are shown in full parity and detail alongside CLI. However, PowerShell is a Windows-centric tool, and its inclusion as a primary method (with CLI) may indicate mild Windows bias. There are no Linux/macOS-specific instructions or notes, and PowerShell is presented as an equal alternative to CLI, which is cross-platform. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux/macOS/Windows.
- Clarify that PowerShell Core (pwsh) is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
- Consider listing Azure CLI examples before PowerShell to emphasize cross-platform support.
- Add a note for Linux/macOS users confirming that all steps can be performed using Azure CLI.
Automation
Create an Azure Automation account using a Resource Manager template
...ation/quickstart-create-automation-account-template.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides deployment instructions for both PowerShell and Azure CLI, but PowerShell is mentioned first and in more detail, including specific parameter usage. The error handling and workaround instructions also reference PowerShell before Azure CLI. There are no Linux/macOS-specific examples or notes, and the CLI instructions are less prominent. The documentation does not mention Linux tools or shell patterns, nor does it address platform-specific differences in running the ARM template.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell instructions to avoid Windows-first bias.
- Include explicit Linux/macOS usage notes, such as running Azure CLI in Bash or Zsh.
- Add example commands for deploying the template using Azure CLI on Linux/macOS, including installation or authentication steps if relevant.
- Clarify that both PowerShell and Azure CLI are cross-platform, and link to platform-specific installation guides.
- Ensure error messages and troubleshooting steps include CLI-based solutions, not just PowerShell.
Automation
Azure Automation Hybrid Runbook Worker Overview
...rticles/automation/automation-hybrid-runbook-worker.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, mentioning both platforms for Hybrid Runbook Worker installation and operation. However, there is a subtle Windows bias: PowerShell cmdlets are listed before Azure CLI and other automation tools when describing onboarding channels, and references to runbook job restarts specifically mention PowerShell Workflow (a Windows-centric technology) without Linux equivalents. The documentation also refers to the local 'System' account on Windows before mentioning the 'nxautomation' account on Linux, and links for managed identities point to Windows VM tutorials first.
Recommendations
- Present onboarding channels in a neutral order (e.g., Azure CLI before PowerShell, or grouped together).
- Include explicit Linux shell (bash) and Azure CLI examples alongside PowerShell examples in installation and management sections.
- Reference Linux-specific managed identity documentation and tutorials equally with Windows.
- Clarify runbook restart/checkpoint behavior for Linux and non-PowerShell workflows.
- When mentioning accounts, list Windows and Linux together or alternate order.
Automation
Forward Azure Automation job data to Azure Monitor logs
...mation/automation-manage-send-joblogs-log-analytics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. PowerShell is mentioned as the example tool for viewing job logs outside the portal, and the only CLI reference is to PowerShell. There are no explicit Linux/macOS CLI examples (such as Azure CLI, Bash, or REST API), nor are cross-platform alternatives discussed. However, most instructions are portal-based and platform-neutral, and the core functionality is accessible to all users.
Recommendations
- Add Azure CLI and/or Bash examples for querying job logs and streams, alongside PowerShell.
- Explicitly mention that all portal instructions apply equally to Linux/macOS users.
- Where PowerShell is referenced, provide equivalent commands for Azure CLI or REST API.
- Include a section on cross-platform automation and log access for non-Windows users.
Automation
Enforce job execution on Azure Automation Hybrid Runbook Worker
...cles/automation/enforce-job-execution-hybrid-worker.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for policy definition and assignment, but PowerShell examples are presented in dedicated sections and with additional context. The PowerShell examples and references are given equal or slightly more prominence than CLI, and there are no Linux/macOS-specific shell examples or explicit mention of platform differences. The CLI examples are cross-platform, but the documentation assumes familiarity with PowerShell patterns and does not clarify that PowerShell is primarily a Windows tool (though it is available on Linux/macOS). No Linux-specific tools or shell commands (e.g., Bash) are mentioned.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is available cross-platform but may require installation on Linux/macOS.
- Add explicit Bash shell examples for Linux/macOS users where appropriate, especially for file creation and manipulation.
- Note any platform-specific prerequisites for PowerShell usage on non-Windows systems.
- Consider presenting CLI examples first, or interleaving them with PowerShell, to avoid implicit Windows-first bias.
Automation
Create an Azure Automation account using a Resource Manager template
...ation/quickstart-create-automation-account-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides deployment instructions for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is mentioned first and in more detail. The error handling and parameter instructions prioritize PowerShell usage, with CLI guidance following. There are no Linux/macOS-specific examples or notes, and the documentation does not explicitly address platform differences or provide parity in example ordering.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell instructions to avoid Windows-first bias.
- Explicitly state that both PowerShell and Azure CLI are cross-platform, and provide links to installation guides for Linux/macOS users.
- Include example commands for Linux/macOS terminal usage, such as bash scripts or CLI usage in a Linux context.
- Add a note clarifying that PowerShell Core is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
- Ensure screenshots and UI references are not Windows-specific, or provide alternatives if differences exist.
Automation
Quickstart: Use Terraform to create an Azure Automation account
...ickstarts/create-azure-automation-account-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but PowerShell is presented as a primary tab and is referenced in the next steps (PowerShell runbook tutorial). There is a slight Windows bias in the ordering and emphasis on PowerShell, which is more commonly used on Windows. However, Azure CLI examples are present and shown first, and all Terraform commands are cross-platform.
Recommendations
- Ensure that Azure CLI examples are always shown first, as CLI is cross-platform.
- Add explicit notes that Azure CLI works on Linux/macOS and Windows, and that PowerShell is available cross-platform but is most common on Windows.
- Include Bash examples for resource cleanup and variable assignment, especially for Linux/macOS users.
- In 'Next steps', provide links to tutorials using Bash or Azure CLI runbooks, not only PowerShell.
Automation
Archive for What's new in Azure Automation
...ocs/blob/main/articles/automation/whats-new-archive.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page provides a balanced overview of Azure Automation updates, with explicit mentions of both Windows and Linux support for key features such as Hybrid Runbook Worker and Update Management. However, some sections (e.g., script naming conventions and onboarding runbook references) mention Windows tools/scripts first or exclusively reference PowerShell modules, which may subtly prioritize Windows users and patterns.
Recommendations
- Ensure that Linux examples, scripts, and tools are mentioned with equal prominence and detail as Windows equivalents.
- When referencing onboarding scripts or modules, provide direct links and naming parity for both Windows and Linux versions.
- Avoid listing Windows scripts or tools before Linux ones unless there is a technical reason; consider alternating or grouping by platform.
- Where PowerShell modules are referenced, clarify if there are equivalent Bash/CLI tools for Linux users.
- Add explicit examples or references for Linux/macOS where only Windows/PowerShell is mentioned.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/includes/automation-dsc-linux-retirement-announcement.md
...cludes/automation-dsc-linux-retirement-announcement.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page mentions the retirement of Azure Automation DSC for Linux but does not provide any examples, guidance, or alternatives for Linux users. The focus is solely on the announcement, with no parity for Linux usage or migration steps, which may leave Linux users without clear direction.
Recommendations
- Include migration guidance specifically for Linux users, such as steps to transition to the guest configuration feature of Azure Policy.
- Provide Linux-specific examples or references to equivalent tools and workflows.
- Ensure that documentation updates address the needs of both Windows and Linux audiences, especially when announcing feature retirements.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/automation-region-dns-records.md
...les/automation/how-to/automation-region-dns-records.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely neutral and platform-agnostic, focusing on DNS records and Azure Automation configuration. However, there is a subtle Windows-first bias in the instructions for obtaining the Automation Account ID, which reference the Azure portal UI and do not mention CLI alternatives (such as Azure CLI or PowerShell for Windows, nor Bash for Linux). There are no explicit PowerShell-heavy examples, Windows tools, or missing Linux examples, but the lack of Linux CLI instructions may disadvantage Linux users.
Recommendations
- Add instructions for obtaining the Automation Account ID using Azure CLI (cross-platform) and Bash commands for Linux users.
- Where UI steps are described, provide equivalent command-line alternatives for both Windows (PowerShell) and Linux (Bash/Azure CLI).
- Explicitly mention that all DNS records and configuration steps apply equally to both Windows and Linux Hybrid Runbook Workers, unless there are platform-specific caveats.
- Ensure troubleshooting and next steps documentation includes links or notes relevant to Linux environments, not just Windows.