Automation
232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
365 issues found
Showing 226-250 of 365 flagged pages
Automation
Edit textual runbooks in Azure Automation
...articles/automation/automation-edit-textual-runbook.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and Windows-specific workflows. All command-line examples use Windows PowerShell and Windows file paths, with no mention of Linux/macOS alternatives or cross-platform PowerShell usage. There are no Bash or Linux-native instructions, and Windows terminology (e.g., 'Windows PowerShell', 'c:\runbooks') is used exclusively.
Recommendations
- Provide examples using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility.
- Include Linux/macOS file path examples (e.g., '/home/user/runbooks') alongside Windows paths.
- Mention that Az.Automation cmdlets can be used on Linux/macOS with PowerShell Core, and note any limitations.
- Add instructions or examples for editing and importing runbooks from Linux/macOS environments.
- Avoid using 'Windows PowerShell' exclusively; use 'PowerShell' or specify when instructions apply to all platforms.
Create Pull Request
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through exclusive use of PowerShell scripts and workflows for migration tasks, with no equivalent Bash, Python, or Linux-native alternatives provided. The instructions and examples for Hybrid Runbook Worker management consistently reference Windows tabs and installation steps before Linux, and the migration process relies entirely on Windows-centric tooling. There is no guidance for Linux users who may prefer or require non-PowerShell solutions.
Recommendations
- Provide equivalent migration scripts in Bash or Python for Linux/macOS users.
- Include Linux-first or cross-platform examples alongside PowerShell, especially for critical migration and automation tasks.
- Explicitly document any platform-specific limitations and offer workarounds for Linux/macOS environments.
- Ensure that installation and management instructions for Hybrid Runbook Workers are presented in parallel for both Windows and Linux, not with Windows-first ordering.
- Reference cross-platform Azure CLI commands where possible, in addition to PowerShell.
Automation
Enable Azure Automation State Configuration
.../main/articles/automation/automation-dsc-onboarding.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell and Windows-centric tools are used as the primary method for configuration, with Linux instructions often appearing after Windows steps or relying on Windows tooling (e.g., WMF 5, PowerShell DSC) even for Linux onboarding. Linux-specific examples are limited, and the workflow for Linux often requires using Windows-based tools or PowerShell scripts. The documentation assumes familiarity with Windows environments and PowerShell, making it less accessible and more cumbersome for Linux/macOS users.
Recommendations
- Provide Linux-first examples and workflows, using native Linux tools and scripting (e.g., Bash, Python) where possible.
- Include step-by-step instructions for generating and applying DSC metaconfigurations entirely from a Linux environment, without requiring WMF 5 or PowerShell.
- Highlight Linux-specific modules, tools, and troubleshooting steps, and ensure parity in detail and clarity with Windows sections.
- Present Linux and Windows instructions side-by-side or in parallel, rather than Windows-first.
- Clarify which steps are platform-specific and offer alternatives for Linux/macOS users.
Automation
Move your Azure Automation account to another subscription
...s/blob/main/articles/automation/how-to/move-account.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides command-line examples exclusively using Azure PowerShell cmdlets (Remove-AzResource, Remove-AzActionGroup), which are most commonly used on Windows and in PowerShell environments. There are no equivalent examples for Azure CLI, which is cross-platform and preferred by many Linux/macOS users. The portal instructions are neutral, but the scripting guidance is Windows-centric.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown, e.g., az resource delete, az monitor action-group delete.
- Explicitly mention that Azure CLI can be used on Linux/macOS and link to relevant CLI documentation.
- Consider presenting CLI and PowerShell examples side-by-side or in tabs to improve parity.
- Review any references to tools or workflows that are Windows-specific and ensure Linux/macOS alternatives are provided.
Automation
Configure data at scale for Azure Automation State Configuration
...cles/automation/automation-dsc-config-data-at-scale.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell DSC, with all examples and instructions referencing Windows PowerShell 5.1 and related tooling. There is no mention of Linux/macOS equivalents, nor examples for non-Windows platforms, despite Azure Automation DSC supporting Linux nodes. The guidance and links are focused on Windows PowerShell and DSC resources, creating friction for Linux users.
Recommendations
- Add explicit instructions and examples for configuring data at scale for Linux/macOS nodes managed by Azure Automation DSC.
- Include references to cross-platform PowerShell (pwsh) and clarify compatibility with non-Windows environments.
- Provide Linux/macOS-specific onboarding and configuration steps, including file formats and MOF generation for those platforms.
- Mention and link to Linux DSC resources and documentation where relevant.
- Clarify which steps are Windows-only and which are cross-platform.
Automation
Convert configurations to composite resources for Azure Automation State Configuration
...articles/automation/automation-dsc-create-composite.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows PowerShell 5.1 and does not provide examples or guidance for Linux/macOS users. All instructions, tooling, and references are centered around Windows PowerShell and its ecosystem, with no mention of cross-platform PowerShell Core or Linux-specific workflows. The only explicit Linux reference is in a link, not in the main content or examples.
Recommendations
- Add explicit instructions and examples for PowerShell Core (pwsh) on Linux/macOS.
- Clarify whether the CompositeResource module and related tooling work on non-Windows platforms.
- Provide Linux/macOS equivalents for configuration loading, module creation, and MOF file generation.
- Include troubleshooting or notes for platform-specific differences (e.g., file paths, permissions).
- Reorder examples or add parity so Linux/macOS workflows are shown alongside Windows.
Automation
Integrate Azure Automation State Configuration with Azure Monitor Logs
...main/articles/automation/automation-dsc-diagnostics.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell-based workflows, with all code examples and setup instructions using PowerShell cmdlets. There are no equivalent CLI, Bash, or Linux-native instructions provided. The prerequisites and tooling references (Az PowerShell module, xDscDiagnostics) are Windows-centric, and there is no mention of how to perform these tasks on Linux/macOS, nor any alternative commands or scripts for those platforms.
Recommendations
- Add Azure CLI (az) equivalents for all PowerShell commands, including authentication, resource ID retrieval, and diagnostic settings configuration.
- Explicitly document how Linux/macOS users can install and use the Az CLI and interact with Azure Automation and Monitor Logs.
- Provide Bash or shell script examples alongside PowerShell, or clarify platform support for each step.
- Note any limitations or differences for Linux/macOS users, especially in light of the referenced 'automation-dsc-linux-retirement-announcement'.
- Reorder examples so that cross-platform or CLI instructions are presented before or alongside PowerShell examples.
Automation
Azure Automation State Configuration overview
...ob/main/articles/automation/automation-dsc-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell and Windows DSC are referenced throughout, with examples and terminology centered on Windows tools and workflows. Windows operating systems are listed first and in detail, while Linux support is mentioned but not elaborated with specific examples or distributions. Proxy configuration and other features are described for Windows first, with Linux details provided as an afterthought. There is a lack of Linux-specific usage examples, and Windows-centric tools (e.g., PowerShell, WinRM) are emphasized.
Recommendations
- Provide Linux-specific examples for onboarding, configuration, and troubleshooting, including common distributions.
- List Linux operating systems and requirements with the same level of detail as Windows.
- Include Linux command-line equivalents alongside PowerShell examples.
- Mention Linux proxy configuration and agent setup before or alongside Windows instructions.
- Reference Linux DSC resources and community documentation where appropriate.
- Ensure screenshots and UI descriptions are inclusive of Linux scenarios.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides more detailed examples and instructions for Windows environments, especially regarding Python interpreter selection for Hybrid Runbook Workers. Windows-specific environment variables and file paths are described explicitly, while Linux equivalents are only mentioned briefly or not at all. There is a lack of concrete Linux examples and instructions, which may create friction for Linux users.
Recommendations
- Include explicit Linux examples for environment variable configuration and Python interpreter selection, such as showing typical Linux paths (e.g., /usr/bin/python3) and environment variable usage.
- Provide step-by-step instructions for both Windows and Linux Hybrid Runbook Workers in parallel, ensuring parity in detail and clarity.
- Mention Linux tools and patterns where relevant, such as package management commands or file system paths.
- Ensure that troubleshooting and configuration sections address Linux-specific scenarios and not just Windows.
- Where environment variables are referenced, show both Windows (e.g., C:\Python2\python.exe) and Linux (/usr/bin/python2) examples.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Windows-specific tools (PowerShell cmdlets) are referenced repeatedly for key tasks like resource deletion, backup/export, and DSC node management, with no Linux CLI or cross-platform alternatives provided. Windows guidance and links are often given before Linux equivalents, and Linux examples are less detailed or missing for several operations. The Linux section for TLS upgrade is present, but other areas lack parity.
Recommendations
- Provide equivalent Linux CLI or Azure CLI examples for tasks currently covered only by PowerShell (e.g., unregistering DSC nodes, exporting runbooks/configurations).
- Include Linux/macOS-specific instructions or scripts for backup/export and asset management.
- Present platform guidance in parallel (side-by-side) rather than Windows-first ordering.
- Reference cross-platform tools (e.g., Azure CLI, REST API) where possible instead of Windows-only cmdlets.
- Add explicit Linux/macOS examples for asset retrieval and runbook/module export.
Automation
Author graphical runbooks in Azure Automation
...les/automation/automation-graphical-authoring-intro.md
Medium 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, code snippets, and references centered around PowerShell cmdlets and syntax. There is no mention of Linux or macOS equivalents, nor any Bash, Python, or cross-platform scripting options. Windows-centric tools and terminology (e.g., System Center Orchestrator, PowerShell expressions, Windows PowerShell scripting overview) are used exclusively and introduced before any alternatives, which are absent. This creates friction for Linux/macOS users, as the documentation assumes familiarity with Windows PowerShell and does not provide guidance for those using non-Windows environments.
Recommendations
- Explicitly state platform requirements and limitations for graphical runbooks (e.g., only supported on Windows-based Automation workers).
- Provide guidance for Linux/macOS users, including any available alternatives or workarounds for graphical runbook authoring.
- Include examples or references for Bash, Python, or other cross-platform scripting languages if supported.
- Clarify whether graphical runbooks can be authored or executed from Linux/macOS environments, and if not, suggest textual runbooks or other Automation options.
- Add a section comparing Windows and Linux support for Azure Automation, highlighting differences and parity gaps.
Automation
Runbook authoring using VS Code in Azure Automation
...in/articles/automation/automation-runbook-authoring.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and most frequently. Examples and directory paths use Windows-style notation (e.g., C:\abc), and there are no explicit Linux/macOS-specific examples or instructions. Debugging support is only described for PowerShell, with Python debugging relegated to a generic recommendation to use a third-party extension. Linux and macOS are listed as supported, but practical parity in examples and instructions is lacking.
Recommendations
- Provide Linux/macOS-specific examples for directory paths and configuration (e.g., /home/user/abc).
- Include instructions for installing required PowerShell modules and Python packages on Linux/macOS.
- Offer parity in debugging guidance for Python on all platforms, not just a generic suggestion.
- List supported operating systems in a neutral order or alternate the order in different sections.
- Explicitly mention any platform-specific limitations or differences in functionality.
- Add screenshots or walkthroughs for Linux/macOS environments where relevant.
Automation
Runbook execution in Azure Automation
...in/articles/automation/automation-runbook-execution.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for Azure Automation Runbook execution is heavily focused on PowerShell and Windows-centric tools, with examples and module references almost exclusively in PowerShell. Windows-specific patterns (such as references to C:\temp, .exe files, IIS, WinSCP.exe, and UAC) are mentioned without Linux equivalents or alternatives. There are no Linux/bash examples, and Linux-specific considerations are only briefly mentioned in passing (e.g., Defender for Cloud constraints). The documentation assumes familiarity with Windows environments and tools, which may create friction for Linux/macOS users.
Recommendations
- Add equivalent bash or Python runbook examples, especially for error handling and file operations.
- Include Linux-specific guidance for Hybrid Runbook Workers (e.g., file paths, elevation, service management).
- Mention Linux alternatives for Windows-only tools (e.g., alternatives to WinSCP.exe, IIS administration).
- Clarify when instructions or modules are Windows-only and provide Linux/macOS alternatives where possible.
- Balance example ordering so Linux/macOS scenarios are presented alongside or before Windows ones when relevant.
Automation
Handle errors in Azure Automation graphical runbooks
...omation/automation-runbook-graphical-error-handling.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses Windows PowerShell terminology, cmdlets, and examples (e.g., Write-Warning, Start-AzAutomationRunbook, Start-AzVM), with no mention of Linux/macOS equivalents or cross-platform scripting options. All error handling concepts and code activities are described in terms of PowerShell, and there are no Bash, Python, or Linux-native examples. The page assumes familiarity with Windows-centric tools and patterns, which may create friction for users automating Linux or cross-platform environments.
Recommendations
- Add examples using Bash, Python, or other cross-platform scripting languages supported in Azure Automation.
- Clarify whether graphical runbooks and error handling features are available and behave identically for Linux hybrid workers.
- Include Linux/macOS-specific error handling scenarios and equivalent tools (e.g., shell error codes, logging).
- Explicitly state platform limitations or parity in the introduction.
- Present examples for both Windows and Linux environments, or note if only Windows is supported.
Automation
Deploy an Amazon Web Services VM with an Azure Automation runbook
...icles/automation/automation-scenario-aws-deployment.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell and PowerShell ISE for all examples and instructions, with no mention of Linux/macOS alternatives such as AWS CLI, Bash, or cross-platform scripting. All tooling and workflow steps assume a Windows-centric environment, creating friction for users on Linux or macOS who may not have access to PowerShell ISE or prefer native shell environments.
Recommendations
- Provide equivalent instructions and examples using AWS CLI and Bash scripts, which are natively supported on Linux and macOS.
- Clarify whether Azure Automation supports Python or other runbook types and offer examples for those.
- Include guidance for installing and using PowerShell Core (pwsh) on Linux/macOS if PowerShell is required.
- Mention cross-platform alternatives to PowerShell ISE, such as VS Code or command-line editors.
- Add explicit notes or sections for Linux/macOS users, detailing any differences or additional steps.
Automation
Automation services in Azure - overview
...s/blob/main/articles/automation/automation-services.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits a moderate Windows bias, primarily through its heavy emphasis on PowerShell for automation examples and repeated references to Windows-centric tools and scenarios (e.g., registry changes, Active Directory, SQL Server). PowerShell is mentioned as the primary scripting language for Azure Automation, with Python as a secondary option. There is frequent mention of Windows-specific management tasks and tools, while Linux equivalents (such as Bash, shell scripting, or Linux-specific configuration management) are not discussed or exemplified. Although Azure Automanage and other services claim Linux support, practical Linux automation patterns and examples are missing, and Windows tools are referenced first or exclusively in several sections.
Recommendations
- Include Linux-specific automation examples, such as Bash or shell scripts, and reference Linux configuration files and management tasks (e.g., systemd, cron, package managers).
- Highlight Linux-compatible modules and connectors in Azure Automation and Logic Apps, and provide examples of automating Linux workloads (e.g., managing Apache, Nginx, or system updates via apt/yum).
- Balance PowerShell references with equivalent Linux scripting options, and clarify cross-platform capabilities where applicable.
- Explicitly mention Linux support in scenarios involving registry changes, configuration drift, and update management, and provide Linux-specific guidance.
- Present examples for both Windows and Linux side-by-side, especially in sections describing automation runbooks, in-guest management, and event responses.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples, module references, and instructions using Windows PowerShell tools and patterns. There are no Bash, CLI, or Linux/macOS-specific examples or guidance. Windows terminology and modules are mentioned exclusively or before any cross-platform alternatives, creating friction for Linux/macOS users.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
- Clarify which steps and modules are cross-platform (e.g., Az PowerShell module vs. Windows PowerShell-only modules).
- Include notes or sections on how to perform credential management and runbook tasks using non-PowerShell tools.
- Explicitly state platform requirements and alternatives for Linux/macOS users.
- Provide links to Linux/macOS-specific documentation where available.
Automation
Manage role permissions and security in Azure Automation
...les/automation/automation-role-based-access-control.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its examples and tooling. All command-line instructions for managing Azure RBAC roles are provided exclusively using Azure PowerShell cmdlets, with no mention or examples of Azure CLI, Bash, or cross-platform alternatives. The 'Configure Azure RBAC' section lists only PowerShell-based workflows, and the page references PowerShell as the primary automation tool, implicitly favoring Windows environments. There are no Linux/macOS-specific instructions or parity examples, which may create friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, including role assignment, listing, and removal.
- Explicitly state that Azure CLI is cross-platform and provide guidance for Linux/macOS users.
- Include Bash script snippets where appropriate, especially for automation scenarios.
- Reference both PowerShell and CLI documentation in 'Next steps' and throughout the page.
- Clarify that all RBAC operations can be performed from Linux/macOS, not just Windows.
Automation
Configure runbook output and message streams
...s/automation/automation-runbook-output-and-messages.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows PowerShell, with all code examples, cmdlet references, and output retrieval instructions using PowerShell syntax and Windows-specific tools. There are no examples or guidance for Linux/macOS users, such as Bash, Python, or cross-platform Azure CLI usage. Windows terminology and tools are used exclusively and introduced first, creating friction for non-Windows users.
Recommendations
- Add equivalent examples using Azure CLI and/or REST API for retrieving runbook output and managing jobs, which are cross-platform.
- Include Python runbook examples and clarify how output and message streams work for Python and other supported languages.
- Provide guidance for Linux/macOS users on installing and using PowerShell Core (pwsh), or offer alternative workflows using Bash or other shells.
- Explicitly mention platform compatibility for cmdlets and features, and note any differences in behavior on non-Windows platforms.
- Reorder sections or provide parallel examples so that Linux/macOS options are presented alongside or before Windows-specific instructions.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell (a Windows-centric technology) is presented first and most extensively, with multiple sections and examples focused on Windows PowerShell and its workflows. Many examples reference Windows file paths (e.g., C:\modules), environment variables (e.g., TEMP), and cmdlets that are specific to Windows environments. There is little to no mention of Linux-specific patterns, file paths, or troubleshooting, and Linux support is only briefly referenced in limitations. Python runbooks receive less coverage and examples, and Linux-specific Python details are minimal. Graphical runbooks are also Windows/PowerShell-centric and explicitly do not support Linux Hybrid Workers.
Recommendations
- Provide Linux-specific examples and troubleshooting steps, especially for PowerShell runbooks running on Linux Hybrid Workers.
- Include Linux file path examples (e.g., /home/user/modules) alongside Windows paths in sample scripts.
- Clarify differences in module management, environment variables, and limitations for Linux Hybrid Workers.
- Expand Python runbook documentation with Linux-focused examples and common issues.
- Add parity in documentation structure and depth for Linux/macOS users, including graphical runbook alternatives or limitations.
- Explicitly state when features or examples are Windows-only, and offer Linux/macOS alternatives where possible.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell examples for all command-line operations, referencing Windows-centric tools and modules (e.g., Az PowerShell), and omitting equivalent instructions for Linux/macOS users (such as Azure CLI or Bash). PowerShell is presented first and often as the only scripting option, which may create friction for users on non-Windows platforms.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell for all command-line steps, especially for identity assignment, Key Vault access policy configuration, and key management.
- Explicitly state that PowerShell examples are cross-platform (if true), or clarify any platform limitations.
- Provide guidance or links for installing and using Azure CLI on Linux/macOS.
- Reorder examples so that cross-platform or platform-neutral options (REST, CLI) are presented before or alongside PowerShell.
- Include troubleshooting notes for Linux/macOS users where PowerShell modules may behave differently.
Automation
Using a system-assigned managed identity for an Azure Automation account
...s/automation/enable-managed-identity-for-automation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. Nearly all code examples use PowerShell, with no Bash, CLI, or Linux-native scripting alternatives provided. Even REST API and ARM template sections use PowerShell for invocation and deployment, rather than cross-platform tools like Azure CLI or curl. Windows tools and patterns (e.g., New-Object, Windows file paths) are referenced exclusively or before Linux equivalents. Linux is only mentioned in passing for Hybrid Runbook Worker version checks, with no practical examples for Linux/macOS users.
Recommendations
- Add Azure CLI and Bash examples for all major tasks (enabling managed identity, assigning roles, verifying assignments, authenticating, etc.).
- Include Linux/macOS-specific instructions for file paths, environment variables, and scripting.
- Show cross-platform REST API invocation examples using curl or httpie, not just PowerShell.
- Present examples in a platform-neutral order, or alternate which platform is shown first.
- Clarify which steps are platform-agnostic and which require OS-specific tooling.
Automation
Start an Azure Automation Runbook from a Webhook
...s/blob/main/articles/automation/automation-webhooks.md
Medium 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 usage. All code examples and instructions for interacting with Azure Automation webhooks use PowerShell cmdlets and Windows-centric tooling (e.g., Invoke-WebRequest, Az Module), with no mention of Linux/macOS alternatives such as Bash, curl, or cross-platform Azure CLI. REST API examples are also shown only via PowerShell, and there are no Linux shell or Azure CLI examples. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
- Add equivalent examples using Bash and curl for webhook creation, invocation, and deletion.
- Include Azure CLI commands for all operations (creating webhooks, invoking them, retrieving job output, etc.), as Azure CLI is cross-platform.
- Show REST API usage with curl or httpie, not just PowerShell's Invoke-RestMethod.
- Explicitly mention platform requirements and provide guidance for Linux/macOS users.
- Reorder examples so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell examples.
Automation
Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent
...g/guidance-migration-log-analytics-monitoring-agent.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides migration guidance for both Windows and Linux VMs, but the scripting section is heavily PowerShell-focused, with no Bash or Linux-native script examples. Windows-centric terminology (e.g., registry, Windows services) is listed before Linux equivalents, and screenshots and walkthroughs are tailored to Azure portal workflows, which are platform-agnostic but may be more familiar to Windows users. There is no explicit Linux shell or CLI example for migration, nor are Linux-specific tools or patterns discussed in detail.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, especially for migration tasks.
- Include Linux-specific instructions or highlight differences in the migration process for Linux VMs.
- List Linux data types (e.g., daemons, files) before or alongside Windows types to avoid Windows-first ordering.
- Clarify any platform-specific limitations or requirements in the prerequisites and migration steps.
- Offer guidance for using Azure CLI or other cross-platform tools for migration, not just PowerShell.
Automation
Delete an Azure Automation Run As account
...blob/main/articles/automation/delete-run-as-account.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on PowerShell and Azure portal methods for deleting a Run As account, with no mention of Linux/macOS command-line tools or cross-platform alternatives. The only CLI example referenced is PowerShell, which is traditionally Windows-centric, and there are no Bash, Azure CLI, or REST API examples provided.
Recommendations
- Add Azure CLI examples for deleting Run As accounts, which work natively on Linux/macOS.
- Include REST API instructions for cross-platform automation.
- Clarify whether PowerShell examples require Windows or if they work with PowerShell Core on Linux/macOS.
- Present CLI examples for both PowerShell and Azure CLI side-by-side.
- Explicitly mention platform compatibility for each method.