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 551-575 of 982 flagged pages
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-compile.md
...lob/main/articles/automation/automation-dsc-compile.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 and PowerShell-based workflows for compiling DSC configurations in Azure Automation. All code examples use Windows PowerShell, and Windows-centric tools and paths (e.g., C:\, WindowsFeature) are referenced exclusively. There are no examples or instructions for compiling DSC configurations from Linux or using cross-platform tools. The documentation also refers to Windows PowerShell as the primary or only scripting environment, and does not mention Linux equivalents or alternatives.
Recommendations
- Add examples and instructions for compiling DSC configurations from Linux environments, using cross-platform PowerShell (pwsh) where possible.
- Clarify which steps and cmdlets are supported on Linux and which are Windows-only.
- Provide Linux file path examples (e.g., /home/user/configs) alongside Windows paths.
- Mention any limitations or differences for Linux users up front, especially in sections where only Windows is supported.
- If Linux support is deprecated or limited (as suggested by the Linux retirement announcement), make this explicit and provide guidance or alternatives for Linux users.
Create Pull Request
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-cd-chocolatey.md
...in/articles/automation/automation-dsc-cd-chocolatey.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All examples, tooling, and workflows are specific to Windows, PowerShell, and Windows-centric package management (Chocolatey, DSC). Linux is only mentioned in passing, and no Linux equivalents or examples are provided. The documentation assumes the user is deploying to Windows VMs and using Windows-specific tools, with no guidance for Linux users.
Recommendations
- Provide equivalent Linux examples using native Linux package managers (e.g., apt, yum) and configuration management tools (e.g., Ansible, Chef, Puppet, or Azure Automation State Configuration for Linux if available).
- Include a section or parallel workflow for setting up continuous deployment for Linux VMs, including scripts and configuration files.
- Mention and demonstrate cross-platform tools and approaches where possible, or explicitly state the Windows-only scope at the beginning.
- If Azure Automation State Configuration for Linux is deprecated or unavailable, provide clear alternatives or migration guidance for Linux users.
- Balance the mention of package managers by giving Linux tools equal prominence and not relegating them to a single sentence.
- Where PowerShell is used, provide Bash or shell script equivalents for Linux scenarios.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-configuration-based-on-stig.md
...tomation/automation-dsc-configuration-based-on-stig.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 and PowerShell, referencing only Windows PowerShell 5.1, PowerShell DSC, and the PowerSTIG project (which is Windows-centric). There are no examples or guidance for Linux systems, and Linux onboarding is only mentioned in a link reference, not in the main content. All tools and patterns discussed are Windows-specific, and Linux equivalents or cross-platform approaches are missing.
Recommendations
- Add explicit Linux examples for configuring STIG compliance with Azure Automation State Configuration.
- Discuss or reference Linux-native tools or DSC resources (such as nx or xDSC resources) where applicable.
- Clarify whether PowerSTIG or similar community projects exist for Linux, or provide guidance for Linux users.
- Balance the 'Next steps' section with links and explanations relevant to Linux DSC usage.
- State up front whether the guidance is Windows-only, or provide parity for Linux users where possible.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-config-data-at-scale.md
...cles/automation/automation-dsc-config-data-at-scale.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 and PowerShell, with all examples and instructions referencing Windows PowerShell DSC and related tooling. Linux is only mentioned in passing (e.g., onboarding Linux machines), with no Linux-specific examples, tools, or guidance provided. The documentation assumes familiarity with Windows-centric tools and workflows, and does not address Linux-native equivalents or cross-platform usage.
Recommendations
- Provide explicit Linux examples for configuring data at scale, including how to use Datum or similar tools on Linux systems.
- Include instructions for using cross-platform PowerShell (PowerShell Core) and clarify any differences in behavior or support compared to Windows PowerShell 5.1.
- Mention and link to Linux-native configuration management tools (such as Ansible, Chef, or native DSC for Linux) where appropriate, or clarify the scope if only Windows is supported.
- Reorder or balance references so that Linux and Windows are treated equally, rather than Windows-first.
- Add a section or callout for Linux users, detailing any prerequisites, limitations, or alternative workflows.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-config-from-server.md
...ticles/automation/automation-dsc-config-from-server.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows environments, specifically PowerShell and Windows DSC tooling. All examples and references are for Windows PowerShell 5.1, with no mention of Linux equivalents or cross-platform DSC solutions. The tools and resources discussed (ReverseDSC, SharePointDSC) are Windows/PowerShell-centric, and there are no Linux-specific instructions or examples provided.
Recommendations
- Add equivalent instructions and examples for Linux systems, including how to extract configurations from Linux servers using cross-platform DSC tools.
- Mention and link to cross-platform DSC resources, such as PowerShell 7+ and the Linux DSC agent.
- Clarify in the introduction that the current solution is Windows-specific, and provide guidance or alternatives for Linux users.
- Include examples or references for managing configurations on Linux servers, not just Windows/SharePoint.
- Balance the documentation structure so that Linux and Windows scenarios are presented with equal prominence where possible.
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 and PowerShell, with all examples and instructions assuming the use of Windows PowerShell 5.1. There is no mention of Linux equivalents, cross-platform PowerShell (PowerShell Core), or how to perform similar tasks on Linux systems. Windows tools and patterns (such as MOF files, PowerShellGet, and Windows-specific DSC resources) are referenced exclusively, and Linux scenarios are not addressed.
Recommendations
- Add explicit guidance for using PowerShell DSC and composite resources on Linux, including any differences in configuration or supported features.
- Include examples using PowerShell Core (pwsh), which is cross-platform, and clarify when instructions are Windows-specific.
- Reference and link to Linux onboarding and configuration documentation more prominently, not just as a secondary link.
- Provide sample configurations and workflows for common Linux scenarios (e.g., managing Apache/Nginx, SSH, Linux firewall, etc.).
- Clarify which features or modules are Windows-only and which are supported on Linux, and update the 'Applies to' section accordingly.
- Mention and link to Linux DSC resources and community modules where relevant.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-extension-history.md
...rticles/automation/automation-dsc-extension-history.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exclusively covers Windows operating systems, PowerShell, and Windows Management Framework (WMF) in all version histories, features, and instructions. There is no mention of Linux support, examples, or parity, despite Azure DSC historically having some Linux support. All examples, troubleshooting, and references are Windows-centric, and the only tools and patterns discussed are Windows/PowerShell-specific.
Recommendations
- Explicitly state the current and historical support status for Linux in the introduction, including any retirement or deprecation notices.
- If Linux support is retired, provide a clear summary and links to migration or alternative solutions for Linux users.
- If any versions supported Linux, include those versions and their features in the version history table.
- Add Linux-specific examples, troubleshooting steps, and references where applicable, or clarify their absence.
- Where PowerShell or WMF is mentioned, note the equivalent (or lack thereof) for Linux, such as Open Management Infrastructure (OMI) or cross-platform DSC implementations.
- Ensure that any future documentation updates maintain parity in describing both Windows and Linux support, or clearly state when features are Windows-only.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-getting-started.md
.../articles/automation/automation-dsc-getting-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature IIS), and the only VM creation instructions link to Windows VM guides. There are no Linux-specific examples, resources, or walkthroughs, and Linux support is only mentioned in passing or in deprecation notices. References and links are almost exclusively for Windows/PowerShell DSC, and no Linux equivalents or cross-platform DSC resources are provided.
Recommendations
- Add Linux-specific examples, such as a DSC configuration that manages a Linux package or service using the nx or cross-platform DSC resources.
- Include instructions and links for creating and managing Linux VMs in Azure, alongside the Windows VM instructions.
- Provide parity in walkthroughs for onboarding both Windows and Linux nodes to Azure Automation State Configuration.
- Reference cross-platform DSC documentation and resources, not just Windows PowerShell DSC.
- Clarify the current and future support status for Linux DSC in Azure Automation, and if deprecated, provide migration guidance or alternatives for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-diagnostics.md
...main/articles/automation/automation-dsc-diagnostics.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 PowerShell-based instructions and examples, referencing Windows-centric tools (such as the Az PowerShell module and xDscDiagnostics), and omitting any Linux or cross-platform CLI alternatives. There are no Bash, Azure CLI, or Linux-native instructions, and the workflow assumes a PowerShell environment throughout. Additionally, the documentation references the retirement of Linux DSC support, but does not offer guidance for Linux users or alternatives.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and works natively on Linux and macOS.
- Explicitly state the platform requirements for the PowerShell examples, and provide guidance for Linux/macOS users (e.g., using PowerShell Core or Azure CLI).
- Where possible, provide Bash script examples or note how Linux users can achieve the same results.
- Clarify the impact of Linux DSC retirement and suggest supported alternatives or migration paths for Linux users.
- Ensure that references to tools and modules (such as xDscDiagnostics) include notes on platform compatibility and alternatives for non-Windows environments.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-overview.md
...ob/main/articles/automation/automation-dsc-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing heavily on PowerShell DSC, referencing Windows tools and patterns first, and providing detailed Windows OS/version support lists before Linux. Examples and references (such as Chocolatey and PowerShell cmdlets) are Windows-centric, and there are no Linux-specific usage examples or equivalent Linux tooling highlighted.
Recommendations
- Provide Linux-specific examples for onboarding, configuration, and troubleshooting, including sample commands and scripts.
- List supported Linux distributions and versions explicitly, similar to the Windows OS list.
- Highlight Linux-native configuration management tools or patterns where relevant, or clarify how PowerShell DSC for Linux integrates with typical Linux workflows.
- Include Linux-focused continuous deployment pipeline examples (e.g., using apt, yum, or native package managers instead of Chocolatey).
- Balance the order of presentation so that Linux and Windows are given equal prominence in prerequisites, examples, and feature descriptions.
- Reference Linux command-line tools and scripting (e.g., Bash) where appropriate, alongside PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-remediate.md
...b/main/articles/automation/automation-dsc-remediate.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and cmdlet references for Windows VMs, while Linux remediation is described only in general terms without concrete script examples. Windows tools and workflows (PowerShell, Update-DscConfiguration) are highlighted first and in more detail, whereas Linux instructions are less actionable and defer to external documentation.
Recommendations
- Provide explicit Linux command-line examples (e.g., shell or Python scripts) for remediating drift, similar to the PowerShell example for Windows.
- List Linux remediation steps before or alongside Windows steps to avoid a 'Windows-first' impression.
- Reference and explain Linux-native tools or scripts directly in the documentation, not just via external links.
- Include parity in detail and clarity for both platforms, ensuring Linux users have actionable, in-page guidance.
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 is heavily biased towards Windows and PowerShell. All examples and instructions are provided exclusively for Windows PowerShell, with explicit notes that PowerShell Core (cross-platform) is not supported. There are no examples or guidance for Linux or macOS users, and all tooling and workflow references assume a Windows environment.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS environments, including how to use Azure Automation with PowerShell Core where possible.
- Clarify which features are Windows-only and suggest alternatives or workarounds for non-Windows users.
- Include notes or links to documentation for managing Office 365/Azure Automation from Linux/macOS, such as using Azure CLI, REST APIs, or cross-platform PowerShell modules.
- If certain modules (like Microsoft Graph PowerShell) are not supported on PowerShell Core, explicitly state this and provide alternative approaches for Linux users.
- Reorder sections or provide parallel instructions so that Windows and Linux users are equally supported and neither is prioritized over the other.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-onboarding.md
.../main/articles/automation/automation-dsc-onboarding.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows and PowerShell bias. Most examples and workflows are described using PowerShell scripts and cmdlets, with Linux instructions often being secondary, less detailed, or requiring use of Windows tools (e.g., generating metaconfigurations on Windows). Windows-specific tools and terminology (WMF 5, PowerShell DSC, Set-DscLocalConfigurationManager) are used throughout, and Linux workflows are often described as adaptations of the Windows process. Linux-specific examples are minimal, and Linux users are frequently directed to use Windows-based tooling for key steps.
Recommendations
- Provide Linux-first and Linux-native examples for all major workflows, including onboarding, metaconfiguration generation, and status checking.
- Document how to generate DSC metaconfigurations entirely on Linux, without requiring Windows or PowerShell.
- Where possible, use cross-platform tools or clearly indicate platform-specific steps, offering parity in detail and clarity.
- Include bash or Python scripts for Linux alongside PowerShell scripts for Windows.
- Clarify when a feature or cmdlet is Windows-only, and offer Linux alternatives or workarounds.
- Reorganize sections so that Linux and Windows instructions are presented with equal prominence and detail.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-edit-textual-runbook.md
...articles/automation/automation-edit-textual-runbook.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on PowerShell and Windows workflows. All command-line examples use Windows PowerShell, with explicit references to Windows paths (e.g., c:\runbooks) and no mention of Linux or cross-platform PowerShell Core usage. There are no examples or instructions for editing runbooks from Linux or macOS environments, nor is there guidance for using PowerShell Core or Azure CLI as alternatives.
Recommendations
- Add equivalent examples using PowerShell Core (pwsh) on Linux/macOS, including Unix-style file paths (e.g., /home/user/runbooks).
- Clarify that the Az PowerShell module and cmdlets can be used cross-platform, and provide instructions for installing and using them on Linux/macOS.
- Include Azure CLI examples for exporting/importing runbooks, if supported, to provide a non-PowerShell alternative.
- Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when instructions apply to Windows-only environments.
- Explicitly state platform compatibility for each method, and provide troubleshooting or caveats for non-Windows users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md
...e-docs/blob/main/articles/automation/delete-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples and references are presented before any mention of cross-platform tools, and there are no Linux-specific instructions or screenshots. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell cmdlets, and omits guidance for users on Linux or macOS platforms.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell command examples where appropriate, especially for unlinking or deleting resources.
- Ensure that references to command-line tools do not assume a Windows environment; clarify that steps can be performed from any OS.
- Where screenshots are used, consider including examples from both Windows and Linux environments if UI differences exist.
- Reorder sections so that Azure CLI and PowerShell examples are presented together or in a neutral order, rather than PowerShell first.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide any OS-specific caveats if needed.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows PowerShell and PowerShell Workflow, with all examples, terminology, and tooling centered around PowerShell cmdlets and syntax. There is no mention of Linux-native scripting, Bash, or cross-platform considerations. The documentation assumes familiarity with Windows-based tools and patterns, and does not provide Linux or cross-platform alternatives or examples.
Recommendations
- Clarify early in the documentation that graphical runbooks in Azure Automation are currently limited to PowerShell and PowerShell Workflow, and explicitly state the lack of Bash or Linux-native scripting support.
- If future support for Linux scripting or Bash is planned, add a roadmap or note to inform users.
- Where possible, provide guidance for Linux users, such as how to author and manage runbooks that interact with Linux VMs or resources, even if the runbook language is PowerShell.
- Include examples of managing Linux resources (e.g., using PowerShell cmdlets to interact with Linux VMs, run commands on Linux, or manage Linux-specific assets).
- Reference cross-platform PowerShell (PowerShell Core) where applicable, and clarify any limitations or differences compared to Windows PowerShell.
- Consider adding a section or FAQ addressing common Linux user questions, such as interoperability, prerequisites for managing Linux resources, and any platform-specific caveats.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-hybrid-runbook-worker.md
...rticles/automation/automation-hybrid-runbook-worker.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is the only scripting example provided for querying Hybrid Runbook Workers, with no equivalent Bash or Linux CLI example. When describing agent-based user Hybrid Runbook Worker deployment, Windows is mentioned before Linux, and the PowerShell-centric workflow is emphasized. References to system accounts and permissions also list Windows first, and the use of Windows-specific tools (PowerShell) is assumed for management tasks. Linux support is acknowledged, but practical examples and tool parity are lacking.
Recommendations
- Provide equivalent Bash or Azure CLI examples for Linux users wherever PowerShell scripts are shown.
- When listing instructions or links for both Windows and Linux, alternate the order or present them together to avoid a 'Windows first' impression.
- Include Linux-specific management guidance, such as using shell scripts or Linux-native tools, for querying and managing Hybrid Runbook Workers.
- Clarify that both Windows and Linux are fully supported, and ensure all operational examples (scripts, permissions, troubleshooting) have Linux counterparts.
- Highlight any differences or similarities in user accounts (e.g., System vs nxautomation) more equally, and provide explicit Linux instructions where relevant.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-manage-send-joblogs-log-analytics.md
...mation/automation-manage-send-joblogs-log-analytics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows/Powershell bias. While the overall content is platform-neutral in its description of Azure Automation and Azure Monitor, it references PowerShell specifically when discussing error streams and job debugging. There are no explicit Linux or cross-platform CLI (e.g., Azure CLI, Bash) examples or mentions. The documentation does not provide Linux-specific guidance or alternative command-line workflows, and it assumes familiarity with PowerShell concepts and terminology.
Recommendations
- Add explicit references and examples for Linux users, such as using Azure CLI or Bash scripts to interact with Azure Automation and Azure Monitor logs.
- When discussing job streams and error handling, mention how non-Windows runbooks (e.g., Python, Bash) handle errors and how their output appears in logs.
- Where PowerShell is referenced, provide equivalent Azure CLI or REST API examples to ensure parity for Linux and macOS users.
- Clarify that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and provide examples or links for each.
- Include a section or note on how to access and query logs from Linux environments, possibly with sample Bash/Azure CLI commands.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-network-configuration.md
...rticles/automation/automation-network-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific DSC resources (such as WaitFor resources in the /powershell/dsc/reference/resources/windows/waitForAllResource link) without mentioning Linux equivalents or cross-platform alternatives. There are no Linux-specific examples or references, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Include references to Linux DSC resources and provide equivalent Linux documentation links where Windows resources are mentioned.
- Add explicit examples or notes for configuring network requirements on Linux-based Hybrid Runbook Workers and State Configuration nodes.
- Clarify that the guidance applies to both Windows and Linux, and highlight any platform-specific differences in network configuration or tooling.
- Where PowerShell or Windows-specific resources are referenced, provide parallel instructions or links for Linux environments (e.g., using OMSAgent or Linux DSC).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-orchestrator-migration.md
...ticles/automation/automation-orchestrator-migration.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 and PowerShell, with all examples and tooling instructions centered around Windows environments. PowerShell is presented as the default and only scripting language, and all file paths and command examples use Windows conventions. There is no mention of Linux or cross-platform alternatives, nor are there any examples or guidance for users working in Linux environments.
Recommendations
- Provide equivalent examples using Azure Automation Python runbooks or Bash scripts, where applicable.
- Include instructions and examples for Linux users, such as using Azure CLI or Bash for automation tasks.
- Clarify whether the migration tools and modules are supported or can be run on Linux/macOS, and provide installation steps for those platforms if possible.
- Use neutral file path examples (e.g., /home/user/runbooks or $HOME/runbooks) alongside Windows paths.
- Mention cross-platform PowerShell (PowerShell Core) and provide guidance for users running PowerShell on Linux or macOS.
- Explicitly state any platform limitations or requirements for the migration toolkit and related modules.
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 a Windows and PowerShell bias. Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and most frequently. Directory path examples use Windows-style paths (e.g., C:\abc), and there are no Linux/macOS path examples. The documentation focuses on PowerShell runbooks and local debugging, with limited mention of Python and no Linux-specific instructions or examples. Linux and macOS are only briefly referenced in the supported OS list, with no parity in examples or troubleshooting.
Recommendations
- Provide Linux/macOS-specific examples for directory paths (e.g., /home/user/abc) alongside Windows examples.
- Include instructions and screenshots for configuring the extension and running/debugging runbooks on Linux/macOS.
- List supported operating systems in a neutral or rotating order, not always starting with Windows.
- Expand Python runbook documentation, including debugging guidance for Linux/macOS users.
- Clarify any OS-specific limitations or differences in feature support.
- Ensure all command palette and settings navigation instructions are valid for Linux/macOS (e.g., keyboard shortcuts).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-execution.md
...in/articles/automation/automation-runbook-execution.md
High Priority
View Details →
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 are in PowerShell, and references to modules, environment variables, and system paths are Windows-specific (e.g., $env:TEMP, C:\temp). Windows tools like WinSCP.exe and IIS are mentioned as module dependencies, with no Linux equivalents or examples provided. There is minimal mention of Linux or Bash scripting, and Linux-specific scenarios are not addressed, leading to a lack of parity for Linux users.
Recommendations
- Provide equivalent Bash or Python examples for common runbook tasks, especially for error handling and file operations.
- Include Linux-specific guidance for Hybrid Runbook Workers, such as recommended temp directories (e.g., /tmp) and handling of permissions/elevation.
- Mention Linux-compatible tools and modules (e.g., sftp, curl, Apache/Nginx) alongside Windows tools like WinSCP and IIS.
- Clarify which features, modules, and cmdlets are supported on Linux Hybrid Runbook Workers, and document any differences.
- Add a section or examples for authoring and running Python runbooks, which are supported in Azure Automation and are cross-platform.
- Balance references to environment variables and file paths by including both Windows and Linux formats (e.g., $env:TEMP and /tmp).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-managing-data.md
...b/main/articles/automation/automation-managing-data.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: Windows-specific tools (PowerShell cmdlets) are referenced more frequently and prominently than Linux equivalents, and examples for backup/export tasks are provided only for Windows/PowerShell. In several sections, Windows instructions or tools are mentioned before Linux, and some Linux guidance is either less detailed or missing entirely.
Recommendations
- Provide Linux command-line examples (e.g., using Azure CLI or Bash scripts) alongside or before Windows/PowerShell examples for tasks like exporting runbooks, DSC configurations, and managing assets.
- Include Linux-specific instructions for tasks such as enabling/disabling TLS protocols, not just a Python script but also relevant shell commands or configuration file edits.
- Reference cross-platform tools (e.g., Azure CLI, REST API) wherever possible, rather than focusing on Windows PowerShell cmdlets.
- Ensure that tables and lists do not always list Windows platforms first; alternate or group by platform type.
- Add explicit Linux examples for asset management, backup, and recovery, not just for TLS configuration.
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 and PowerShell bias. All command-line examples for configuring Azure RBAC are provided exclusively using Azure PowerShell cmdlets, with no mention or examples of equivalent Azure CLI (cross-platform) commands. The only scripting language shown is PowerShell, which is primarily associated with Windows environments. There is no guidance or examples for Linux/macOS users, nor is there mention of using Azure CLI or REST API for role assignments. The structure and ordering of the documentation also present PowerShell before any other tooling, reinforcing a Windows-first approach.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for role assignment, listing, and removal.
- Explicitly mention that Azure CLI and REST API can be used for these operations, and provide links or examples.
- Where scripts are provided, offer both PowerShell and Bash (Azure CLI) versions side-by-side.
- Clarify that PowerShell is available cross-platform, but also highlight the native experience for Linux/macOS users via Azure CLI.
- Review all sections for implicit assumptions of a Windows environment and update language to be inclusive of Linux/macOS users.
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 is heavily focused on PowerShell and Windows-centric tools, with almost exclusive reference to the PowerShell Gallery, PowerShell modules, and Windows Azure VMs. There are no Linux-specific examples, tools, or workflows provided, and the only mention of Linux is in a tag suggestion. All example runbooks and scenarios are Windows/PowerShell oriented, and there is no parity in guidance for Linux automation or modules.
Recommendations
- Add equivalent examples and workflows for Linux automation, such as using Python runbooks or Bash scripts.
- Include references to Linux Azure VMs and provide sample runbooks for managing Linux VMs (e.g., copying files to/from Linux VMs, managing Linux services).
- Highlight cross-platform capabilities of Azure Automation, and clarify which features are Windows-only and which are available for Linux.
- Provide parity in documentation structure: if PowerShell Gallery and modules are discussed, also discuss Python package sources or Bash script repositories where applicable.
- Include at least one end-to-end example for Linux users, such as importing and running a Python runbook on a Linux VM.