Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 226-250 of 2185 flagged pages
Azure Docs
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 focused on Windows and PowerShell, with all examples and references centered around Windows PowerShell DSC and related tools. There is no mention of Linux equivalents or examples, and the tools and community projects referenced (ReverseDSC, SharePointDSC) are Windows-specific. Linux onboarding is only referenced via a link, with no substantive guidance or parity in the main content.
Recommendations
- Add explicit examples and workflows for Linux servers, including how to extract configurations and generate MOF files from Linux systems.
- Reference and link to Linux DSC resources (such as OMIGODSC or native Linux DSC support) alongside Windows resources.
- Clarify in the introduction and steps which parts of the process are Windows-only and provide alternative instructions or links for Linux users.
- Include at least one end-to-end Linux example, or clearly state current limitations if Linux is not supported.
- Balance references to Windows and Linux onboarding in the main body, not just in the links section.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-child-runbooks.md
...main//articles/automation/automation-child-runbooks.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 (e.g., Start-AzAutomationRunbook, PowerShell Workflow), with all examples and guidance provided exclusively in PowerShell syntax. There is no mention of Linux/Unix shell scripting, Python runbooks, or cross-platform approaches. Windows/PowerShell patterns and modules are presented as the default and only option, with no Linux or non-PowerShell alternatives discussed.
Recommendations
- Add equivalent examples using Python runbooks, which are supported in Azure Automation and are cross-platform.
- Include references to Bash or other Linux shell scripting options where applicable, or explicitly state their support status.
- Clarify which features and cmdlets are available or behave differently on Linux Hybrid Runbook Workers.
- Balance the documentation by providing Linux-first or at least parallel Linux examples alongside PowerShell/Windows ones.
- Mention any limitations or differences for Linux users up front, and provide links to Linux-specific guidance if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-dsc-overview.md
...b/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 heavily on PowerShell DSC (a Windows-centric technology), listing Windows operating systems and requirements before Linux, referencing Windows-specific tools and features (such as WMF, WinRM, and Chocolatey), and providing more detailed configuration and proxy support instructions for Windows than for Linux. Linux support is mentioned, but examples, details, and parity in guidance are lacking.
Recommendations
- Provide equal prominence to Linux in all sections, including listing supported Linux distributions explicitly alongside Windows versions.
- Include Linux-specific examples and configuration steps, not just references to external documentation.
- Offer parity in technical detail for Linux, such as explicit instructions for proxy configuration, agent installation, and troubleshooting.
- Mention Linux tools and package managers (e.g., apt, yum) where Windows tools like Chocolatey are referenced.
- Balance the use of PowerShell-centric language with references to cross-platform or Linux-native configuration management tools where possible.
- Ensure screenshots and UI walkthroughs include Linux node scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-dsc-cd-chocolatey.md
...n//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 toward Windows environments. All examples, tooling, and workflows are Windows-centric, relying exclusively on PowerShell, Windows Server, Chocolatey (a Windows package manager), and Windows-specific DSC resources. Linux is only mentioned in passing, and no Linux equivalents, examples, or tools are provided. There are no instructions or code samples for Linux systems, nor is there guidance for achieving similar outcomes on Linux platforms.
Recommendations
- Provide parallel Linux-focused examples using native Linux tools (e.g., apt, yum, or snap) and configuration management solutions (e.g., Ansible, Chef, or Puppet) where possible.
- Include sample workflows for setting up continuous deployment on Linux VMs, possibly using Azure Automation State Configuration with Linux-compatible DSC resources or alternatives.
- Explicitly mention the current limitations or retirement status for Linux support, and offer migration or alternative guidance for Linux users.
- Balance the narrative by introducing Linux concepts and tools alongside Windows ones, rather than only referencing Linux in passing.
- Where PowerShell is used, provide Bash or shell script equivalents for Linux scenarios.
- If Azure Automation State Configuration is no longer supporting Linux, provide links to recommended alternatives for Linux configuration management in Azure.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/tutorial-create-assignment-python.md
...ticles/automanage/tutorial-create-assignment-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating a Windows virtual machine, omitting Linux VM creation steps. Additionally, the PowerShell examples and references to Windows-specific tools are presented alongside Azure CLI, but there is no mention of Linux-specific considerations or examples. The Azure CLI installation link defaults to the Windows tab, and the VM creation uses a Windows image without offering a Linux alternative.
Recommendations
- Add parallel examples for creating a Linux virtual machine (e.g., using --image UbuntuLTS in Azure CLI and the equivalent in PowerShell).
- Include a section or tab for Linux-specific instructions, such as SSH key setup and Linux admin username conventions.
- Ensure Azure CLI installation instructions are cross-platform, or at least link to Linux/macOS installation guides equally.
- When referencing PowerShell, clarify that it is available cross-platform, or provide Bash alternatives where appropriate.
- Use neutral language and ordering (e.g., 'Create a Windows or Linux virtual machine') to avoid implying Windows is the default or only supported OS.
Azure Docs
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 references centered around Windows PowerShell DSC. There is no mention of Linux equivalents or cross-platform DSC usage, and the prerequisites and links are all Windows/PowerShell-specific. Linux onboarding is only referenced in a link, with no substantive guidance or examples provided.
Recommendations
- Add explicit examples and guidance for configuring data at scale with Linux nodes, including how to use DSC on Linux.
- Include references to cross-platform PowerShell Core where applicable, and clarify which steps are Windows-only versus cross-platform.
- Provide Linux command-line examples (e.g., Bash, PowerShell Core on Linux) alongside Windows/PowerShell examples.
- Mention and link to Linux DSC documentation and resources, not just Windows PowerShell DSC.
- Clarify in the prerequisites and applicability section whether the solution is Windows-only or can be used with Linux, and provide parity in instructions if possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-dsc-compile.md
...ob/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 tooling for compiling DSC configurations in Azure Automation. All code examples use Windows PowerShell, and Windows-specific cmdlets and modules are referenced exclusively. There are no examples or guidance for Linux users or cross-platform PowerShell Core usage. Windows tools and patterns are mentioned first and often exclusively, with no mention of Linux equivalents or considerations.
Recommendations
- Provide examples using PowerShell Core (pwsh), which is cross-platform, and clarify which steps work on Linux/macOS.
- Include explicit notes about Linux support status, especially in light of the referenced Linux retirement announcement.
- If Linux compilation is deprecated, clearly state this at the top and provide migration guidance for Linux users.
- Where possible, offer alternative workflows for Linux users (e.g., using Azure CLI, REST API, or other cross-platform tools).
- Add a section or callout summarizing platform support and any differences in workflow between Windows and Linux.
- Ensure that any references to file paths, modules, or commands are either cross-platform or have Linux/macOS equivalents provided.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-set-up-dev-tunnels.md
...ob/main//articles/dev-box/how-to-set-up-dev-tunnels.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias: it references Windows-specific tools (such as Windows App, Remote Desktop client, and WSL) without mentioning Linux or macOS alternatives. All remote connection examples and troubleshooting steps are framed in the context of Windows environments, and there are no instructions or screenshots for connecting from Linux or macOS clients. The only mention of Linux is via WSL, which is a Windows feature, not native Linux.
Recommendations
- Add explicit instructions and screenshots for connecting to Dev Box tunnels from Linux and macOS clients using VS Code.
- Mention and provide examples for remote connection methods available on Linux/macOS (e.g., SSH, VS Code Remote SSH extension).
- When listing connection methods (browser, Windows App, Remote Desktop client), include cross-platform options such as 'Remote Desktop clients for Linux/macOS' or 'open-source RDP clients'.
- Provide parity in troubleshooting steps for users on Linux and macOS.
- Avoid assuming WSL is the only way to use Linux tools; mention native Linux environments as well.
Azure Docs
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 Linux-specific examples, tools, or guidance, and all linked resources and next steps are Windows/PowerShell oriented. Linux is only mentioned in passing as a possible onboarding target, with no further details or parity in configuration guidance.
Recommendations
- Include equivalent Linux configuration guidance, such as using DSC for Linux or alternative tools (e.g., Chef, Ansible) for STIG compliance.
- Provide Linux-specific examples for configuring STIG baselines, including sample configurations and MOF generation for Linux nodes.
- Reference Linux-compatible community projects or modules for STIG compliance, if available.
- Balance 'Next steps' and resource links to include Linux documentation and resources, not just Windows PowerShell DSC.
- Clarify in the introduction whether the guidance is Windows-only, or expand scope to cover Linux scenarios explicitly.
Azure Docs
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-compatible DSC implementations (such as PowerShell Core or cross-platform DSC), nor are there any Linux-specific examples or guidance. Windows-centric tools and workflows (MOF files, PowerShellGet, Windows PowerShell DSC) are referenced exclusively or before any Linux alternatives, and the prerequisites explicitly state applicability to Windows PowerShell 5.1 only.
Recommendations
- Add explicit guidance and examples for Linux environments, including how to use cross-platform PowerShell (pwsh) and DSC on Linux.
- Clarify which steps or tools are Windows-only and provide Linux equivalents where possible.
- Reference and link to documentation for Linux DSC implementations (such as Open Management Infrastructure (OMI) or DSC for Linux).
- Include examples of managing Linux resources (e.g., configuring Apache instead of IIS, managing Linux firewall settings, etc.).
- Update the prerequisites to indicate support for PowerShell Core and/or cross-platform scenarios if available.
- Ensure parity in documentation structure and depth for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-managing-data.md
.../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 demonstrates a Windows bias by frequently referencing Windows-specific tools (such as PowerShell cmdlets), providing detailed instructions for Windows before Linux, and omitting Linux equivalents for some operations. Most backup and export instructions rely on Windows PowerShell cmdlets, and Linux guidance is limited or absent for several tasks.
Recommendations
- Provide Linux CLI (e.g., Azure CLI, Bash) examples alongside or before Windows/PowerShell examples for all operations, such as exporting runbooks and DSC configurations.
- Include Linux-native tools and scripts for managing assets, backing up data, and other Automation account operations.
- Ensure parity in documentation depth and clarity for both Windows and Linux, avoiding the assumption that users are on Windows.
- Where only PowerShell cmdlets are available, explicitly note the lack of Linux alternatives and suggest workarounds or roadmap plans.
- Reorganize sections to avoid always listing Windows before Linux, or present both together in parallel tables or tabs.
Azure Docs
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 oriented towards Windows and PowerShell, with all examples, tools, and migration steps based on Windows technologies. There are no Linux or cross-platform examples, and the use of Windows PowerShell cmdlets and modules is assumed throughout. The documentation does not mention or provide alternatives for Linux users, nor does it discuss how to migrate or run runbooks in Linux environments.
Recommendations
- Include examples and guidance for migrating runbooks that use Python or Bash scripts, which are supported in Azure Automation and are common in Linux environments.
- Document how to use Azure Automation on Linux Hybrid Runbook Workers, including any prerequisites, limitations, or differences from Windows workers.
- Provide equivalent Linux command-line examples (e.g., using Bash or Azure CLI) alongside PowerShell examples.
- Clarify which features or modules are Windows-specific and which are cross-platform, and suggest alternatives for Linux users where possible.
- Mention and link to documentation on authoring and running runbooks in non-Windows environments.
- Highlight any differences in asset or variable management for Linux-based runbooks.
Azure Docs
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, scripts, and workflows are presented using PowerShell and Windows-specific tooling (e.g., WMF 5, PowerShell DSC cmdlets), with Linux instructions either presented later, in less detail, or as adaptations of Windows-centric processes. Linux enablement is often described as an exception or afterthought, and Linux-native workflows are not given equal prominence or clarity. Some Linux steps require using Windows/PowerShell to generate configuration files, and Linux-native equivalents are not always provided.
Recommendations
- Provide Linux-native examples and workflows (e.g., using Bash, Python, or native Linux tools) alongside or before Windows/PowerShell examples.
- Avoid requiring a Windows machine or PowerShell to generate or apply configurations for Linux nodes; document fully Linux-native onboarding and management paths.
- Ensure that Linux-specific tools (such as Register.py and SetDscLocalConfigurationManager.py) are documented with the same level of detail and step-by-step guidance as PowerShell cmdlets.
- Where possible, present Linux and Windows instructions in parallel sections, rather than as exceptions or afterthoughts.
- Clarify any limitations or differences for Linux up front, and provide alternative solutions or workarounds.
- Expand troubleshooting and status-checking sections to include Linux-specific guidance and tools.
Azure Docs
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 exclusively covers Windows operating systems, Windows Management Framework (WMF), and PowerShell DSC, with no mention of Linux support, Linux DSC equivalents, or cross-platform scenarios. All examples, features, and troubleshooting steps are Windows-centric, and Windows tools and patterns are referenced throughout. There is no guidance or parity for Linux users, and the only mention of Linux is in a retirement announcement include, with no technical details or migration advice.
Recommendations
- Add a dedicated section summarizing the history and status of Linux support for the Azure DSC extension, including key dates, feature differences, and deprecation details.
- Provide explicit guidance or migration paths for users managing Linux VMs, such as alternatives (e.g., Azure Automation State Configuration, Azure Policy, or third-party configuration management tools like Ansible, Chef, or Puppet).
- Include references and links to documentation on Linux configuration management in Azure.
- If Linux support is retired, clearly state this at the top of the page and provide a link to the retirement announcement and any relevant migration resources.
- If any versions of the DSC extension supported Linux in the past, document those versions, their features, and any known issues or limitations.
- Avoid using 'DSC' or 'extension' generically when the content is Windows-only—clarify that the information applies to Windows VMs.
- Where possible, provide parity in examples or troubleshooting for both Windows and Linux, or explain the lack thereof.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-dsc-remediate.md
.../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 provides detailed, actionable PowerShell examples for remediating configuration drift on Windows VMs, but offers no equivalent command-line examples for Linux VMs. The Windows remediation section is presented first, with explicit PowerShell cmdlets and links, while the Linux section lacks concrete script examples and instead refers users to external documentation or general processes. Windows tools and patterns (PowerShell, Update-DscConfiguration) are emphasized, while Linux remediation is described as less direct and less supported.
Recommendations
- Provide explicit command-line examples for Linux remediation, such as shell or Python scripts that can be run manually or via custom script extensions.
- Present Windows and Linux remediation steps in parallel, giving equal prominence and detail to both platforms.
- Include references to Linux-native tools or commands (e.g., shell scripts, cloud-init, or Python DSC clients) where appropriate.
- Clarify any feature gaps (such as Run Command support) but offer alternative Linux workflows with step-by-step instructions.
- Ensure that links to Linux documentation are as direct and actionable as those for Windows, ideally including inline code snippets.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-hrw-run-runbooks.md
...in//articles/automation/automation-hrw-run-runbooks.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Windows instructions, tools, and examples are often presented before their Linux equivalents, and some sections (such as credential usage and runbook authentication) provide only PowerShell/Windows-centric examples or omit Linux-specific guidance. Windows tools and patterns (e.g., Control Panel, Windows environment variable setup, Windows file paths, Windows event logs) are described in detail, while Linux instructions are more concise or missing in some cases. PowerShell is the primary language for code samples, with limited or no Bash or Python examples for Linux users.
Recommendations
- Ensure that Linux instructions are presented alongside Windows instructions, not after them, and with equal detail.
- Provide Linux-specific code examples (e.g., Bash, Python) wherever PowerShell examples are given for Windows.
- Include Linux equivalents for all Windows tools and patterns mentioned (e.g., environment variable setup, logging locations, credential management).
- Where Windows file paths or UI navigation are described, provide the corresponding Linux paths or commands.
- Add explicit Linux authentication/runbook examples (e.g., using managed identities, credential assets) where only PowerShell/Windows examples are currently shown.
- Balance the use of PowerShell with examples in Bash or Python, especially for common automation tasks.
- Clarify any features or limitations that are Windows-only or Linux-only, and provide workarounds or alternatives where possible.
Azure Docs
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 workflows centered around PowerShell cmdlets and syntax. There is no mention of Linux, Bash, or cross-platform scripting, and the only scripting language referenced is PowerShell. The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide Linux equivalents or alternatives.
Recommendations
- Explicitly state that graphical runbooks in Azure Automation currently only support PowerShell and PowerShell Workflow, and clarify if/when support for other scripting languages (such as Python or Bash) is planned.
- If Linux or cross-platform support is available or planned, provide equivalent examples using Bash or Python, and reference relevant modules or tools.
- Mention the limitations of graphical runbooks for Linux-based automation, and provide guidance or links for users who wish to automate Linux environments (e.g., using textual Python runbooks or hybrid worker solutions).
- Include a section comparing graphical runbooks with textual runbooks, highlighting cross-platform options and their respective use cases.
- Avoid assuming all users are familiar with Windows PowerShell; provide introductory links or context for users from Linux or non-Windows backgrounds.
Azure Docs
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
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and Windows-centric workflows. All code examples and command-line instructions use Windows PowerShell, with explicit references to Windows file paths (e.g., c:\runbooks) and no mention of Linux, macOS, or cross-platform PowerShell Core (pwsh). There are no examples or guidance for editing runbooks from non-Windows environments, nor any mention of using PowerShell on Linux/macOS or alternative tools.
Recommendations
- Add examples using PowerShell Core (pwsh) on Linux and macOS, including appropriate file path syntax (e.g., /home/user/runbooks).
- Clarify that Az PowerShell modules and Azure Automation can be used cross-platform, and provide instructions for non-Windows environments.
- Avoid using 'Windows PowerShell' as the default term; instead, use 'PowerShell' and specify when something is Windows-specific.
- Include notes or sections on editing and managing runbooks from Linux/macOS, including any limitations or differences.
- Where file paths are shown, provide both Windows and Linux/macOS equivalents.
- Mention or link to Azure CLI or REST API alternatives for users who may not use PowerShell.
Azure Docs
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 demonstrates a moderate Windows bias. While it mentions both Windows and Linux support for Hybrid Runbook Workers, Windows terminology, tools, and patterns (such as PowerShell cmdlets, System account references, and Run As accounts) are more prominent. Windows is often mentioned first, and there is a lack of Linux-specific examples or details (e.g., Linux authentication, Linux-specific deployment nuances, or command-line examples). The documentation references Windows-centric concepts (like the System account and PowerShell Workflow checkpoints) without providing Linux equivalents or clarifications.
Recommendations
- Provide Linux-specific examples and details alongside Windows ones, such as Linux shell commands for deployment, configuration, and troubleshooting.
- When referencing accounts (e.g., System on Windows), also explain the Linux equivalent (e.g., nxautomation) and clarify any behavioral differences.
- Include Linux-native tooling (such as Bash, systemd, or Linux package managers) in onboarding and management instructions, not just PowerShell or Windows tools.
- Ensure that Linux is mentioned equally or first in lists and tables where both platforms are supported.
- Add troubleshooting and operational guidance specific to Linux environments.
- Clarify authentication and permission models for Linux, including managed identities and Run As alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-dsc-diagnostics.md
...ain//articles/automation/automation-dsc-diagnostics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The prerequisites and setup steps assume the use of the Az PowerShell module, and there is no guidance for users on Linux or macOS platforms. The documentation does not acknowledge or provide alternatives for non-Windows environments, despite Azure Automation State Configuration supporting Linux nodes in the past.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Explicitly state platform compatibility for each step and tool, and mention any limitations or deprecations for Linux support.
- Include a section or callout for Linux/macOS users, outlining any differences in setup or usage.
- Reference Bash or shell scripting alternatives where applicable, especially for authentication and resource management.
- Clarify the current and future support status for Linux nodes in Azure Automation State Configuration, given the included retirement announcement.
Azure Docs
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias. It references Windows-specific DSC resources (e.g., WaitFor resources in the /powershell/dsc/reference/resources/windows/waitForAllResource link) without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or clarifications for Linux-based Hybrid Runbook Workers or DSC nodes, and the only resource link for DSC is to a Windows-specific path. No Linux tools, patterns, or resources are mentioned, and the documentation implicitly assumes a Windows environment for configuration and troubleshooting.
Recommendations
- Include references and links to Linux DSC resources and documentation, such as the Linux DSC resource kit or official Linux agent documentation.
- Provide examples or notes for configuring Hybrid Runbook Worker and State Configuration on Linux nodes, including any differences in network requirements or agent behavior.
- Mention Linux-specific tools or commands where relevant (e.g., using curl or iptables for network testing/configuration).
- Ensure parity in documentation structure by providing both Windows and Linux examples or clarifying when instructions are OS-agnostic.
Azure Docs
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 First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and workflows for managing Azure RBAC in Automation accounts. All command-line instructions use Azure PowerShell cmdlets, with no mention or examples of Azure CLI (cross-platform) or bash scripting. There is no guidance for Linux or macOS users, and the documentation implicitly assumes a Windows/PowerShell environment for automation tasks.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell examples for all RBAC management tasks, including role assignment, listing, and removal.
- Explicitly mention that Azure CLI can be used from Linux, macOS, and Windows, and provide bash script examples where appropriate.
- Where scripts are shown, provide both PowerShell and bash/CLI versions, or link to cross-platform documentation.
- Clarify in introductory sections that both PowerShell and CLI are supported, and provide links to relevant documentation for each.
- Review references to 'PowerShell' in headings and ensure parity with CLI tooling in both content and prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-runbook-authoring.md
...n//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 are listed first in the supported OS matrix, and all directory path examples use Windows-style paths (e.g., C:\abc). The documentation focuses heavily on PowerShell (including Windows PowerShell 5.1), with limited mention of Python and no mention of Bash or Linux-native scripting. There are no Linux/macOS-specific examples, and all configuration and usage patterns (such as changing directories) are described using Windows conventions.
Recommendations
- Provide Linux/macOS path examples (e.g., /home/user/abc) alongside Windows paths.
- List supported operating systems in a neutral or rotating order (e.g., Ubuntu, macOS, Windows) to avoid Windows-first bias.
- Include examples and instructions for Linux/macOS users, such as using the terminal or command palette on those platforms.
- Mention Linux-native tools or shell environments where relevant, and clarify any platform-specific behaviors.
- Expand Python-related documentation and provide parity in debugging and usage instructions for non-PowerShell runbooks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-troubleshoot-dev-box-task-view.md
...icles/dev-box/how-to-troubleshoot-dev-box-task-view.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, referencing only Windows-specific features (Task view, Registry Editor, Windows App) and providing no Linux or cross-platform alternatives or troubleshooting steps. All instructions, tools, and UI references are exclusive to Windows, with no mention of Linux or macOS support or equivalent workflows.
Recommendations
- Clarify early in the documentation whether Task view and the Windows App are available or relevant on non-Windows platforms (Linux, macOS).
- If the dev box feature is accessible from Linux or macOS, provide equivalent troubleshooting steps for those platforms, such as how to remove stale connections or cached entries.
- If the Windows App is cross-platform, include installation, removal, and troubleshooting steps for Linux and macOS (e.g., using package managers or command-line tools).
- If certain features (like registry edits) are Windows-only, explicitly state this and provide guidance for users on other platforms.
- Consider adding a section or callout for Linux/macOS users, even if only to state current limitations or to link to platform-specific documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/how-to/move-account.md
.../blob/main//articles/automation/how-to/move-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only PowerShell examples for command-line operations (such as deleting resources and action groups), without any equivalent Azure CLI or Bash examples. The use of PowerShell cmdlets (Remove-AzResource, Remove-AzActionGroup) caters primarily to Windows users, and there is no mention or demonstration of Linux-native tools or workflows.
Recommendations
- Add equivalent Azure CLI examples (az resource delete, az monitor action-group delete, etc.) alongside PowerShell examples for all resource management tasks.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide Bash-friendly command snippets where appropriate.
- Ensure that screenshots and step-by-step instructions are platform-neutral or include notes for both Windows and Linux users.
- Consider including a table or section that compares PowerShell and Azure CLI commands for common tasks in this workflow.