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 76-100 of 365 flagged pages
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-connections.md
...lob/main/articles/automation/automation-connections.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. PowerShell cmdlets and workflows are presented first and in detail, with explicit references to 'Windows PowerShell' and Az modules. There are no examples or guidance for Linux shell environments (e.g., Bash, CLI), nor are Linux-native tools or patterns mentioned. The only alternatives provided are Python examples, but these are not positioned as Linux-specific, and the overall workflow assumes a Windows-centric approach to automation and connection management.
Recommendations
- Add Azure CLI examples for managing connections, including creation, retrieval, and deletion, to provide parity for Linux and cross-platform users.
- Include Bash shell script samples for accessing connection assets and authenticating with Azure, where possible.
- Explicitly mention cross-platform compatibility and clarify which steps/tools are Windows-only versus available on Linux/macOS.
- Reorder sections so that PowerShell and CLI/Bash examples are presented side-by-side or in parallel tabs, rather than PowerShell-first.
- Reference Linux-native tools and workflows (e.g., OpenSSL, jq, curl) where appropriate, especially in custom module and authentication scenarios.
- Provide troubleshooting and usage notes for Linux environments, including any differences in module installation or asset management.
Create Pull Request
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-create-standalone-account.md
...les/automation/automation-create-standalone-account.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 only Azure PowerShell examples for key management and runbook creation, referencing PowerShell runbooks and cmdlets extensively, and omitting equivalent instructions for Linux users (e.g., Azure CLI or Bash). The 'Next steps' section also prioritizes PowerShell tutorials and references, with Python mentioned only after multiple PowerShell links. No Linux-specific tools or workflows are discussed.
Recommendations
- Add Azure CLI (az) command examples for all operations currently shown only with Azure PowerShell, such as key rotation.
- Include Bash or shell script examples where relevant, especially for Linux users.
- In the 'Next steps' section, provide equal prominence to Python and Azure CLI tutorials, and add links to Bash or cross-platform automation resources.
- Mention cross-platform tools and workflows (e.g., Azure CLI, REST API) alongside PowerShell, not just as an afterthought.
- Clearly indicate that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide alternative instructions for those platforms.
- Wherever a PowerShell cmdlet is referenced, provide the equivalent Azure CLI command.
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 and PowerShell. It only references Windows PowerShell 5.1, PowerShell DSC, and Windows-centric tools and resources (SharePointDSC, ReverseDSC). There are no Linux-specific examples, tools, or instructions, and all guidance assumes a Windows environment. Linux onboarding is mentioned only as a link, with no substantive content or parity in the main instructions.
Recommendations
- Add explicit examples and instructions for Linux environments, including how to generate configurations from Linux servers.
- Reference and link to Linux equivalents for Desired State Configuration, such as Open Management Infrastructure (OMI) or Ansible.
- Clarify which steps are Windows-specific and provide alternative steps for Linux users.
- Include sample scripts or walkthroughs for Linux configuration extraction and MOF file generation.
- Ensure that documentation titles, introductions, and prerequisites reflect cross-platform applicability, or clearly state Windows-only scope if Linux is not supported.
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 page demonstrates a Windows bias by focusing primarily on PowerShell DSC, listing Windows operating systems and requirements in detail before Linux, referencing Windows-specific tools (WMF, WinRM), and providing examples and links that are PowerShell-centric. Linux support is mentioned but lacks equivalent detail, examples, and tool references. There are no Linux-specific configuration or onboarding examples, and the continuous deployment example uses Chocolatey, a Windows package manager.
Recommendations
- Provide Linux-specific examples for onboarding, configuration, and management using Azure Automation State Configuration.
- Include parity in operating system requirements by listing supported Linux distributions explicitly, not just referencing external documentation.
- Add examples of continuous deployment pipelines using common Linux tools (e.g., apt, yum, or Ansible) alongside the Chocolatey example.
- Reference and link to Linux-specific DSC resources and documentation in the same detail as Windows/PowerShell resources.
- Clarify any feature differences or limitations for Linux nodes, especially in areas like proxy support and reporting.
- Ensure that PowerShell and Windows terminology is balanced with Linux equivalents throughout the documentation.
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
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation prioritizes Windows remediation by providing a direct PowerShell example and referencing Windows-specific tools first. Linux remediation is described in less detail, lacks direct script examples, and is presented as less convenient, with no equivalent to the Windows Run Command feature. References and next steps further emphasize Windows/PowerShell tools.
Recommendations
- Provide explicit Linux shell script examples for remediation, similar to the PowerShell example given for Windows.
- Clarify and expand on Linux remediation options, including any available command-line or automation tools.
- Present Windows and Linux instructions in parallel sections, giving equal prominence to both.
- Reference Linux-specific tools and modules (e.g., Azure CLI, Python scripts) with direct links and usage examples.
- Avoid language that implies Linux is less supported or more difficult to remediate; instead, highlight alternative workflows.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-faq.md
...e-docs/blob/main/articles/automation/automation-faq.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. In the section about Hybrid Runbook Workers and Python version selection, only Windows-specific environment variables and file paths (e.g., C:\Python2\python.exe) are described in detail, with no equivalent Linux examples or instructions. Windows Hybrid Runbook Workers are mentioned before Linux ones, and the guidance for Linux is less specific. There are no Linux-specific code examples, environment variable names, or file path conventions provided. The documentation assumes familiarity with Windows tools and patterns, while Linux users are left with generic recommendations.
Recommendations
- Add explicit Linux examples for environment variables and file paths (e.g., /usr/bin/python3).
- Provide step-by-step instructions for configuring Python versions on Linux Hybrid Runbook Workers, similar to the Windows guidance.
- Include Linux-specific troubleshooting tips and references where Windows ones are given.
- Ensure that Linux and Windows instructions are presented with equal detail and prominence.
- Where possible, provide cross-platform code samples or clarify platform-specific differences.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-aws-deployment.md
...icles/automation/automation-scenario-aws-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses PowerShell and Windows-centric tooling (PowerShell Gallery, PowerShell ISE) for all examples and instructions. There are no references to Linux-native tools, Bash, or cross-platform alternatives for authoring or deploying runbooks. The instructions assume the user is familiar with PowerShell and Windows environments, and do not provide parity for Linux users or those preferring AWS CLI or Python SDKs.
Recommendations
- Add equivalent examples using Bash scripts and the AWS CLI for VM provisioning.
- Include instructions for importing and using AWS CLI or Python modules in Azure Automation, which are supported on Linux-based Hybrid Runbook Workers.
- Mention cross-platform editors (such as VS Code) and how to author runbooks for Linux environments.
- Provide guidance on authenticating to AWS using environment variables or credential files, which are common on Linux.
- Clarify which steps are Windows-specific and offer Linux alternatives where possible.
- Reference AWS documentation for Linux and CLI usage alongside PowerShell links.
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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-centric tools are mentioned as onboarding and management channels before Linux equivalents, and there is a lack of explicit Linux-specific examples or instructions. The documentation refers to the 'System' account for Windows and only briefly mentions the 'nxautomation' account for Linux, without further Linux-specific operational details. The onboarding and management channels (Azure portal, PowerShell cmdlets, Bicep, ARM templates, REST API, Azure CLI) are listed with PowerShell first, reinforcing a Windows-first perspective. There are no Linux shell (bash) or Linux-native tool examples, and troubleshooting or operational guidance is not balanced between Windows and Linux.
Recommendations
- Provide explicit Linux shell (bash) examples alongside PowerShell for installation, management, and troubleshooting.
- Ensure Linux-specific operational details (such as permissions, service accounts, log locations, and troubleshooting steps) are documented at parity with Windows.
- List onboarding and management channels in a neutral order or alternate between Windows and Linux tools (e.g., Azure CLI before PowerShell in some sections).
- Include screenshots or walkthroughs for Linux environments, not just Windows.
- Clarify any differences in behavior, limitations, or requirements between Windows and Linux Hybrid Runbook Workers.
- Add troubleshooting guidance and common scenarios specifically for Linux hosts.
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 shows evidence of Windows bias. It references Windows-specific DSC resources (such as WaitFor resources with a Windows documentation link), and does not provide Linux equivalents or examples. There are no explicit Linux-focused instructions or references to Linux DSC resources, nor are there examples or guidance for Linux systems. The documentation implicitly assumes a Windows environment by mentioning Windows DSC resources and omitting Linux-specific details.
Recommendations
- Include examples and references for Linux DSC resources, such as links to Linux DSC documentation.
- Provide explicit instructions or notes for configuring network requirements for Linux nodes, including any Linux-specific considerations.
- Add parity in documentation by mentioning both Windows and Linux DSC resources, and clarify when instructions apply to both or only one platform.
- Where Windows-specific resources (e.g., WaitForAllResource) are mentioned, also mention or link to Linux equivalents or note their absence.
- Ensure that examples and references do not default to Windows unless the feature is Windows-only, and clarify platform support where relevant.
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 page demonstrates a Windows bias by listing Windows operating systems first in the supported OS matrix, focusing heavily on PowerShell (with Windows PowerShell 5.1 and PowerShell Core), and providing directory path examples only in Windows format (e.g., C:\abc). There is a lack of Linux/macOS-specific examples, such as directory paths or shell commands, and the documentation does not mention Linux-specific tools or patterns. Debugging features are described only for PowerShell, with Python debugging relegated to a generic suggestion to install a debugger extension.
Recommendations
- Include Linux/macOS directory path examples (e.g., /home/user/abc) alongside Windows paths.
- Provide shell command equivalents (e.g., bash/zsh) for relevant operations where possible.
- List supported operating systems in a neutral or alphabetical order rather than Windows-first.
- Add examples and instructions for using the extension on Linux/macOS, including installation of Python packages and PowerShell modules.
- Clarify support and limitations for Linux/macOS users, especially regarding debugging and asset management.
- Mention Linux/macOS-specific tools or patterns where applicable, such as file permissions or environment setup.
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 page exhibits a strong Windows bias. All examples and tooling references are centered on Windows PowerShell, with no mention of Linux or cross-platform alternatives. The conversion process, modules, and cmdlets are described exclusively in terms of Windows tools and file paths. There are no Linux shell (bash) examples, nor any discussion of Linux-compatible automation workflows or modules. The documentation assumes the user is operating in a Windows environment and does not address Linux users or provide parity in guidance.
Recommendations
- Include Linux/bash examples for runbook conversion and management, where possible.
- Clarify whether the Runbook Converter and related modules can be used on Linux/macOS (e.g., via PowerShell Core), and provide instructions if so.
- Mention cross-platform PowerShell (PowerShell Core/7+) compatibility and any limitations.
- Provide guidance for Linux users on how to prepare, convert, and import runbooks, including file path conventions and asset management.
- Reference Linux tools or patterns for automation alongside Windows tools, or explicitly state if only Windows is supported.
- Add a section addressing Linux-specific considerations, such as Hybrid Runbook Worker deployment on Linux machines.
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
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell. All examples, scenarios, and tooling references are centered around PowerShell, the PowerShell Gallery, and Windows-centric workflows. There are no Linux-specific examples, tools, or instructions, and even Python runbooks are mentioned only briefly. Scenarios such as copying files to/from Azure VMs are described only for Windows, with no mention of Linux equivalents. The documentation assumes familiarity with Windows and PowerShell, with no parity for Linux users or Bash/Shell scripting.
Recommendations
- Include Linux-specific examples for common scenarios, such as copying files to/from Linux Azure VMs using SSH or SCP.
- Provide instructions and examples for creating and importing Bash or Python runbooks, not just PowerShell.
- Mention and link to Linux tools and patterns (e.g., Bash scripts, cron jobs, Linux authentication methods) where relevant.
- Ensure that scenarios and tooling references are presented in a cross-platform manner, with Windows and Linux options side-by-side.
- Clarify module compatibility with Linux and PowerShell Core, and provide guidance for Linux users on module selection and usage.
- Add documentation sections or notes specifically for Linux users, highlighting any differences or additional steps required.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-graphical-error-handling.md
...omation/automation-runbook-graphical-error-handling.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 by exclusively referencing PowerShell concepts, cmdlets, and error types. All examples, terminology, and recommended practices are centered around PowerShell and Windows-centric tools (e.g., Write-Warning, Start-AzAutomationRunbook, Start-AzVM). There is no mention of Linux equivalents, Bash scripting, or cross-platform considerations, and the error handling discussion is framed entirely in terms of PowerShell behavior.
Recommendations
- Add examples using Bash or Python activities in graphical runbooks, illustrating error handling for Linux-based automation.
- Discuss error types and handling patterns relevant to Linux environments, such as exit codes and stderr/stdout parsing.
- Reference cross-platform cmdlets or tools, and clarify which features are available on Linux Hybrid Workers.
- Include notes or sections on differences in error handling between Windows and Linux runbook executions.
- Provide links to documentation for Linux automation scenarios and best practices.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-scenario-using-watcher-task.md
...s/automation/automation-scenario-using-watcher-task.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 by exclusively using PowerShell scripts and commands, referencing Windows filesystem paths (e.g., D:\examplefiles), and providing examples only for Windows environments. There are no Linux or cross-platform equivalents mentioned, and the instructions assume the use of Windows tools and conventions throughout. Linux scenarios, such as using Bash or Linux file paths, are entirely omitted.
Recommendations
- Include Linux-specific examples, such as using Bash scripts and Linux file paths (e.g., /home/examplefiles).
- Clarify whether watcher tasks and hybrid runbook workers support Linux hosts, and provide setup instructions for Linux if supported.
- Provide equivalent commands for creating test files on Linux (e.g., using 'touch ExampleFile1.txt').
- Mention cross-platform considerations for runbook authoring, such as using PowerShell Core or Bash.
- Add notes or sections highlighting differences or additional steps required for Linux users.
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 page exclusively uses PowerShell and Az/AzureRM cmdlets for all examples and explanations, which are primarily associated with Windows environments. There are no references to Linux-native tools, Bash, CLI examples, or cross-platform scripting approaches. The guidance, terminology, and code samples are all Windows-centric, with no mention of how Linux users or those using Bash/CLI might manage Azure context switching in Automation runbooks.
Recommendations
- Add equivalent Azure CLI (az) examples for context management and switching, especially for runbooks that might be authored in Bash or Python.
- Explicitly mention cross-platform support for Azure Automation, including how context switching issues manifest and are resolved in Linux-based runbooks.
- Include a section comparing PowerShell and CLI approaches, and clarify which recommendations apply regardless of OS.
- Provide sample Bash or Python runbook code snippets demonstrating context isolation and management.
- Reference Linux tools and patterns (e.g., environment variables, az login, az account set) alongside PowerShell cmdlets.
- Reorder sections or examples so that Windows and Linux approaches are presented with equal prominence.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-overview.md
...in/articles/automation/automation-security-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets as the primary automation interface, mentioning Azure Resource Manager and PowerShell together, and omitting Linux-specific examples or tools. There is no mention of Bash, Linux CLI, or cross-platform scripting approaches. The documentation implicitly assumes a Windows-centric workflow and does not provide parity for Linux users or administrators.
Recommendations
- Include examples and references for Bash, Azure CLI, and Linux shell scripting alongside PowerShell examples.
- Explicitly mention cross-platform support for runbooks, including how to authenticate from Linux-based Hybrid Runbook Workers.
- Provide guidance on using Linux tools (e.g., curl, OpenSSL) for authentication and automation tasks.
- Add documentation sections or notes clarifying how Linux users can perform equivalent operations and where to find relevant resources.
- Ensure that examples and instructions are presented in a platform-neutral order or grouped by platform, rather than defaulting to Windows/PowerShell first.
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
Windows First
Missing Linux Example
Summary
The documentation page is heavily biased toward Windows and PowerShell usage. All code examples and instructions use PowerShell, with explicit references to Windows PowerShell modules and cmdlets. There are no examples or guidance for Linux users, such as using Bash, Azure CLI, or cross-platform scripting. Windows tools and patterns (PSCredential, Get-Credential, PowerShell Gallery) are mentioned exclusively and before any Linux or cross-platform equivalents.
Recommendations
- Add equivalent examples using Azure CLI and Bash for Linux/macOS users.
- Mention cross-platform authentication methods, such as using service principals with Azure CLI.
- Clarify which steps and modules are available on Linux and macOS, and provide links to relevant documentation.
- Include a section comparing PowerShell and Azure CLI approaches for Azure Automation authentication.
- Avoid using 'Windows PowerShell' terminology when referring to cross-platform PowerShell Core, or clarify the distinction.
- Reference Microsoft Graph SDK usage in non-PowerShell environments, such as Python or REST API.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/change-tracking-data-collection-rule-creation.md
...cking/change-tracking-data-collection-rule-creation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing detailed registry settings and a reference JSON script exclusively for Windows file settings, while Linux settings are less detailed and lack equivalent examples. Windows-specific concepts (e.g., registry keys, drive letters) are prominent, and the 'Next steps' link prioritizes Windows tutorials. Linux examples are present but less comprehensive and not given equal prominence.
Recommendations
- Provide a reference JSON script for Linux file settings, similar to the Windows example.
- Include detailed Linux-specific configuration options (e.g., common config file paths, service management patterns) alongside Windows registry settings.
- Balance the documentation by presenting Linux and Windows examples in parallel, rather than focusing first or exclusively on Windows.
- Update 'Next steps' and tutorial links to include Linux-specific guidance and tabs.
- Explicitly mention platform differences and ensure parity in explanation depth for both Windows and Linux.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-local-authentication.md
...in/articles/automation/disable-local-authentication.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 examples and referencing Windows-centric tools (PowerShell cmdlets) for managing Azure Automation authentication settings. There are no examples or guidance for Linux users, such as using curl, bash, or other cross-platform tools to interact with the REST API. The instructions and verification steps are written entirely in PowerShell, which is traditionally associated with Windows environments, and no alternatives for Linux shells or platforms are mentioned.
Recommendations
- Add equivalent REST API usage examples using curl or HTTPie in bash, suitable for Linux and macOS users.
- Include instructions for verifying the disableLocalAuth property using Azure CLI (az) or direct REST calls from Linux.
- Explicitly mention cross-platform options and clarify that PowerShell Core is available on Linux, but provide native bash examples for parity.
- Reorder or parallelize examples so that Linux-friendly methods are presented alongside or before Windows/PowerShell methods.
- Reference documentation for Azure CLI and REST API usage in addition to PowerShell cmdlets.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/disable-managed-identity-for-automation.md
.../automation/disable-managed-identity-for-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and examples using PowerShell cmdlets, which are primarily Windows-centric. There are no equivalent examples for Linux users (e.g., using Azure CLI, curl, or bash scripting), and Windows tools (PowerShell, Az modules) are mentioned exclusively and before any cross-platform alternatives. This creates a bias toward Windows users and leaves Linux users without clear guidance.
Recommendations
- Add equivalent examples using Azure CLI and/or curl for REST API calls, suitable for Linux/macOS environments.
- Include bash script snippets for authentication and request execution.
- Mention cross-platform tools (e.g., Azure CLI) alongside PowerShell, and present them in parallel or before Windows-specific tools.
- Explicitly state that the steps can be performed on Linux/macOS and provide links to relevant cross-platform documentation.
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
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI or Bash examples. The PowerShell instructions are presented before any mention of cross-platform alternatives, and there is no guidance for Linux or macOS users. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell and the Azure portal, without offering parity for Linux environments.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell examples are primarily for Windows users, and provide Bash/CLI alternatives for Linux/macOS users.
- Include instructions for managing Automation accounts using REST API with curl or similar Linux tools.
- Ensure that cross-platform tools and patterns are presented before or alongside Windows-specific ones, rather than after.
- Add a section or tab for Linux/macOS users, detailing steps and commands relevant to those platforms.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/move-account.md
...s/blob/main/articles/automation/how-to/move-account.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 only PowerShell examples for resource deletion and action group removal, referencing Windows-centric tools (PowerShell cmdlets) without mentioning equivalent Azure CLI or REST API commands. The step-by-step instructions and screenshots focus on the Azure portal, which is platform-neutral, but all command-line automation is shown using PowerShell, with no Linux shell or Azure CLI alternatives. This may disadvantage users working primarily on Linux or macOS environments.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, such as resource and action group deletion.
- Explicitly mention that both PowerShell and Azure CLI (and REST API) can be used, and provide links or code samples for each.
- Ensure that command-line instructions are presented in a platform-neutral way, or provide parallel examples for Windows (PowerShell) and Linux/macOS (Azure CLI/bash).
- Where possible, order examples so that platform-neutral or cross-platform tools (e.g., Azure CLI) are shown before or alongside Windows-specific tools.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/how-to/private-link-security.md
...in/articles/automation/how-to/private-link-security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a PowerShell-only example for configuring the 'Public Network Access' property, with no equivalent CLI or Linux-native instructions. PowerShell is a Windows-centric tool, and its exclusive use here suggests a Windows bias. Additionally, the documentation references Windows and Linux agents in parity, but the only explicit command-line example is for PowerShell, and there are no Azure CLI, Bash, or ARM template examples. The documentation also describes PowerShell DSC in the State Configuration section, which is Windows-focused, and does not mention Linux equivalents such as Chef, Ansible, or native Linux DSC support.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash examples for all PowerShell scripts, especially for configuring 'publicNetworkAccess'.
- Include ARM/Bicep template snippets for resource property configuration to support cross-platform automation.
- Mention and provide examples for Linux-native configuration management tools (e.g., Ansible, Chef) or clarify Linux DSC support.
- Ensure that any references to agents, configuration, or automation steps are accompanied by both Windows and Linux instructions where applicable.
- Consider reordering or balancing examples so that Linux and Windows are presented with equal prominence.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/create-azure-automation-account-portal.md
.../quickstarts/create-azure-automation-account-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal (web UI) to create an Automation account, which is cross-platform. However, the 'Next steps' section directs users to a PowerShell runbook tutorial, implying a Windows-centric automation approach. There are no references to Linux tools, Bash, or cross-platform scripting alternatives, and PowerShell is mentioned as the default next step for automation, which can be perceived as Windows-first and PowerShell-heavy bias. No Linux-specific examples or parity guidance are provided.
Recommendations
- Include links to tutorials for creating Automation accounts using Azure CLI and Bash, which are cross-platform and commonly used on Linux.
- Add examples or references for creating and managing Automation accounts using REST API or ARM templates, which are platform-agnostic.
- In the 'Next steps' section, provide parallel tutorials for creating runbooks using Python or Bash, not just PowerShell.
- Explicitly mention that PowerShell can be used cross-platform, but also highlight Linux-native options for automation.
- Ensure that screenshots and instructions do not imply Windows-only usage, and clarify that the Azure portal is accessible from any OS.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runtime-environment.md
...main/articles/automation/manage-runtime-environment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell as the primary scripting language, referencing Windows PowerShell modules and patterns, and providing examples and instructions that are PowerShell-centric. Windows tools (e.g., PowerShell Gallery, Az PowerShell module, Get-Module cmdlet) are mentioned and used extensively, while Linux-specific tools, patterns, or examples are either absent or only briefly referenced (e.g., Python packages for Linux). The documentation lacks parity in examples and guidance for Linux users, especially in terms of package management, scripting, and troubleshooting.
Recommendations
- Provide equivalent Linux/bash examples alongside PowerShell instructions, especially for common automation tasks.
- Include guidance on using Azure CLI and bash scripts as first-class citizens, not only as add-ons to PowerShell environments.
- Reference Linux package formats (e.g., .tar.gz, .deb, .rpm) and repositories (e.g., PyPI, system package managers) where appropriate.
- Offer troubleshooting steps and module/package management examples for Linux environments, not just PowerShell.
- Clarify when instructions or screenshots are Windows-specific and provide Linux alternatives where possible.
- Highlight Python and Azure CLI as cross-platform automation options, with equal detail and prominence as PowerShell.