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 776-800 of 982 flagged pages
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily PowerShell-centric, with all CLI examples using Windows PowerShell cmdlets and patterns. Windows tools and terminology (e.g., PSCredential, PowerShell modules) are referenced exclusively or before Python equivalents. There are no examples or guidance for Linux/macOS users who might want to use Azure Automation credentials via Bash, Azure CLI, or other non-Windows scripting environments.
Recommendations
  • Add examples for managing credentials using Azure CLI or REST API, which are cross-platform.
  • Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported for these cmdlets and, if so, provide examples.
  • Explicitly state any platform limitations (e.g., if only Windows PowerShell is supported for certain operations).
  • Provide parity in example ordering: show Python and cross-platform options alongside PowerShell, not after.
  • Mention how Linux/macOS users can interact with Azure Automation credentials, or note if such support is unavailable.
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-30 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 PowerShell-centric, with all code examples and module references using PowerShell. It specifically mentions 'Windows PowerShell' and does not provide any examples or guidance for Bash, Azure CLI, or cross-platform scripting. Linux/macOS users are not given equivalent examples or instructions, which may create friction for those not using Windows or PowerShell.
Recommendations
  • Add Azure CLI (az) examples for authentication and credential management alongside PowerShell examples.
  • Clarify that PowerShell Core (pwsh) is cross-platform and supported, and update references from 'Windows PowerShell' to 'PowerShell' where appropriate.
  • Provide guidance or links for using Microsoft Entra ID authentication in Azure Automation with non-PowerShell runbooks (e.g., Python).
  • Explicitly state if certain features or modules are only available in Windows PowerShell, and suggest alternatives for Linux/macOS users.
  • Reorder sections so that cross-platform or platform-agnostic methods are presented before Windows-specific instructions.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for Azure Automation disaster recovery is notably PowerShell-centric, with all migration scripts and runbook examples provided only in PowerShell and PowerShell Workflow. There are no equivalent examples or guidance for Linux-native tools (such as Bash, Python, or CLI), nor is there mention of cross-platform alternatives. Windows/PowerShell instructions are presented first and exclusively, creating friction for Linux/macOS users who may prefer or require non-PowerShell solutions.
Recommendations
  • Provide equivalent migration scripts and runbook examples using Azure CLI, Bash, or Python to support Linux/macOS users.
  • Explicitly mention whether PowerShell Core (7.x) is supported and cross-platform, and clarify any Windows-only limitations.
  • Add guidance or links for Linux/macOS users on how to install and use PowerShell Core if PowerShell is required.
  • Where possible, offer ARM template or REST API examples for asset migration, which are platform-agnostic.
  • Reorder examples so that cross-platform solutions (e.g., Azure CLI, REST API) are presented before or alongside PowerShell examples.
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-30 00:00
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 bias toward Windows/PowerShell environments. Most examples, code snippets, and workflows are centered around PowerShell and PowerShell Workflow runbooks, with detailed explanations and screenshots. The process for passing parameters, especially from local machines, is exclusively described using PowerShell commands, with no equivalent CLI or Linux/macOS shell examples. SDK and REST API sections are platform-neutral, but the practical, step-by-step guidance for local execution is Windows/PowerShell-centric. Python runbooks are mentioned, but only briefly and without concrete parameter-passing examples from Linux/macOS environments.
Recommendations
  • Add equivalent examples for starting runbooks and passing parameters using Azure CLI (az automation runbook start) and Bash scripts, suitable for Linux/macOS users.
  • Include instructions for preparing and passing JSON objects to runbooks using Azure CLI or REST API from non-Windows platforms.
  • Provide sample workflows for Python runbooks, including parameter passing from Linux/macOS terminals.
  • Clarify that PowerShell examples are cross-platform where applicable (e.g., PowerShell Core/7+), or explicitly note Windows-only limitations.
  • Reorder or balance examples so that PowerShell and non-PowerShell approaches are presented with equal prominence.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell and Windows-centric workflows. All CLI examples use PowerShell, and Windows tools and cmdlets are presented first and in greater detail. There are no examples using Bash, Azure CLI, or Linux-native certificate management tools. Python examples are provided, but only in the context of runbooks, not for certificate management tasks outside of runbooks. This creates friction for Linux/macOS users who may prefer or require non-PowerShell approaches.
Recommendations
  • Add equivalent Azure CLI or REST API examples for certificate management tasks (create, get, remove, set).
  • Provide guidance or examples for uploading certificates from Linux/macOS environments, including using Bash or OpenSSL.
  • Clarify that PowerShell examples are cross-platform (if true), or explicitly mention any platform limitations.
  • Include a section comparing PowerShell and Azure CLI approaches for certificate management.
  • List prerequisites for Linux/macOS users, such as installing PowerShell Core or using Azure CLI.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-30 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 for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All command-line examples use PowerShell cmdlets, and the only non-PowerShell examples are for Python runbooks. There are no examples or guidance for Linux/macOS users who may wish to interact with Azure Automation credentials via Bash, CLI, or other cross-platform tools. The documentation refers to 'Windows PowerShell' explicitly and does not mention alternatives for Linux or macOS environments, nor does it clarify whether PowerShell Core (pwsh) is supported.
Recommendations
  • Add examples using Azure CLI (az) for credential management, if supported.
  • Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported for these cmdlets, and provide examples if so.
  • Explicitly state platform requirements and limitations for PowerShell cmdlets (e.g., Windows-only or cross-platform).
  • Provide guidance or links for Linux/macOS users on how to manage credentials, including any REST API or SDK options.
  • Consider including Bash or shell script examples where possible, or note if such functionality is unavailable.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation frequently references Windows tools and PowerShell cmdlets for critical operations (such as unregistering DSC nodes, exporting runbooks, and DSC configurations), with Linux equivalents either missing or not mentioned. Windows registry/TLS configuration guidance is provided with direct links, while Linux guidance is more generic. Windows examples and tools are often presented first or exclusively.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using Azure CLI or REST API) for tasks currently only described with PowerShell cmdlets, such as unregistering DSC nodes, exporting runbooks, and exporting DSC configurations.
  • When referencing Windows registry or PowerShell steps, add equivalent Linux/OpenSSL or cross-platform instructions where possible.
  • In tables and lists, alternate or parallelize Windows and Linux guidance, rather than listing Windows first.
  • Link to Linux-specific documentation or official Azure CLI docs for Linux users.
  • Clarify when a feature or cmdlet is Windows-only, and suggest alternatives for Linux users.
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-27 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, referencing Windows PowerShell modules, cmdlets, and patterns throughout. All code examples are in PowerShell, and there is no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The use of PSCredential and related cmdlets are Windows-centric, and Linux/macOS users are not provided with equivalent guidance or examples.
Recommendations
  • Add Azure CLI examples for credential management and authentication workflows.
  • Clarify which steps are cross-platform and which are Windows-specific.
  • Provide Bash or Python runbook examples for managing Azure resources.
  • Document any limitations or differences for Linux/macOS users in Azure Automation.
  • Reference cross-platform modules or SDKs (e.g., Microsoft Graph SDK for Python, Azure CLI) where applicable.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no mention of Bash, Python, or other Linux-native scripting alternatives. All migration examples and instructions are PowerShell-based, and tabs/defaults reference Windows first. While the Automation service itself is cross-platform, Linux users may encounter friction due to the lack of Linux-centric guidance.
Recommendations
  • Provide equivalent migration scripts or runbook examples using Bash, Python, or Azure CLI to support Linux/macOS users.
  • Explicitly state PowerShell Core (cross-platform) compatibility and provide instructions for running scripts on Linux/macOS, if supported.
  • Include tabs or sections with Linux-first examples, or clarify any platform limitations for the provided scripts.
  • Reference Azure CLI or REST API alternatives for asset migration, if available.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and PowerShell cmdlets are mentioned first and more frequently throughout the page. Key backup and retention operations reference Windows PowerShell cmdlets without Linux CLI or REST API equivalents, and Windows registry settings are linked before Linux OpenSSL guidance. Linux examples are present for TLS, but parity is lacking for backup/export and resource management tasks.
Recommendations
  • Provide equivalent Linux CLI (az CLI, Bash) or REST API examples for resource management and backup/export tasks currently described only with PowerShell cmdlets.
  • Ensure Linux instructions are presented alongside or before Windows instructions in tables and step-by-step guides.
  • Reference Linux tools (such as Bash scripts, az CLI, or Python) for operations like exporting runbooks, DSC configurations, and managing resources.
  • Clarify which cmdlets or procedures are Windows-only, and offer alternative guidance for Linux/macOS users where possible.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell cmdlets and workflows, with most examples and instructions using PowerShell. The guidance for creating certificates via the portal recommends PowerShell as a workaround for CSP accounts, and all advanced examples (including Resource Manager template deployment) use PowerShell. There is minimal mention of Linux/macOS workflows, and no CLI (az), Bash, or cross-platform scripting examples. The Python section is present, but only for retrieving certificates in runbooks, not for management operations like creation or deletion.
Recommendations
  • Add Azure CLI (az) examples for certificate management tasks, such as creating, retrieving, and deleting certificates.
  • Include Bash or cross-platform scripting examples where possible, especially for certificate upload and management.
  • Clarify which operations can be performed from Linux/macOS environments and provide guidance or alternatives for those that are PowerShell-only.
  • If PowerShell is required for certain tasks, explicitly state platform requirements and suggest PowerShell Core (pwsh) usage on Linux/macOS.
  • Expand Python examples to include certificate management (creation, deletion) if supported via SDKs or REST API.
  • Add a section or table comparing management options across platforms (Windows, Linux, macOS).
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-27 00:00
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 and Windows-centric tools and patterns. Most examples, code snippets, and instructions use PowerShell, PowerShell Workflow, and Windows-specific cmdlets. SDK and REST API sections are platform-neutral, but all CLI-based examples use PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS workflows. The Python runbook section is brief and lacks parity in example depth. There are no Linux/macOS-specific instructions or examples for starting runbooks or passing parameters.
Recommendations
  • Add equivalent examples using Azure CLI (az automation runbook start ...) for Linux/macOS users.
  • Include Bash shell examples for passing parameters to runbooks, especially for JSON input.
  • Clarify which instructions are platform-agnostic (e.g., REST API, SDK) and which are Windows/PowerShell-specific.
  • Expand the Python runbook section to include more detailed parameter passing and invocation examples.
  • Add notes or links to cross-platform tooling for Azure Automation (e.g., az CLI, Bash, Python SDK).
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples use PowerShell cmdlets, and the creation of credential assets is described only via the Azure portal or Windows PowerShell. There is no mention of Bash, Linux shell, or cross-platform CLI alternatives for credential management. PowerShell examples are presented before Python, and no Linux/macOS-specific guidance is provided for credential asset creation or retrieval outside of Python runbooks.
Recommendations
  • Add Azure CLI examples for credential asset management, if supported, to provide parity for Linux/macOS users.
  • Clarify whether credential asset creation and management can be performed via REST API or SDKs, and provide examples.
  • Explicitly state any platform limitations (e.g., if PowerShell is required for certain operations) to set expectations for non-Windows users.
  • If PowerShell Core (pwsh) is supported cross-platform, mention it and provide usage guidance for Linux/macOS.
  • Consider including a section or note on how Linux/macOS users can interact with Azure Automation credentials outside of Python runbooks.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tools and patterns. All CLI examples use PowerShell cmdlets, and the only non-PowerShell language covered is Python (for runbooks). There are no Bash, Azure CLI, or Linux-native examples for credential asset management. The documentation refers to 'Windows PowerShell' specifically when describing how to create credential assets, and PowerShell cmdlets are listed before Python functions. No Linux/macOS shell or tool alternatives are mentioned.
Recommendations
  • Add Azure CLI examples for creating, retrieving, and managing credential assets, if supported.
  • Clarify whether PowerShell examples work cross-platform (e.g., PowerShell Core on Linux/macOS), or provide guidance for non-Windows environments.
  • Include Bash or shell script examples for credential management, if possible.
  • Explicitly state platform requirements and limitations for each method.
  • Reorder examples to present cross-platform or platform-neutral options first, or in parallel.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell, with all detailed command-line examples using PowerShell cmdlets and Windows-centric patterns. The creation and management of certificates are demonstrated exclusively via PowerShell, with no equivalent CLI, Bash, or Linux-native instructions. While Python examples are provided for runbook usage, there are no Linux shell or cross-platform CLI examples for certificate management tasks. PowerShell is presented first and most thoroughly, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) alongside PowerShell.
  • Include Bash or shell script snippets for uploading certificates, using az CLI or REST API.
  • Explicitly mention cross-platform alternatives where PowerShell is referenced, and clarify if PowerShell Core (pwsh) is supported on Linux/macOS for these tasks.
  • Reorder examples or provide tabs for both PowerShell and CLI/Bash, so Linux/macOS users see parity.
  • Document any limitations or differences for Linux/macOS users when using Azure Automation certificate features.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation presents a strong bias towards Windows and PowerShell. All migration examples and scripts are PowerShell-based, with no mention of Bash, Python, or Linux-native alternatives. The installation and migration instructions reference Windows tabs and PowerShell workflows first, and do not provide parity for Linux users or cross-platform scripting. Although Azure Automation supports both Linux and Windows VMs, Linux users are left to adapt Windows-centric instructions, which may create friction.
Recommendations
  • Provide equivalent migration scripts or runbook examples using Bash, Python, or Azure CLI for Linux users.
  • Explicitly document how Linux users can perform asset migration, including prerequisites and platform-specific steps.
  • When referencing installation or configuration guides, ensure both Windows and Linux tabs/examples are present and equally visible.
  • Clarify any platform limitations (e.g., if PowerShell is required regardless of OS, explain why and suggest installation steps for Linux).
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-26 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, referencing Windows PowerShell modules and cmdlets throughout, with no mention of Bash, CLI, or Linux/macOS alternatives. All code examples and instructions use PowerShell, and the creation of credential assets is described only via the Azure portal or Windows PowerShell. There is no guidance for users who prefer or require Linux/macOS environments, nor are cross-platform tools like Azure CLI or REST API referenced.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts for credential asset creation and runbook management.
  • Clarify which steps are platform-agnostic (e.g., Azure portal) and which are Windows/PowerShell-specific.
  • Reference cross-platform authentication methods, such as using managed identities or service principals with Azure CLI.
  • Explicitly state any platform limitations if certain features require PowerShell/Windows.
  • Link to documentation for using Azure Automation with Linux/macOS where applicable.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but Windows instructions and PowerShell cmdlets are consistently mentioned first and more prominently. Backup and retention examples rely heavily on Windows PowerShell cmdlets, with no equivalent CLI or Linux-native examples. Windows registry settings and tools are referenced before Linux OpenSSL guidance, and asset management is described primarily in terms of Windows-centric tooling.
Recommendations
  • Provide Azure CLI or Bash examples alongside PowerShell cmdlets for backup/export tasks, especially for runbooks and DSC configurations.
  • Include Linux-native instructions for asset management and data retention tasks, such as using az CLI or REST API.
  • Balance the order of platform-specific guidance so Linux instructions are presented alongside or before Windows instructions where appropriate.
  • Reference Linux tools (e.g., OpenSSL, systemd, shell scripts) equally when discussing configuration or troubleshooting steps.
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-26 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 on configuring runbook input parameters in Azure Automation exhibits a notable Windows/PowerShell bias. Most examples, code snippets, and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are inherently PowerShell-based). The use of PowerShell cmdlets, Windows-centric terminology, and screenshots of the Azure portal with PowerShell parameters dominate the content. Python runbooks are mentioned briefly, with minimal example coverage and no parity in walkthroughs or screenshots. There are no references to Linux shell (Bash) or cross-platform CLI usage, nor are Linux/macOS-specific considerations addressed.
Recommendations
  • Add equivalent examples for starting and passing parameters to Python runbooks, including code snippets for Bash/CLI usage where applicable.
  • Include explicit instructions or examples for using Azure CLI (az automation runbook start) to start runbooks and pass parameters, highlighting cross-platform compatibility.
  • Clarify which features and workflows are platform-agnostic and which are PowerShell-specific, to help Linux/macOS users understand applicability.
  • Provide screenshots or walkthroughs for Python runbooks and parameter assignment in the portal, not just PowerShell-based runbooks.
  • Mention any limitations or differences when using Azure Automation from Linux/macOS environments, especially around authentication and context management.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page 'Manage certificates in Azure Automation' demonstrates a notable bias towards Windows/PowerShell tooling and workflows. PowerShell cmdlets are featured prominently and exclusively for certificate management tasks (creation, deletion, modification), with no equivalent CLI or Linux-native examples. The only alternatives shown are Python runbook functions, but these are limited to certificate retrieval and do not cover management operations. The portal workaround also recommends PowerShell as the solution. Windows/PowerShell tools and patterns are mentioned first and most extensively.
Recommendations
  • Add Azure CLI examples for certificate management tasks (create, update, delete) to support Linux/macOS users.
  • Include REST API or ARM template deployment instructions that can be executed from any platform.
  • Clarify which operations are platform-agnostic and which require Windows/PowerShell, and provide parity where possible.
  • If PowerShell is required for certain tasks, explicitly state this and suggest alternatives for Linux/macOS users where feasible.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions (with links to registry settings and PowerShell cmdlets) are mentioned first and in greater detail. Several backup and retention examples reference Windows PowerShell cmdlets without offering equivalent Linux CLI or Azure CLI alternatives, and asset management relies on Windows-centric tooling. Linux instructions are present but less detailed and less integrated into the workflow.
Recommendations
  • Provide Azure CLI or REST API equivalents for PowerShell cmdlets used in backup/export/recovery operations, especially for Linux/macOS users.
  • Include Linux-first or cross-platform examples where possible, such as using Bash scripts or Azure CLI for exporting runbooks and DSC configurations.
  • Balance the order of presentation so that Linux and Windows guidance are given equal prominence, or group platform-specific instructions clearly.
  • Clarify which operations are platform-agnostic and which require Windows, and offer alternatives or workarounds for Linux/macOS users.
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-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page on configuring runbook input parameters in Azure Automation demonstrates a notable bias towards Windows and PowerShell environments. Most examples, screenshots, and step-by-step instructions focus on PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). There is minimal coverage of Python runbooks, and no examples or guidance for Bash, Linux shell scripts, or cross-platform command-line usage. Additionally, all CLI examples use PowerShell syntax and Windows-centric cmdlets, with no mention of Linux/macOS equivalents or considerations.
Recommendations
  • Add examples for starting runbooks and passing parameters using Azure CLI (az automation runbook ...), which is cross-platform.
  • Provide sample code or instructions for Bash or shell script usage, especially for Linux/macOS users.
  • Expand the Python runbook section with concrete parameter passing examples, including how to invoke Python runbooks from Linux/macOS.
  • Clarify which features or steps are platform-agnostic and which are Windows/PowerShell-specific.
  • Include notes or links for Linux/macOS users on prerequisites and alternative tooling.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or Linux-native alternatives. While the page states applicability to both Linux and Windows VMs, all migration examples and tooling are PowerShell-based, and instructions reference Windows tabs and patterns first. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Provide equivalent migration scripts or runbook examples using Bash, Python, or Azure CLI to support Linux/macOS users.
  • Clarify whether PowerShell Core (cross-platform) is supported and provide instructions for installation/use on Linux/macOS.
  • Add tabs or sections for Linux/macOS users in all step-by-step instructions, especially where 'windows' tabs are referenced.
  • Explicitly mention any limitations or requirements for Linux users, such as PowerShell module compatibility.
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-24 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-centric tooling, with all examples and instructions using PowerShell modules and cmdlets. There are no references to Bash, Azure CLI, or Linux/macOS scripting environments. The credential management and runbook examples are exclusively PowerShell-based, and the use of Windows PowerShell is explicitly mentioned. This creates friction for Linux/macOS users who may prefer or require Bash or Azure CLI workflows.
Recommendations
  • Add equivalent Azure CLI and Bash examples for credential asset creation and runbook authentication.
  • Clarify which steps are platform-agnostic and which are Windows/PowerShell-specific.
  • Include guidance for Linux/macOS users on how to interact with Azure Automation and Microsoft Entra ID using non-PowerShell tools.
  • Mention cross-platform alternatives (e.g., Azure CLI, REST API) where possible.
  • Rephrase sections to avoid implying PowerShell is the only supported or recommended approach unless that is truly the case.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples are in PowerShell, and Windows PowerShell is explicitly referenced as the method for creating credential assets outside the portal. There are no Bash, Linux shell, or cross-platform CLI examples. The Python section is present, but only for runbooks, not for asset management. Windows/PowerShell tools and patterns are mentioned first and exclusively for asset management tasks.
Recommendations
  • Add Azure CLI examples for credential asset management, if supported.
  • Clarify whether credential management can be performed via REST API or Azure CLI, and provide examples.
  • Explicitly state if PowerShell is the only supported method for credential asset management, to set expectations for Linux/macOS users.
  • If possible, provide guidance for Linux/macOS users on installing and using PowerShell Core cross-platform.
  • Include a note about platform support and limitations for credential management tasks.
GitHub Create Pull Request
← Previous Page 32 of 40 Next →