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 251-275 of 982 flagged pages
Automation
Track updated files with an Azure Automation watcher task
...s/automation/automation-scenario-using-watcher-task.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 environments. All examples, instructions, and screenshots use PowerShell and Windows-style paths (e.g., D:\examplefiles). There is no mention of Linux equivalents, such as Bash scripts, Linux file paths, or how to configure watcher tasks on Linux-based Hybrid Runbook Workers. The only tooling referenced is PowerShell, and all operational steps assume a Windows OS.
Recommendations
- Add parallel examples for Linux environments, using Bash or Python scripts and Linux file paths (e.g., /home/examplefiles).
- Explicitly mention that watcher tasks can run on Linux Hybrid Runbook Workers, if supported, and provide setup instructions.
- Include screenshots or terminal output from Linux systems.
- Reference Linux tools (e.g., touch, ls) alongside PowerShell commands.
- Clarify any platform-specific limitations or requirements for watcher tasks.
- Update prerequisites to mention Linux as a supported OS for Hybrid Runbook Worker, if applicable.
Create Pull Request
Automation
Automation services in Azure - overview
...s/blob/main/articles/automation/automation-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows and PowerShell-centric automation approaches. PowerShell is repeatedly emphasized as the primary scripting language for Azure Automation, with references to the PowerShell Gallery and integration with Windows-based tools (e.g., Active Directory, SQL Server). Examples and scenarios focus on Windows-centric infrastructure and tools, with little to no explicit mention of Linux-specific automation patterns, tools, or shell scripting. Linux support is only briefly mentioned in Azure Automanage, without concrete examples or guidance for Linux users.
Recommendations
- Provide explicit Linux-based examples for automation scenarios, such as using Bash, Python, or Ansible scripts in Azure Automation and Functions.
- Highlight Linux-compatible modules and tooling in Azure Automation, including integration with common Linux services (e.g., systemd, cron, SSH, package managers).
- Balance PowerShell references with equivalent Bash or Python examples, especially in runbook and function app documentation.
- Include guidance for managing Linux VMs and resources, such as configuration management, update management, and compliance, with Linux-specific best practices.
- Clarify cross-platform capabilities and limitations for each automation service, ensuring Linux users understand how to leverage Azure Automation effectively.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell tooling, with all examples and instructions using PowerShell cmdlets and Windows-centric concepts (e.g., PSCredential, Windows PowerShell modules). There are no examples or guidance for Linux users, such as using Bash, Azure CLI, or Python SDKs. Windows tools and patterns are mentioned exclusively and before any Linux alternatives, which are entirely absent.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for credential management and authentication, suitable for Linux/macOS environments.
- Include instructions for creating and managing credential assets via REST API or SDKs (e.g., Python, JavaScript), which are cross-platform.
- Provide sample runbooks or scripts in Bash or Python, demonstrating how to authenticate to Azure using Microsoft Entra ID from non-Windows environments.
- Mention cross-platform authentication patterns, such as using service principals and managed identities, with examples for both PowerShell and CLI.
- Clearly indicate which steps or modules are Windows-specific and offer Linux/macOS alternatives where possible.
Automation
Start an Azure Automation Runbook from a Webhook
...s/blob/main/articles/automation/automation-webhooks.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 walkthroughs use PowerShell cmdlets and scripting, which are native to Windows and not available by default on most Linux distributions. The instructions for creating, using, and managing webhooks rely exclusively on PowerShell tools (Az Module, Invoke-WebRequest, etc.), and there are no equivalent examples for Linux shell environments (e.g., Bash, curl, Azure CLI). REST API usage is also shown only via PowerShell's Invoke-RestMethod, not with cross-platform tools. The page does not provide Linux or macOS-specific guidance, nor does it mention or demonstrate using Azure CLI, curl, or other non-Windows tools. The PowerShell runbook example is given first and exclusively, with no alternatives for Python or graphical runbooks, and Python webhook support is explicitly marked as unsupported.
Recommendations
- Add Linux/macOS examples using Bash and curl for REST API calls to create, update, and delete webhooks.
- Provide Azure CLI equivalents for all PowerShell Az Module commands (e.g., az automation webhook create, az automation job output).
- Include instructions and sample scripts for using webhooks from non-Windows environments, such as using curl or wget.
- Present cross-platform REST API usage with generic HTTP tools, not only PowerShell's Invoke-RestMethod.
- Clarify which steps/tools are platform-agnostic and which are Windows-specific.
- Where PowerShell is used, note how to install and use PowerShell Core (pwsh) on Linux/macOS, or offer alternatives.
- If Python runbooks are not supported with webhooks, suggest alternative runbook types for Linux users or clarify limitations.
Automation
Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent
...g/guidance-migration-log-analytics-monitoring-agent.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is the only scripting example provided for migration, with no Bash or Linux-native alternatives. Windows-specific concepts (services, registry, MSI installer) are mentioned more frequently and in greater detail than Linux equivalents. The prerequisites and instructions for scripting focus on PowerShell installation and modules, which are more familiar to Windows users. There are no explicit Linux command-line examples, and the migration steps and screenshots are presented in a way that assumes familiarity with Windows-centric tools and workflows.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, alongside PowerShell.
- Include Linux-specific migration steps and screenshots (e.g., using Azure CLI, Bash, or Linux-native tools).
- Clarify Linux agent removal procedures and limitations, especially for agents installed via package managers (apt, yum, etc.).
- List Linux data types and migration considerations with equal prominence to Windows (e.g., daemons, config files).
- Add tabs or sections for Linux-specific instructions wherever Windows instructions are given.
- Reference Linux documentation and troubleshooting resources as prominently as Windows ones.
Automation
Disable local authentication in Azure Automation
...in/articles/automation/disable-local-authentication.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 exclusively providing PowerShell examples and referencing Windows-centric tools (e.g., PowerShell cmdlets like Invoke-AzRestMethod and Get-AzAutomationAccount). There are no CLI, Bash, or Linux-native examples, nor is there mention of cross-platform alternatives. The instructions and verification steps are written for PowerShell, which is most commonly used on Windows, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for disabling and verifying local authentication, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Provide REST API usage examples with curl or httpie, which are native to Linux/macOS environments.
- Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell must be used, and provide installation guidance.
- Reorder or balance examples so that Linux/macOS methods are presented alongside or before Windows-specific instructions.
- Include troubleshooting or verification steps using cross-platform tools, not just PowerShell.
Automation
Context switching in Azure Automation
...ocs/blob/main/articles/automation/context-switching.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Azure PowerShell cmdlets and usage patterns, with all examples and recommendations provided in PowerShell. There is no mention of Linux-native tools, Bash, Azure CLI, or cross-platform scripting approaches. The guidance and code samples assume a Windows/PowerShell environment, which may disadvantage Linux users or those using other shells.
Recommendations
- Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
- Include Bash or shell script snippets demonstrating context management in Azure Automation.
- Explicitly mention platform compatibility for the provided PowerShell examples, and clarify if they work on PowerShell Core on Linux.
- Provide guidance for users running runbooks in Linux-based sandboxes or hybrid environments.
- List both PowerShell and CLI approaches side-by-side where possible, to ensure parity and inclusivity.
Automation
Manage your Azure Automation account
...e-docs/blob/main/articles/automation/delete-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The use of PowerShell cmdlets is emphasized for automation tasks, while Linux-native tools, shell scripts, or CLI commands are absent. Additionally, the ordering of examples consistently presents the Azure portal and PowerShell before mentioning the Azure CLI or REST API, which are only referenced in the introduction and not in the step-by-step instructions.
Recommendations
- Add Azure CLI examples alongside PowerShell for all automation and deletion tasks, using Bash syntax where appropriate.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Provide REST API example requests for deletion and recovery operations.
- Include guidance or scripts for Linux users, such as Bash or shell script equivalents for resource management.
- Balance the ordering of examples so that CLI and PowerShell are presented together or alternate which is listed first.
- Clarify tool/platform requirements for each example, helping users choose the best option for their environment.
Automation
Using a system-assigned managed identity for an Azure Automation account
...s/automation/enable-managed-identity-for-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily biased toward Windows and PowerShell usage. All code examples for enabling and using managed identities, assigning roles, and accessing resources are provided in PowerShell, with only a single Python example (which is not Linux-specific and is generic). There are no Bash, CLI, or Linux shell examples, and Windows tools and paths are mentioned first and more frequently. The prerequisites and instructions consistently reference PowerShell modules and Windows file paths before their Linux equivalents, and REST API usage is demonstrated via PowerShell rather than curl or other cross-platform tools.
Recommendations
- Add equivalent Azure CLI and Bash examples for all PowerShell code blocks, especially for enabling managed identity, assigning roles, and accessing resources.
- Include Linux-specific instructions and examples, such as using curl for REST API calls and referencing Linux file paths and environment variables.
- Present Windows and Linux prerequisites and instructions in parallel, rather than listing Windows first or exclusively.
- Provide Python and/or Bash runbook examples that demonstrate managed identity usage on Linux Hybrid Runbook Workers.
- Reference cross-platform tools and patterns (e.g., Azure CLI, REST via curl) before or alongside Windows/PowerShell tools.
- Clarify where instructions or code are platform-specific, and offer alternatives for both Windows and Linux users.
Automation
Use Azure Private Link to securely connect networks to Azure Automation
...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 in several ways. The only code example provided for configuring public network access uses PowerShell, with no equivalent shown for Linux (e.g., Azure CLI, Bash, or REST API). The State Configuration section emphasizes PowerShell Desired State Configuration (DSC), a Windows-centric technology, without mentioning or linking to Linux equivalents or alternatives. Throughout the guide, Windows tools and patterns (PowerShell, DSC) are referenced first or exclusively, while Linux-specific instructions, examples, or tools are either missing or only mentioned in passing (e.g., Log Analytics agent for Windows or Linux).
Recommendations
- Add equivalent Linux examples for all configuration steps, such as using Azure CLI, Bash scripts, or REST API calls alongside PowerShell.
- Include Linux-focused configuration guidance for Desired State Configuration, such as references to native Linux DSC support or alternative configuration management tools.
- Ensure that all agent installation and configuration instructions are provided for both Windows and Linux, with clear parity in detail and examples.
- Where PowerShell is used, provide side-by-side examples for Azure CLI or REST API to support cross-platform usage.
- Explicitly mention Linux support and considerations in all relevant sections, not just as a secondary note.
Automation
Use the Azure Automation graphical runbook SDK (preview)
...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows and PowerShell. All examples and terminology are based on PowerShell commands and workflows, with no mention of Linux shell equivalents or cross-platform scripting. The SDK and its activities are described exclusively in terms of PowerShell, and Windows-centric tools (DLLs, PowerShell cmdlets) are referenced without alternatives for Linux users. There are no examples or guidance for using the SDK in Linux environments or with non-PowerShell scripting languages.
Recommendations
- Add explicit statements about platform compatibility, clarifying whether the SDK and graphical runbooks can be used on Linux and macOS, or if they are Windows-only.
- Provide examples or guidance for Linux users, such as how to author runbooks using Bash or Python if supported, or clarify limitations.
- Mention Linux equivalents for PowerShell commands or workflows, or provide alternative approaches for Linux automation.
- If the SDK is Windows-only, suggest cross-platform alternatives or document how Linux users can interact with Azure Automation.
- Include notes on how to install and use the SDK on Linux (if possible), or state that it is not supported.
Automation
Manage Office 365 services using Azure Automation
...ocs/blob/main/articles/automation/manage-office-365.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. All examples use Windows PowerShell, and there is an explicit note that PowerShell Core (used on Linux/macOS) is not supported for the Microsoft Graph PowerShell module. No Linux or cross-platform alternatives are mentioned, and all instructions assume a Windows environment and tools.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS users, including any supported cross-platform automation methods.
- Clarify whether Azure Automation supports Bash, Python, or other runbook types for Office 365 management, and provide sample scripts if possible.
- If Microsoft Graph PowerShell is Windows-only, suggest alternative approaches for Linux users (such as using Microsoft Graph REST API with curl or Python).
- Explicitly state platform limitations and offer guidance for non-Windows environments.
- Reorder sections to mention cross-platform options before or alongside Windows-specific instructions.
Automation
Manage Runtime Environment and Associated Runbooks in Azure Automation
...main/articles/automation/manage-runtime-environment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a clear bias toward Windows and PowerShell. Most examples, screenshots, and REST API payloads focus on PowerShell runbooks and the Az PowerShell module. Windows-centric tools and patterns (e.g., PowerShell Gallery, Get-Module, .zip files for modules) are mentioned first and in detail, while Linux and Python equivalents are only briefly referenced. There is a lack of Linux-specific examples, such as using Python packages, Linux-based runbooks, or CLI tools outside PowerShell. The documentation assumes familiarity with Windows/PowerShell conventions and does not provide parity for Linux users.
Recommendations
- Add explicit examples for Python runbooks, including REST API payloads and portal workflows.
- Include screenshots and walkthroughs for creating and managing Python runtime environments and runbooks.
- Mention Linux-specific packaging formats and workflows (e.g., .whl files, pip, requirements.txt) with equal prominence to PowerShell/.zip.
- Provide examples of using Azure CLI and other cross-platform tools in Python runbooks.
- Clarify which runtime environments run on Linux versus Windows, and discuss any platform-specific behaviors.
- Ensure that instructions for uploading packages, viewing installed modules, and troubleshooting are provided for both PowerShell and Python/Linux contexts.
- Balance the order of presentation so that Python/Linux options are not always secondary to PowerShell/Windows.
Automation
Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation
...g-agent-based-hybrid-worker-to-extension-based-workers.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias in several key areas. Examples and templates for Bicep and ARM are exclusively for Windows VMs, with no Linux equivalents provided. PowerShell is heavily featured, and Windows-specific tools and patterns (such as Windows PowerShell 5.1, .NET Framework, and registry editing) are mentioned and used before or instead of Linux alternatives. Linux instructions are minimal, often limited to brief bash commands, and lack parity with the detailed Windows steps and scripts.
Recommendations
- Provide equivalent Bicep and ARM template examples for Linux VMs, including supported OS images and extension types.
- Include detailed Linux CLI and scripting examples (e.g., bash, cloud-init, Ansible) for installing and managing Hybrid Worker extensions.
- Expand Linux prerequisites and troubleshooting sections to match the depth of Windows coverage.
- List Linux requirements and steps alongside Windows, not after or separately, to ensure equal visibility.
- Offer PowerShell Core examples for Linux where applicable, and clarify cross-platform cmdlet support.
- Ensure all extension installation instructions (REST API, Azure CLI, PowerShell) explicitly show both Windows and Linux extension types and settings.
Automation
Manage runbooks in Azure Automation
...-docs/blob/main/articles/automation/manage-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for managing runbooks in Azure Automation exhibits a strong Windows bias. All code examples use PowerShell, with no Bash, CLI, or Linux-native scripting shown. File paths and script references (e.g., C:\Runbooks\Sample_TestRunbook.ps1) are Windows-centric. The use of PowerShell cmdlets is pervasive, and there is no mention of Azure CLI, Bash, or Linux shell alternatives for any operation. Windows/PowerShell patterns and tools are presented exclusively and before any mention of Python (which is only referenced for package management, not for runbook management or automation tasks). There are no Linux-specific instructions, examples, or troubleshooting notes.
Recommendations
- Add equivalent Azure CLI and Bash examples for all major operations (create, import, publish, schedule, retrieve job status, restore deleted runbook, etc.).
- Show file path examples using Linux conventions (e.g., /home/user/runbooks/Sample_TestRunbook.py) alongside Windows paths.
- Include instructions for managing Python runbooks beyond package management, such as creating, importing, and publishing Python runbooks using CLI or REST API.
- Explicitly mention cross-platform compatibility and note any differences or limitations for Linux users.
- Provide troubleshooting guidance for Linux environments, including common issues with Hybrid Runbook Worker on Linux.
- Reference Linux tools and patterns (e.g., cron for scheduling, shell scripting for automation) where appropriate.
Automation
Manage databases in Azure SQL databases using Azure Automation
...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 page demonstrates a strong Windows and PowerShell bias. All code samples and automation instructions exclusively use PowerShell cmdlets and patterns, with no mention of Bash, Azure CLI, or Linux-native tooling. The guidance for Hybrid Runbook Worker setup and module installation is written for elevated PowerShell prompts, which are specific to Windows environments. There are no Linux or cross-platform examples, and Windows-centric terminology and tools are presented first and exclusively.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for connecting and managing Azure SQL databases.
- Include instructions for installing required modules and running automation tasks on Linux-based Hybrid Runbook Workers.
- Mention cross-platform compatibility of Azure Automation and clarify which steps/tools are Windows-specific.
- Provide guidance for users who prefer Linux environments, including troubleshooting and environment setup.
- Balance PowerShell examples with Azure CLI and REST API usage to ensure platform neutrality.
Automation
Migrate from a Run As account to Managed identities
...automation/migrate-run-as-accounts-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily biased toward Windows environments, specifically PowerShell. All code samples, migration steps, and graphical runbook instructions use PowerShell cmdlets and concepts (e.g., Connect-AzAccount, Get-AutomationConnection), which are native to Windows. There are no examples or guidance for Linux-based automation, Bash, Python, or CLI usage. The documentation assumes the use of Windows tooling and patterns, and does not mention or prioritize Linux equivalents.
Recommendations
- Add equivalent examples using Azure CLI (az) and REST API for authentication and resource management, which are cross-platform and commonly used on Linux.
- Provide sample scripts in Bash and Python for managed identity authentication and resource access.
- Include instructions for migrating runbooks written in Python or Bash, not just PowerShell.
- Clarify which steps or features are platform-agnostic and which are specific to Windows/PowerShell.
- Mention and link to documentation for using managed identities in Linux-based hybrid runbook workers.
- Ensure that graphical runbook instructions note platform limitations and alternatives for Linux users.
Automation
Manage Python 3 packages in Azure Automation
...ocs/blob/main/articles/automation/python-3-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exhibits Windows bias in several areas. For Python 3.8, instructions and examples consistently reference Windows environments (e.g., 'use a 64-bit Windows machine'), and wheel file naming conventions prioritize Windows architectures (win_amd64) before Linux equivalents. PowerShell cmdlets are provided for package management, with no Linux CLI or Bash alternatives. There is a lack of Linux-specific instructions or parity for managing packages on Linux-based Hybrid Runbook Workers, especially for Python 3.8. Windows tools and patterns are mentioned exclusively or before Linux equivalents, and Linux examples are missing where relevant.
Recommendations
- Provide equivalent Linux instructions and examples for Python 3.8 package preparation and import, including wheel file creation on Linux.
- Include Bash, Azure CLI, or Python-based alternatives to PowerShell cmdlets for package management, especially for users on Linux or macOS.
- Present Linux and Windows instructions side-by-side or in tabs, rather than prioritizing Windows.
- Clarify which steps apply to Windows, Linux, or both, and ensure Linux Hybrid Runbook Worker scenarios are covered.
- Reference Linux tools and patterns (e.g., pip, wheel, bash scripts) alongside Windows tools.
- Add explicit guidance for Linux users on preparing and importing packages for Python 3.8 Hybrid Runbook Workers.
Automation
Create an Azure Automation account using a Resource Manager template
...ation/quickstart-create-automation-account-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned explicitly as a method for deploying the ARM template, and the error message example references running from PowerShell first, with Azure CLI mentioned second. There are no explicit Linux shell/bash examples, and the deployment instructions do not provide parity for Linux users. The references to PowerShell and the lack of Linux-specific guidance or examples may make the documentation less accessible to users on Linux or macOS platforms.
Recommendations
- Add explicit bash/Linux shell examples for deploying the ARM template, including sample commands using Azure CLI from bash.
- Reorder instructions so that Azure CLI (cross-platform) examples appear before PowerShell examples, or present both together.
- Clarify that both PowerShell and Azure CLI are cross-platform, but provide guidance for Linux/macOS users on installing and using Azure CLI.
- Include troubleshooting tips for common errors encountered on Linux/macOS when deploying ARM templates.
- Avoid using Windows-centric terminology (e.g., 'run from PowerShell') without also mentioning Linux alternatives.
Automation
Quickstart: Use Terraform to create an Azure Automation account
...ickstarts/create-azure-automation-account-terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence despite being Windows-centric. The 'Next steps' section specifically links to a PowerShell runbook tutorial, reinforcing Windows tooling. There are no Linux shell-specific examples (e.g., Bash), nor is there mention of Linux-native tools or patterns. The documentation implicitly assumes familiarity with Windows tools and workflows.
Recommendations
- Add explicit Bash/Linux shell examples for verification steps, alongside Azure CLI and PowerShell.
- Include links to tutorials for creating Automation accounts and runbooks using Bash or Python, not just PowerShell.
- Clarify that Azure CLI is cross-platform and highlight its use on Linux/macOS as well as Windows.
- Balance 'Next steps' by providing both PowerShell and Bash/Python runbook tutorials.
- Mention Linux-native tools or patterns where relevant, and avoid assuming PowerShell as the default automation language.
Automation
Quickstart - Enable managed identities for your Automation account using the Azure portal
...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 focuses exclusively on enabling managed identities for Azure Automation using the Azure portal, with no mention of Linux-specific tools, CLI commands, or cross-platform alternatives. The only runbook example provided in 'Next steps' is for PowerShell, which is traditionally Windows-centric, and there are no Bash or Python runbook examples or references to Linux automation patterns.
Recommendations
- Include examples and links for creating and using managed identities with Bash or Python runbooks, which are common on Linux.
- Add instructions for enabling managed identities using Azure CLI or Azure PowerShell (cross-platform), not just the portal UI.
- Provide parity in 'Next steps' by linking to tutorials for Bash and Python runbooks using managed identities.
- Explicitly mention that the steps apply to both Windows and Linux automation scenarios, or clarify any platform-specific differences.
Automation
Azure Quickstart - Configure a VM with Desired State Configuration
...n/articles/automation/quickstarts/dsc-configuration.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 bias. It centers on PowerShell-based Desired State Configuration (DSC), references Windows-centric tools (such as Chocolatey), and provides examples only in PowerShell. While it mentions deploying a LAMP stack (Linux), the configuration and instructions are exclusively in PowerShell, with no Linux-native alternatives or parity for Linux users. The retirement of Azure Automation DSC for Linux is noted, but the documentation does not offer guidance for Linux users on alternative approaches.
Recommendations
- Provide equivalent examples using Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) or Azure Policy Guest Configuration for Linux.
- Include instructions for configuring Linux VMs using supported methods post-DSC retirement, such as Azure Policy Guest Configuration.
- Offer shell script or YAML-based configuration examples for Linux users, not just PowerShell.
- Reference Linux package managers and service controllers (e.g., apt, systemctl) where appropriate.
- Clarify the limitations and alternatives for Linux users in the prerequisites and throughout the guide.
Automation
Runtime Environment in Azure Automation
...in/articles/automation/runtime-environment-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 primarily on PowerShell as the main scripting language, listing multiple PowerShell runtime versions before Python, and highlighting Windows-centric tools such as Az PowerShell and Azure CLI in the context of PowerShell. There are no Linux-specific examples, nor is Bash or other Linux shell scripting mentioned as a supported language. The documentation also refers to package sources like PSGallery (PowerShell Gallery) before mentioning PyPI, and does not provide parity in examples or tooling for Linux users.
Recommendations
- Add explicit examples and guidance for Bash or other Linux shell scripting in Azure Automation, if supported.
- List Python runtime versions and package management options before or alongside PowerShell to avoid Windows-first ordering.
- Include Linux-centric tools and workflows, such as examples using Azure CLI in Python or Bash runbooks.
- Provide parity in documentation for package sources, mentioning PyPI and other Linux-friendly repositories equally with PSGallery.
- Clarify any platform limitations or differences in capabilities between Windows (PowerShell) and Linux (Python/Bash) environments.
- Link to Python documentation alongside PowerShell docs in the 'Next steps' section.
Automation
Use Source Control Integration in Azure Automation
...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 focused on Windows and PowerShell, providing only PowerShell-based examples and instructions for source control integration in Azure Automation. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. The documentation assumes the use of Windows tools and patterns, and does not mention or demonstrate Linux-compatible workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, especially for assigning roles and configuring source control.
- Include Bash shell examples and instructions for Linux/macOS users.
- Clearly indicate which steps are platform-agnostic and which are specific to Windows/PowerShell.
- Provide guidance on using cross-platform tools (e.g., Azure CLI, REST API) for source control integration.
- Mention any limitations or differences for Linux/macOS users explicitly.
- Ensure that screenshots and UI instructions are not Windows-centric where possible.
Automation
Remove DSC and node from Automation State Configuration
...configuration/remove-node-and-configuration-package.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 prioritizing PowerShell and Windows-centric tools and examples. PowerShell cmdlets are mentioned and explained before Linux equivalents, and manual deletion instructions for Windows use PowerShell, while Linux instructions are less detailed and lack command-line examples for configuration removal. The use of Windows-specific terminology and tools (e.g., Remove-DscConfigurationDocument) is more prominent, and Linux steps are brief and less supported with examples.
Recommendations
- Provide Linux command-line examples for unregistering nodes and deleting configuration files, similar to the PowerShell examples given for Windows.
- Include equivalent Linux tooling or scripts (e.g., Bash commands) for configuration management tasks, not just references to file paths.
- Present Windows and Linux instructions in parallel, ensuring equal detail and visibility for both platforms.
- Avoid using Windows terminology or tools exclusively; mention Linux alternatives wherever possible.
- Add screenshots or step-by-step guides for Linux users, matching the detail provided for Windows/PowerShell.