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 226-250 of 982 flagged pages
Automation
Compile DSC configurations in Azure Automation State Configuration
...lob/main/articles/automation/automation-dsc-compile.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. All code examples use Windows PowerShell, and Windows-specific modules and patterns (such as WindowsFeature, C:\ paths, and PowerShell cmdlets) are used exclusively. There are no Linux-specific examples, tools, or workflows presented, and Linux support is only mentioned in the context of retirement. The documentation assumes the reader is working in a Windows environment and does not provide parity for Linux users.
Recommendations
- Add explicit Linux examples for compiling DSC configurations, including workflows using Linux-compatible tools (e.g., Bash, Python, or cross-platform PowerShell Core).
- Include information about DSC resources and modules available for Linux, and how to manage them in Azure Automation.
- Present Linux-specific patterns (such as file paths, service management, and node configuration) alongside Windows examples.
- Clarify which features are Windows-only and which are cross-platform, and provide guidance for Linux users where features differ or are unavailable.
- If Linux support is deprecated, provide migration guidance or alternatives for Linux users.
Create Pull Request
Automation
Convert configurations to composite resources for Azure Automation State Configuration
...articles/automation/automation-dsc-create-composite.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows PowerShell 5.1, with all examples and instructions centered around PowerShell workflows and tooling. There is no mention of Linux-specific equivalents, nor are there examples or guidance for Linux environments, despite Azure Automation DSC supporting Linux nodes. Windows tools and patterns are referenced exclusively, and Linux is only mentioned in passing as a target for onboarding, not as a platform for authoring or managing configurations.
Recommendations
- Add explicit examples and instructions for authoring and managing DSC configurations for Linux nodes, including any platform-specific considerations.
- Include references to cross-platform PowerShell (PowerShell Core) and clarify compatibility for Linux/macOS environments.
- Provide Linux shell (bash) equivalents where possible, or note when only PowerShell is supported.
- Mention and link to Linux DSC resources, modules, and documentation, and clarify any differences in workflow or tooling.
- Ensure that onboarding and usage steps for Linux nodes are given equal prominence and detail as Windows instructions.
Automation
Create a standalone Azure Automation account
...les/automation/automation-create-standalone-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by predominantly featuring PowerShell examples and references, mentioning PowerShell runbooks and cmdlets before alternatives, and omitting Linux-specific guidance or CLI examples. Windows-centric tools and patterns (PowerShell, Az.Automation) are highlighted, while Linux equivalents (Azure CLI, Bash scripting) are not presented or referenced.
Recommendations
- Add Azure CLI examples alongside PowerShell for key operations (e.g., account creation, key rotation).
- Include Bash or shell script samples for common automation tasks.
- Present Linux-compatible instructions and tools (such as az CLI) before or alongside Windows/PowerShell options.
- Reference documentation for Linux users, including how to use Azure Automation with Python or Bash runbooks.
- Balance the 'Next steps' section to equally feature Linux-friendly tutorials and resources.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.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 exclusive use of PowerShell scripts and workflows for disaster recovery asset migration, with no mention of Bash, Python, or other Linux-native scripting options. All migration examples and instructions are PowerShell-centric, and the prerequisites list only PowerShell modules. While the article claims applicability to both Linux and Windows VMs, Linux-specific guidance, tools, or examples are absent. References to installation steps for Hybrid Runbook Workers default to Windows tabs/links, and the migration process is described only in terms of PowerShell, which is natively a Windows technology (though available on Linux, it is less commonly used there).
Recommendations
- Provide equivalent Bash or Python scripts for asset migration to support Linux-native automation.
- Include Linux-specific instructions and examples for Hybrid Runbook Worker installation and management.
- List Linux-compatible modules and dependencies alongside PowerShell modules.
- Ensure that documentation tabs and links default to a neutral or Linux-first view where appropriate.
- Clarify whether PowerShell scripts are fully supported and tested on Linux, and offer troubleshooting guidance for Linux environments.
Automation
Configure data at scale for Azure Automation State Configuration
...cles/automation/automation-dsc-config-data-at-scale.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, with all examples and instructions referencing Windows PowerShell DSC and related tooling. There are no Linux-specific examples, instructions, or references to Linux-native configuration management tools. The prerequisites and next steps exclusively mention Windows PowerShell, and the workflow assumes a Windows-centric approach.
Recommendations
- Add explicit instructions and examples for configuring data at scale using Linux nodes, including how to use DSC on Linux.
- Include references to Linux-compatible DSC agents and clarify any differences in workflow or tooling for Linux environments.
- Provide parity in examples, such as showing how to organize configuration data and generate MOF files from a Linux system.
- Mention and link to Linux-specific documentation or community resources for DSC on Linux.
- Clarify any limitations or differences in Azure Automation State Configuration support for Linux versus Windows.
Automation
Set up Azure Automation continuous deployment with Chocolatey
...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples, tooling, and instructions centered around Windows Server, PowerShell DSC, and Chocolatey. Linux equivalents (such as apt-get) are mentioned only in passing, and there are no Linux-specific examples, instructions, or tooling references. The documentation assumes the use of Windows VMs and does not provide guidance for Linux-based automation or package management.
Recommendations
- Add parallel examples for Linux environments, using native Linux package managers (e.g., apt, yum) and configuration management tools (e.g., Ansible, Chef, Puppet, or native Linux DSC).
- Include instructions for setting up Azure Automation State Configuration for Linux VMs, if supported, or provide alternatives for Linux automation.
- Reference Linux VM extensions and how to use them for configuration management in Azure Resource Manager templates.
- Provide sample configuration scripts for Linux nodes, using Bash or Python, alongside PowerShell examples.
- Clarify in the introduction whether the guidance is Windows-only, and if so, link to Linux-specific documentation or note the retirement status of Linux DSC in Azure Automation.
Automation
Integrate Azure Automation State Configuration with Azure Monitor Logs
...main/articles/automation/automation-dsc-diagnostics.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 setup instructions use PowerShell and Az PowerShell modules, which are native to Windows environments. There are no equivalent Bash, CLI, or Linux-native instructions or examples. The prerequisites and troubleshooting modules referenced are PowerShell-centric, and the workflow assumes the user is operating from a Windows or PowerShell-enabled environment. There is no mention of Linux command-line tools or cross-platform alternatives, and the only reference to Linux is an end-of-life announcement for Automation DSC Linux support.
Recommendations
- Add Azure CLI (az) examples for all steps currently shown only in PowerShell.
- Include Bash or shell script equivalents for Linux users.
- Clarify which steps are cross-platform and which are Windows-specific.
- Reference Linux-compatible modules or tools where possible.
- Explicitly state platform requirements and alternatives in the prerequisites section.
- If Linux support is deprecated, provide guidance for migration or alternative solutions for Linux users.
Automation
Get started with Azure Automation State Configuration
.../articles/automation/automation-dsc-getting-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature), with no Linux equivalents or cross-platform examples. The prerequisites and instructions focus on Windows VMs, and links reference Windows-specific guides. Linux support is only mentioned in passing or in retirement notices, with no practical guidance or examples for Linux systems.
Recommendations
- Add equivalent Linux DSC configuration examples, such as using nxFile or nxPackage resources.
- Include step-by-step instructions for onboarding and managing Linux VMs with Azure Automation State Configuration.
- Reference Linux-specific documentation and tools alongside Windows ones, not just in retirement announcements.
- Clarify current Linux support status and provide migration or alternative guidance for Linux users.
- Ensure all PowerShell examples are accompanied by notes or examples for Linux-compatible DSC resources and workflows.
Automation
Edit textual runbooks in Azure Automation
...articles/automation/automation-edit-textual-runbook.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 and Windows-centric workflows. All code examples use Windows PowerShell, with explicit references to Windows file paths (e.g., c:\runbooks) and no mention of Linux or cross-platform alternatives. There are no Bash or Linux shell examples, nor any guidance for users working on non-Windows environments. The use of 'Windows PowerShell' terminology and exclusive reliance on PowerShell cmdlets further reinforces the Windows bias.
Recommendations
- Provide equivalent examples using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility.
- Include Linux/macOS file path examples (e.g., /home/user/runbooks) alongside Windows paths.
- Mention that Az PowerShell modules can be used on Linux/macOS, and note any differences in usage or prerequisites.
- Add Bash/CLI examples for exporting/importing runbooks, if supported, or clarify PowerShell is required.
- Avoid using 'Windows PowerShell' exclusively; use 'PowerShell' or specify when Windows-only features are required.
- Explicitly state platform requirements and provide guidance for Linux/macOS users where applicable.
Automation
Author graphical runbooks in Azure Automation
...les/automation/automation-graphical-authoring-intro.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for authoring graphical runbooks in Azure Automation exhibits a strong Windows bias. All examples, code snippets, and workflow references are exclusively based on Windows PowerShell and PowerShell Workflow. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows-centric tools and patterns (e.g., cmdlets, PowerShell expressions, System Center Orchestrator), and does not provide parity for Linux users or those using non-Windows environments.
Recommendations
- Add explicit notes about platform support, clarifying whether graphical runbooks and the Azure Automation graphical editor are Windows-only or cross-platform.
- Include examples or guidance for Linux users, such as how to author runbooks using Bash or Python if supported, or clarify limitations.
- Reference cross-platform PowerShell (PowerShell Core/7+) where applicable, and note any differences in cmdlet availability or behavior on Linux.
- Mention alternative tools or workflows for Linux environments, or provide links to relevant documentation.
- Ensure terminology and examples do not assume exclusive Windows usage; consider adding a section on cross-platform automation best practices.
Automation
Work with Azure Desired State Configuration extension version history
...rticles/automation/automation-dsc-extension-history.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page exclusively covers Windows operating systems and Windows-specific technologies (PowerShell, Windows Management Framework, Nano Server) in all version histories and examples. There is no mention of Linux support, Linux equivalents, or cross-platform parity. The focus is entirely on Windows Server and related tools, with PowerShell and WMF as the only configuration mechanisms discussed.
Recommendations
- Explicitly state the current status of Linux support for the DSC extension, including any retirement or deprecation notices.
- If Linux support is retired, provide historical context and links to alternative solutions for Linux configuration management (e.g., Azure VM Custom Script Extension, Ansible, Chef, Puppet).
- If Linux support is available in older versions, include a section detailing supported Linux distributions, extension versions, and configuration patterns.
- Add Linux-specific examples and usage patterns where relevant, or clearly indicate that only Windows is supported.
- Reference cross-platform configuration management tools and best practices for Azure VMs.
- Update the 'Next steps' section to include links to Linux configuration management documentation and guidance.
Automation
Azure Automation State Configuration overview
...ob/main/articles/automation/automation-dsc-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing heavily on PowerShell DSC, listing Windows operating systems and requirements first and in more detail, referencing Windows-specific tools and features (e.g., WMF, WinRM, Chocolatey), and providing more granular information for Windows than Linux. Linux support is mentioned but lacks equivalent detail, examples, or tool references, and Linux-specific documentation links are less prominent.
Recommendations
- Provide Linux-specific configuration and onboarding examples alongside Windows examples.
- Include references to Linux-native tools and package managers (e.g., apt, yum) in continuous deployment pipeline examples, not just Chocolatey.
- List supported Linux distributions explicitly, similar to the Windows OS list, and link directly to relevant documentation.
- Offer parity in troubleshooting and requirements sections for Linux (e.g., mention dependencies, agent installation steps, and configuration specifics).
- Balance PowerShell-centric language with Bash or other Linux scripting references where appropriate.
- Ensure that Linux proxy configuration examples are as detailed as Windows, including sample scripts and environment variable usage.
Automation
Remediate noncompliant Azure Automation State Configuration servers
...b/main/articles/automation/automation-dsc-remediate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation prioritizes Windows remediation by providing direct PowerShell examples and references to Windows-specific tools (Update-DscConfiguration, PowerShell, Chocolatey). Linux remediation is described as less straightforward, lacking direct command/script examples and relying on re-registration or external Python scripts. The Windows approach is presented first and in more detail, while Linux instructions are less actionable and less integrated.
Recommendations
- Provide direct, actionable Linux remediation examples, such as shell or Python scripts, similar to the PowerShell example for Windows.
- Include Linux-specific tools and commands (e.g., native DSC operations, Ansible, or shell commands) where appropriate.
- Present Windows and Linux remediation instructions in parallel, giving equal detail and prominence to both.
- Reference Linux documentation and resources as prominently as Windows ones, including links to official guides and repositories.
- Clarify any feature parity gaps and suggest alternative workflows for Linux users.
Automation
Azure Automation Hybrid Runbook Worker Overview
...rticles/automation/automation-hybrid-runbook-worker.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology (e.g., 'System account', PowerShell Workflow runbooks, Run As accounts) is mentioned before or more prominently than Linux equivalents. PowerShell and Windows-centric tools are referenced as onboarding channels, and examples or details for Linux (such as the 'nxautomation' account) are minimal and appear after Windows mentions. There are no Linux-specific usage examples, troubleshooting tips, or operational details, and the documentation assumes familiarity with Windows concepts and tools.
Recommendations
- Provide Linux-specific examples for installation, configuration, and troubleshooting, including command-line instructions and operational details.
- Mention Linux equivalents (e.g., shell scripts, Linux authentication mechanisms) alongside or before Windows/PowerShell references.
- Clarify differences in runbook execution, permissions, and accounts between Windows and Linux platforms.
- Include Linux-focused onboarding channels (e.g., bash scripts, Ansible, cloud-init) and highlight parity with PowerShell and Windows tools.
- Add troubleshooting guidance and best practices for Linux environments.
- Ensure that all tables and feature lists explicitly address both Windows and Linux, not just generically or with Windows-first language.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias through several patterns: Windows-specific tools (PowerShell cmdlets) are referenced more frequently and in greater detail than Linux equivalents, and Windows guidance is often presented before Linux guidance. Examples for backup and retention operations rely heavily on Windows PowerShell cmdlets, with no Linux CLI or scripting alternatives provided. While TLS upgrade instructions are included for both platforms, the Windows instructions are linked and described first, and Linux guidance is less detailed and less integrated. Overall, Linux users are not given parity in terms of actionable examples or tool references.
Recommendations
- Provide equivalent Linux command-line examples (e.g., Azure CLI, Bash scripts) for all operations currently described with Windows PowerShell cmdlets, such as exporting runbooks, DSC configurations, and unregistering nodes.
- Ensure Linux guidance is presented alongside or before Windows guidance in each section, rather than after.
- Reference Linux-native tools (e.g., Azure CLI, shell scripts) wherever Windows tools (PowerShell) are mentioned.
- Expand Linux-specific documentation for asset management, backup, and retention, including step-by-step instructions.
- Add links to Linux documentation and official guides for relevant Azure Automation operations.
Automation
Runbook authoring using VS Code in Azure Automation
...in/articles/automation/automation-runbook-authoring.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows and PowerShell bias. Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and in greater detail. Directory path examples use Windows-style paths (e.g., C:\abc), and there are no Linux/macOS-specific examples or instructions. The documentation assumes familiarity with Windows conventions and tools, with little to no parity for Linux users.
Recommendations
- Provide Linux/macOS-specific examples alongside Windows ones, especially for directory paths (e.g., use ~/abc or /home/user/abc).
- List supported operating systems in a neutral or rotating order, or group by OS type rather than listing Windows first.
- Include instructions or notes for installing and using PowerShell Core on Linux/macOS, and clarify any OS-specific limitations or differences.
- Offer examples of runbook management and debugging using Linux/macOS conventions and shell environments.
- Explicitly mention any differences in extension behavior or prerequisites on Linux/macOS.
- Where keyboard shortcuts or UI navigation are described, include equivalents for macOS (e.g., Cmd+Shift+P instead of Ctrl+Shift+P).
Automation
Azure Automation network configuration details
...rticles/automation/automation-network-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page shows evidence of Windows bias. It references Windows-specific DSC resources (e.g., WaitFor resources with a Windows path), and does not provide equivalent Linux DSC resource examples or mention Linux-specific network requirements. The documentation also links to Windows-centric PowerShell DSC resources without clarifying Linux alternatives, and generally assumes Windows tooling and patterns.
Recommendations
- Include explicit examples and references for Linux DSC resources and their network requirements.
- Mention Linux equivalents (such as nxWaitFor resources) when discussing DSC resources that communicate between nodes.
- Provide links to both Windows and Linux DSC resource documentation.
- Clarify any differences in network configuration for Linux Hybrid Runbook Workers or managed nodes.
- Ensure that examples and documentation are platform-neutral or provide parity between Windows and Linux where possible.
Automation
Manage role permissions and security in Azure Automation
...les/automation/automation-role-based-access-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for managing Azure RBAC and role assignments, without mentioning or providing equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The configuration and scripting sections focus exclusively on PowerShell cmdlets, and references to platform-specific tooling (such as 'devx-track-azurepowershell') reinforce this bias. There is no mention of Linux-native tools, nor are Linux command-line patterns or examples provided alongside the PowerShell instructions.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, including role assignment, removal, and querying.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide step-by-step instructions.
- Where scripts are provided, offer both PowerShell and Bash/CLI versions, and clarify platform compatibility.
- Update references and links to include Azure CLI documentation alongside PowerShell documentation.
- Review and update any screenshots or UI references to ensure they are not Windows-specific, or clarify cross-platform availability.
- Consider including a section on managing Azure Automation permissions from Linux environments, highlighting best practices and tool parity.
Automation
Use Azure Automation runbooks and modules in PowerShell Gallery
...main/articles/automation/automation-runbook-gallery.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 and PowerShell bias. All examples and workflows center around PowerShell, PowerShell Gallery, and Windows-centric tools and terminology. There is no mention of Linux-specific tools, workflows, or examples, and scenarios such as copying files to/from Azure VMs are described only for Windows. Python is mentioned as a supported runbook type, but no Python or Linux examples are provided. The documentation assumes familiarity with PowerShell and Windows conventions, and does not address Linux users' needs or alternative approaches.
Recommendations
- Add equivalent Linux/Bash examples for common scenarios, such as importing runbooks/modules, and copying files to/from Azure VMs.
- Include references to Linux tools (e.g., Bash, SSH, SCP) and how they can be used in Azure Automation runbooks.
- Provide sample Python runbooks and workflows, especially for Linux environments.
- Explicitly mention cross-platform compatibility and limitations (e.g., which modules/runbooks work on Linux vs. Windows).
- Highlight any differences in Azure Automation usage between Windows and Linux environments.
- Ensure that documentation sections do not assume PowerShell as the default, and offer parity for Linux users.
Automation
Handle errors in Azure Automation graphical runbooks
...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 Windows bias by exclusively referencing PowerShell, Windows cmdlets, and Windows-centric error handling patterns. All examples and recommended practices use PowerShell syntax and Windows tools (e.g., Write-Warning, Start-AzVM), with no mention of Linux equivalents, Bash scripting, or cross-platform considerations. The terminology and guidance assume a Windows environment, omitting Linux automation scenarios and tools.
Recommendations
- Include Linux/Bash examples alongside PowerShell, showing how error handling can be implemented in graphical runbooks using Bash or Python activities.
- Reference Linux-specific tools and cmdlets (e.g., Azure CLI, Bash scripts) where appropriate, and provide parity in examples.
- Clarify which features and error handling patterns are platform-agnostic and which are specific to Windows/PowerShell.
- Add a section discussing cross-platform automation, including any limitations or differences when using Linux hybrid workers.
- Ensure that terminology and screenshots do not assume exclusive use of Windows or PowerShell, and mention Linux support where relevant.
Automation
Deploy an Amazon Web Services VM with an Azure Automation runbook
...icles/automation/automation-scenario-aws-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, referencing the AWS PowerShell module and PowerShell Gallery. There are no examples or mentions of Linux-native tools (e.g., Bash, AWS CLI in shell scripts), nor is there guidance for users who may prefer or require Linux-based automation. The workflow assumes familiarity with Windows-centric tools and patterns, such as PowerShell ISE, and does not provide parity for Linux users.
Recommendations
- Add equivalent examples using Bash and the AWS CLI, demonstrating how to automate VM provisioning from a Linux environment.
- Include instructions for importing and using AWS CLI modules in Azure Automation, and how to author runbooks using Python or Bash.
- Provide guidance for Linux users on credential management and environment setup within Azure Automation.
- Ensure that both Windows and Linux approaches are presented side-by-side, or at least referenced, to avoid platform bias.
- Mention cross-platform compatibility and clarify which steps are specific to Windows/PowerShell and which can be adapted for Linux.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by prioritizing PowerShell (a Windows-centric technology) in both recommendations and examples, referencing Windows-specific tools and file paths (e.g., C:\modules), and providing detailed PowerShell guidance before Python. Linux-specific considerations are mentioned only in passing, and there are no Linux shell (bash) examples or explicit Linux parity guidance. Many limitations and known issues reference Windows environments and tools, and the documentation often assumes Windows as the default context.
Recommendations
- Add explicit Linux shell (bash) examples for common automation scenarios alongside PowerShell examples.
- Clarify when instructions or file paths are Windows-specific, and provide Linux equivalents (e.g., use /home/user/modules instead of C:\modules).
- Highlight Linux Hybrid Runbook Worker capabilities and limitations in parity with Windows, including any differences in module/package management.
- Ensure that recommendations and examples for Python runbooks include Linux-specific guidance and troubleshooting.
- Where PowerShell is recommended, clarify its cross-platform capabilities and limitations, and avoid implying Windows as the default unless necessary.
- Provide a table or section comparing Windows and Linux support for each runbook type, including supported features and known issues.
Automation
Azure Automation account authentication overview
...in/articles/automation/automation-security-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the primary method for Azure Automation authentication, without mentioning Linux-native tools or providing Bash/CLI examples. There is no discussion of Linux authentication patterns, nor are Linux-specific tools or workflows referenced. The documentation assumes Windows-centric approaches and omits parity for Linux environments.
Recommendations
- Include examples using Azure CLI and Bash scripts for authentication, alongside PowerShell examples.
- Explicitly mention how Linux-based Hybrid Runbook Workers can authenticate, including any differences or requirements.
- Reference Linux-native tools (e.g., OpenSSL, curl, jq) where relevant for credential management and authentication.
- Add a section comparing authentication workflows for Windows and Linux environments.
- Ensure that instructions for creating and managing Automation accounts are platform-agnostic or provide parallel steps for both Windows and Linux users.
Automation
Send an email from an Azure Automation runbook
...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 exclusively uses PowerShell for all code examples and automation steps, assumes the use of the Azure Az PowerShell module, and does not provide any Bash, CLI, or Python alternatives. All instructions and scripts are written for PowerShell, which is traditionally associated with Windows environments, and there is no mention of Linux-native tools or cross-platform scripting approaches. This creates a strong Windows/PowerShell bias and may alienate users who prefer or require Linux-based automation.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands and Bash scripts for all major steps, including Key Vault creation, secret management, and role assignments.
- Include a section or examples for creating and running runbooks using Python, which is supported in Azure Automation and is popular in Linux environments.
- Explicitly mention that PowerShell Core is cross-platform, but also clarify how to adapt the instructions for Linux/macOS environments.
- Reference Linux tools and patterns (e.g., using curl for REST calls, jq for JSON manipulation) where appropriate.
- Reorder or parallelize instructions so that Linux/Bash/CLI examples are presented alongside or before PowerShell/Windows examples to avoid a 'Windows-first' impression.
- Add notes or links to documentation for users who want to use the Azure portal, REST API, or SDKs from non-Windows platforms.
Automation
Configure runbook output and message streams
...s/automation/automation-runbook-output-and-messages.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page is heavily focused on Windows PowerShell, with all code examples, cmdlet references, and tooling instructions centered around PowerShell and its conventions. There is no mention of Linux-native automation tools, Bash, or cross-platform scripting approaches. Retrieval of runbook output is described only via Windows PowerShell cmdlets, and preference variables are discussed solely in the context of Windows PowerShell. No Linux or Bash equivalents are provided, and the documentation implicitly assumes a Windows/PowerShell environment throughout.
Recommendations
- Add equivalent examples and instructions for Bash and Python runbooks, including how to handle output and message streams in those environments.
- Include references to cross-platform tools (e.g., Azure CLI, REST API) for retrieving runbook output and messages, with sample commands for Linux/macOS.
- Clarify which features and cmdlets are specific to Windows PowerShell and which are available in PowerShell Core (cross-platform).
- Provide guidance on managing runbook output and message streams when authoring runbooks on Linux or macOS, including any limitations or differences.
- Reorder sections or add parallel examples so that Linux/Bash/Python approaches are presented alongside or before Windows/PowerShell ones, where applicable.