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 276-300 of 982 flagged pages
Automation
Azure Quickstart - Install Hybrid Worker extension on Azure portal.
...omation/quickstarts/install-hybrid-worker-extension.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension selection refer only to 'Azure Automation Windows Hybrid Worker', with no mention or example for Linux VMs. The prerequisites specifically require a Windows VM, and there is no guidance or illustration for Linux equivalents, despite the initial claim that both Windows and Linux are supported.
Recommendations
- Add parallel instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
- Update the prerequisites to include Linux VM requirements and considerations.
- Explicitly mention and show the selection of the Linux Hybrid Worker extension in the Azure portal, if available.
- Provide examples or notes on any differences in configuration or operation for Linux VMs.
- Ensure that references to Windows tools or extensions are balanced with Linux equivalents throughout the documentation.
Create Pull Request
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias, primarily focusing on PowerShell and Windows-centric tools and patterns. All code examples, parameter definitions, and automation scenarios use PowerShell, PowerShell Workflow, or graphical runbooks (which are also PowerShell-based). There is minimal coverage of Python runbooks, and no mention or examples of Bash, Linux shell scripts, or Linux-native tools. The instructions for passing parameters, starting runbooks, and handling JSON objects are exclusively shown using PowerShell and Windows tools, with no Linux equivalents or cross-platform alternatives provided.
Recommendations
- Add equivalent examples for Bash or Linux shell scripts, showing how to start runbooks and pass parameters using Azure CLI or REST API from a Linux environment.
- Include instructions and code snippets for using Azure CLI (az automation runbook start ...) on Linux/macOS, alongside PowerShell examples.
- Provide Python runbook examples that demonstrate parameter passing and automation scenarios, not just a brief mention.
- Explicitly mention cross-platform compatibility and highlight any differences or limitations when using Linux/macOS tools.
- Where PowerShell is referenced, clarify if PowerShell Core (pwsh) on Linux/macOS is supported and provide examples.
- Add a section comparing Windows and Linux approaches to Azure Automation, including tooling, scripting, and parameter handling.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by focusing almost exclusively on PowerShell cmdlets and workflows, which are native to Windows environments. All detailed examples for certificate management use PowerShell, and Windows-specific tools like Add-AzureCertificate are mentioned without Linux equivalents. There are no examples or guidance for managing certificates using Linux-native tools, Bash, or CLI, and PowerShell is presented as the primary or default method throughout the document. Python examples are included, but only in the context of Azure Automation runbooks, not for general certificate management. No Linux shell or cross-platform CLI examples are provided.
Recommendations
- Add equivalent examples using Azure CLI and Bash for certificate management tasks, such as uploading, retrieving, and deleting certificates.
- Include references to Linux-native tools (e.g., OpenSSL) for certificate creation and manipulation, and show how they can be integrated with Azure Automation.
- Present cross-platform workflows first, or in parallel with PowerShell, to avoid implying PowerShell is the only or preferred method.
- Document any platform-specific limitations or differences, and provide guidance for Linux/macOS users.
- Expand the 'Create a new certificate' section to show how certificates can be generated and uploaded from Linux systems.
- Ensure that all major steps (creation, retrieval, deployment) have both Windows/PowerShell and Linux/Bash/Azure CLI examples.
Automation
Manage schedules in Azure Automation
...main/articles/automation/shared-resources/schedules.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell cmdlets and examples for command-line operations. There are no Bash, Azure CLI, or Linux-native examples provided, and PowerShell is presented as the primary automation tool for scripting and schedule management. The documentation does not mention or prioritize Linux tools or cross-platform alternatives, and all scripting instructions assume a Windows/PowerShell environment.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlet operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples for common scheduling tasks, demonstrating how Linux users can interact with Azure Automation.
- Explicitly mention that PowerShell Core is available cross-platform, but clarify any differences or limitations when running on Linux/macOS.
- Provide guidance or links for installing and using Az PowerShell modules on Linux and macOS, if PowerShell is required.
- Where possible, use neutral terminology such as 'command-line' instead of 'PowerShell' when describing scripting options, and present both Windows and Linux approaches side-by-side.
- Highlight any platform-specific considerations (e.g., timezone handling, authentication) that may differ between Windows and Linux environments.
Automation
Manage variables in Azure Automation
...main/articles/automation/shared-resources/variables.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by centering examples and instructions around Windows PowerShell and PowerShell cmdlets. Windows tools and terminology (e.g., PowerShell, Hybrid Runbook Worker) are mentioned exclusively or before alternatives. There is no mention of Linux shell (bash), CLI, or Linux-specific workflows, and no examples are provided for managing variables using Linux-native tools or environments. The documentation assumes the use of Windows-centric patterns and omits Linux parity in both conceptual and practical guidance.
Recommendations
- Add examples for managing Azure Automation variables using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
- Include bash shell script examples for interacting with Azure Automation variables, especially for Linux Hybrid Runbook Workers.
- Clarify which features and cmdlets are available or supported on Linux-based Hybrid Runbook Workers, and note any limitations or differences.
- Reorder sections so that platform-neutral or cross-platform methods (e.g., Azure portal, Azure CLI, REST API) are presented before Windows-specific tools.
- Explicitly mention Linux support and provide guidance for Linux users, including troubleshooting and best practices.
- Add notes or tables comparing Windows and Linux approaches for variable management in Azure Automation.
Automation
Start a runbook in Azure Automation
...e-docs/blob/main/articles/automation/start-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing examples and instructions for Windows PowerShell, referencing Windows-specific tools and cmdlets, and omitting any Linux or cross-platform CLI (such as Azure CLI or Bash) equivalents. The order of presentation also places Windows PowerShell before more platform-neutral options. There are no examples or guidance for starting runbooks from Linux environments or using non-Windows automation tools.
Recommendations
- Add equivalent examples using Azure CLI (az automation runbook start ...) for Linux/macOS users.
- Include Bash or shell script samples for interacting with Azure Automation via REST API.
- Clarify that PowerShell Core is cross-platform and provide examples for running on Linux/macOS, if applicable.
- Reorder sections to present platform-neutral methods (API, CLI) before Windows-specific tools.
- Explicitly mention Linux support and provide troubleshooting or setup guidance for non-Windows environments.
Automation
Troubleshoot Azure Automation State Configuration issues
...automation/troubleshoot/desired-state-configuration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias. Most troubleshooting steps, examples, and tool references are centered around PowerShell DSC and Windows-specific commands, such as PowerShell cmdlets and Windows event logs. Windows tools (e.g., xDscDiagnostics, w32tm) and patterns are mentioned exclusively or before Linux equivalents. Linux troubleshooting is only briefly addressed in a single scenario, with no Linux-specific commands, logs, or diagnostic tools provided. There is a lack of parity in examples and guidance for Linux users.
Recommendations
- Add Linux-specific troubleshooting steps and examples for each scenario, including relevant shell commands and log locations.
- Reference Linux DSC agent logs and provide guidance on how to collect and interpret them.
- Include Linux equivalents for PowerShell cmdlets (e.g., using shell scripts or DSC agent commands on Linux).
- Mention Linux tools and patterns alongside Windows tools, not only in a separate scenario.
- Ensure that guidance for module management, certificate handling, and network troubleshooting includes Linux instructions.
- Provide parity in onboarding, registration, and error resolution steps for both Windows and Linux nodes.
Automation
Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation
.../troubleshoot/extension-based-hybrid-runbook-worker.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In most troubleshooting steps and scenarios, Windows instructions, paths, and tools (especially PowerShell scripts and registry edits) are presented first or in greater detail. Windows-specific tools and patterns (e.g., PowerShell scripts, registry manipulation, event logs) are emphasized, while Linux equivalents are sometimes less detailed or missing (e.g., no Linux event log guidance, less explanation of Linux troubleshooting tools). Some scenarios are exclusively Windows-focused, with no Linux counterpart or guidance.
Recommendations
- Alternate the order of Windows and Linux instructions to avoid consistently presenting Windows first.
- Ensure Linux troubleshooting steps are as detailed as Windows ones, including explanations of Linux-specific logs, permissions, and troubleshooting tools.
- Provide Linux equivalents for Windows-only tools (e.g., PowerShell scripts), such as Bash or Python scripts for Linux.
- Include guidance for Linux event log analysis, systemd service troubleshooting, and other common Linux admin patterns.
- Where scenarios are Windows-only (e.g., registry, UAC), clarify that these do not apply to Linux, and offer Linux-specific troubleshooting tips if relevant.
- Review all examples and ensure Linux commands, file paths, and procedures are present and complete alongside Windows instructions.
Automation
Troubleshoot Azure Automation managed identity issues
...n/articles/automation/troubleshoot/managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias by exclusively using PowerShell commands and examples (e.g., Connect-AzAccount, Get-AzVM), referencing Windows-centric tools and patterns, and omitting any Linux shell (bash, CLI) equivalents. All troubleshooting steps and code samples are written for PowerShell, with no mention of how to perform these tasks on Linux-based Hybrid Runbook Workers or using Azure CLI/bash. This may hinder Linux users from effectively troubleshooting managed identity issues in Azure Automation.
Recommendations
- Provide equivalent examples using Azure CLI (az) and bash scripts alongside PowerShell examples for each scenario.
- Explicitly mention how troubleshooting steps apply to both Windows and Linux Hybrid Runbook Workers.
- Include notes or sections on differences in managed identity usage between Windows and Linux environments.
- Add troubleshooting steps and code samples for Linux environments, such as using curl or wget to query the managed identity endpoint.
- Ensure documentation is platform-neutral by presenting Windows and Linux solutions in parallel, or clarifying when a solution is platform-specific.
Automation
Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation
...icles/automation/troubleshoot/hybrid-runbook-worker.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: troubleshooting examples and resolutions are predominantly Windows-focused, with PowerShell commands and Windows-specific tools (event logs, registry keys, configuration files) featured heavily and often before Linux equivalents. Many scenarios provide detailed Windows steps, while Linux instructions are less frequent, less detailed, or appear later. Some troubleshooting steps (e.g., editing Orchestrator.Sandbox.exe.config, checking Microsoft-SMA event logs, registry edits) are only described for Windows, with no Linux analogs provided.
Recommendations
- Ensure that every troubleshooting scenario includes both Windows and Linux steps/examples where applicable.
- Provide Linux equivalents for Windows-specific tools and patterns (e.g., event log checks, configuration file edits, registry changes).
- Include Linux command-line examples (bash, systemctl, journalctl, etc.) alongside PowerShell commands.
- Present Windows and Linux troubleshooting guidance in parallel, rather than grouping all Windows content first.
- Expand Linux troubleshooting sections to match the detail and coverage given to Windows.
- Reference Linux documentation and resources as prominently as Windows ones.
Automation
Troubleshoot Azure Automation runbook issues
...blob/main/articles/automation/troubleshoot/runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for troubleshooting Azure Automation runbook issues exhibits a strong Windows and PowerShell bias. All code examples and troubleshooting steps are provided exclusively in PowerShell, with no equivalent examples for Bash, Python, or Linux shell environments. Windows-centric tools and patterns (such as PowerShell ISE, Windows Management Instrumentation, and Windows Installer) are referenced without mention of Linux alternatives. The documentation assumes familiarity with Windows/PowerShell workflows and does not address Linux-specific troubleshooting scenarios or provide parity for Linux users.
Recommendations
- Add equivalent troubleshooting examples for Bash, Python, and Linux shell environments where applicable.
- Include guidance for Linux-based Hybrid Runbook Workers, such as troubleshooting with systemd, journalctl, or Linux authentication mechanisms.
- Reference cross-platform tools and editors (e.g., VS Code on Linux, nano, vim) alongside Windows tools like PowerShell ISE.
- Clarify which troubleshooting steps are platform-agnostic and which are Windows-specific; provide Linux-specific alternatives where needed.
- Mention and provide examples for using Azure CLI in addition to PowerShell, especially for authentication, module management, and runbook execution.
- Include notes or sections on common Linux errors, permissions, and environment issues encountered in Azure Automation.
Automation
Configure machines to a desired state in Azure Automation
...automation/tutorial-configure-servers-desired-state.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments and PowerShell tooling. All examples use Windows-specific features (e.g., WindowsFeature IIS), and only Windows VM creation is described in prerequisites. There are no Linux-specific configuration examples, nor any mention of Linux DSC resources or onboarding Linux VMs. PowerShell is the only automation language shown, and all cmdlets are Windows-centric. The documentation references Windows tools and patterns exclusively, with no parity for Linux users.
Recommendations
- Add Linux-specific configuration examples, such as installing Apache or Nginx using DSC resources for Linux.
- Include onboarding steps and prerequisites for Linux VMs, referencing the appropriate Azure documentation.
- Show how to use cross-platform tools (e.g., Azure CLI, Bash) for managing DSC configurations and nodes.
- Mention and link to Linux DSC resource documentation and clarify current support status for Linux nodes.
- If Linux support is deprecated, clearly state alternatives or migration paths for Linux users.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page for Azure Automation updates shows a notable Windows bias. PowerShell is consistently mentioned as the primary automation language, with frequent announcements of new PowerShell versions and features. Windows terminology and tools (e.g., PowerShell, AzureRM, Az modules) are referenced more often and in greater detail than Linux equivalents. Examples and feature descriptions tend to lead with Windows/PowerShell, with Linux support mentioned as an add-on or secondary. There is limited explicit mention of Linux-specific tooling or parity in examples.
Recommendations
- Provide equivalent Linux/bash examples and highlight them alongside PowerShell in feature announcements.
- Explicitly mention Linux support and capabilities in all relevant updates, not just as an afterthought.
- Include references to Linux-native automation tools (e.g., bash, shell scripts, cron) where appropriate.
- Ensure documentation for new features and retirements addresses both Windows and Linux users equally, with clear migration paths and tooling for both.
- Add more detail about Python runbooks and Linux hybrid worker scenarios, including troubleshooting and best practices.
- Where possible, alternate the order of Windows and Linux mentions to avoid 'Windows first' pattern.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/add-user-assigned-identity.md
...main/articles/automation/add-user-assigned-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, with no Bash, Azure CLI, or Linux-native shell examples. Even REST API and ARM template deployment examples are shown using PowerShell. The only non-PowerShell code sample is a single Python example, but it is not presented as an alternative to PowerShell for the main workflows. There is no mention of Linux shell, Azure CLI, or cross-platform scripting approaches, and Windows/PowerShell tools and patterns are assumed throughout.
Recommendations
- Provide equivalent Azure CLI (az) examples for all PowerShell workflows, including authentication, resource management, and REST API invocation.
- Show Bash or shell script examples for REST API calls and ARM template deployments, using curl and az deployment group create.
- Clearly indicate that all PowerShell examples can be run on Linux/macOS with PowerShell Core, or provide explicit cross-platform notes.
- Add a section or callouts for Linux users, highlighting any differences or additional steps required.
- Include at least one end-to-end example using only Azure CLI and Bash, to demonstrate parity for non-Windows environments.
- Where possible, use generic terms (e.g., 'command line', 'shell') instead of assuming PowerShell as the default.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-alert-triggered-runbook.md
...utomation/automation-create-alert-triggered-runbook.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code examples and instructions use PowerShell, with no mention of Bash, Azure CLI, or Linux shell equivalents. The prerequisites and links reference Windows VMs and PowerShell modules, and the runbook creation process exclusively uses PowerShell scripts. There are no Linux-specific instructions, nor are cross-platform alternatives presented. Windows tools and patterns are mentioned first and exclusively throughout the page.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for Linux users.
- Include instructions for managing Linux VMs, not just Windows VMs.
- Reference both Windows and Linux VM quickstart guides in prerequisites.
- Provide runbook samples in Python or other cross-platform languages supported by Azure Automation.
- Clarify that Azure Automation and alerts can be used with both Windows and Linux VMs, and show how.
- Mention installation of Az CLI as an alternative to PowerShell for cross-platform usage.
- Balance the documentation by presenting Linux and Windows options side-by-side where possible.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-disaster-recovery.md
...in/articles/automation/automation-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page for Azure Automation disaster recovery demonstrates a Windows bias. All migration scripts and runbook examples are provided exclusively in PowerShell and PowerShell Workflow, which are Windows-centric technologies. There are no equivalent Bash, Python, or Linux-native script examples. The installation and management steps for Hybrid Runbook Workers link to instructions with Windows tabs as default, and Windows terminology/tools are mentioned before Linux equivalents. Linux users are left to infer or adapt Windows-centric instructions, and Linux asset migration is not addressed directly.
Recommendations
- Provide equivalent migration scripts and runbook examples using Bash or Python, suitable for Linux environments.
- Include explicit Linux instructions and examples alongside Windows ones, especially for Hybrid Runbook Worker installation and management.
- Document how to migrate Python packages and Linux-specific modules/assets, not just PowerShell modules.
- Ensure that links and tabs do not default to Windows instructions; present Windows and Linux options equally.
- Clarify any platform-specific limitations or requirements for disaster recovery steps.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-gallery.md
...main/articles/automation/automation-runbook-gallery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell. All examples and instructions focus exclusively on PowerShell, PowerShell Gallery, and Windows-centric tools and patterns. There is no mention of Linux shell equivalents, Linux-specific modules, or cross-platform scripting approaches. Even in sections referencing Python, there are no concrete Linux or bash examples. The common scenarios and runbooks highlighted are Windows/PowerShell-centric, and the documentation does not address Linux automation workflows or provide parity for Linux users.
Recommendations
- Add examples and instructions for importing and using runbooks/modules with Linux tools (e.g., bash, Azure CLI, Python).
- Include Linux-specific runbook scenarios and modules, such as those for managing Linux VMs or using bash scripts.
- Mention and demonstrate cross-platform compatibility for runbooks and modules, clarifying which are usable on Linux and how to use them.
- Provide parity in documentation structure, ensuring Linux and Windows approaches are presented side-by-side or with equal prominence.
- Reference Linux automation best practices and tools (e.g., cron, systemd, shell scripting) where relevant.
- Clarify limitations and support for PowerShell Core (pwsh) on Linux, and provide guidance for Linux users where Azure Automation does not support PowerShell Core.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-create-composite.md
...articles/automation/automation-dsc-create-composite.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows PowerShell and Windows-centric tooling (DSC, MOF files, PowerShellGet, etc.), with examples and instructions exclusively referencing Windows environments and workflows. Linux is only mentioned in passing (as a target for onboarding), with no Linux-specific examples, commands, or equivalent tooling described. The documentation assumes familiarity with Windows PowerShell and does not provide parity for Linux users or those using cross-platform PowerShell Core.
Recommendations
- Add explicit examples for Linux environments, including how to author, convert, and deploy DSC configurations on Linux nodes.
- Clarify which steps and tools are supported on PowerShell Core (cross-platform) versus Windows PowerShell 5.1.
- Provide Linux-specific instructions for configuration management, including MOF generation, module packaging, and deployment.
- Mention and link to Linux DSC resources and community projects, if available.
- Reorder or balance references so that Linux is not only mentioned after Windows, but given equal prominence in onboarding and usage scenarios.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-authoring.md
...in/articles/automation/automation-runbook-authoring.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by listing Windows operating systems first in the supported OS matrix, focusing heavily on PowerShell (especially Windows PowerShell 5.1), and providing directory path examples only in Windows format (e.g., C:\abc). There is no mention of Linux/macOS-specific directory path formats or shell usage, and examples and notes reference Windows tools and conventions exclusively. Python support is mentioned but lacks parity in debugging features and examples.
Recommendations
- Present supported operating systems in a neutral or rotating order, or group by platform (Windows, Linux, macOS) rather than listing Windows first.
- Include Linux/macOS directory path examples (e.g., /home/user/abc) alongside Windows paths.
- Provide shell-agnostic or bash/zsh examples for common operations, not just PowerShell.
- Clarify support for Linux/macOS features and limitations, and mention equivalent tools or workflows where possible.
- Expand Python runbook debugging guidance to include recommended VS Code extensions for Linux/macOS.
- Explicitly state any platform-specific limitations or differences in feature support.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/context-switching.md
...ocs/blob/main/articles/automation/context-switching.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell and Az/AzureRM cmdlets for all examples and recommendations, which are Windows-centric tools. There are no Bash, CLI, or Linux-native examples or references. The guidance assumes use of PowerShell and Windows patterns, and does not mention or prioritize Linux or cross-platform alternatives.
Recommendations
- Add equivalent Azure CLI (az) examples for context management and runbook authentication, demonstrating how to avoid context switching issues in Bash or shell scripts.
- Explicitly mention that Azure Automation supports Python and other runbook types, and provide guidance for those environments.
- Clarify whether context switching issues apply to non-PowerShell runbooks, and if so, provide mitigation steps for those platforms.
- Reorder sections or add notes to ensure Linux and cross-platform tools are given equal prominence as Windows/PowerShell tools.
- Include troubleshooting examples and error messages for Linux or CLI-based runbooks, not just PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-graphical-authoring-intro.md
...les/automation/automation-graphical-authoring-intro.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows PowerShell workflows and cmdlets, with all examples and explanations centered around PowerShell syntax and Windows-centric tools. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows PowerShell and does not provide parity for Linux users or those using non-Windows environments.
Recommendations
- Add explicit statements clarifying platform support, including whether graphical runbooks can run on Linux-based Automation workers.
- Provide examples or guidance for authoring runbooks using Bash or Python, if supported, or clarify their absence.
- Include references to cross-platform PowerShell (PowerShell Core) and note any differences or limitations compared to Windows PowerShell.
- Mention Linux-specific considerations, such as authentication, asset management, or module availability, if applicable.
- Add links to documentation about using Azure Automation with Linux environments and non-Windows scripting languages.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md
...b/main/articles/automation/automation-runbook-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows PowerShell and PowerShell Workflow runbooks, referencing Windows-specific file paths and environment variables, and providing examples and troubleshooting steps that assume a Windows environment. Linux support is mentioned but not illustrated with concrete examples, and Linux-specific limitations or patterns are rarely discussed. Windows tools and conventions (such as C:\ paths, .ps1 scripts, and environment variables) are referenced exclusively or before Linux equivalents.
Recommendations
- Add explicit Linux examples for PowerShell runbooks, including file paths, environment variables, and troubleshooting steps relevant to Linux Hybrid Runbook Workers.
- Where file paths or environment variables are referenced (e.g., C:\modules, TEMP), provide Linux equivalents (e.g., /usr/src/PSModules, /tmp) and clarify platform-specific differences.
- Include parity in limitations and known issues for Linux Hybrid Runbook Workers, not just Windows.
- When discussing Python runbooks, provide Linux-specific installation and configuration guidance, not just for Windows.
- Ensure that examples and sample scripts are provided for both Windows and Linux environments, or clearly indicate which platform each example applies to.
- Avoid using Windows terminology or tools exclusively (e.g., .ps1, PowerShell Workflow) without mentioning Linux alternatives or limitations.
- Consider reordering sections to present Windows and Linux support equally, rather than defaulting to Windows-first explanations.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-office-365.md
...ocs/blob/main/articles/automation/manage-office-365.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily biased toward Windows and PowerShell. All examples use Windows PowerShell, with explicit notes that PowerShell Core (cross-platform) is not supported. There are no Linux or cross-platform alternatives provided, and the workflow assumes a Windows environment and tools. Windows terminology and tools are mentioned exclusively and first, with no mention of Bash, Linux, or macOS equivalents.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS environments, including any supported cross-platform tools.
- Clarify whether Azure Automation supports Bash or Python runbooks for Office 365 management, and provide sample scripts if possible.
- Explicitly state platform limitations and offer workarounds or alternatives for non-Windows users.
- If Microsoft Graph PowerShell is Windows-only, suggest REST API or SDK alternatives for Linux users.
- Add notes or sections for Linux/macOS users, including how to install prerequisites and connect to Office 365 services from those platforms.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-role-based-access-control.md
...les/automation/automation-role-based-access-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias, especially in the sections covering role assignment and management. All command-line examples use Azure PowerShell cmdlets, which are most commonly used and best supported on Windows. There are no examples or guidance for using Azure CLI, Bash, or other Linux-native tools for RBAC management. References to automation tasks and hybrid worker installation link to Windows-specific instructions first or exclusively. The absence of Linux or cross-platform examples may hinder users who primarily use Linux environments.
Recommendations
- Add Azure CLI examples alongside or before PowerShell examples for all RBAC management tasks.
- Include Bash script samples for common operations, such as assigning/removing roles.
- Explicitly mention cross-platform support for Azure CLI and PowerShell Core, and clarify any differences in usage or output.
- Provide links to Linux-specific hybrid worker installation and management guides, and ensure parity in documentation depth.
- Where possible, use neutral terminology (e.g., 'command-line tools' instead of 'PowerShell') and avoid assuming a Windows environment.
- Add a section comparing PowerShell and Azure CLI approaches, highlighting when each is preferable or required.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-use-azure-ad.md
...ob/main/articles/automation/automation-use-azure-ad.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All code examples and module references are PowerShell-specific, with no mention of Linux, Bash, or cross-platform alternatives. Windows tools and patterns (such as PSCredential, Get-AutomationPSCredential, and Windows PowerShell modules) are referenced exclusively and are presented as the default or only option. There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
- Mention cross-platform modules or SDKs (such as Azure CLI, Python SDK, or REST API usage) alongside PowerShell options.
- Clarify which steps or modules are Windows-specific and offer alternatives for non-Windows environments.
- Include a section or table comparing authentication methods and tooling across Windows, Linux, and macOS.
- Update terminology to refer to 'PowerShell' rather than 'Windows PowerShell' where appropriate, and clarify support for PowerShell Core on Linux/macOS.