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 201-225 of 982 flagged pages
Automation
Troubleshoot Azure Automation runbook issues
...blob/main/articles/automation/troubleshoot/runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell environments. All troubleshooting examples, code snippets, and recommended tools are based on PowerShell cmdlets and modules, with no equivalent examples for Linux shell scripting, Python, or cross-platform automation. Windows-specific tools and patterns (such as PowerShell ISE, Windows Management Instrumentation, and Windows Installer) are referenced, while Linux-native tools and troubleshooting approaches are absent. The documentation assumes a Windows-centric workflow and does not provide parity for Linux users or those using Python runbooks.
Recommendations
- Provide equivalent troubleshooting examples and code snippets for Python runbooks, including common error scenarios and resolutions.
- Include Linux shell (bash) examples for hybrid worker troubleshooting, module management, and runbook execution.
- Reference cross-platform editors (such as VS Code) with Linux setup instructions, not just PowerShell ISE.
- Document Linux-specific issues and solutions for Hybrid Runbook Workers, such as service management, permissions, and environment setup.
- Mention and link to Linux-native tools and patterns (e.g., systemd, journalctl, bash scripting) where relevant.
- Ensure that troubleshooting steps and recommendations are applicable to both Windows and Linux environments, or clearly indicate platform-specific guidance.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page for Azure Automation updates demonstrates a moderate Windows bias. PowerShell is consistently featured as the primary automation language, with frequent announcements about new PowerShell versions and capabilities, often before or with more detail than Python equivalents. Windows-centric tools and modules (e.g., AzureRM, Az PowerShell) are referenced more often than Linux-specific alternatives. While Linux support is mentioned (especially for Hybrid Runbook Workers), examples, tooling, and migration guidance tend to prioritize Windows and PowerShell. There are few explicit Linux shell (bash, sh) or Linux-native automation examples, and Windows/PowerShell terminology is used as the default.
Recommendations
- Add equivalent Linux shell (bash/sh) and Python examples alongside PowerShell in feature announcements and migration guides.
- Explicitly mention Linux support and parity when introducing new features, especially for Hybrid Runbook Workers and runtime environments.
- Highlight Linux-native tools and modules where applicable, and provide links to Linux-specific documentation or usage patterns.
- Ensure that migration and retirement notices include Linux-focused guidance and examples, not just Windows/PowerShell.
- Balance the order of presentation so that Linux and Windows are given equal prominence in lists, examples, and feature rollouts.
Automation
Configure data based on STIG for Azure Automation State Configuration
...tomation/automation-dsc-configuration-based-on-stig.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell, with all examples and tooling references centered around PowerShell DSC and the PowerSTIG project. The 'Applies To' section explicitly mentions Windows PowerShell 5.1, and all instructions and next steps are PowerShell/Windows-centric. There are no Linux-specific examples, tools, or guidance, and Linux is only briefly mentioned as a target for onboarding, without further detail.
Recommendations
- Add equivalent Linux examples for configuring STIG compliance, such as using Ansible, Chef, or native Linux DSC implementations.
- Include references to Linux-specific tools or modules that support STIG configuration and compliance.
- Provide step-by-step instructions for onboarding and managing Linux machines, not just referencing them in passing.
- Clarify which aspects of the process are Windows-only and which are cross-platform, and update the 'Applies To' section to reflect Linux support if available.
- Consider including a comparison table of Windows and Linux approaches to STIG compliance in Azure Automation State Configuration.
Automation
Forward Azure Automation job data to Azure Monitor logs
...mation/automation-manage-send-joblogs-log-analytics.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily through references to PowerShell and Windows-centric patterns. It mentions using PowerShell to view job logs, describes error streams in the context of PowerShell, and does not provide any Linux-specific examples or mention Linux tools for interacting with Azure Automation logs. All instructions and screenshots are based on the Azure portal UI, which is platform-agnostic, but any command-line or scripting references are exclusively Windows/PowerShell oriented. There are no Bash, CLI, or Linux-native tool examples, nor is there guidance for Linux users on how to perform equivalent tasks.
Recommendations
- Add examples using Azure CLI (az) for querying and managing Automation logs, alongside PowerShell examples.
- Explicitly mention that the Azure portal and Kusto queries are platform-independent, and provide guidance for Linux users.
- Include Bash or shell script examples for common tasks, such as querying logs or automating alert setup.
- Reference cross-platform tools (e.g., az CLI, REST API) before or alongside PowerShell, rather than only mentioning PowerShell.
- Clarify any differences or considerations for Linux users when working with Azure Automation and Monitor logs.
Automation
Create configurations from existing servers for Azure Automation State Configuration
...ticles/automation/automation-dsc-config-from-server.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell, with all examples and references centered around Windows PowerShell DSC and related community projects. There is no mention of Linux-specific configuration extraction tools or examples, and the prerequisites and next steps are exclusively Windows-oriented. Although there is a brief mention of onboarding Linux machines, no Linux parity is provided in terms of tooling, examples, or guidance.
Recommendations
- Include equivalent Linux examples for extracting configurations, such as using Ansible, Chef, or native Linux DSC implementations.
- Mention and link to Linux-compatible tools or community projects for configuration extraction and management.
- Clarify whether ReverseDSC or similar solutions support Linux, and if not, suggest alternatives for Linux users.
- Provide step-by-step instructions or references for creating and uploading configurations from Linux servers to Azure Automation.
- Balance the documentation by listing both Windows and Linux onboarding steps and configuration management workflows.
Automation
Migrate from Orchestrator to Azure Automation (Beta)
...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 demonstrates a strong Windows bias. All examples and tooling references are centered around Windows PowerShell, with no mention of Linux alternatives or cross-platform scripting. The migration process, modules, and cmdlets are described exclusively in the context of Windows environments, and the only example provided is a PowerShell command using Windows-style paths. There is no guidance for Linux users, such as using Bash, Python, or cross-platform modules, nor are Linux file paths or automation patterns discussed.
Recommendations
- Provide Linux-specific migration guidance, including how to use Azure Automation with Linux Hybrid Runbook Workers.
- Include examples using Bash, Python, or other cross-platform scripting languages supported by Azure Automation.
- Document how to author and import runbooks from Linux systems, including file path conventions and asset management.
- Mention cross-platform modules and clarify which features are Windows-only and which are available on Linux.
- Add notes or sections on differences in automation patterns between Windows and Linux environments.
- Offer parity in troubleshooting and log file management for Linux users.
Automation
Delete an Azure Automation Run As account
...blob/main/articles/automation/delete-run-as-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page focuses on deleting an Azure Automation Run As account and provides instructions using PowerShell and the Azure portal. There is a clear Windows bias: only PowerShell (a Windows-centric tool) is mentioned for scripting, with no Linux shell (bash/CLI) examples or references. The Azure portal instructions are platform-neutral, but the scripting guidance is Windows-first and omits Linux alternatives.
Recommendations
- Add equivalent Azure CLI or Bash examples for deleting Run As accounts to ensure Linux users have clear guidance.
- Explicitly mention that PowerShell is available cross-platform, or provide links to install/use PowerShell on Linux if PowerShell is required.
- Where possible, use platform-neutral tools (such as Azure CLI) in examples and documentation.
- Review other related articles to ensure Linux parity in automation and scripting instructions.
Automation
Move your Azure Automation account to another subscription
...s/blob/main/articles/automation/how-to/move-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for resource deletion and action group removal, referencing Windows-centric tools and cmdlets (Remove-AzResource, Remove-AzActionGroup), and omitting equivalent Azure CLI or REST API examples that would be more familiar to Linux users. The narrative and screenshots focus on the Azure portal and PowerShell, with no mention or ordering of Linux-friendly alternatives.
Recommendations
- Add Azure CLI examples alongside PowerShell for all resource management steps, including deleting resources and action groups.
- Explicitly mention REST API options and provide sample requests where appropriate.
- Where PowerShell is referenced, clarify that equivalent operations can be performed using Azure CLI or REST API, and link to relevant documentation.
- Ensure that examples and tool references are balanced between Windows and Linux platforms, possibly by alternating or grouping them together.
- Include notes or sections for Linux/macOS users, highlighting cross-platform tooling and usage patterns.
Automation
Enable Azure Automation State Configuration
.../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 and workflows are described primarily or exclusively for Windows environments, with PowerShell as the main tool. Linux support is mentioned, but Linux-specific instructions are often brief, less detailed, or require using Windows-based tools (such as generating metaconfigurations on Windows with PowerShell). Windows tools and patterns (e.g., PowerShell cmdlets, WMF 5, Set-DscLocalConfigurationManager) are presented first and in more depth, while Linux equivalents are either missing, less detailed, or require workarounds.
Recommendations
- Provide Linux-first or Linux-parallel examples for all major workflows, including onboarding, metaconfiguration generation, and registration.
- Expand Linux sections to include step-by-step instructions that do not require a Windows machine or PowerShell, using native Linux tools and scripts.
- Where PowerShell is used for both platforms, clarify cross-platform compatibility and provide Bash or Python alternatives where possible.
- Document how to generate and apply DSC metaconfigurations entirely on Linux, without requiring WMF 5 or Windows tools.
- Ensure that Linux-specific tools (e.g., Register.py, SetDscLocalConfigurationManager.py) are documented with usage examples and troubleshooting guidance equivalent to the Windows/PowerShell sections.
- Avoid presenting Windows/PowerShell workflows first by default; instead, structure documentation so that Linux and Windows instructions are given equal prominence or are clearly separated for parity.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.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 providing detailed PowerShell examples for all major configuration steps, referencing Windows-centric tools (Azure Az PowerShell module), and omitting equivalent examples for Linux users (e.g., Bash, Azure CLI). PowerShell is presented as the primary method for interacting with Azure Automation and Key Vault, with REST API calls as a secondary option. There is only a brief mention of Azure CLI in the context of revoking access, but no CLI or Bash examples are provided for the main workflows.
Recommendations
- Add equivalent Azure CLI examples for all major workflows (assigning managed identity, configuring Key Vault access policy, reconfiguring encryption keys, etc.).
- Include Bash script snippets to demonstrate how Linux users can perform these tasks.
- Reference cross-platform tools (e.g., Azure CLI, SDKs) alongside PowerShell, and avoid presenting PowerShell as the default or only option.
- Explicitly state that all operations can be performed from Linux/macOS environments, and provide guidance for those platforms.
- Where images show PowerShell output, consider adding screenshots or sample outputs from CLI/Bash for parity.
Automation
Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation
...ation/extension-based-hybrid-runbook-worker-install.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page, while nominally covering both Windows and Linux, demonstrates a Windows bias in several ways: Windows examples, tools, and patterns are consistently presented first; PowerShell is the primary automation language throughout, even for Linux scenarios; Bicep and ARM template examples are exclusively for Windows VMs; permissions and troubleshooting sections focus on Windows-specific paths and registry keys; and there is a lack of parity in Linux-specific automation and deployment examples (e.g., no Linux VM creation or extension install examples via Bicep/ARM).
Recommendations
- Present Windows and Linux instructions/examples in parallel, or alternate which platform is shown first.
- Provide Linux-specific examples for Bicep, ARM templates, and REST API, including creation and extension installation for Linux VMs.
- Include Bash and/or Python automation examples for Linux scenarios, not just PowerShell.
- Expand permissions and troubleshooting sections to cover Linux file paths, permissions, and common issues.
- Reference Linux tools and patterns (e.g., systemd, shell scripts) where appropriate, alongside Windows equivalents.
- Ensure all CLI and API examples explicitly show both Windows and Linux extension types and settings.
- Clarify any platform-specific limitations or differences in all relevant sections.
Automation
Runbook execution in Azure Automation
...in/articles/automation/automation-runbook-execution.md
High Priority
View Details →
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 focus on PowerShell runbooks, Windows-centric tools (e.g., WMI, WinSCP, IIS), and examples written only in PowerShell. There is little to no mention of Linux equivalents, Bash, Python, or cross-platform scripting approaches. Windows-specific patterns and tools are referenced before or instead of Linux alternatives, and no Linux-specific examples or guidance are provided.
Recommendations
- Include examples for Bash and Python runbooks, especially in sections demonstrating error handling, process execution, and resource management.
- Add references to Linux tools and patterns (e.g., using SSH, cron, systemd, Linux file paths) alongside Windows tools like WMI and WinSCP.
- Provide parity in documentation for Linux Hybrid Runbook Workers, including guidance on installing modules, handling elevation, and managing temporary storage.
- Explicitly mention and link to documentation for Linux runbook types and modules, and clarify any differences in execution environments and limitations.
- Balance the presentation order so that Linux and cross-platform scenarios are described alongside or before Windows-specific ones.
- Add troubleshooting and security guidance relevant to Linux environments, such as SELinux, sudo, and Linux authentication mechanisms.
Automation
Disable system-assigned managed identity for Azure Automation account
.../automation/disable-managed-identity-for-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed PowerShell-based instructions for disabling a system-assigned managed identity in Azure Automation, including use of Windows-specific cmdlets and tools. There are no examples or guidance for performing the same operation from Linux or macOS environments, nor are cross-platform tools (such as Azure CLI or curl) mentioned. The documentation implicitly assumes a Windows user and workflow.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Provide REST API invocation examples using curl, a common tool on Linux/macOS.
- Explicitly mention that the operation can be performed from any OS and provide steps for non-Windows environments.
- Include authentication guidance for Linux/macOS users (e.g., using az login and az account get-access-token).
- Reorder or parallelize examples so that Windows and Linux/macOS instructions are given equal prominence.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. It exclusively references PowerShell DSC concepts, cmdlets, and types (e.g., [PSCredential]), and all examples and screenshots are based on Windows-centric workflows. Windows tools like Chocolatey are mentioned as deployment examples, while Linux equivalents are absent. The retirement announcement for Linux DSC is included, but no Linux-specific guidance or parity is provided.
Recommendations
- Add examples and screenshots for Linux node configuration workflows, if still supported.
- Reference Linux DSC alternatives or migration paths for users affected by Linux retirement.
- Include equivalent Linux tools (e.g., apt, yum) in deployment pipeline examples alongside Chocolatey.
- Clarify which features are Windows-only and provide links to Linux documentation or alternatives.
- Balance PowerShell references with Bash or other Linux scripting examples where applicable.
Automation
Remove user-assigned managed identity for Azure Automation account
...n/articles/automation/remove-user-assigned-identity.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 examples and instructions for command-line and scripting operations. There are no examples using Bash, Azure CLI, or other Linux-native tools. Even when describing REST API usage, the example relies on PowerShell cmdlets and patterns. Windows tools and workflows are mentioned first and exclusively, with no Linux equivalents or parity.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for all operations currently shown with PowerShell.
- Provide Bash shell script examples for REST API calls, using curl or wget, and demonstrate authentication via Azure CLI.
- Include instructions for verifying results using Azure CLI or Bash, not just PowerShell cmdlets.
- Reorder sections or present Windows and Linux options side-by-side to avoid implicit prioritization of Windows tools.
- Explicitly mention cross-platform support and clarify that operations can be performed from Linux, macOS, or Windows environments.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Automation demonstrates a Windows bias in several ways. PowerShell is emphasized as the primary language for runbooks and configuration management (DSC), with repeated references to PowerShell Gallery and Microsoft Script Center. The configuration management section focuses exclusively on PowerShell DSC, with no mention of Linux-native equivalents like Ansible or Chef. Examples and scenarios frequently mention Windows-centric tools and services (Active Directory, SQL Server, SharePoint Server) before Linux alternatives, and there is a lack of concrete Linux-specific examples or guidance. While Linux support is acknowledged, it is generally mentioned after Windows, and Linux-specific automation patterns, tools, or examples are missing.
Recommendations
- Add Linux-native configuration management examples (e.g., Ansible, Chef, Puppet) and clarify how they integrate with Azure Automation.
- Provide Linux-specific runbook examples and scenarios, including common Linux administration tasks (e.g., package management, service control, log rotation).
- Include references to Linux package repositories and community resources alongside PowerShell Gallery and Script Center.
- Balance scenario examples to include Linux workloads (e.g., Apache, NGINX, MySQL) and not just Windows-centric services.
- Explicitly document any differences or additional steps required for Linux environments in hybrid automation setups.
- Ensure that Linux and Windows are given equal prominence when listing supported platforms and capabilities.
Automation
Manage modules in Azure Automation
...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 page is heavily focused on PowerShell modules and Windows-centric workflows. Examples, instructions, and tooling are almost exclusively PowerShell-based, with repeated references to Windows PowerShell, AzureRM/Az modules, and cmdlets. Internal cmdlets and features are explicitly unavailable on Linux Hybrid Runbook Workers, and there are no equivalent Linux or cross-platform examples provided. Python is mentioned briefly, but without parity in examples or guidance. The documentation assumes a Windows-first approach, with little attention to Linux users or non-PowerShell automation scenarios.
Recommendations
- Add Linux-specific guidance and examples for module management, including instructions for Linux Hybrid Runbook Workers.
- Provide parity for internal cmdlets or document Linux alternatives/workarounds where features are unavailable.
- Include examples using Bash, Azure CLI, or Python for common tasks (importing, updating, deleting modules).
- Clearly indicate which features/tools are Windows-only and suggest Linux-compatible approaches.
- Expand documentation on Python modules to match the detail given to PowerShell, including cross-platform best practices.
- Where possible, use cross-platform terminology and avoid assuming PowerShell/Windows as the default.
Automation
Quickstart - Create an Azure Automation account using the portal
.../quickstarts/create-azure-automation-account-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on creating an Azure Automation account using the Azure portal, which is platform-neutral. However, the 'Next steps' section directs users to a PowerShell runbook tutorial, implicitly prioritizing Windows tooling and workflows. There are no references to Linux shell scripting, Bash, or cross-platform alternatives, and no examples or guidance for Linux users are provided.
Recommendations
- Include links to tutorials for creating Automation runbooks using Bash or Python, in addition to PowerShell.
- Add examples or references for Linux users, such as using Azure CLI or Bash scripts to interact with Automation accounts.
- Ensure parity in 'Next steps' by offering both PowerShell and Linux shell scripting paths for further automation tasks.
- Mention cross-platform tools (e.g., Azure CLI, REST API) where relevant, and clarify that Automation accounts can be managed from any OS.
Automation
Troubleshoot Azure Automation shared resource issues
...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 page exhibits a strong bias towards Windows and PowerShell environments. All troubleshooting steps and code examples use PowerShell cmdlets and scripts, with no mention of Linux shell equivalents or cross-platform alternatives. Windows-specific tools and patterns (such as .psd1, .psm1 files, DLL errors, and PowerShell runbooks) are referenced exclusively, and there is no guidance for users operating in Linux environments or using Python/CLI-based automation. The documentation assumes familiarity with Windows-centric workflows and does not provide parity for Linux users.
Recommendations
- Add equivalent troubleshooting steps and examples using Azure CLI, Bash, or Python for Linux environments.
- Include notes or sections explaining how module import and management differ on Linux-based Automation accounts, if applicable.
- Provide guidance for handling DLL-related errors in cross-platform scenarios, or clarify if such errors are Windows-specific.
- Mention and demonstrate how to authenticate and manage Azure Automation using non-PowerShell tools (e.g., Azure CLI, REST API).
- Ensure that examples and instructions are presented for both Windows and Linux users, or clearly indicate platform-specific limitations.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. It focuses almost exclusively on PowerShell cmdlets and Windows-centric tools for credential management in Azure Automation. All CLI examples are in PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. The creation and management of credentials are described using Windows PowerShell and related modules, with no mention of Linux shell commands or cross-platform approaches. Python examples are provided, but only as runbook code, not for credential management via CLI or shell. There is no guidance for Linux users or parity in tooling.
Recommendations
- Add equivalent examples using Azure CLI (az) for credential management, which is cross-platform.
- Include Bash or shell script examples for common credential operations.
- Explicitly mention Linux support and provide instructions for managing credentials from Linux/macOS environments.
- Clarify which features are Windows-specific and which are available cross-platform.
- Provide links to cross-platform tools and documentation, such as Azure CLI credential management.
- Consider adding a section on best practices for credential management in Linux environments.
Automation
Using a user-assigned managed identity for an Azure Automation account
...main/articles/automation/add-user-assigned-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong bias towards Windows and PowerShell. All command-line examples use PowerShell, including REST API invocations, ARM template deployments, and access token retrieval. There are no Bash, Azure CLI, or Linux shell examples. Even generic HTTP requests are shown using PowerShell, and file paths use Windows-style backslashes. The only non-PowerShell example is a Python snippet, but it does not address Linux-specific patterns or tools. There is no mention of Linux equivalents, nor are cross-platform alternatives (such as Azure CLI or Bash) provided.
Recommendations
- Add equivalent examples using Azure CLI and Bash for all PowerShell commands, especially for REST API calls, ARM template deployments, and role assignments.
- Show file paths using both Windows and Linux conventions, or use cross-platform syntax.
- Include instructions for Linux users, such as how to install required modules or authenticate using managed identities from a Linux environment.
- Provide guidance on running automation tasks from Linux-based Hybrid Runbook Workers, including any differences in authentication or environment variables.
- Explicitly mention cross-platform compatibility and highlight any differences in behavior or prerequisites between Windows and Linux environments.
Automation
Create modular runbooks in Azure Automation
.../main/articles/automation/automation-child-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias by exclusively using PowerShell-based examples and cmdlets (e.g., Start-AzAutomationRunbook, Get-AzVM), referencing Windows PowerShell and PowerShell Workflow runbooks, and omitting any mention of Linux shell scripting, Bash, or cross-platform alternatives. All examples and guidance are tailored to Windows-centric tooling and patterns, with no Linux or Bash equivalents provided.
Recommendations
- Add equivalent examples using Bash or Python runbooks, which are supported in Azure Automation.
- Explicitly mention cross-platform runbook types and their interoperability (e.g., Bash, Python) alongside PowerShell.
- Provide guidance and examples for invoking child runbooks from Linux-based scripts, including authentication and parameter passing.
- Reference Linux tools and patterns where relevant, such as using Azure CLI in Bash scripts.
- Reorder sections or tables to present cross-platform options first, or at least in parallel with Windows/PowerShell options.
Automation
Use an alert to trigger an Azure Automation runbook
...utomation/automation-create-alert-triggered-runbook.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code examples and instructions use PowerShell, which is traditionally associated with Windows, and there are no Bash, CLI, or Linux-native examples. The prerequisites and links reference Windows virtual machines and PowerShell modules exclusively, with no mention of Linux VMs or cross-platform alternatives. The workflow assumes the use of PowerShell both locally and in runbooks, and does not provide parity for Linux users or those preferring Azure CLI or Bash scripting.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for runbook creation and VM management.
- Include instructions and links for managing Linux VMs, not just Windows VMs.
- Reference both Windows and Linux VM quickstart guides in prerequisites.
- Provide guidance for installing and using Az modules on Linux/macOS, not just Windows/PowerShell.
- Offer sample runbooks written in Python or Bash, which are supported in Azure Automation.
- Clarify that PowerShell is cross-platform, but explicitly show how to use/run scripts on Linux/macOS.
- Balance references to Windows tools with Linux equivalents (e.g., mention Bash, Azure CLI, Python).
Automation
Authenticate Azure Automation runbooks with Amazon Web Services
...n/articles/automation/automation-config-aws-account.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 AWS credential management via the AWS PowerShell user guide, omitting Linux or cross-platform CLI examples. The instructions and linked resources focus on Azure portal and PowerShell workflows, with no mention of Linux tools (e.g., AWS CLI on Linux) or shell scripting alternatives. There are no examples or guidance for users operating from Linux environments.
Recommendations
- Include equivalent instructions for managing AWS credentials using the AWS CLI on Linux/macOS.
- Provide examples of storing and retrieving credentials in Azure Automation using Bash or Python runbooks.
- Reference AWS documentation for Linux and cross-platform credential management, not just PowerShell.
- Add a section highlighting platform-agnostic approaches and clarify that runbooks can be authored in multiple languages and environments.
Automation
Manage connections in Azure Automation
...lob/main/articles/automation/automation-connections.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a clear Windows/PowerShell bias. All command-line examples for creating and managing connections use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tooling. The term 'Windows PowerShell' is explicitly used, and cmdlets are presented as the primary automation interface. Python is included, but only in the context of runbooks, not for general connection management. There are no examples or instructions for Linux users or cross-platform command-line tools. The documentation assumes familiarity with PowerShell and Windows-centric patterns.
Recommendations
- Add equivalent Azure CLI examples for creating, retrieving, and managing Automation connections, and present them alongside PowerShell examples.
- Avoid using 'Windows PowerShell' as the default term; instead, use 'PowerShell' or specify cross-platform compatibility where applicable.
- Include explicit instructions and examples for Linux/macOS users, such as using Bash or Azure CLI.
- Mention and document any platform-specific limitations or differences in Automation connection management.
- Ensure that all code samples and workflows are presented in a platform-neutral order (e.g., PowerShell and CLI side by side, or CLI first where appropriate).