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 826-850 of 982 flagged pages
Automation Convert configurations to composite resources for Azure Automation State Configuration ...articles/automation/automation-dsc-create-composite.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows PowerShell 5.1 and PowerShell DSC, with no explicit mention of Linux/macOS equivalents or cross-platform PowerShell Core usage. All examples and tooling references are Windows-centric, and there are no instructions or examples for Linux users, despite Azure Automation DSC supporting Linux nodes.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to author and convert configurations using PowerShell Core.
  • Provide examples for Linux DSC resources and modules, and clarify any differences in workflow or tooling.
  • Mention cross-platform compatibility of the CompositeResource module and any limitations.
  • Include links to documentation on managing Linux nodes with Azure Automation DSC.
  • Ensure that steps and terminology are inclusive of non-Windows platforms (e.g., avoid assuming MOF generation or PowerShell session usage is Windows-only).
GitHub Create Pull Request
Automation Integrate Azure Automation State Configuration with Azure Monitor Logs ...main/articles/automation/automation-dsc-diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tooling. The prerequisites and setup instructions assume the use of PowerShell, and there are no Linux/macOS-specific instructions or examples. The only nod to Linux is the retirement announcement, but no guidance is provided for Linux users who may still need to perform these tasks.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for authentication, resource ID retrieval, and diagnostic settings.
  • Explicitly state platform compatibility for each step, clarifying whether steps can be performed on Linux/macOS and how.
  • Provide Bash script examples for common tasks, or reference cross-platform tools.
  • Include a section addressing Linux/macOS users, especially in light of the Linux retirement announcement, with guidance on alternatives or migration paths.
  • Reorder examples so that cross-platform solutions (e.g., Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Automation Azure Automation State Configuration overview ...ob/main/articles/automation/automation-dsc-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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 tools first, and providing more detailed information for Windows nodes (such as specific OS versions and proxy configuration via metaconfiguration scripts). Linux support is mentioned but lacks equivalent detail, examples, and tool references. There are no Linux-specific configuration examples or troubleshooting steps, and Windows-centric tools and patterns (PowerShell, WinRM, WMF) are emphasized throughout.
Recommendations
  • Provide Linux-specific configuration and onboarding examples, including sample DSC configurations for Linux nodes.
  • List supported Linux distributions explicitly, similar to the Windows OS list.
  • Include troubleshooting steps and requirements for Linux nodes, such as dependencies and agent installation details.
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate examples, list Linux first in some sections).
  • Reference Linux-native tools and patterns where relevant (e.g., shell scripts, systemd integration, Linux DSC agent specifics).
GitHub Create Pull Request
Automation Azure Automation network configuration details ...rticles/automation/automation-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-specific DSC resources (e.g., WaitFor resources in PowerShell DSC) and links to Windows-focused documentation before mentioning or providing Linux equivalents. There are no explicit Linux/macOS examples or references to cross-platform DSC resources, which may cause confusion or friction for non-Windows users.
Recommendations
  • Include explicit references to Linux/macOS DSC resources and their documentation.
  • Provide examples or notes for configuring network requirements on Linux/macOS systems.
  • Clarify which sections or resources are Windows-only and offer Linux alternatives where applicable.
  • Add links to cross-platform DSC documentation and resources.
GitHub Create Pull Request
Automation Enable Azure Automation State Configuration .../main/articles/automation/automation-dsc-onboarding.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows and PowerShell workflows. Most examples and scripts use PowerShell, and Windows-specific tools (e.g., WMF 5, PowerShell DSC cmdlets) are referenced throughout. Linux enablement is described, but Linux-specific examples are sparse, and Linux instructions often require a Windows machine to generate configuration files. In several sections, Windows instructions and tools are presented first or exclusively, with Linux guidance appearing later or being less detailed.
Recommendations
  • Provide Linux-native examples and workflows, such as generating and applying DSC metaconfigurations entirely on Linux without requiring a Windows machine or PowerShell.
  • Include bash or Python script equivalents for key tasks currently shown only in PowerShell.
  • Present Linux and Windows instructions in parallel, or clearly separate them, to avoid Windows-first ordering.
  • Reference and link to Linux-native tools and documentation (e.g., Open Management Infrastructure, native DSC for Linux docs) alongside Windows tools.
  • Clarify any limitations or differences in support for Linux vs. Windows up front, and provide alternative solutions where possible.
GitHub Create Pull Request
Automation Edit textual runbooks in Azure Automation ...articles/automation/automation-edit-textual-runbook.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-specific workflows. All code examples use Windows PowerShell, with file paths in Windows format (e.g., c:\runbooks), and there is no mention of Linux/macOS equivalents or cross-platform PowerShell usage. The use of Windows PowerShell and Windows-centric instructions creates friction for Linux/macOS users, who may use PowerShell Core or require different file path conventions.
Recommendations
  • Provide 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.
  • Explicitly state whether Az.Automation cmdlets work with PowerShell Core on Linux/macOS, and provide troubleshooting tips if there are limitations.
  • Add notes or sections for editing runbooks from Linux/macOS environments, including any required setup.
  • Consider reordering examples or providing parallel instructions for both Windows and Linux/macOS users.
GitHub Create Pull Request
Automation Delete an Azure Automation Run As account ...blob/main/articles/automation/delete-run-as-account.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy Windows First
Summary
The documentation focuses exclusively on deleting Azure Automation Run As accounts using PowerShell or the Azure portal, both of which are Windows-centric tools. There are no examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting. The mention of PowerShell is prominent, and no Linux alternatives are provided.
Recommendations
  • Add instructions and examples for deleting Run As accounts using Azure CLI, which is cross-platform.
  • Include Bash or shell script examples for Linux/macOS users.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if relevant.
  • Present cross-platform tools and examples before or alongside Windows-specific ones.
  • Clarify any platform-specific limitations or requirements.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools (PowerShell cmdlets) are referenced repeatedly for key tasks such as resource deletion, backup, and DSC node management, with no Linux CLI or cross-platform alternatives provided. Windows instructions and links appear before Linux equivalents, and Linux guidance is limited to a single Python/OpenSSL example for TLS configuration. Many backup and export procedures reference only PowerShell cmdlets, omitting Linux or Azure CLI examples.
Recommendations
  • Provide Azure CLI or REST API examples for all tasks currently described only with PowerShell cmdlets (e.g., exporting runbooks, DSC configurations, unregistering DSC nodes).
  • Include Linux/macOS-specific instructions for backup and export operations, not just TLS configuration.
  • Present platform guidance in a parallel, side-by-side format, ensuring Linux/macOS examples are given equal prominence and order.
  • Reference cross-platform tools and commands where possible (e.g., az CLI, bash scripts) instead of Windows-only utilities.
  • Clarify which procedures are platform-agnostic and which require OS-specific steps.
GitHub Create Pull Request
Automation Migrate from Orchestrator to Azure Automation (Beta) ...ticles/automation/automation-orchestrator-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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, tools, and migration steps centered around Windows environments. PowerShell is presented as the primary (and only) scripting language, and all paths, modules, and commands use Windows conventions. There is no mention of Linux/macOS equivalents, nor any guidance for users on those platforms. This creates friction for non-Windows users attempting to follow the migration process.
Recommendations
  • Provide equivalent examples for Linux/macOS environments, including bash or Python alternatives where possible.
  • Clarify whether the migration toolkit, Runbook Converter, and integration modules can be used on Linux/macOS, and document any limitations.
  • Offer instructions for installing and running PowerShell Core (cross-platform) and note any differences in usage or compatibility.
  • Include file path examples using Linux/macOS conventions (e.g., /home/user/runbooks) alongside Windows paths.
  • Explicitly state platform requirements and offer guidance for users who do not have access to Windows systems.
GitHub Create Pull Request
Automation Runbook authoring using VS Code in Azure Automation ...in/articles/automation/automation-runbook-authoring.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and in more detail. Examples for directory paths use Windows-style (C:\abc), and there is a lack of Linux/macOS-specific examples or instructions. Debugging support is focused on PowerShell, with Python debugging explicitly unsupported and no mention of Linux/macOS debugging workflows. The use of Windows-centric terminology and examples may create friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS-specific examples for directory paths (e.g., /home/user/abc).
  • Include instructions or screenshots showing configuration steps on Linux/macOS.
  • Clarify how local debugging works on Linux/macOS, especially for PowerShell and Python.
  • Mention Linux/macOS equivalents alongside Windows tools and terminology.
  • Reorder or balance the presentation of supported operating systems and tools so Windows is not always listed first.
  • Add troubleshooting tips for Linux/macOS users where workflows or features differ.
GitHub Create Pull Request
Automation Runbook execution in Azure Automation ...in/articles/automation/automation-runbook-execution.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Automation runbook execution is heavily focused on PowerShell, which is primarily associated with Windows environments. Most examples, explanations, and referenced modules are PowerShell-centric, with no mention of Bash, Python, or Linux-native scripting approaches. Windows-specific tools (e.g., WinSCP.exe, IIS) are referenced without Linux equivalents, and file paths use Windows conventions (C:\temp). There is no guidance or examples for Linux/macOS users, nor are Linux-specific scenarios (such as using Bash scripts or Linux file paths) addressed.
Recommendations
  • Add examples and guidance for Python runbooks, which are supported in Azure Automation and commonly used on Linux/macOS.
  • Include Linux/macOS file path conventions (e.g., /tmp) alongside Windows paths when discussing temporary storage.
  • Reference Linux equivalents for Windows tools (e.g., scp or sftp for WinSCP, Apache/nginx for IIS) in module requirements.
  • Provide Bash or shell script runbook examples where appropriate.
  • Clarify which features and modules are available or limited on Linux Hybrid Runbook Workers.
  • Reorder examples and references so that Linux/macOS scenarios are presented alongside or before Windows-specific ones, where possible.
GitHub Create Pull Request
Automation Manage role permissions and security in Azure Automation ...les/automation/automation-role-based-access-control.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias in its examples and tooling. All command-line instructions for managing Azure RBAC and Automation roles are exclusively shown using Azure PowerShell cmdlets, with no mention of Azure CLI or cross-platform alternatives. The 'Configure Azure RBAC' section provides detailed PowerShell examples and outputs, but omits equivalent Azure CLI commands, which are natively supported on Linux and macOS. The documentation also references PowerShell scripts for runbook role assignments, reinforcing a Windows-centric approach. There is no guidance for Linux/macOS users, nor are Linux-friendly tools or workflows presented.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, especially for role assignment, listing, and removal.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Where scripts are provided, offer both PowerShell and Bash/CLI alternatives.
  • Clarify that Azure PowerShell can be installed and run on Linux/macOS, but recommend Azure CLI for native experience.
  • Ensure that screenshots and UI references are not Windows-specific unless necessary.
GitHub Create Pull Request
Automation Handle errors in Azure Automation graphical runbooks ...omation/automation-runbook-graphical-error-handling.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on Windows PowerShell, with all examples, terminology, and cmdlets specific to PowerShell and Windows environments. There is no mention of Linux or cross-platform alternatives, nor are Bash or Python examples provided. Windows tools and patterns (e.g., PowerShell cmdlets, Write-Warning, Start-AzAutomationRunbook) are referenced exclusively and first, creating friction for Linux/macOS users who may use Azure Automation with hybrid workers or non-Windows environments.
Recommendations
  • Include equivalent examples using Bash, Python, or other supported languages for graphical runbooks.
  • Clarify whether graphical runbooks and error handling features are available and supported on Linux/macOS hybrid workers.
  • Mention cross-platform cmdlets or automation approaches where possible.
  • Add notes or sections on how Linux/macOS users can implement error handling logic in graphical runbooks, including any limitations.
  • Avoid assuming PowerShell is the only or default automation language.
GitHub Create Pull Request
Automation Use Azure Automation runbooks and modules in PowerShell Gallery ...main/articles/automation/automation-runbook-gallery.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell and Windows-centric workflows, with examples and references almost exclusively using PowerShell Gallery, PowerShell modules, and Windows Azure VMs. There is minimal mention of Linux or cross-platform alternatives, and Linux-specific scenarios or tools are not provided. Windows tools and patterns are referenced first and often exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add explicit examples and guidance for Linux/macOS users, such as using Python runbooks and modules.
  • Include references to Linux Azure VMs and provide sample runbooks for Linux scenarios (e.g., file copy to/from Linux VMs).
  • Highlight cross-platform compatibility of runbooks and modules, and clarify which steps or modules are Windows-only.
  • Provide parity in documentation for managing modules and runbooks using Linux/macOS command line tools (e.g., Bash, Azure CLI).
  • List Linux/macOS prerequisites and troubleshooting tips where relevant.
GitHub Create Pull Request
Automation Azure Automation Runbook Types ...b/main/articles/automation/automation-runbook-types.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell (a Windows-centric technology) is presented first and in far greater detail than Python, with multiple sections and examples focused on PowerShell and its various versions. Many examples and known issues reference Windows-specific paths (e.g., C:\modules), environment variables, and tools. There is little to no mention of Linux equivalents, and Linux-specific considerations are minimal or absent. Python (the main cross-platform alternative) receives less coverage, and Linux-specific instructions/examples are missing or brief.
Recommendations
  • Provide Linux-specific examples and troubleshooting steps, especially for PowerShell runbooks on Linux Hybrid Runbook Workers.
  • Include Linux file path examples and clarify differences in environment variables and module management for Linux.
  • Expand Python runbook documentation to include Linux package management, environment setup, and common issues.
  • Reorder sections or provide parallel examples so that Linux/macOS users do not always see Windows-first instructions.
  • Explicitly document limitations and workarounds for Linux Hybrid Runbook Workers in each runbook type.
  • Add links to Linux/macOS-specific tutorials and best practices for Azure Automation.
GitHub Create Pull Request
Automation Configure runbook output and message streams ...s/automation/automation-runbook-output-and-messages.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily focused on Windows PowerShell, with all examples and tooling references using PowerShell cmdlets and syntax. There is no mention of Linux/macOS equivalents, Bash, or cross-platform scripting approaches. The retrieval of runbook output is described only via Windows PowerShell tools, and preference variables are discussed solely in the context of Windows PowerShell. No Linux or cross-platform examples are provided, and Windows terminology and tools are used throughout.
Recommendations
  • Add equivalent examples using Bash, Azure CLI, or Python for Linux/macOS users.
  • Clarify which features and cmdlets are available in cross-platform PowerShell (pwsh) and which are Windows-only.
  • Include instructions for retrieving runbook output using Azure CLI or REST API, which are platform-agnostic.
  • Explicitly state any limitations or differences when using Azure Automation from Linux/macOS environments.
  • Provide links to cross-platform scripting documentation and tools.
GitHub Create Pull Request
Automation Start an Azure Automation Runbook from a Webhook ...s/blob/main/articles/automation/automation-webhooks.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and instructions for creating, using, and managing Azure Automation webhooks. All CLI and scripting examples use PowerShell cmdlets or tools (e.g., Invoke-WebRequest, ConvertTo-Json), with no mention of Bash, curl, or other Linux/macOS-native tools. Even REST API usage is shown via PowerShell. There are no Linux/macOS shell equivalents, nor are cross-platform alternatives discussed. This bias may create friction for users on Linux/macOS platforms who do not use PowerShell.
Recommendations
  • Add equivalent examples using Bash and common Linux/macOS tools (e.g., curl, jq) for creating and invoking webhooks.
  • Show how to authenticate and interact with Azure using Azure CLI (az) commands, which are cross-platform.
  • Provide REST API invocation examples using curl or httpie, not just PowerShell's Invoke-RestMethod.
  • Include notes or sections specifically for Linux/macOS users, highlighting any differences or considerations.
  • Reorder examples so that cross-platform or REST API methods are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Automation Context switching in Azure Automation ...ocs/blob/main/articles/automation/context-switching.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell cmdlets and examples (Az, AzureRM), which are most commonly associated with Windows environments. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform scripting approaches. All code samples and recommendations are PowerShell-centric, and the page assumes the reader is using PowerShell, which is traditionally a Windows-first tool, despite its cross-platform availability.
Recommendations
  • Add equivalent Azure CLI examples for context management and runbook authentication.
  • Include Bash or shell script snippets for Linux/macOS users.
  • Explicitly mention PowerShell Core (pwsh) and its cross-platform support if PowerShell is required.
  • Reorder examples or provide parallel examples for both PowerShell and Azure CLI to avoid Windows-first impression.
  • Clarify whether the recommendations apply to Linux-hosted runbooks or hybrid worker scenarios.
GitHub Create Pull Request
Automation Using a system-assigned managed identity for an Azure Automation account ...s/automation/enable-managed-identity-for-automation.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows and PowerShell bias. Nearly all command-line examples use PowerShell, including REST API calls, ARM template deployments, and authentication steps. There are no CLI/bash examples for Linux/macOS users, and PowerShell is assumed as the default automation tool. Even REST API and HTTP token acquisition examples are given only in PowerShell, despite being platform-agnostic. The only non-PowerShell code sample is a brief Python example, but it does not cover the full workflow. Windows-specific paths and instructions are provided before Linux equivalents, and Windows tooling is referenced throughout.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, especially for enabling managed identity, assigning roles, and verifying assignments.
  • Provide bash/shell script examples for REST API calls and token acquisition, using curl or wget, to support Linux/macOS users.
  • Include instructions for deploying ARM templates using Azure CLI (az deployment group create) and/or Bicep.
  • Where file paths or agent instructions are given, present Linux and Windows steps side-by-side or in parallel, not Windows-first.
  • Clarify that PowerShell commands can be run cross-platform (with PowerShell Core), or explicitly note platform requirements.
  • Expand Python examples to cover more scenarios, such as role assignment and resource access, to demonstrate parity.
GitHub Create Pull Request
Automation Encryption of secure assets in Azure Automation ...icles/automation/automation-secure-asset-encryption.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based examples and instructions for configuring Azure Automation encryption, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. PowerShell is referenced as the primary tool for all command-line operations, and Windows-centric modules (Az PowerShell) are highlighted. REST API examples are provided, but the only detailed step-by-step guidance is for PowerShell, and Azure CLI is mentioned only in passing for revocation, without examples. This creates friction for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for key tasks like assigning managed identities, configuring Key Vault access policies, and switching encryption keys.
  • Include Bash script snippets where appropriate to demonstrate cross-platform usage.
  • Explicitly state that PowerShell commands can be run on Linux/macOS (via PowerShell Core), or clarify any platform limitations.
  • Present Azure CLI and REST API examples before or alongside PowerShell, rather than after.
  • Reference Linux/macOS prerequisites and installation steps for required tools.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell tooling, with all examples and instructions given in PowerShell. There is no mention of Bash, CLI, or Linux/macOS-specific workflows, and Windows terminology (such as 'Windows PowerShell') is used throughout. Linux users are left without guidance for equivalent tasks, and the documentation assumes familiarity with Windows-centric patterns.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for Linux/macOS users.
  • Clarify which steps are platform-agnostic and which are Windows-specific.
  • Include notes or links for Linux/macOS users on how to install and use Azure modules.
  • Provide guidance on credential management using cross-platform tools.
  • Avoid using 'Windows PowerShell' terminology when referring to platform-neutral PowerShell unless necessary.
GitHub Create Pull Request
Automation Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent ...g/guidance-migration-log-analytics-monitoring-agent.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides migration guidance for both Windows and Linux VMs, but the only scripting example is a PowerShell script, which is Windows-centric (though PowerShell Core is cross-platform). There are no Bash or native Linux shell script examples. The prerequisites and instructions for scripting focus on PowerShell installation and modules, and do not mention Linux-specific tools or workflows. The portal-based instructions are platform-neutral, but scripting guidance is Windows-first and lacks Linux parity.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, especially for migration tasks.
  • Explicitly document how Linux users can run the PowerShell script (e.g., using PowerShell Core on Linux), and mention any Linux-specific prerequisites.
  • Include Linux-native tooling or workflows where possible, such as az CLI commands or ARM templates.
  • Ensure examples and instructions alternate or equally represent both Windows and Linux scenarios.
  • Add troubleshooting or notes for common Linux issues (e.g., permissions, agent removal differences).
GitHub Create Pull Request
Automation Manage your Azure Automation account ...e-docs/blob/main/articles/automation/delete-account.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides command-line examples exclusively using Azure PowerShell, with no equivalent Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its usage is shown before any mention of cross-platform alternatives. There are no Linux/macOS-specific instructions or screenshots, and the only command-line automation shown is for PowerShell, which may create friction for users on Linux or macOS who prefer Azure CLI or Bash.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, especially for deleting Automation accounts and solutions.
  • Include Bash script snippets where appropriate.
  • Explicitly mention that Azure CLI is cross-platform and provide parity in instructions for Linux/macOS users.
  • Ensure screenshots and UI instructions do not assume Windows-only environments.
  • Consider adding a table or tabs for PowerShell, Azure CLI, and REST API for each operation.
GitHub Create Pull Request
Automation Disable system-assigned managed identity for Azure Automation account .../automation/disable-managed-identity-for-automation.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides a detailed PowerShell-based example for disabling a system-assigned managed identity via REST API, relying exclusively on Windows-centric tools and cmdlets. There are no equivalent examples or instructions for Linux/macOS users (e.g., using curl, Azure CLI, or Bash), nor is there mention of cross-platform alternatives. The PowerShell workflow is presented as the only programmatic method, creating friction for non-Windows users.
Recommendations
  • Add equivalent example using Azure CLI (az rest) for Linux/macOS users.
  • Provide a curl-based example for sending the PATCH request, including authentication guidance for non-Windows platforms.
  • Explicitly mention that PowerShell examples are Windows-centric and offer cross-platform alternatives.
  • Reorder examples to present cross-platform methods (CLI/curl) before or alongside PowerShell.
GitHub Create Pull Request
Automation Move your Azure Automation account to another subscription ...s/blob/main/articles/automation/how-to/move-account.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides command-line examples exclusively using Azure PowerShell cmdlets (Remove-AzResource, Remove-AzActionGroup), with no equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users, who are more likely to use Azure CLI or REST API. The documentation also references PowerShell tools and patterns without mentioning Linux-native alternatives or providing parity in example coverage.
Recommendations
  • Add Azure CLI examples for all resource deletion and management tasks alongside PowerShell examples.
  • Include REST API sample calls for resource operations, especially for users on platforms where PowerShell is not native.
  • Explicitly mention that PowerShell examples are platform-agnostic (if true), or clarify installation requirements for non-Windows users.
  • Present CLI and REST API examples before or alongside PowerShell to avoid Windows-first impression.
  • Consider a table or tabbed interface for examples, allowing users to select their preferred tool (PowerShell, CLI, REST API).
GitHub Create Pull Request
← Previous Page 34 of 40 Next →