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 526-550 of 982 flagged pages
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/start-runbooks.md
...e-docs/blob/main/articles/automation/start-runbooks.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 and PowerShell bias. All command-line examples use Windows PowerShell cmdlets, and there are no equivalent examples for Linux users (e.g., using Azure CLI, Bash, or cross-platform PowerShell Core). The term 'Windows PowerShell' is used explicitly, and the documentation does not mention or provide guidance for Linux-native tools or workflows. The structure and ordering of the content also present Windows/PowerShell methods before platform-neutral or Linux-friendly alternatives.
Recommendations
- Add equivalent Azure CLI examples for starting and managing runbooks, including parameter passing and job status retrieval.
- Clarify that PowerShell Core (pwsh), which is cross-platform, can also be used, and provide examples where appropriate.
- Avoid using 'Windows PowerShell' exclusively; refer to 'PowerShell' and specify when examples are compatible with both Windows and Linux.
- Include a section or table row for Linux/macOS users, highlighting supported tools and methods (e.g., Azure CLI, REST API, PowerShell Core).
- Ensure that all parameter handling examples are shown in both PowerShell and Azure CLI syntax.
- Review terminology and ordering to avoid presenting Windows-specific tools and workflows before cross-platform or Linux-native options.
Create Pull Request
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-manage-send-joblogs-log-analytics.md
...mation/automation-manage-send-joblogs-log-analytics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Powershell bias. It references PowerShell as the tool for viewing job logs outside the portal and discusses error streams in the context of PowerShell. There are no examples or mentions of Linux tools or command-line interfaces (such as Azure CLI, Bash, or Linux shell scripting) for interacting with Azure Automation logs. The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide Linux-specific guidance or parity in examples.
Recommendations
- Include examples using Azure CLI for querying or managing Automation logs, alongside or instead of PowerShell.
- Explicitly mention that the log querying and monitoring features are available and supported on Linux systems, not just Windows.
- Provide sample scripts or command-line instructions for Linux users (e.g., Bash scripts, use of az CLI, or Kusto queries executed via CLI).
- Clarify that runbooks can be authored and managed from Linux environments, and provide links or references to Linux-compatible tooling.
- Avoid language that assumes PowerShell is the default or only way to interact with Azure Automation logs; present alternatives equally.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-webhooks.md
...s/blob/main/articles/automation/automation-webhooks.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 examples for creating, using, and managing webhooks are provided exclusively in PowerShell, with no equivalent examples for Bash, curl, or other common Linux tooling. Even REST API usage is shown via PowerShell's Invoke-RestMethod. There are no references to Linux command-line tools, and the workflow assumes a Windows/PowerShell environment throughout. This limits accessibility for Linux users and those working in cross-platform environments.
Recommendations
- Provide equivalent examples using Bash and curl for all webhook operations (creation, invocation, deletion, etc.).
- Show how to authenticate and interact with Azure using Azure CLI (az) commands, not just PowerShell Az module.
- For REST API sections, include examples using curl or httpie, not only PowerShell's Invoke-RestMethod.
- When presenting multiple approaches, do not always list PowerShell first; alternate or present both together.
- Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
- Where possible, include notes or troubleshooting tips relevant to Linux environments (e.g., file path formats, authentication differences).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-guidelines.md
.../articles/automation/automation-security-guidelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-specific instructions and tools (such as the Hybrid Runbook Worker VM extension with '?tabs=windows'), and omitting Linux-specific examples or guidance. All links and examples for installing or managing Hybrid Runbook Workers default to Windows, with no mention of Linux equivalents or cross-platform considerations. This may lead Linux users to feel unsupported or unclear about best practices for their environments.
Recommendations
- Provide explicit Linux-specific instructions and examples alongside Windows ones, especially for installing and managing Hybrid Runbook Workers.
- Ensure all links that currently default to '?tabs=windows' also reference or highlight the Linux tab or equivalent documentation.
- Mention Linux tools, patterns, and security considerations where relevant, such as differences in permissions, authentication, or network isolation on Linux systems.
- Add a section or callout clarifying cross-platform support and any differences in implementation or security best practices between Windows and Linux environments.
- Review all examples and ensure parity by including both PowerShell (Windows) and Bash/Shell (Linux) script examples where automation or scripting is discussed.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runbooks.md
...-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 is heavily biased towards Windows and PowerShell usage. All code examples are in PowerShell, with no Bash, CLI, or Linux-native scripting examples. File paths and script types referenced (e.g., .ps1, C:\Runbooks\) are Windows-centric. There is no mention of Linux shell scripting, Azure CLI, or cross-platform automation tools. The documentation assumes the user is operating from a Windows environment and using PowerShell, omitting guidance for Linux users.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands for each PowerShell example, especially for creating, importing, publishing, and managing runbooks.
- Include Bash shell script examples and reference Linux file paths (e.g., /home/user/Runbooks/) alongside Windows paths.
- Explicitly mention and demonstrate how to use runbooks authored in Python or Bash, not just PowerShell.
- Clarify which features and procedures are available or different on Linux-based Hybrid Runbook Workers.
- Add a section or callouts for Linux/macOS users, including prerequisites and environment setup.
- Ensure that references to tools and patterns (such as credential management, file import, and job status retrieval) include both PowerShell and cross-platform alternatives.
- Review and update terminology to avoid assuming a Windows-only environment (e.g., avoid only referencing .ps1 files and C:\ paths).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/change-tracking-data-collection-rule-creation.md
...cking/change-tracking-data-collection-rule-creation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific settings and examples. The JSON script heavily details Windows registry paths and file settings, while Linux settings are less detailed and lack equivalent examples. The only reference example for file settings is for Windows paths, with no Linux file path example provided. Windows-specific tools and patterns (e.g., registry keys, Windows directory paths) are mentioned exclusively, and Windows is consistently presented before Linux.
Recommendations
- Provide equivalent Linux file settings examples alongside Windows examples, such as a JSON snippet for tracking files in typical Linux directories (e.g., /var/log/* or /etc/*).
- Include more detailed Linux-specific configuration options, similar to the depth given for Windows registry and file settings.
- When listing both Windows and Linux extensions or settings, present them in parallel or alternate the order to avoid always listing Windows first.
- Add explanatory notes or tables comparing Windows and Linux settings, highlighting differences and similarities.
- Ensure that all examples and reference sections include both Windows and Linux use cases to achieve parity.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-aws-deployment.md
...icles/automation/automation-scenario-aws-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (such as PowerShell ISE and the AWSPowerShell module) for all examples and instructions. There are no references to Linux-native tools, Bash scripting, or cross-platform alternatives such as AWS CLI or Python. The workflow assumes a Windows environment and does not provide parity for Linux users, omitting any Linux shell or cross-platform scripting guidance.
Recommendations
- Provide equivalent examples using AWS CLI commands in Bash scripts, which can be run on Linux or macOS Automation Hybrid Workers.
- Include instructions for importing and using the AWS Tools for PowerShell Core, which is cross-platform, or clarify if only Windows PowerShell is supported.
- Add a section or callout for Linux/macOS users, describing how to author and execute runbooks using Python or Bash, and how to install necessary modules or packages.
- Mention and demonstrate the use of cross-platform editors (such as VS Code) instead of PowerShell ISE, which is Windows-only.
- Clarify any platform limitations in prerequisites, and provide links to Azure Automation documentation for Linux Hybrid Workers.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-managed-identity-for-automation.md
.../automation/disable-managed-identity-for-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page provides only PowerShell-based examples for disabling a system-assigned managed identity via the REST API, with no equivalent examples for Linux or cross-platform tools (such as Azure CLI or curl). The scripting and authentication steps are tailored to Windows environments and PowerShell users, and there is no mention of Linux-native workflows or tools.
Recommendations
- Add equivalent Azure CLI examples for authentication and sending the PATCH request, which work cross-platform (Windows, Linux, macOS).
- Provide a curl example for sending the REST API request, including details on how to obtain an access token using Azure CLI (az account get-access-token).
- Explicitly mention that the PowerShell example is Windows-centric and offer alternative instructions for Linux/macOS users.
- Consider reordering or parallelizing the examples so that Windows and Linux instructions are presented together, or at least ensure Linux examples are not omitted.
- Reference relevant documentation for Linux users, such as Azure CLI authentication and REST API invocation.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/graphical-runbook-sdk.md
...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, with all examples and terminology referencing PowerShell commands, workflows, and Windows-centric assemblies. There are no Linux or cross-platform scripting examples, nor is there mention of Bash, Python, or other non-Windows automation tools. The SDK and activities are described exclusively in terms of PowerShell, and the prerequisites and workflows assume a Windows environment.
Recommendations
- Add explicit statements about platform support, clarifying whether the SDK and graphical runbooks can be authored or executed on Linux/macOS environments.
- If supported, provide equivalent examples using Bash, Python, or other cross-platform scripting languages.
- Mention any Linux-compatible tools or workflows, or clearly state if the SDK is Windows-only.
- Include guidance for Linux users on how to interact with Azure Automation graphical runbooks, or provide alternative automation options for non-Windows environments.
- Reorder explanations and examples to avoid always presenting Windows/PowerShell first, or provide parallel examples for other platforms.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-office-365.md
...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, with all examples and instructions using Windows PowerShell. There is an explicit note that the Microsoft Graph PowerShell module cmdlets must be run from Windows PowerShell, and no Linux or cross-platform alternatives are provided. The use of Windows-specific tools and patterns (such as Send-MailMessage and credential assets for PowerShell) further reinforces the Windows bias. There are no Bash, Azure CLI, or PowerShell Core examples, nor any mention of how to perform these tasks on Linux or macOS.
Recommendations
- Provide equivalent examples using PowerShell Core (pwsh), which is cross-platform, and clarify which cmdlets are supported.
- Include Azure CLI examples for authentication and management where possible, as Azure CLI is cross-platform.
- Explicitly state platform limitations and suggest workarounds or alternatives for Linux/macOS users.
- Highlight any Office 365 or Azure Automation features that are not available on non-Windows platforms.
- Where Windows PowerShell is required, suggest using cloud-based automation (e.g., Azure Automation runbooks) that abstracts away the local OS, and clarify that local scripting on Linux/macOS is not supported for these features.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-run-as-accounts-managed-identity.md
...automation/migrate-run-as-accounts-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily focused on PowerShell-based automation, with all code samples and instructions using PowerShell cmdlets and modules (Az, AzureRM), which are most commonly used in Windows environments. There are no examples or guidance for using other scripting languages or tools (such as Python, Bash, or CLI), nor is there mention of Linux-native automation patterns. The documentation assumes the use of the Azure portal UI, which is platform-agnostic but often associated with Windows workflows. Linux or cross-platform automation scenarios are not addressed.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
- Include sample scripts in Bash or Python for authenticating with managed identities in Azure Automation, especially for hybrid runbook workers running on Linux.
- Explicitly mention support for Linux-based hybrid runbook workers and provide migration steps or code samples for those environments.
- Clarify that managed identities and Azure Automation are supported on both Windows and Linux, and link to relevant Linux documentation.
- Balance the order of presentation by including Linux or cross-platform examples alongside or before PowerShell/Windows examples.
- Reference Linux tools (such as cloud-init, systemd, or cron) where relevant for automation scenarios.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-local-authentication.md
...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 referencing PowerShell cmdlets (e.g., Get-AzAutomationAccount, Set-AzAutomationAccount) for checking and modifying the local authentication setting. There are no CLI, Bash, or Linux-native examples provided, nor are cross-platform tools like Azure CLI mentioned. The documentation assumes familiarity with Windows tooling and does not offer Linux-equivalent commands or workflows.
Recommendations
- Add Azure CLI examples (e.g., using 'az automation account show/update') alongside PowerShell cmdlets for all operations.
- Include REST API curl examples for Linux users, especially since the note mentions REST API usage.
- Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux administrators.
- Reorder examples or present them in parallel (PowerShell and CLI) to avoid Windows-first bias.
- Reference Linux-native tools or scripting environments where applicable.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-output-and-messages.md
...s/automation/automation-runbook-output-and-messages.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/PowerShell bias. All code samples, explanations, and tool references are exclusively for Windows PowerShell and related cmdlets. There is no mention of Linux, Bash, or cross-platform scripting, nor are there examples or guidance for users running Azure Automation from non-Windows environments. The documentation assumes the reader is using PowerShell and Windows-centric tools, and Linux or cross-platform users are not addressed.
Recommendations
- Add equivalent examples for Python runbooks, which are supported in Azure Automation, especially in sections discussing output and message streams.
- Include information and examples for retrieving runbook output and messages using Azure CLI (az command), which is cross-platform and widely used on Linux.
- Clarify which features and cmdlets are available or behave differently in Linux Hybrid Runbook Workers or in cross-platform environments.
- Where PowerShell preference variables or cmdlets are discussed, note their applicability (or lack thereof) in Python or other supported runbook types.
- Provide links to documentation or guides for managing Azure Automation from Linux environments, and mention any limitations or differences.
- Rephrase sections that refer to 'Windows PowerShell' to 'PowerShell', and clarify when instructions apply to Windows-only versus cross-platform PowerShell Core.
- Explicitly state if certain features (such as graphical runbooks or specific cmdlets) are only available on Windows, and suggest alternatives for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-services.md
...s/blob/main/articles/automation/automation-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation exhibits a Windows bias, primarily through a heavy emphasis on PowerShell-based automation, repeated references to Windows-centric tools and scenarios (e.g., Active Directory, SQL Server, registry changes), and by mentioning Windows/PowerShell approaches before Linux or cross-platform alternatives. While Linux is mentioned in passing (e.g., 'Linux and Windows support' in Automanage), there is a lack of Linux-specific examples, tools, or guidance, and the documentation assumes familiarity with Windows administration patterns.
Recommendations
- Provide Linux-specific examples and scenarios alongside Windows/PowerShell ones, such as using Bash scripts, Linux configuration management (e.g., Ansible, Chef, or native Azure DSC for Linux), and Linux-based monitoring.
- Explicitly mention and demonstrate how Azure Automation and related services can be used with Linux VMs, including common Linux administrative tasks (e.g., package management, log rotation, cron jobs).
- Balance references to PowerShell with equivalent Python or Bash scripting examples, and clarify cross-platform capabilities where applicable.
- Include Linux-native tools and patterns (e.g., systemd, journald, apt/yum/zypper) in automation scenarios.
- Highlight any differences or additional steps required for Linux environments, especially in areas like update management, configuration drift, and hybrid automation.
- Ensure that tables and scenario descriptions do not assume Windows as the default, and use neutral or inclusive language (e.g., 'servers' instead of 'Windows servers').
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-child-runbooks.md
.../main/articles/automation/automation-child-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All examples use PowerShell syntax and cmdlets (such as Start-AzAutomationRunbook, Disable-AzContextAutosave, Connect-AzAccount), and there is no mention or example of using Python or other runbook types supported by Azure Automation (such as Python runbooks, which are commonly used on Linux). The terminology and instructions assume a Windows/PowerShell environment, and there are no Linux/bash equivalents or guidance for non-Windows users.
Recommendations
- Add equivalent examples for Python runbooks, which are supported in Azure Automation and commonly used in Linux environments.
- Include bash/CLI examples where possible, or at least mention how Linux users can achieve similar functionality.
- Explicitly state the platform support and limitations for each approach (e.g., which features are PowerShell-only, which are cross-platform).
- Reorganize sections to avoid always presenting Windows/PowerShell approaches first; consider parallel presentation of PowerShell and Python/bash examples.
- Reference Azure CLI or REST API alternatives for starting and managing runbooks, which are platform-agnostic.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-config-aws-account.md
...n/articles/automation/automation-config-aws-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing AWS credential management via a link to the AWS PowerShell documentation, without mentioning or linking to equivalent Linux/CLI or SDK methods. There are no Linux-specific examples or references to cross-platform tools for credential management or automation, and the only external guidance provided is for PowerShell users.
Recommendations
- Include references and links to AWS CLI documentation for credential management, not just PowerShell.
- Provide examples for storing and using AWS credentials in Automation runbooks using both PowerShell and Python (or other cross-platform languages).
- Mention and link to Linux/macOS compatible tools and workflows for AWS credential management.
- Ensure that all example commands and workflows are presented in both Windows (PowerShell) and Linux (Bash/CLI) formats where applicable.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-managed-identity-for-automation.md
.../automation/disable-managed-identity-for-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only PowerShell-based examples for interacting with the Azure REST API, with no equivalent examples for Linux or cross-platform tools such as Azure CLI or curl. The workflow assumes the use of Windows tools and patterns (e.g., PowerShell cmdlets, Windows file paths), and does not mention or prioritize Linux or cross-platform alternatives.
Recommendations
- Add equivalent examples using Azure CLI and/or curl for sending the PATCH request, suitable for Linux/macOS users.
- Include bash shell scripting examples alongside PowerShell to ensure parity.
- Use platform-neutral file path examples or clarify paths for both Windows and Linux.
- Mention both PowerShell and CLI/curl options in the introduction to REST API usage, rather than focusing solely on PowerShell.
- Ensure that authentication steps are described for both PowerShell and Azure CLI (e.g., az login).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-use-azure-ad.md
...ob/main/articles/automation/automation-use-azure-ad.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell environments. All examples, prerequisites, and instructions are specific to Windows (e.g., requiring Windows Management Framework, .NET Framework, and Windows PowerShell). There is no mention of Linux, macOS, or cross-platform PowerShell Core support. Installation and usage steps assume a Windows OS, and no Bash, CLI, or cross-platform alternatives are provided.
Recommendations
- Add equivalent instructions and examples for Linux and macOS environments, including how to use PowerShell Core (pwsh) and the Azure CLI.
- Clarify which steps are Windows-specific and provide alternative steps for non-Windows users (e.g., installing modules on Linux/macOS, using dotnet instead of .NET Framework).
- Include Bash/Azure CLI examples for authentication and automation tasks, not just PowerShell.
- Mention cross-platform compatibility of the Az module and how to use it in non-Windows environments.
- Explicitly state OS requirements and provide links to relevant installation guides for Linux/macOS.
- Where Windows tools (e.g., Sign-in Assistant, WMF) are required, note their absence or alternatives on other platforms.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-connections.md
...lob/main/articles/automation/automation-connections.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 and PowerShell bias. All command-line examples for creating and managing connections use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. The 'Create a new connection' section provides only a Windows PowerShell example, and the PowerShell tab appears before the Python tab in code samples. There is no guidance for users working from Linux or macOS environments, nor are cross-platform command-line alternatives (such as Azure CLI) presented.
Recommendations
- Add equivalent Azure CLI examples for creating and managing Automation connections, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include explicit instructions or notes for users on Linux/macOS, clarifying how they can perform the same tasks without PowerShell.
- Reorder or parallelize example sections so that PowerShell and Python (or CLI) examples are presented side-by-side, or at least do not always lead with Windows/PowerShell.
- Mention and link to any relevant Linux tools or scripts that can interact with Azure Automation, if available.
- Clarify in the introduction that the documented PowerShell cmdlets are available cross-platform (if true), or specify platform limitations.
- Where GUI steps are described, note any differences or limitations for users accessing the Azure portal from non-Windows systems.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/compose-configurationwithcompositeresources.md
...omation/compose-configurationwithcompositeresources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell DSC, with all examples and terminology centered around Windows-centric tools and patterns. There are no Linux-specific examples or mentions of Linux equivalents, and the only reference to Linux is an announcement about retirement, not usage or configuration.
Recommendations
- Provide examples or references for composing configurations with Linux nodes, if still supported.
- Include Linux-native configuration management tools or patterns where applicable, or clarify the lack of support.
- Balance references to PowerShell and Windows tools with equivalent Linux tools or workflows, or clearly state platform limitations.
- If Linux support is deprecated, make this explicit at the beginning and suggest alternative solutions for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/context-switching.md
...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 page is heavily focused on Azure PowerShell cmdlets and Windows-centric tooling, with all examples and recommendations provided exclusively in PowerShell. There is no mention of Linux-native tools, Bash, or cross-platform scripting approaches. The guidance assumes the use of PowerShell and does not address how context switching or runbook management would be handled in Linux environments or with other automation languages supported by Azure Automation.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
- Include Bash or Python runbook examples to demonstrate context management outside of PowerShell.
- Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and clarify if context switching issues are unique to PowerShell or apply to other languages.
- Reorganize sections to present cross-platform solutions first or in parallel, rather than focusing solely on Windows/PowerShell.
- Reference Linux tools or patterns where appropriate, and ensure troubleshooting steps and error messages are relevant to both Windows and Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/add-user-assigned-identity.md
...main/articles/automation/add-user-assigned-identity.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 providing only PowerShell-based CLI examples for all command-line operations, including REST API calls, ARM template deployment, and role assignments. There are no examples using Bash, Azure CLI (az), or Linux-native tools. File paths use Windows-style backslashes, and all scripting assumes a PowerShell environment. The only non-PowerShell code sample is a Python runbook, but even this relies on environment variables typically set in Azure Automation, not on Linux shell usage. There are no explicit instructions or examples for Linux users or those using Bash or Azure CLI.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for all PowerShell examples, especially for adding managed identities, assigning roles, and deploying ARM templates.
- Provide Bash shell script examples for REST API calls using curl or httpie, including authentication steps for Linux environments.
- Use platform-neutral file path syntax (forward slashes or mention both styles) when referring to file locations.
- Explicitly mention that all PowerShell examples can be run on PowerShell Core on Linux, or provide alternative commands for Bash users.
- Include a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
- When listing options (e.g., portal, PowerShell, REST API, ARM template), present Azure CLI and Bash examples alongside or before PowerShell to avoid 'windows_first' ordering.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-standalone-account.md
...les/automation/automation-create-standalone-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 providing PowerShell examples exclusively, referencing PowerShell runbooks and cmdlets as the primary automation method, and omitting equivalent CLI or Linux-native instructions. The 'Next steps' section prioritizes PowerShell tutorials and references, with only a single Python runbook tutorial mentioned. There are no examples or instructions for using Azure CLI, Bash, or Linux-native tools to perform the same tasks, nor is there guidance for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlet instructions, especially for key management and account creation.
- Include Bash shell examples where appropriate, particularly for Linux/macOS users.
- Balance the 'Next steps' section by providing links to both PowerShell and Azure CLI tutorials, as well as Python and other cross-platform runbook types.
- Explicitly state that all steps can be performed from any OS via the Azure portal, and clarify any OS-specific requirements.
- Reference cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and avoid assuming PowerShell as the default automation tool.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-disaster-recovery.md
...in/articles/automation/automation-disaster-recovery.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. All migration scripts and runbook examples are provided exclusively in PowerShell, with no mention of Bash, Python, or other Linux-native scripting options. The instructions for Hybrid Runbook Worker installation and migration consistently link to Windows-first tabs or examples, and there is no step-by-step guidance or code samples tailored for Linux users. The documentation assumes PowerShell as the default automation tool, which may not be familiar or preferred by Linux administrators.
Recommendations
- Provide equivalent migration scripts and runbook examples in Bash and/or Python, and document how to execute them on Linux-based Automation accounts.
- Include explicit Linux/Unix instructions and screenshots alongside Windows/PowerShell examples, ensuring parity in all step-by-step guides.
- When referencing installation or configuration steps for Hybrid Runbook Workers, ensure both Windows and Linux tabs are present and that Linux is not secondary or omitted.
- Mention and, where possible, demonstrate the use of cross-platform tools (such as Azure CLI or REST API) for asset migration and automation tasks.
- Clarify any limitations or differences for Linux users, and provide workarounds or alternatives where PowerShell is not available or preferred.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-alert-triggered-runbook.md
...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 is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples, instructions, and prerequisites are written for PowerShell, with no mention of Linux, Bash, or cross-platform alternatives. The only VM creation link points to a Windows VM via PowerShell, and there are no references to Linux VMs or Bash/Azure CLI usage. This creates a strong Windows bias and may alienate users working in Linux or cross-platform environments.
Recommendations
- Provide equivalent examples using Azure CLI (az) and Bash scripts, especially for steps like assigning permissions, creating runbooks, and managing VMs.
- Include links to both Windows and Linux VM quickstart guides, not just Windows/PowerShell.
- When listing prerequisites, mention both PowerShell and Azure CLI as supported options.
- Show how to create and trigger runbooks using Bash or Azure CLI, not just PowerShell.
- Add a section or callouts for Linux users, clarifying any differences or additional steps.
- Ensure that runbook examples are language-agnostic where possible, or provide both PowerShell and Python (or Bash) samples.