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 926-950 of 982 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-13 00:00
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 first or exclusively in several sections, especially for Python 3.8. Instructions for generating wheel files for Python 3.8 are only provided for Windows, while Linux instructions are only given for Python 3.10. The PowerShell cmdlets for managing Python packages are shown without mention of Linux/macOS CLI alternatives. There is little guidance for Linux/macOS users managing Python 3.8 packages or using non-Windows tooling.
Recommendations
  • Add Linux/macOS instructions for generating wheel files for Python 3.8 packages, mirroring the Windows steps.
  • Provide CLI or cross-platform alternatives to PowerShell cmdlets for managing Python packages, such as Azure CLI or REST API examples.
  • Present examples for both Windows and Linux/macOS environments side-by-side, especially in sections where OS-specific steps are required.
  • Explicitly state OS requirements and limitations for each step, and link to platform-specific guidance where available.
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 00:00
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 packages and dependencies only on Windows, with no equivalent Linux/macOS guidance. The primary example for manual package download uses Windows paths and tools, and there is no mention of how to perform the same task on Linux or macOS systems.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using 'pip' or 'python2.7 -m pip' on those platforms.
  • Include sample commands for downloading packages and dependencies on Linux/macOS, e.g., 'pip2 download -d <output dir> <package name>'.
  • Clarify that the process is not limited to Windows and provide cross-platform guidance.
  • Consider listing both Windows and Linux/macOS instructions side-by-side for parity.
GitHub Create Pull Request
Automation Quickstart - Enable managed identities for your Automation account using the Azure portal ...cles/automation/quickstarts/enable-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is focused exclusively on using the Azure portal UI, which is cross-platform, but the only next step provided is a PowerShell runbook tutorial. This suggests a bias towards Windows and PowerShell users, as Linux/macOS users may prefer Bash or Python runbooks. There are no CLI or code-based examples (e.g., Azure CLI, REST API), and PowerShell is mentioned as the default automation language, reinforcing Windows-first patterns.
Recommendations
  • Add links to tutorials for Bash and Python runbooks using managed identity, not just PowerShell.
  • Include examples for enabling managed identities using Azure CLI and/or REST API for users who prefer command-line or automation approaches.
  • Ensure that references to automation languages and tools are presented in a neutral order (e.g., 'PowerShell, Bash, or Python').
  • Explicitly mention that the Azure portal is accessible from any OS and clarify that the steps are not Windows-specific.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, with a strong emphasis on PowerShell-based examples, Windows-centric tools, and patterns. PowerShell is presented as the primary runbook language, with detailed parameter configuration and usage examples. Linux/macOS alternatives (such as Bash, CLI, or Python) are minimally covered, and when present, lack parity in depth and practical examples. Windows tools and terminology (e.g., PowerShell cmdlets, .NET types, screenshots of Windows UI) are used exclusively or before any Linux equivalents. There are no examples showing how to start runbooks or pass parameters using Bash, Azure CLI, or from Linux/macOS environments.
Recommendations
  • Add equivalent Azure CLI and Bash examples for starting runbooks and passing parameters, especially for Linux/macOS users.
  • Provide Python runbook parameter examples with real-world scenarios, matching the detail given to PowerShell.
  • Include screenshots and instructions for Linux/macOS environments where applicable (e.g., terminal usage, file paths).
  • Clarify cross-platform compatibility for PowerShell commands and note any differences in behavior on Linux/macOS.
  • List Linux/macOS tools and patterns alongside Windows tools, not just after or as an afterthought.
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 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 is heavily focused on Windows PowerShell and related cmdlets for credential management in Azure Automation. All CLI examples are PowerShell-based, and Windows tools (e.g., PSCredential, Get-Credential) are referenced exclusively. There are no Bash, Azure CLI, or Linux-native scripting examples for credential asset management. The Python section is present but limited to runbook usage, not asset creation or management. The instructions for creating credentials outside the portal are Windows PowerShell-only, with no Linux/macOS alternatives.
Recommendations
  • Add equivalent examples using Azure CLI for credential asset creation and management.
  • Include Bash or shell script examples for Linux/macOS users where possible.
  • Clarify which steps are platform-agnostic (e.g., Azure portal) and which are Windows-specific.
  • Provide guidance on how Linux/macOS users can interact with Azure Automation credentials outside of PowerShell.
  • Expand Python examples to cover asset creation and management, not just retrieval.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is emphasized as the primary scripting language, with multiple runtime versions listed and discussed in detail. Azure CLI is only mentioned as a default package within PowerShell 7.4 environments, with no reference to its use in Python or other Linux-friendly contexts. Examples and references are exclusively Windows-centric (PowerShell, .dll files, PSGallery), and Linux/macOS equivalents (e.g., Bash, shell scripting, Linux package management, Python modules) are not mentioned or exemplified. There are no Linux/macOS-specific instructions or parity in tooling or workflow.
Recommendations
  • Include examples and guidance for Python runbooks, especially for Azure CLI usage in Python environments.
  • Mention and provide examples for Bash/shell scripting where applicable.
  • Clarify how Linux/macOS users can leverage Azure Automation, including package management (e.g., pip for Python) and runtime configuration.
  • List Linux/macOS equivalents alongside Windows tools (e.g., .dll files vs. .so files, PSGallery vs. PyPI).
  • Ensure documentation references and links include Python and Linux/macOS resources, not just PowerShell.
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 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 is heavily focused on PowerShell and Windows-centric tools, such as PowerShell cmdlets and Windows certificate providers. All code examples for certificate creation and management use PowerShell, with no Linux shell or cross-platform CLI equivalents. Windows tools and patterns (e.g., PowerShell, .pfx files, Microsoft Enhanced RSA and AES Cryptographic Provider) are mentioned exclusively or before any Linux alternatives. There are no examples or guidance for Linux/macOS users on how to create or upload certificates using Bash, Azure CLI, or OpenSSL.
Recommendations
  • Add equivalent examples using Azure CLI (az) for certificate management tasks.
  • Provide Linux/macOS shell (bash) examples for certificate creation and upload, using OpenSSL and az commands.
  • Clarify cross-platform compatibility of certificate formats and providers, and note any platform-specific requirements.
  • Mention and link to Linux/macOS documentation for certificate management in Azure Automation.
  • Reorder examples to present cross-platform or neutral options first, or provide parallel examples for each platform.
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples for command-line operations, referencing only Windows-centric tools and patterns, and omitting equivalent instructions for Linux/macOS users (e.g., Azure CLI, Bash). PowerShell cmdlets are presented as the primary automation method, with no mention of cross-platform alternatives, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script examples where appropriate, especially for ARM template deployments and schedule management.
  • Explicitly state PowerShell Core (pwsh) compatibility for Linux/macOS, or provide installation guidance if PowerShell is required.
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Reference Linux/macOS-specific considerations, such as file paths, shell environments, and authentication methods.
GitHub Create Pull Request
Automation Remove DSC and node from Automation State Configuration ...configuration/remove-node-and-configuration-package.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell-based instructions and tools are presented first and in more detail, with explicit cmdlet references for Windows, while Linux instructions are less detailed and rely on manual file deletion or package removal. Windows tooling (PowerShell cmdlets) is mentioned before Linux equivalents, and Linux steps are less integrated into the workflow.
Recommendations
  • Provide equivalent Linux command-line examples for unregistering nodes (e.g., using Azure CLI or REST API, if available).
  • Include Linux-specific automation or scripting examples, not just manual file deletion.
  • Present Windows and Linux instructions side-by-side or in parallel tabs, rather than Windows first.
  • Reference Linux management tools (such as Azure CLI) where possible, not just PowerShell.
  • Clarify any differences in process or tooling between platforms, and ensure Linux users have clear, actionable steps.
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 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 modules and cmdlets, with nearly all examples, instructions, and tooling centered around Windows PowerShell and the Az/AzureRM modules. Windows-specific features (such as internal cmdlets and the Orchestrator.AssetManagement.Cmdlets module) are described in detail, while Linux support is only briefly mentioned, often as a limitation or exclusion. There are no Linux or cross-platform CLI examples, and Linux users are repeatedly reminded of missing functionality (e.g., internal cmdlets not available on Linux Hybrid Runbook Workers). The documentation assumes a Windows-centric workflow and does not provide parity for Linux/macOS users.
Recommendations
  • Add equivalent examples and instructions for Linux/macOS environments, such as using Azure CLI or Python modules where possible.
  • Clearly indicate which features are Windows-only and provide alternative workflows for Linux users.
  • Include Linux Hybrid Runbook Worker usage patterns and troubleshooting steps.
  • Provide cross-platform module management guidance, including Python and bash examples for module import and management.
  • Reorder sections to avoid always presenting Windows/PowerShell options first; consider parallel presentation of Windows and Linux approaches.
GitHub Create Pull Request
Automation Manage variables in Azure Automation ...main/articles/automation/shared-resources/variables.md
Medium Priority View Details →
Scanned: 2026-01-13 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 demonstrates a notable Windows bias. PowerShell and Windows-specific cmdlets (Az modules, internal cmdlets) are referenced and exemplified throughout, with no mention of Linux shell equivalents or cross-platform CLI usage. All scripting examples outside Python are PowerShell-based, and the guidance for complex variable types and management is exclusively tied to Windows PowerShell. There are no Bash, Azure CLI, or Linux-native examples, and Windows terminology is used as the default context.
Recommendations
  • Add examples using Azure CLI for variable management, which is cross-platform and works on Linux/macOS.
  • Include Bash or shell script samples for common variable operations, especially for Linux Hybrid Runbook Workers.
  • Clarify which features and cmdlets are available on Linux/macOS, and note any platform-specific limitations.
  • Present examples in a platform-neutral order (e.g., Azure portal, Azure CLI, PowerShell, Python) rather than Windows-first.
  • Explicitly mention Linux/macOS compatibility for runbooks and DSC configurations where relevant.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation State Configuration issues ...automation/troubleshoot/desired-state-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Most troubleshooting steps, examples, and cmdlets are PowerShell-centric, with instructions and tooling (e.g., xDscDiagnostics, PowerShell DSC extension, Windows event logs, Windows time sync commands) tailored for Windows environments. Linux-specific guidance is minimal and appears only in one scenario, with no parity in diagnostic tooling or example commands. Windows instructions and tools are presented first and in greater detail, while Linux users are often left to infer or seek external resources.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples for each scenario, including shell commands and log locations.
  • Document Linux-specific DSC extension management and certificate handling, with sample commands (e.g., using bash, systemctl, openssl).
  • Include references to Linux DSC logs and diagnostic tools, or clarify limitations and alternatives for Linux users.
  • When mentioning PowerShell cmdlets or Windows tools, add Linux alternatives or note platform applicability.
  • Balance the order of presentation so Linux and Windows instructions are given equal prominence.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Troubleshooting steps and examples are frequently presented for Windows first, with PowerShell commands and Windows-specific tools (e.g., registry edits, event logs) featured prominently. Several scenarios provide detailed Windows instructions (including file paths, config edits, and PowerShell scripts) but lack equivalent detail or examples for Linux. Linux troubleshooting is covered in a separate section, but often with less depth and fewer concrete examples. In some cases, only Windows solutions or references are given, or Windows tools are mentioned before their Linux equivalents.
Recommendations
  • Ensure that every troubleshooting scenario includes both Windows and Linux instructions/examples where applicable.
  • Provide Linux equivalents for Windows-specific tools (e.g., event logs, registry edits), such as relevant log file locations, commands, or configuration steps.
  • Present Windows and Linux troubleshooting steps in parallel, rather than grouping all Windows content before Linux.
  • Include Linux shell commands and file paths alongside PowerShell examples.
  • Expand Linux troubleshooting sections to match the detail and specificity of Windows sections, including example error messages, commands, and config file edits.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux for most troubleshooting steps, including file paths, log locations, and extension management. However, there is a consistent pattern of presenting Windows examples, tools, and troubleshooting steps before Linux equivalents. Several scenarios (such as registry and event log troubleshooting, and PowerShell-based remediation) are Windows-specific, with no Linux analogs or guidance. Some advanced troubleshooting (e.g., registry edits, event log checks, .NET errors) is only described for Windows, leaving Linux users without equivalent instructions.
Recommendations
  • Alternate the order of Windows and Linux instructions or present them in parallel to avoid implicit prioritization.
  • Where Windows-specific tools (like PowerShell scripts or registry edits) are mentioned, provide Linux equivalents or explicitly state if not applicable.
  • For event log and error code troubleshooting, include Linux log file locations and example commands (e.g., journalctl, syslog) for similar diagnostics.
  • Ensure that all scenarios (especially those with detailed Windows steps) have Linux guidance or a note explaining differences/limitations.
  • Highlight OS-specific differences clearly, so Linux/macOS users know when a step is not relevant or requires a different approach.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation runbook issues ...blob/main/articles/automation/troubleshoot/runbooks.md
Medium Priority View Details →
Scanned: 2026-01-13 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 is heavily focused on PowerShell-based troubleshooting and examples, which are most relevant to Windows environments. All code samples and troubleshooting steps use PowerShell cmdlets, with no Bash, CLI, or Linux/macOS-specific examples. Windows-centric tools and patterns (e.g., PowerShell ISE, Windows Management Instrumentation, Windows Installer service) are referenced, and troubleshooting steps assume familiarity with Windows/PowerShell workflows. There is no mention of Linux/macOS equivalents or cross-platform usage, even though Azure Automation supports Python runbooks and Hybrid Runbook Workers can run on Linux.
Recommendations
  • Add troubleshooting examples for Python runbooks, including common errors and diagnostic steps for Python on Linux/macOS.
  • Include Azure CLI or Bash examples alongside PowerShell, especially for tasks like authentication, module management, and job monitoring.
  • Clarify which troubleshooting steps apply to Linux/macOS Hybrid Runbook Workers and provide platform-specific guidance where necessary.
  • Reference cross-platform editors (e.g., VS Code) and avoid exclusive mention of Windows tools like PowerShell ISE.
  • Explicitly state platform requirements and limitations for each scenario (e.g., which errors are Windows-specific, which apply to Linux/macOS).
GitHub Create Pull Request
Automation Azure Automation extension for Visual Studio Code ...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page for the Azure Automation extension for Visual Studio Code shows a bias towards Windows environments by referencing PowerShell modules as a prerequisite and not providing equivalent Linux or cross-platform guidance. There are no examples or instructions for Linux-specific tools, shell environments, or package management, and the documentation assumes PowerShell is the default scripting language and runtime for local testing, which is more common on Windows.
Recommendations
  • Include explicit instructions for installing and using the extension on Linux and macOS, such as verifying compatibility and any required dependencies.
  • Add examples for using Python runbooks, including guidance on installing Python and required packages on Linux/macOS.
  • Clarify whether Bash or other shell scripts are supported and provide examples if so.
  • Mention cross-platform PowerShell (PowerShell Core) and provide installation steps for Linux/macOS.
  • List any platform-specific limitations or differences in the extension's behavior.
  • Ensure screenshots and UI references are not Windows-specific, or provide alternatives for other platforms.
GitHub Create Pull Request
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally maintains cross-platform awareness, mentioning both Windows and Linux Hybrid Runbook Workers. However, in the section describing how a Hybrid Runbook Worker selects the Python interpreter, only Windows-specific environment variables and paths (e.g., C:\Python2\python.exe) are described in detail, with no equivalent Linux example or explanation. This prioritizes Windows usage and omits Linux-specific guidance, which may hinder Linux users.
Recommendations
  • Add explicit Linux examples for environment variable configuration and Python interpreter path resolution (e.g., describe use of /usr/bin/python3 and relevant environment variables on Linux).
  • Include Linux-specific troubleshooting steps or notes where Windows-specific instructions are given.
  • Ensure that all platform-specific instructions are presented in parallel, with equal detail for both Windows and Linux.
  • Review other sections for subtle Windows-first phrasing and update to present both platforms with parity.
GitHub Create Pull Request
Automation Forward Azure Automation job data to Azure Monitor logs ...mation/automation-manage-send-joblogs-log-analytics.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. It references PowerShell as the tool for viewing individual job logs and mentions PowerShell error streams when discussing job errors. There are no explicit Linux or cross-platform CLI examples, nor is there mention of Linux-specific tools or shell environments. The documentation assumes familiarity with PowerShell concepts and does not provide parity for Linux users (e.g., Bash, CLI, or cross-platform scripting).
Recommendations
  • Add explicit references to cross-platform tools such as Azure CLI and Bash where applicable, especially for querying or automating tasks.
  • Provide examples for viewing job logs and streams using Azure CLI or REST API, not just PowerShell.
  • Clarify that Azure Automation and Azure Monitor log querying is platform-agnostic and can be performed from any OS using supported tools.
  • When discussing error streams, mention how non-terminating errors are handled in Bash or other Linux scripting environments, if relevant.
  • Ensure that introductory sections do not imply PowerShell is the only or primary method for interacting with Azure Automation logs.
GitHub Create Pull Request
Automation Enforce job execution on Azure Automation Hybrid Runbook Worker ...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 examples are presented with equal prominence and detail as CLI, and PowerShell is mentioned first in the introductory text. There are no Linux-specific shell examples (e.g., Bash) or references to Linux-native tooling, and the documentation does not clarify cross-platform usage of Azure CLI or PowerShell. The examples and instructions assume familiarity with PowerShell, which is traditionally Windows-centric, and do not address Linux-specific considerations for Hybrid Runbook Workers.
Recommendations
  • Explicitly state that Azure CLI and Azure PowerShell are cross-platform and provide guidance for running commands on Linux, macOS, and Windows.
  • Add Bash shell examples for Azure CLI usage to demonstrate Linux-native workflows.
  • Clarify any platform-specific prerequisites or differences for Hybrid Runbook Worker configuration and policy assignment.
  • Ensure that introductory text and example ordering do not prioritize Windows/PowerShell over Linux/Bash; alternate the order or provide a neutral introduction.
  • Mention that Azure PowerShell can be installed and used on Linux and macOS, and provide installation links or references.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing package download instructions exclusively for Windows (using a Windows 64-bit machine and referencing C:\Python27\Scripts), with no equivalent guidance for Linux or macOS users. There are no Linux-specific examples, commands, or tools mentioned, and Windows is presented as the default platform for offline package management.
Recommendations
  • Add equivalent instructions for downloading Python 2 packages and dependencies on Linux and macOS, using standard Python and pip commands.
  • Provide example commands for Linux (e.g., using 'pip download' in a bash shell) alongside Windows examples.
  • Clarify that the process is cross-platform and specify any platform-specific considerations.
  • Include screenshots or terminal outputs from Linux environments where appropriate.
  • Avoid presenting Windows as the default or only supported platform for package management tasks.
GitHub Create Pull Request
Automation Archive for What's new in Azure Automation ...ocs/blob/main/articles/automation/whats-new-archive.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page generally maintains cross-platform parity, mentioning both Windows and Linux support for Azure Automation features. However, there are subtle signs of Windows bias: Windows-specific tools and scripts (e.g., PowerShell Gallery, Az modules, Windows HybridWorker) are referenced by name, sometimes before or more prominently than their Linux equivalents. Windows operating system support is called out in dedicated sections, while Linux support is often grouped or referenced as an afterthought. The onboarding script update and runbook examples tend to highlight Windows/PowerShell tools first.
Recommendations
  • Ensure Linux examples and tools are mentioned with equal prominence and detail as Windows equivalents.
  • When referencing scripts or onboarding processes, present both Windows and Linux options side-by-side, rather than listing Windows first.
  • Include explicit Linux command-line examples (e.g., bash, shell scripts) where PowerShell or Windows tools are mentioned.
  • Highlight Linux-specific features, troubleshooting, and best practices in dedicated sections, not just as grouped mentions.
  • Review headings and ordering to avoid consistently listing Windows before Linux.
GitHub Create Pull Request
Automation Archive for What's new in Azure Automation ...ocs/blob/main/articles/automation/whats-new-archive.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally maintains cross-platform coverage, mentioning both Windows and Linux in several features and updates. However, there are subtle signs of Windows bias: Windows-specific tools and scripts (e.g., PowerShell Gallery, Windows HybridWorker scripts) are referenced by name and sometimes appear before Linux equivalents. Windows operating systems and modules (e.g., Az modules, Windows Server 2008 R2) are called out in feature updates, while Linux coverage is often grouped or referenced generically. Some script/tool names are Windows-centric, and PowerShell modules are mentioned without Linux CLI alternatives.
Recommendations
  • Ensure that Linux examples, tools, and scripts are mentioned with equal prominence and specificity as Windows equivalents.
  • When referencing scripts or onboarding tools, provide explicit Linux CLI or shell script alternatives alongside PowerShell/Windows versions.
  • Avoid naming conventions that prioritize Windows (e.g., 'Create Automation Windows HybridWorker') and use neutral or parallel naming for Linux scripts.
  • Include links to Linux-specific documentation, repositories, and modules where possible.
  • When mentioning supported operating systems, list Linux and Windows in parallel rather than grouping Linux generically or after Windows.
  • Where PowerShell modules are referenced, also mention Azure CLI or bash alternatives for Linux users.
GitHub Create Pull Request
Automation Azure Automation FAQ ...e-docs/blob/main/articles/automation/automation-faq.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally maintains platform neutrality, but in the section describing how a Hybrid Runbook Worker chooses the Python interpreter, only Windows-specific environment variables and file paths (e.g., C:\Python2\python.exe) are described in detail. There is no equivalent example or explanation for Linux Hybrid Runbook Workers, even though Linux is mentioned elsewhere. This may cause confusion for Linux users and suggests a subtle Windows-first bias.
Recommendations
  • Add explicit examples and explanations for Linux Hybrid Runbook Workers, such as how environment variables (e.g., PYTHON_2_PATH, PYTHON_3_PATH) should be set and validated on Linux (e.g., /usr/bin/python2, /usr/bin/python3).
  • Include Linux file path examples alongside Windows examples when discussing interpreter discovery.
  • Clarify any differences in environment variable handling or path validation between Windows and Linux Hybrid Runbook Workers.
  • Review other sections for similar patterns and ensure Linux parity in all technical explanations and examples.
GitHub Create Pull Request
Automation Enforce job execution on Azure Automation Hybrid Runbook Worker ...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 is given equal or slightly greater prominence (dedicated sections, parameter explanations, and example variable usage). There are no Linux-specific shell examples (e.g., Bash scripts), and the use of PowerShell may implicitly favor Windows users, as PowerShell is natively available on Windows and only optionally installed on Linux. The documentation does not mention Linux-specific tools, nor does it clarify cross-platform usage for PowerShell or CLI commands.
Recommendations
  • Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide guidance for installing and using PowerShell on Linux if needed.
  • Add Bash shell script examples for policy creation and assignment using Azure CLI to demonstrate Linux parity.
  • Clarify that Azure CLI commands can be run from any OS, and provide instructions for installing Azure CLI on Linux.
  • Avoid using variable assignment and resource retrieval examples that are PowerShell-specific unless a Linux shell equivalent is also provided.
  • Consider adding a section or note about platform compatibility for all command-line tools mentioned.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing explicit instructions and command-line examples only for Windows environments (e.g., using a Windows 64-bit machine and referencing C:\Python27\Scripts\pip2.7.exe), with no equivalent Linux instructions or examples. This may disadvantage users on Linux or macOS platforms who need to perform similar package management tasks.
Recommendations
  • Add Linux and macOS instructions for downloading Python packages and dependencies, such as using 'pip download' in a bash shell.
  • Provide command-line examples for Linux (e.g., 'pip2 download -d <output dir> <package name>') and clarify any differences in file paths or environment setup.
  • Mention cross-platform compatibility considerations and tools where relevant.
  • Ensure screenshots and references do not imply Windows exclusivity unless required by Azure Automation constraints.
GitHub Create Pull Request
← Previous Page 38 of 40 Next →