Automation

232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 176-200 of 365 flagged pages
Automation Track updated files with an Azure Automation watcher task ...s/automation/automation-scenario-using-watcher-task.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is strongly biased toward Windows environments, with all examples and instructions using PowerShell and Windows-style paths (e.g., D:\examplefiles). There are no Linux or macOS equivalents provided for file creation, directory paths, or hybrid worker setup. The only scripting language mentioned is PowerShell, and the runbooks referenced are PowerShell-based, with no Bash or Python alternatives. The instructions for triggering watcher tasks explicitly require remoting into a worker and using PowerShell commands, which may not be directly applicable to Linux/macOS hybrid workers.
Recommendations
  • Add Linux/macOS examples for file creation (e.g., using 'touch ExampleFile1.txt' in Bash).
  • Clarify whether hybrid runbook workers can run on Linux, and if so, provide setup and usage instructions for non-Windows environments.
  • Include notes on path formats for Linux/macOS (e.g., '/home/examplefiles' instead of 'D:\examplefiles').
  • Offer alternative runbook examples using Bash or Python, if supported.
  • Explicitly state any platform limitations for watcher tasks and hybrid runbook workers.
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-13 06:17
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-centric tools and patterns. All code examples and module references are PowerShell-specific, with no mention of Linux/macOS equivalents or cross-platform scripting options. Windows PowerShell is referenced explicitly, and there are no Bash, Azure CLI, or cross-platform automation examples provided.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux/macOS.
  • Clarify which steps are PowerShell-specific and provide guidance or links for Linux/macOS users.
  • Include Bash or Python runbook examples, or reference the ability to use these languages in Azure Automation.
  • Mention that Azure Automation supports Python runbooks and provide a simple Python example for credential management.
  • Reorder sections or explicitly state that PowerShell examples are for all platforms where PowerShell Core is available, or provide platform-specific instructions.
GitHub Create Pull Request
Automation Automation services in Azure - overview ...s/blob/main/articles/automation/automation-services.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias, primarily through the heavy emphasis on PowerShell for automation, frequent references to Windows-centric tools (e.g., registry, Active Directory, SQL Server), and by mentioning PowerShell before Python or other cross-platform scripting options. While Linux support is acknowledged (especially in Azure Automanage), examples and scenarios are often Windows-oriented, and Linux-specific guidance or parity is lacking.
Recommendations
  • Provide Linux-specific examples and scenarios alongside Windows ones, especially for Azure Automation and in-guest management.
  • Highlight Bash, Python, and other cross-platform scripting options equally with PowerShell, including sample runbooks and integration patterns.
  • Explicitly mention Linux equivalents for Windows tools (e.g., systemd, cron, Linux file system monitoring) in automation scenarios.
  • Clarify which features and modules are cross-platform and which are Windows-only, to help users plan accordingly.
  • Add links to Linux-focused documentation or tutorials for Azure Automation, Functions, and Automanage.
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-13 06:17
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 (despite PowerShell Core being cross-platform). There are no Bash or Linux-native CLI examples, and the prerequisites and instructions for scripting focus on PowerShell modules and patterns. The portal-based instructions are platform-neutral, but scripting and automation guidance is biased towards Windows/PowerShell users. Linux users may face friction due to lack of native examples.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, especially for automation and bulk migration scenarios.
  • Include Azure CLI instructions for migration tasks where possible, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly document any Linux-specific considerations or steps, such as agent removal or DCR assignment, in addition to Windows steps.
  • Clarify which steps or scripts are supported on Linux/macOS, and provide troubleshooting guidance for non-Windows environments.
  • Consider reordering examples so that platform-neutral or Linux instructions are presented alongside or before Windows/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-13 06:17
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 Azure PowerShell cmdlets and runbooks, with all examples and recommendations using PowerShell syntax and tools. There is no mention of Linux-native automation tools, Bash, CLI equivalents, or cross-platform scripting approaches. This creates friction for Linux/macOS users who may prefer or require non-PowerShell solutions.
Recommendations
  • Add equivalent Azure CLI (az) examples for context management and runbook automation.
  • Include Bash or Python script snippets demonstrating context switching and management.
  • Explicitly state platform requirements and provide guidance for Linux/macOS users.
  • Mention cross-platform automation options and how context switching issues manifest outside PowerShell.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page focuses on deleting Azure Automation Run As accounts primarily through PowerShell or the Azure portal, both of which are Windows-centric. There are no examples or instructions for Linux/macOS users (e.g., Azure CLI, Bash), and PowerShell is mentioned as the main scripting tool. The portal instructions also implicitly favor Windows due to common usage patterns.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
  • Include Bash script samples for deleting Run As accounts.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell is required, and provide platform-agnostic command examples.
  • Reorder examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
  • Clarify any portal steps that may differ for non-Windows users (e.g., browser compatibility, UI 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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for managing Azure Automation accounts primarily via the Azure portal and Azure PowerShell. PowerShell examples are given for deletion and solution removal, but there are no equivalent Azure CLI or Bash examples, nor are Linux/macOS-specific instructions or considerations mentioned. PowerShell is a Windows-centric tool, and its usage is presented before any alternative command-line options. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, especially for deleting Automation accounts and removing Log Analytics solutions.
  • Explicitly mention that Azure CLI can be used from Linux/macOS and provide syntax parity.
  • Where PowerShell is referenced, clarify cross-platform availability or link to installation guides for non-Windows systems.
  • Ensure that command-line examples are presented in parallel tabs (PowerShell, CLI, REST) and not just PowerShell.
  • Add a section or note on managing Automation accounts from Linux/macOS environments.
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-13 06:17
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 on Windows-specific tools and cmdlets. There are no equivalent examples or instructions for Linux/macOS users (e.g., using curl, Azure CLI, or bash), and the workflow assumes familiarity with PowerShell and Windows authentication patterns.
Recommendations
  • Add Linux/macOS examples using curl or HTTPie to send the PATCH request.
  • Provide Azure CLI equivalents for authentication and REST API invocation.
  • Include instructions for obtaining an access token on Linux/macOS (e.g., via Azure CLI).
  • Present cross-platform examples side-by-side or indicate which steps are OS-agnostic.
  • Avoid assuming PowerShell as the default scripting environment.
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-13 06:17
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 biased towards Windows and PowerShell usage. All code examples for enabling and using managed identities (except one Python example) are written in PowerShell, with no Bash, CLI, or Linux-native scripting alternatives. Windows tools and paths are mentioned first or exclusively in several places, and Linux instructions are minimal and less detailed. This bias creates friction for Linux/macOS users, who may struggle to follow or adapt the steps without additional guidance.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell for all major tasks, including enabling managed identity, assigning roles, and authenticating.
  • Include Bash shell script examples for REST API calls, using curl or httpie, especially for token acquisition and ARM template deployment.
  • Add Linux/macOS-specific instructions for file paths, environment variables, and runbook worker setup.
  • Ensure all steps that use PowerShell have equivalent CLI or Bash alternatives, and present them in parallel or alternate sections.
  • Mention cross-platform tools (e.g., Azure CLI, curl) before or alongside Windows-specific tools.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and provide guidance for Linux/macOS users where necessary.
GitHub Create Pull Request
Automation Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation ...ation/extension-based-hybrid-runbook-worker-install.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page, while claiming to support both Windows and Linux Hybrid Runbook Workers, demonstrates several Windows biases. Windows-specific tools (PowerShell 5.1, .NET Framework) are emphasized, with PowerShell-based examples and cmdlets shown first and in greater detail. ARM/Bicep/CLI/REST examples focus almost exclusively on Windows VM creation and extension installation, with Linux equivalents either missing or only referenced generically. Folder permissions and troubleshooting notes are Windows-centric, and the Bicep/ARM templates only provision Windows VMs. Linux-specific requirements and patterns are less detailed, and Linux extension installation is not covered in the infrastructure-as-code sections.
Recommendations
  • Provide equivalent Linux VM creation and extension installation examples in Bicep, ARM templates, CLI, and REST API sections.
  • Include Linux-specific troubleshooting steps and folder permission guidance, similar to the Windows coverage.
  • Add Linux-first or side-by-side examples for PowerShell, CLI, and REST API usage, not just Windows-first.
  • Expand documentation of Linux prerequisites, supported tools, and hardening/permissions requirements.
  • Ensure infrastructure-as-code samples (Bicep/ARM) include Linux VM images and extension installation.
  • Clarify when PowerShell Core is required or supported for Linux, and provide Bash/SSH alternatives where applicable.
GitHub Create Pull Request
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based examples for disabling local authentication in Azure Automation. All command-line instructions use PowerShell cmdlets, with no mention of Linux/macOS alternatives (e.g., Bash, curl, or Azure CLI). The PowerShell example is presented as the primary (and only) method, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API calls with curl for Linux/macOS users.
  • Explicitly mention platform-agnostic alternatives and clarify that PowerShell is not required if using REST API directly.
  • Reorder or parallelize examples so that Linux/macOS methods are shown alongside or before Windows/PowerShell examples.
  • Provide guidance on authentication and prerequisites for non-Windows environments.
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-13 06:17
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 portal instructions are platform-neutral, but all scripting guidance is Windows/PowerShell-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown (e.g., az resource delete, az monitor action-group delete).
  • Include REST API sample requests for resource deletion and action group removal.
  • Explicitly mention that PowerShell examples require installation on non-Windows platforms and link to cross-platform installation guides.
  • Present CLI and PowerShell examples side-by-side or alternate their order to avoid Windows-first bias.
GitHub Create Pull Request
Automation Manage Python 3 packages in Azure Automation ...ocs/blob/main/articles/automation/python-3-packages.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell examples are presented for Python 3.8 package management, with explicit instructions to use a Windows machine for wheel generation, while Linux instructions are only given for Python 3.10. PowerShell cmdlets are provided for package management, but no equivalent Linux CLI or Bash examples are offered. Windows terminology and tooling (e.g., win_amd64, PowerShell) appear before or instead of Linux alternatives, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalents for all package management steps, especially for Python 3.8 (e.g., show how to generate wheels on Linux for 3.8).
  • Include Bash/Azure CLI examples for package operations alongside PowerShell cmdlets.
  • Present Linux and Windows instructions in parallel or in tabs, rather than Windows-first.
  • Clarify which steps are OS-agnostic and which require specific platforms, and offer guidance for both.
  • Add explicit notes or sections for macOS users where relevant.
GitHub Create Pull Request
Automation Manage databases in Azure SQL databases using Azure Automation ...articles/automation/manage-sql-server-in-automation.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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-centric tools, with all code samples and automation instructions using PowerShell cmdlets. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. The instructions for Hybrid Runbook Worker setup and module installation are also PowerShell-specific, and Windows terminology (e.g., elevated PowerShell prompt) is used throughout.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Include instructions for installing required modules on Linux/macOS Hybrid Runbook Workers.
  • Clarify cross-platform compatibility of Azure Automation and Hybrid Runbook Worker, and document any OS-specific limitations.
  • Present examples for both Windows and Linux/macOS environments, or explicitly state if only Windows is supported.
  • Add notes or links to official documentation for Linux/macOS users on connecting to Azure SQL and managing identities.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. In critical migration and deployment sections, examples and templates (Bicep, ARM, PowerShell) are exclusively or primarily for Windows VMs, with explicit references to Windows images, PowerShell, and Windows-specific extension types. Linux equivalents are either missing, mentioned as alternatives without examples, or relegated to notes. PowerShell is emphasized as the main scripting tool, with Linux instructions and bash commands only present in the removal section. The use of 'HybridWorkerForWindows' as the default extension type in code samples further reinforces this bias.
Recommendations
  • Provide full Bicep and ARM template examples for Linux VMs, including image references and extension types (e.g., 'HybridWorkerForLinux').
  • Include PowerShell and Azure CLI commands specifically for Linux VMs, demonstrating installation and management of the Hybrid Worker extension.
  • Ensure REST API examples clearly show both Windows and Linux extension types, with sample payloads for each.
  • Present Linux and Windows instructions side-by-side or in parallel tabs, rather than Windows-first or Windows-only.
  • Expand Linux prerequisites and troubleshooting sections to match the depth of Windows coverage.
  • Reference Linux-specific documentation and tools where appropriate, not just Windows/PowerShell.
GitHub Create Pull Request
Automation Migrate from a Run As account to Managed identities ...automation/migrate-run-as-accounts-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward PowerShell-based automation and examples, with all code samples and migration steps using PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzResourceGroup). There are no examples or guidance for users who may use Python, Bash, or other scripting languages commonly used on Linux/macOS. The documentation assumes the use of PowerShell and Windows-centric tools, which may not be familiar or available to Linux/macOS users, especially for hybrid worker scenarios.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
  • Provide sample scripts in Python (using the Azure SDK for Python) for authenticating with managed identities in Azure Automation.
  • Explicitly mention that PowerShell Core (pwsh) is available cross-platform, and clarify if the scripts are compatible with PowerShell Core on Linux/macOS.
  • Include notes or links for Linux/macOS users on how to set up and use PowerShell or alternative tools in Azure Automation.
  • Where possible, provide Bash or shell script equivalents for common tasks, especially for role assignment and resource queries.
GitHub Create Pull Request
Automation Azure Automation overview ...s/azure-docs/blob/main/articles/automation/overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is repeatedly emphasized as the primary automation language, especially in the context of Desired State Configuration (DSC) and runbooks. Windows-centric tools and scenarios (Active Directory, SharePoint Server, SQL Server) are mentioned, and PowerShell Gallery integration is highlighted before Python support. While Linux support is acknowledged, examples and tooling references are predominantly Windows-focused, and Linux-specific patterns or tools are not equally detailed.
Recommendations
  • Provide Linux-specific examples and scenarios, such as automating common Linux services (e.g., Apache, Nginx, systemd units) alongside Windows examples.
  • Highlight Bash, Shell, or Python runbooks with equal prominence to PowerShell, including links to relevant galleries or repositories for Linux scripts.
  • Expand on Linux configuration management options, such as Ansible or native Linux DSC resources, and clarify how Azure Automation integrates with them.
  • List Linux tools and patterns (e.g., cron, systemd timers) in shared capabilities and common scenarios sections.
  • Ensure that documentation for modules, galleries, and hybrid worker setup includes Linux-specific instructions and troubleshooting.
GitHub Create Pull Request
Automation Manage Python 2 packages in Azure Automation ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides explicit instructions for downloading Python package dependencies only on Windows, with no equivalent Linux/macOS example. The command given is for Windows (using a Windows path and pip executable), and the text specifies 'On a Windows 64-bit machine...' without mentioning Linux or macOS alternatives. This creates friction for non-Windows users who need to perform the same task.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using 'pip download' in a bash shell.
  • Clarify that the process is cross-platform and provide commands for both Windows and Linux/macOS.
  • Avoid language that implies Windows is required unless it is truly the only supported platform.
  • Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias by focusing almost exclusively on PowerShell-based examples and workflows, which are native to Windows. All code samples, parameter configuration, and runbook invocation instructions use PowerShell or Windows-centric tools and patterns. There are no Linux shell (bash), cross-platform CLI, or macOS-specific examples for starting or interacting with runbooks. Even SDK and REST API sections use Windows-centric terminology (e.g., GUID creation in PowerShell). Python runbooks are mentioned but lack concrete examples for Linux/macOS users. This bias may create friction for users on Linux or macOS platforms who do not use PowerShell.
Recommendations
  • Add equivalent examples using Azure CLI (az) for starting runbooks and passing parameters, which is cross-platform.
  • Provide bash or shell script examples for Linux/macOS users, especially for tasks like passing JSON objects.
  • Clarify which steps and tools are platform-agnostic and which are Windows-specific.
  • Include notes or sections for macOS/Linux users, such as how to generate GUIDs, manage JSON files, and invoke REST APIs without PowerShell.
  • Expand Python runbook examples to show parameter passing from Linux/macOS environments.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell cmdlets and Windows-centric tooling for certificate management in Azure Automation. All CLI examples are in PowerShell, and Windows tools (e.g., Add-AzureCertificate, New-AzAutomationCertificate) are referenced exclusively. There are no Bash, Azure CLI, or Linux-native examples for certificate upload or management. Python examples are provided for runbook access, but not for certificate creation or upload. The documentation assumes the use of Windows cryptographic providers and PowerShell workflows, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for certificate creation, upload, and management.
  • Document Linux/macOS workflows for preparing and uploading certificates, including OpenSSL usage.
  • Clarify cross-platform compatibility of certificate providers and formats.
  • Provide guidance for Linux users on how to interact with Azure Automation certificates outside of PowerShell.
  • List Python or REST API methods for certificate asset creation and management.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is heavily focused on Windows PowerShell and related cmdlets for managing credentials in Azure Automation. All CLI examples are PowerShell-based, with no Bash, Linux shell, or cross-platform CLI alternatives provided. Windows tools and patterns (e.g., PSCredential, PowerShell modules) are mentioned exclusively and before Python equivalents. There is no mention of Linux/macOS-specific workflows or guidance for users who do not have access to Windows/PowerShell environments.
Recommendations
  • Add Azure CLI examples for credential management, which are cross-platform and work on Linux/macOS.
  • Include Bash or shell script snippets for common credential operations where possible.
  • Explicitly state platform requirements for PowerShell examples and provide alternatives for non-Windows users.
  • Document how Linux/macOS users can interact with Azure Automation credentials (e.g., via REST API, Azure CLI, or Python SDK).
  • Reorder sections so that cross-platform methods (Azure portal, Azure CLI, Python SDK) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Automation Remove user-assigned managed identity for Azure Automation account ...n/articles/automation/remove-user-assigned-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 command-line and scripting tasks. There are no Linux/macOS shell (e.g., Bash, Azure CLI) equivalents, and PowerShell is presented as the default tool for REST API calls and verification steps. Windows tools and patterns (such as PowerShell cmdlets and Windows-style file paths) are used throughout, with no mention of Linux-native alternatives or cross-platform approaches.
Recommendations
  • Add Azure CLI examples for all operations currently shown only in PowerShell.
  • Provide Bash shell examples for REST API calls (e.g., using curl) and verification steps.
  • Use platform-neutral file path syntax or clarify path differences for Linux/macOS.
  • Explicitly state cross-platform support for all steps, and note any OS-specific requirements.
  • Include notes or links for installing and using PowerShell Core on Linux/macOS if PowerShell must be used.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is emphasized as the primary scripting language, with multiple runtime versions listed and examples focused on PowerShell environments. Azure CLI usage is described only in the context of PowerShell 7.4, with no mention of Bash or native Linux shell environments. Package management examples and references (e.g., PSGallery) are Windows-centric, and Linux/macOS equivalents (such as Bash scripting, pip for Python, or native shell usage) are not discussed. The documentation does not provide Linux/macOS-specific guidance or examples, making it less accessible for non-Windows users.
Recommendations
  • Include examples and guidance for using Azure CLI in Bash or native Linux/macOS shells.
  • Add explicit instructions for Python runbooks, including package management via pip and usage in Linux/macOS environments.
  • Reference Linux/macOS package sources (e.g., PyPI) and shell scripting alternatives alongside PowerShell.
  • Clarify cross-platform support and limitations for each runtime environment.
  • Provide parity in documentation structure, listing Linux/macOS options and examples before or alongside Windows/PowerShell ones.
GitHub Create Pull Request
Automation Manage modules in Azure Automation ...b/main/articles/automation/shared-resources/modules.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric tools, with most examples and instructions tailored to Windows environments. Internal cmdlets and modules are explicitly unavailable on Linux Hybrid Runbook Workers, and there are no equivalent Linux or cross-platform examples provided. The guidance for module authoring, importing, and management is almost entirely PowerShell/Windows-oriented, with only brief mention of Python modules and no detailed Linux/macOS instructions or parity.
Recommendations
  • Add equivalent Linux/macOS examples for module management, including CLI and scripting approaches using Bash or Azure CLI.
  • Document limitations and alternatives for Linux Hybrid Runbook Workers more prominently, and provide guidance for Linux users where Windows-only features are unavailable.
  • Include cross-platform best practices for authoring and importing modules, such as using .NET Core or PowerShell Core for compatibility.
  • Expand the Python section to include more detail and parity with PowerShell instructions.
  • Clearly mark Windows-only features and suggest Linux/macOS alternatives or workarounds.
GitHub Create Pull Request
Automation Manage schedules in Azure Automation ...main/articles/automation/shared-resources/schedules.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 strong bias towards Windows and PowerShell. All CLI examples use PowerShell cmdlets, with no mention or examples of Bash, Azure CLI, or cross-platform scripting. The use of PowerShell-specific constructs (e.g., .NET types, PowerShell syntax) further limits applicability for Linux/macOS users. Windows/PowerShell tools are referenced exclusively and presented before any mention of alternatives. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, using Bash syntax where appropriate.
  • Explicitly state cross-platform options for managing schedules (e.g., Azure CLI, REST API) and link to relevant documentation.
  • Include notes or sections clarifying which instructions are platform-agnostic and which are Windows/PowerShell-specific.
  • Provide guidance for Linux/macOS users on installing and using Azure CLI or REST API for schedule management.
  • Where PowerShell is required, clarify how to use PowerShell Core on Linux/macOS, or offer alternatives.
GitHub Create Pull Request
← Previous Page 8 of 15 Next →