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 326-350 of 365 flagged pages
Automation Manage Python 3 packages in Azure Automation ...ocs/blob/main/articles/automation/python-3-packages.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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-specific instructions and examples are presented first or exclusively in several sections, particularly for Python 3.8. The PowerShell cmdlets for managing Python packages are shown without Linux or cross-platform CLI alternatives. Instructions for generating wheel files for Python 3.8 explicitly require a Windows machine, while Linux instructions are only provided for Python 3.10. There is little guidance for Linux/macOS users on managing packages for Python 3.8, and no parity for PowerShell cmdlets on non-Windows platforms.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-only instructions, especially for Python 3.8 package preparation.
  • Include cross-platform CLI alternatives (such as Azure CLI or REST API examples) alongside PowerShell cmdlets.
  • Present examples for both Windows and Linux/macOS environments, or clarify platform requirements for each step.
  • Add notes or tables summarizing which steps/tools are platform-specific and how to achieve parity on other OSes.
  • Ensure screenshots and UI instructions are not Windows-centric unless the feature is unavailable elsewhere.
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-11 06:20
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 command-line operations, including REST API calls and verification steps. No Linux/macOS shell (e.g., Bash, curl, az CLI) equivalents are provided, and PowerShell is assumed for scripting and authentication. Windows tools and patterns (PowerShell cmdlets, Windows-style file paths) are mentioned exclusively and before any cross-platform alternatives.
Recommendations
  • Add equivalent examples using Bash, az CLI, and curl for REST API operations.
  • Provide Linux/macOS shell commands for authentication and resource management (e.g., az login, az automation account update).
  • Use platform-neutral file path examples or clarify path differences.
  • Explicitly state that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
  • Include verification steps using az CLI or Bash commands.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 primarily on PowerShell as the scripting language, mentioning multiple PowerShell runtime versions, and providing examples and package details centered on PowerShell and Azure CLI integration. Linux/macOS equivalents, such as Bash or native Python usage, are not discussed, and there are no examples or guidance for non-Windows environments. The documentation also references Windows-centric tools and patterns (PowerShell, *.dll* files, PSGallery) before mentioning alternatives like pypi, and does not provide parity for Linux users in terms of examples or supported workflows.
Recommendations
  • Add explicit examples and guidance for Linux/macOS users, such as using Bash or Python runbooks.
  • List Linux-compatible runtime environments and clarify support for Bash scripts and native Python workflows.
  • Provide parity in package management instructions, including examples for pypi and Linux-native modules.
  • Mention cross-platform considerations and limitations, especially where features are Windows-specific.
  • Ensure that documentation does not assume PowerShell as the default or only scripting language.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 strong bias toward Windows and PowerShell usage. All CLI examples for certificate management use PowerShell cmdlets, with no mention of Linux/macOS shell equivalents or cross-platform Azure CLI commands. Windows-specific tools and patterns (e.g., PowerShell, .pfx files, Windows cryptographic provider requirements) are referenced exclusively or first. There are no bash, Azure CLI, or Linux-native certificate management examples, making it difficult for Linux/macOS users to follow the instructions without resorting to PowerShell on those platforms.
Recommendations
  • Add Azure CLI examples for certificate management tasks, such as uploading and retrieving certificates.
  • Provide bash or shell script examples for Linux/macOS users, especially for certificate file handling and base64 encoding.
  • Clarify cross-platform compatibility of PowerShell cmdlets (e.g., whether they work on PowerShell Core on Linux/macOS).
  • Mention Linux/macOS certificate provider requirements or alternatives to the 'Microsoft Enhanced RSA and AES Cryptographic Provider'.
  • Reorder examples so that cross-platform or platform-neutral approaches (e.g., Azure CLI, REST API) are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Automation Manage schedules in Azure Automation ...main/articles/automation/shared-resources/schedules.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 Windows bias by exclusively providing PowerShell examples and cmdlets for schedule management in Azure Automation. There are no CLI, Bash, or cross-platform scripting examples, and PowerShell is presented as the primary automation tool. Windows-centric tools and patterns are referenced throughout, with no mention of Linux/macOS alternatives or parity. This creates friction for users on non-Windows platforms, as PowerShell is not always the default or preferred shell, and some users may not have it installed.
Recommendations
  • Add equivalent Azure CLI examples for all schedule management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script examples where applicable, especially for tasks that can be performed via REST API or Azure CLI.
  • Explicitly state PowerShell's cross-platform availability and provide installation guidance for Linux/macOS users.
  • Reorder sections to present cross-platform solutions (Azure CLI, REST API) before or alongside PowerShell examples.
  • Reference Linux/macOS-specific considerations, such as file paths, environment setup, and shell compatibility.
GitHub Create Pull Request
Automation Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation .../troubleshoot/extension-based-hybrid-runbook-worker.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides parity between Windows and Linux for most troubleshooting steps, including paths, tools, and commands. However, there is a noticeable Windows bias in several areas: Windows examples and scenarios are often presented first, PowerShell scripts and registry operations are described in detail for Windows but not matched with equivalent Linux scripting or automation examples, and some troubleshooting steps reference Windows-specific tools (e.g., Microsoft-SMA event logs, registry edits) without Linux equivalents or alternatives. Additionally, some scenarios (e.g., certificate management, event log troubleshooting) are described only for Windows, with Linux guidance missing or less detailed.
Recommendations
  • Alternate the order of Windows and Linux instructions to avoid always presenting Windows first.
  • Provide equivalent Linux automation examples (e.g., bash scripts for log collection, service management, certificate installation) where PowerShell is used for Windows.
  • Include Linux equivalents for Windows-specific tools, such as event log analysis (e.g., using journalctl or syslog), and clarify how to troubleshoot similar issues on Linux.
  • Expand Linux troubleshooting scenarios to match the depth of Windows guidance, especially for authentication, permissions, and certificate management.
  • Where registry edits are described for Windows, provide guidance on Linux configuration files or environment variables if applicable.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation managed identity issues ...n/articles/automation/troubleshoot/managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM, Invoke-RestMethod) and Windows-centric scripting patterns in all troubleshooting scenarios. There are no examples or guidance for Linux/macOS users, such as Bash, Azure CLI, or Python SDK usage. The troubleshooting steps and error messages are tailored to Windows/PowerShell environments, creating friction for users on other platforms.
Recommendations
  • Add equivalent troubleshooting steps and examples using Azure CLI (az), Bash, or Python for Linux/macOS users.
  • Include error messages and resolutions relevant to non-Windows environments.
  • Present examples for both PowerShell and cross-platform tools side-by-side, or clearly indicate which steps apply to which OS.
  • Reference platform-agnostic documentation where possible.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation shared resource issues ...n/articles/automation/troubleshoot/shared-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 troubleshooting steps and code examples use PowerShell cmdlets and scripts, with no mention of Bash, CLI, or Linux/macOS alternatives. Windows-specific DLL errors are discussed without Linux equivalents or guidance. The documentation assumes users are working in a Windows/PowerShell environment, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for each PowerShell cmdlet or script.
  • Include troubleshooting steps relevant to Linux/macOS environments, such as common errors and their resolutions.
  • Mention cross-platform tools and patterns, and clarify which steps are Windows-specific.
  • Reorder examples so that cross-platform or CLI solutions are presented before or alongside PowerShell/Windows solutions.
  • Add notes or links for Linux/macOS users where PowerShell or Windows-specific guidance is given.
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-11 06:20
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 cmdlets, with nearly all examples, instructions, and module lists centered around Windows PowerShell and Az/AzureRM modules. Internal cmdlets and features like Orchestrator.AssetManagement.Cmdlets are explicitly unavailable on Linux Hybrid Runbook Workers. There are no Linux or bash examples, and Linux-specific guidance is minimal or absent. Windows tools and patterns (PowerShell, .psm1/.psd1/.dll, registry settings, etc.) are referenced throughout, and Windows PowerShell features are assumed as the default context.
Recommendations
  • Add equivalent Linux/bash examples for module management tasks, such as importing, deleting, and authoring modules.
  • Clearly indicate which features and modules are Windows-only and provide Linux alternatives or workarounds where possible.
  • Include guidance for managing Python modules and runbooks on Linux Hybrid Runbook Workers, with concrete examples.
  • Provide a comparison table of feature parity between Windows and Linux Hybrid Runbook Workers.
  • Mention and link to Linux-specific documentation where relevant, especially for users running Automation on Linux.
  • Avoid assuming PowerShell as the only scripting environment; reference bash, Python, or other supported environments where appropriate.
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 bias by exclusively providing PowerShell-based examples and instructions for configuring source control integration in Azure Automation. There are no equivalent examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI), and the use of Windows-centric tools and terminology (PowerShell console, PowerShell cmdlets) is pervasive throughout critical configuration steps. This creates friction for users on non-Windows platforms, who must find their own workarounds.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for all PowerShell cmdlets and workflows, especially for role assignment and source control configuration.
  • Explicitly mention cross-platform options and clarify which steps can be performed from Linux/macOS environments.
  • Provide links to relevant Azure CLI documentation and REST API usage for source control integration.
  • Include troubleshooting tips for Linux/macOS users, such as handling authentication and secure string creation outside PowerShell.
  • Reorder examples so that platform-neutral or cross-platform methods (e.g., portal, REST API, Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/hybrid-runbook-worker.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Troubleshooting steps and examples for common issues are predominantly described for Windows environments, often using Windows-specific tools (PowerShell, registry edits, Windows event logs) and file paths. Windows scenarios and resolutions are frequently presented before Linux equivalents, and some workarounds (such as editing Orchestrator.Sandbox.exe.config) are only described for Windows. Linux troubleshooting is covered in a separate section, but with less detail and fewer example scripts. Some issues (e.g., updating Az modules, event log checks) lack Linux-specific guidance.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples for all major scenarios, especially those currently described only for Windows.
  • Include Linux command-line equivalents for PowerShell commands (e.g., systemctl/service commands for agent management).
  • Add guidance for Linux log locations and diagnostic tools analogous to Windows event logs.
  • Ensure parity in detail and coverage between Windows and Linux sections, including configuration file locations and update/upgrade caveats.
  • Where possible, present platform-agnostic troubleshooting steps before platform-specific ones.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation runbook issues ...blob/main/articles/automation/troubleshoot/runbooks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 use PowerShell cmdlets, with no Bash, CLI, or Linux/macOS-specific guidance. Troubleshooting steps and recommendations consistently reference Windows tools (PowerShell ISE, modules, cmdlets) and do not mention Linux or macOS equivalents. There are no examples or instructions for using Azure Automation runbooks with Bash, Python (except a brief mention of Python runbooks in one error), or cross-platform CLI tools. This creates friction for Linux/macOS users and those who prefer non-PowerShell environments.
Recommendations
  • Add equivalent troubleshooting examples for Bash, Azure CLI, and Python runbooks.
  • Include guidance for using Azure Automation from Linux/macOS environments, such as VS Code on Linux, Azure CLI, and shell scripting.
  • Provide parity in code samples, showing both PowerShell and CLI/Bash approaches where possible.
  • Mention cross-platform editors and tools (e.g., VS Code, Azure CLI) alongside PowerShell ISE.
  • Clarify which troubleshooting steps are applicable regardless of OS, and call out any Windows-specific limitations.
GitHub Create Pull Request
Automation What's New in Azure Automation .../azure-docs/blob/main/articles/automation/whats-new.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Automation 'What's New' shows a notable bias towards Windows and PowerShell. Most examples and feature announcements focus on PowerShell runbooks, with frequent mention of specific PowerShell versions and modules (e.g., AzureRM, Az). Windows terminology and tools are referenced more often and earlier than Linux equivalents. While Linux is sometimes mentioned (e.g., Hybrid Runbook Worker for Windows and Linux), there are few explicit Linux-focused examples, and Python support is discussed less frequently and with less detail. There are no clear Linux-specific usage patterns, troubleshooting, or examples provided.
Recommendations
  • Include Linux-specific examples and usage scenarios, especially for Python runbooks and shell scripting.
  • Ensure parity in documentation for both Windows and Linux, such as migration guides, troubleshooting, and feature announcements.
  • Present examples for both PowerShell and Bash (or other Linux shells) where applicable.
  • Avoid listing Windows/PowerShell features first; alternate or group by OS where possible.
  • Highlight Linux-specific tools, modules, and best practices for Azure Automation.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed PowerShell-based instructions for disabling a system-assigned managed identity, including use of Windows-specific cmdlets and authentication patterns. There are no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or Azure CLI), and the only programmatic example is Windows-centric. This creates friction for non-Windows users attempting to automate or script the process.
Recommendations
  • Add Linux/macOS-friendly examples using Bash and curl for the REST API PATCH request.
  • Include Azure CLI commands for authentication and REST API invocation, which work cross-platform.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell must be used, and provide compatible examples.
  • Present cross-platform examples before or alongside Windows-specific instructions.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-run-as-account.md ...blob/main/articles/automation/delete-run-as-account.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on deleting Azure Automation Run As accounts, mentioning PowerShell and the Azure portal as the primary methods. There is a notable absence of Linux-specific examples, such as using Azure CLI or Bash scripts, and the mention of PowerShell comes before any cross-platform alternatives. This indicates a Windows-first bias and a lack of Linux parity in the instructions.
Recommendations
  • Add examples using Azure CLI commands for deleting Run As accounts, which are cross-platform and commonly used on Linux.
  • Include Bash script snippets for automation tasks, where applicable.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, or clarify when instructions are Windows-specific.
  • Provide parity in tool recommendations, listing Azure CLI and Bash alternatives alongside PowerShell and Azure portal steps.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/runbook-authoring-extension-for-vscode.md ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing PowerShell modules as a prerequisite and omitting explicit Linux or cross-platform instructions. There are no examples or guidance for Linux users regarding Python package management, shell usage, or troubleshooting. The documentation assumes familiarity with Windows-centric tools and does not mention Linux-specific considerations, such as using Bash, installing Python packages via pip, or handling permissions.
Recommendations
  • Add explicit instructions and examples for Linux users, such as how to install Python packages using pip and manage dependencies.
  • Clarify that both PowerShell and Python are supported, and provide guidance for using Bash or other shells on Linux.
  • Include troubleshooting steps or notes for common Linux issues, such as file permissions or environment setup.
  • Mention cross-platform compatibility of the Azure Automation extension and highlight any differences in behavior or requirements between Windows and Linux.
  • Provide screenshots or terminal commands from Linux environments to ensure parity and inclusivity.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enforce-job-execution-hybrid-worker.md ...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell examples are consistently presented after CLI, and PowerShell is highlighted as a primary method for obtaining policy definition IDs. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users (such as shell scripting or references to Linux package managers). The CLI examples are platform-neutral, but the prominence and detail of PowerShell usage may imply a Windows-centric approach.
Recommendations
  • Explicitly state that Azure CLI commands work on both Windows and Linux/macOS platforms.
  • Add Bash shell script examples for Linux users, especially for file creation and command chaining.
  • Include notes or links about running Azure CLI in native Linux environments, such as Ubuntu or CentOS.
  • Mention installation instructions for Azure CLI and PowerShell on Linux, or link to cross-platform setup guides.
  • Balance the order of examples by sometimes presenting CLI/Bash first, or grouping examples by platform.
  • Clarify that PowerShell Core is cross-platform, and provide examples using pwsh on Linux/macOS if relevant.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-packages.md ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively providing instructions and examples for downloading Python packages and dependencies using Windows tools and paths (e.g., 'C:\Python27\Scripts\pip2.7.exe') and explicitly stating to use a Windows 64-bit machine. There are no equivalent instructions or examples for Linux or macOS users, nor is there mention of cross-platform alternatives.
Recommendations
  • Add equivalent instructions for Linux and macOS, such as using 'pip2.7 download -d <output dir> <package name>' in a bash shell.
  • Include examples with Linux file paths and commands (e.g., '/usr/bin/pip2.7').
  • Clarify that the process is not limited to Windows and provide guidance for users on other platforms.
  • Mention any platform-specific considerations (e.g., wheel compatibility, Python installation locations) for Linux/macOS.
  • Ensure screenshots and references do not imply Windows exclusivity unless truly required.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstart-create-automation-account-template.md ...ation/quickstart-create-automation-account-template.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned before Azure CLI when describing how to run the ARM template, and the error handling example is given first for PowerShell. The sample runbooks include a PowerShell runbook and a Python runbook, but no explicit Bash or Linux shell example. References to running the template from PowerShell are given before Azure CLI, and the instructions for specifying parameters use PowerShell syntax first.
Recommendations
  • Present Azure CLI and PowerShell instructions in parallel, or list Azure CLI first to avoid Windows-first ordering.
  • Add explicit Bash or Linux shell runbook examples alongside PowerShell and Python.
  • Ensure error messages and troubleshooting steps include both PowerShell and Azure CLI examples, with equal prominence.
  • Reference Linux tools and workflows where appropriate, such as running ARM templates from Bash or other Linux shells.
  • Clarify that both Windows and Linux users can follow the steps, and provide links to platform-specific guidance if needed.
GitHub Create Pull Request
Automation https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-terraform.md ...ickstarts/create-azure-automation-account-terraform.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence despite being Windows-centric. The 'Next steps' section specifically links to a PowerShell runbook tutorial, reinforcing a Windows/PowerShell bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux tools or patterns. The initial instructions and Terraform usage are platform-neutral, but verification and follow-up content lean toward Windows/PowerShell.
Recommendations
  • Add explicit Bash/Linux shell examples for verification steps alongside Azure CLI and PowerShell.
  • Include links to tutorials for creating Automation runbooks using Python or Bash, not just PowerShell.
  • Clarify that Azure CLI commands work cross-platform and highlight usage on Linux/macOS.
  • Balance 'Next steps' by featuring non-PowerShell runbook options.
  • Mention Linux compatibility in the prerequisites and throughout the guide.
GitHub Create Pull Request
Automation Enforce job execution on Azure Automation Hybrid Runbook Worker ...cles/automation/enforce-job-execution-hybrid-worker.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell (a Windows-centric tool) is given equal prominence and is described in detail. There is a slight 'Windows first' bias in that PowerShell is presented as a primary option, and some explanatory details (such as resource ID retrieval) are shown only for PowerShell. No Linux/macOS-specific issues are present, but the documentation assumes familiarity with PowerShell, which is less common on non-Windows platforms.
Recommendations
  • Ensure all command examples are fully covered for Azure CLI, which is cross-platform, and clarify that Azure CLI works natively on Linux/macOS.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Where PowerShell-specific instructions are given (e.g., retrieving ResourceId), provide equivalent Azure CLI commands.
  • Explicitly state that both Azure CLI and PowerShell are supported on all platforms, and recommend Azure CLI for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell to reduce perceived Windows bias.
GitHub Create Pull Request
Automation Forward Azure Automation job data to Azure Monitor logs ...mation/automation-manage-send-joblogs-log-analytics.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias, primarily through the use of PowerShell as the only mentioned CLI tool for interacting with job logs, and by referencing Windows-centric patterns (PowerShell error streams) when discussing job errors. There are no explicit Linux/macOS CLI examples (e.g., Azure CLI, Bash), nor is there mention of cross-platform alternatives for querying or automating these tasks outside of the Azure Portal and PowerShell. However, the majority of the instructions are portal-based and platform-agnostic, and the core log querying uses Kusto Query Language (KQL), which is not platform-specific.
Recommendations
  • Add examples using Azure CLI (az) for querying job logs and managing diagnostic settings, alongside PowerShell.
  • Explicitly mention that all portal-based steps are platform-agnostic and accessible from any OS.
  • Where PowerShell is referenced (e.g., error streams), clarify how equivalent behavior or output can be obtained when using Bash or Python runbooks.
  • Provide links or references to cross-platform automation and scripting documentation for Azure Automation.
GitHub Create Pull Request
Automation Azure Automation Hybrid Runbook Worker Overview ...rticles/automation/automation-hybrid-runbook-worker.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, explicitly stating support for both platforms in most sections. However, there are subtle signs of Windows bias: PowerShell is mentioned as a primary onboarding channel before alternatives, and references to runbook job restarts specifically mention 'PowerShell Workflow runbooks' (which are Windows-centric). Windows terminology (e.g., 'System account') is used first, with Linux equivalents mentioned second. No Linux/macOS-specific examples, tools, or troubleshooting are provided, and onboarding instructions link to a combined Windows/Linux page without previewing Linux-specific steps.
Recommendations
  • Provide explicit Linux/macOS examples and troubleshooting steps, especially for onboarding and runbook execution.
  • Mention Linux tools and patterns (e.g., Bash, shell scripts) alongside PowerShell, and avoid listing PowerShell first unless contextually necessary.
  • Clarify differences in runbook execution and permissions between Windows and Linux (e.g., differences in local accounts, service management).
  • Ensure that all references to onboarding, management, and troubleshooting equally highlight Linux/macOS workflows.
  • Consider adding a dedicated section or callouts for Linux/macOS users where platform-specific behavior or requirements exist.
GitHub Create Pull Request
Automation Create an Azure Automation account using a Resource Manager template ...ation/quickstart-create-automation-account-template.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is mentioned first and in more detail. The error handling and parameter instructions reference PowerShell before Azure CLI, and the example parameter syntax is shown for PowerShell first. There are no Linux-specific tools or shell examples (e.g., Bash), and the documentation does not mention platform differences or considerations for Linux/macOS users.
Recommendations
  • Present Azure CLI (cross-platform) instructions before PowerShell, or in parallel, to avoid Windows-first bias.
  • Include explicit Bash examples for Linux/macOS users where command-line deployment is discussed.
  • Clarify that both PowerShell and Azure CLI are available on all platforms, and link to installation guides for Linux/macOS.
  • Add a note about platform neutrality of the ARM template deployment process.
  • Ensure error messages and troubleshooting steps reference both PowerShell and Azure CLI equally.
GitHub Create Pull Request
Automation Quickstart: Use Terraform to create an Azure Automation account ...ickstarts/create-azure-automation-account-terraform.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but PowerShell is given equal prominence and is referenced in the 'Next steps' section. The final tutorial link specifically highlights PowerShell runbooks, which are Windows-centric, without mentioning Linux or Python alternatives. No Linux-specific tools or shell examples are provided, though the Azure CLI is cross-platform.
Recommendations
  • Add explicit Bash/Linux shell examples for verification steps, showing usage in native Linux/macOS environments.
  • Mention that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific notes.
  • In the 'Next steps' section, include links to tutorials for creating Python runbooks or using Linux-based automation, not just PowerShell.
  • Clarify that PowerShell is available cross-platform, but also highlight alternatives for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 14 of 15 Next →