Automation
123
Total Pages
24
Linux-Friendly Pages
99
Pages with Bias
80.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
982 issues found
Showing 476-500 of 982 flagged pages
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 strong bias towards Windows and PowerShell environments. Most examples, screenshots, and REST API payloads focus on PowerShell runbooks and the Az PowerShell module. Windows/PowerShell-specific tooling and patterns (such as PowerShell Gallery, .zip modules, and Get-Module cmdlet) are described in detail, while Linux/Python equivalents are only briefly mentioned or omitted. There is minimal guidance for Python or Linux-based automation, and Linux-specific package management is only referenced in passing.
Recommendations
- Provide parallel, detailed examples for Python runbooks, including REST API payloads and portal workflows.
- Include Linux-specific instructions and screenshots, such as uploading .whl files, using pip, or viewing installed Python packages.
- Mention and demonstrate the use of Azure CLI and Python modules with the same depth as PowerShell/Az modules.
- Reorder sections or examples to present PowerShell and Python/Linux options equally, rather than PowerShell/Windows first.
- Clarify when instructions or features are specific to Windows/PowerShell versus cross-platform or Linux/Python.
- Add troubleshooting and best practices sections for Python/Linux automation scenarios.
Create Pull Request
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md
...e-docs/blob/main/articles/automation/delete-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The only scripting interface shown is PowerShell, which is most familiar to Windows users. Additionally, the structure and ordering of examples consistently present PowerShell before any mention of CLI, and in some cases, CLI is not mentioned at all. There is no guidance for Linux users or those preferring Bash or Azure CLI, and no mention of Linux-native tools or workflows.
Recommendations
- Add Azure CLI examples alongside all PowerShell commands, using Bash syntax where appropriate.
- Where possible, provide both PowerShell and CLI tabs for all command-line operations.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Ensure that instructions and screenshots are not Windows-specific and clarify that the Azure portal is platform-agnostic.
- Review the ordering of examples so that PowerShell and CLI are presented with equal prominence, or alternate their order.
- Consider including a section or note for Linux/macOS users to highlight any platform-specific considerations.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md
.../troubleshoot/extension-based-hybrid-runbook-worker.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In general troubleshooting steps and scenarios, Windows examples, tools, and paths are consistently listed before Linux equivalents. Several scenarios provide detailed PowerShell-based instructions and registry edits for Windows, while Linux instructions are less detailed or missing for similar cases (e.g., registry permissions, event log checks). Windows-specific tools (e.g., PowerShell scripts, registry, event logs) are referenced without always providing Linux analogs or guidance. Some troubleshooting steps and resolutions are Windows-only, with no Linux equivalent provided.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them in parallel, to avoid always listing Windows first.
- Where PowerShell or Windows registry/event log instructions are given, provide equivalent Linux commands or log file locations (e.g., systemd journal, syslog, Linux file permissions).
- For troubleshooting tools, ensure Linux scripts/utilities are described with the same level of detail as Windows (e.g., how to run, interpret output).
- For scenarios that are Windows-specific (e.g., registry, UAC), clarify that they do not apply to Linux, and consider adding Linux-specific troubleshooting scenarios where relevant.
- Where only Windows event logs are referenced, include Linux logging equivalents (e.g., journalctl, /var/log/messages) for parity.
- Ensure that all steps for installation, troubleshooting, and uninstallation are equally detailed for both platforms.
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 demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples are presented as the only scripting/automation option, and the documentation does not mention or prioritize Linux-native tools or workflows. The structure and examples assume a Windows-centric approach, potentially excluding Linux users or those preferring cross-platform tools.
Recommendations
- Add Azure CLI examples (az automation account delete, az monitor log-analytics solution delete, etc.) alongside PowerShell for all relevant operations.
- Include Bash shell snippets where appropriate, especially for users on Linux or macOS.
- When listing command-line options, present Azure CLI before or alongside PowerShell to avoid the impression of Windows-first bias.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider providing REST API examples using curl or httpie for users who prefer direct API calls.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing only Windows browser UI elements).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md
...b/main/articles/automation/automation-runbook-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows and PowerShell bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in much greater detail than Python or Linux-specific options. Many examples, sample scripts, and troubleshooting steps reference Windows file paths (e.g., C:\modules), Windows environment variables, and Windows-specific behaviors. There is little to no coverage of Linux-specific runbook authoring, execution, or troubleshooting, and no Linux shell (bash) examples are provided. Even where Linux is mentioned (e.g., Hybrid Runbook Workers), details are minimal compared to the extensive PowerShell/Windows coverage.
Recommendations
- Add Linux-specific examples and troubleshooting steps, especially for Hybrid Runbook Workers running on Linux.
- Provide parity in sample scripts, such as showing how to manage modules, file paths, and environment variables on Linux (e.g., using /opt, $HOME, or /tmp instead of C:\ paths).
- Include bash or Python shell examples where appropriate, not just PowerShell.
- Clarify which features and limitations apply to Linux Hybrid Runbook Workers, and document any Linux-specific constraints or workarounds.
- Reorder or balance the presentation so that Python and Linux options are not always secondary to Windows/PowerShell.
- Explicitly mention Linux support (or lack thereof) in each runbook type's description and limitations.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-webhooks.md
...s/blob/main/articles/automation/automation-webhooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for creating, using, and managing webhooks are provided exclusively in PowerShell, with no equivalent Bash, curl, or CLI examples for Linux or cross-platform users. Windows/PowerShell tools and cmdlets (e.g., Invoke-WebRequest, Get-Content, Az Module) are used throughout, and there is no mention of Linux-native tools or workflows. Even REST API usage is shown only via PowerShell. The documentation does not address how to perform these tasks from a Linux environment or with cross-platform tools, and the PowerShell-first approach may hinder accessibility for non-Windows users.
Recommendations
- Provide equivalent examples using Bash and curl for all webhook operations (creation, invocation, deletion, etc.), especially for REST API calls.
- Include Azure CLI (az) command examples for creating and managing Automation webhooks, as Azure CLI is cross-platform.
- Show how to use common Linux tools (e.g., jq, curl, wget) to interact with webhooks and parse responses.
- Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
- Where PowerShell is required (e.g., for runbook code), clarify that PowerShell Core is available cross-platform and provide notes on any differences.
- Add a section or callouts for Linux/macOS users, outlining any prerequisites or differences in workflow.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-use-azure-ad.md
...ob/main/articles/automation/automation-use-azure-ad.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and module references using Windows PowerShell cmdlets and patterns. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. Windows-specific tools and classes (e.g., PSCredential, Get-Credential) are mentioned exclusively, and the documentation does not acknowledge or provide alternatives for Linux environments.
Recommendations
- Add equivalent Azure CLI (az) examples for all major steps, such as authentication, credential management, and resource management, to support Linux and macOS users.
- Include Bash or Python script examples for common automation tasks, demonstrating how to interact with Azure Automation and Microsoft Entra ID from non-Windows platforms.
- Explicitly mention cross-platform options and clarify which steps or modules are Windows-only, providing links or references to Linux-compatible alternatives.
- Reorganize sections to present cross-platform or CLI approaches alongside PowerShell, rather than only after or not at all.
- Reference documentation for Azure CLI and SDKs in the 'Next steps' section, not just PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md
...b/main/articles/automation/automation-runbook-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric technology) in both structure and content. PowerShell runbooks are described first and in the most detail, with extensive examples and troubleshooting based on Windows file paths (e.g., C:\modules). Many examples and known issues reference Windows-specific patterns, such as environment variables and file paths, with little or no equivalent Linux guidance. The documentation also references Windows tools and concepts (e.g., PowerShell Workflow, graphical runbooks based on Windows PowerShell) and often omits or minimizes Linux-specific details, especially for hybrid worker scenarios. Python runbooks receive less coverage, and Linux-specific instructions or examples are sparse or missing.
Recommendations
- Provide Linux-specific examples and troubleshooting steps alongside or before Windows examples, especially for hybrid worker scenarios.
- Avoid using only Windows file paths (e.g., C:\modules); include Linux equivalents (e.g., /opt/automation/modules) where relevant.
- Clarify which features and limitations apply to Windows, Linux, or both, particularly for hybrid runbook workers.
- Expand Python runbook documentation to include Linux-specific package management, environment setup, and known issues.
- Where PowerShell is discussed, explicitly note cross-platform capabilities and provide Linux usage notes or caveats.
- For graphical and workflow runbooks, clearly state platform support and provide alternatives or workarounds for Linux users.
- Ensure that all code samples, troubleshooting steps, and environment variable references are presented for both Windows and Linux contexts.
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 steps by providing a clear PowerShell example and direct guidance for Windows VMs, while Linux remediation is described in less detail, lacks direct script examples, and is presented as less supported (e.g., 'you don't have the option of using the Run command'). Windows tools and cmdlets are referenced directly, while Linux solutions are only linked or described in passing.
Recommendations
- Provide a direct Linux command-line example (e.g., Bash or Python) for remediating drift, similar to the PowerShell example for Windows.
- Clarify and expand on the Linux remediation process, including step-by-step instructions and sample scripts.
- Reference Linux-native tools and workflows explicitly, not just through external links.
- Present Windows and Linux remediation sections with equal prominence and detail.
- If certain features (like Run Command) are unavailable for Linux, suggest alternative Azure-native or open-source solutions, and explain any workarounds.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md
...g-agent-based-hybrid-worker-to-extension-based-workers.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a Windows bias in several ways: (1) Windows-specific examples and tools (e.g., PowerShell, Windows registry paths) are provided first or exclusively in key sections, especially in the Bicep, ARM template, PowerShell, and removal instructions. (2) There is a lack of equivalent Linux-focused examples for core automation scenarios (e.g., Bicep/ARM templates and PowerShell/CLI commands are tailored to Windows VMs and extensions, with no Linux VM or extension examples). (3) PowerShell is heavily featured, with less emphasis on bash or Linux-native scripting. (4) Windows-specific requirements and tools (e.g., .NET Framework, Windows PowerShell 5.1) are highlighted, while Linux requirements are less detailed or are presented as secondary.
Recommendations
- Provide Linux-specific examples alongside Windows examples for Bicep, ARM templates, REST API, Azure CLI, and PowerShell sections. For instance, show how to deploy a Linux VM and install the HybridWorkerForLinux extension.
- Ensure that Linux commands and requirements are given equal prominence and detail as Windows, including bash scripts and Linux-native automation tools.
- When listing prerequisites, present Windows and Linux requirements in parallel, and avoid listing Windows first by default.
- For PowerShell-heavy sections, provide equivalent bash or shell script examples for Linux users.
- Clarify when a step or tool is Windows-only, and always provide the Linux alternative immediately after or in a side-by-side format.
- In code samples and parameter tables, include Linux OS options and extension types (e.g., HybridWorkerForLinux) wherever Windows options are shown.
- Expand the removal instructions for Linux to include cleanup of all related components, matching the detail provided for Windows.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-graphical-authoring-intro.md
...les/automation/automation-graphical-authoring-intro.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows PowerShell and PowerShell Workflow, with all examples, terminology, and workflows centered around PowerShell cmdlets and scripting. There is no mention of Linux, Bash, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide parity or guidance for Linux users or those using non-Windows environments.
Recommendations
- Explicitly state that Azure Automation graphical runbooks are currently limited to PowerShell and clarify platform support (e.g., Windows-only or cross-platform PowerShell Core).
- If Linux support is available (e.g., via PowerShell Core on Linux), provide examples and guidance for Linux users, including any differences in cmdlet availability or behavior.
- Include a section comparing graphical runbooks with textual runbooks, highlighting scenarios where Bash, Python, or other languages (supported in Azure Automation) may be preferable, and link to relevant documentation.
- Mention any limitations or considerations for Linux-based Automation workers, if applicable.
- Where possible, provide cross-platform PowerShell examples (using PowerShell Core syntax) and clarify when examples are Windows-specific.
- Add references or links to documentation for authoring and running runbooks in other languages (Bash, Python) for users who do not use PowerShell.
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 First
Missing Linux Example
Windows Tools
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 any explicit mention of Linux tools, Bash, or cross-platform scripting examples. There are no Linux-specific authentication workflows, nor are there examples or guidance for Linux users. The documentation assumes a Windows-centric approach to automation, both in terminology and in the tools referenced.
Recommendations
- Include examples of authenticating and automating tasks using Bash, Azure CLI, or Python scripts, not just PowerShell.
- Explicitly mention that Azure Automation supports both Windows and Linux Hybrid Runbook Workers, and provide parity in examples.
- Add sections or notes describing how Linux users can authenticate and interact with Azure Automation, including any differences in setup or permissions.
- Reference cross-platform tools (e.g., Azure CLI) alongside PowerShell, and avoid presenting Windows tools or patterns first or exclusively.
- Provide links to Linux-specific or cross-platform documentation where appropriate.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-secure-asset-encryption.md
...icles/automation/automation-secure-asset-encryption.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 providing only PowerShell examples for all command-line operations, referencing PowerShell modules and cmdlets exclusively, and omitting equivalent instructions for Linux environments (such as Azure CLI or Bash). Windows-centric tools and patterns are mentioned first and often exclusively, with no parity for Linux-native workflows.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Include Bash script examples where appropriate, especially for automation scenarios.
- Mention both PowerShell and CLI options in prerequisites and throughout the documentation, not just PowerShell.
- Clarify that PowerShell can be used cross-platform, but also highlight native Linux workflows.
- Add a section or callouts for Linux/macOS users, ensuring they can follow the same procedures without relying on Windows tools.
Automation
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-based runbooks and Windows-centric tools (such as the Az PowerShell module and cmdlets like Start-AzAutomationRunbook). All examples are in PowerShell, and there is no mention of Linux-native scripting (e.g., Bash, Python) or cross-platform approaches. The documentation assumes the use of Windows/PowerShell patterns and does not provide parity for Linux users or those preferring non-PowerShell automation.
Recommendations
- Add equivalent examples using Python and Bash runbooks, which are supported in Azure Automation.
- Include references to Linux-based scripting environments and clarify which features are available for non-PowerShell runbooks.
- Mention and provide examples for starting and managing runbooks using the Azure CLI (az automation runbook ...), which is cross-platform.
- Reorganize sections to mention cross-platform options (Python, Bash, Azure CLI) alongside or before Windows/PowerShell-specific tools.
- Clarify any limitations or differences in behavior for non-PowerShell runbooks (e.g., parameter passing, job output retrieval).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-output-and-messages.md
...s/automation/automation-runbook-output-and-messages.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/PowerShell bias. All code examples, tool references, and explanations are exclusively based on Windows PowerShell cmdlets and patterns. There are no examples or guidance for Linux-based automation, Bash, or Python runbooks (except for a brief note about Python output language support). Retrieval of runbook output is only shown using Windows PowerShell tools, and preference variables are discussed only in the context of PowerShell. No Linux-native or cross-platform CLI (such as Azure CLI) equivalents are provided.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for retrieving runbook output and managing jobs, which work cross-platform.
- Include Bash or Python runbook examples where applicable, especially in sections discussing output and message streams.
- When referencing tools or commands, mention cross-platform options (e.g., Azure CLI, REST API) alongside or before Windows PowerShell.
- Clarify which features or behaviors are specific to PowerShell-based runbooks versus those available in Python or other supported runbook types.
- Provide links to documentation for managing Azure Automation from Linux/macOS environments.
- If certain features are only available in PowerShell runbooks, explicitly state this and suggest alternatives for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-disaster-recovery.md
...in/articles/automation/automation-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a significant Windows and PowerShell bias. All migration scripts and automation examples are provided exclusively in PowerShell, with no mention of Bash, Python, or cross-platform scripting alternatives. The instructions for Hybrid Runbook Worker installation and management link first (and sometimes only) to Windows-specific tabs or documentation. There are no Linux-specific or cross-platform code samples, and the required modules and runtime environments are all Windows/PowerShell-centric. This creates an impression that Linux users are secondary or unsupported, despite the initial claim of Linux VM applicability.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or at least reference cross-platform alternatives if available.
- Include explicit Linux examples and instructions, especially for Hybrid Runbook Worker deployment and management.
- Ensure that documentation tabs and links are balanced, offering both Windows and Linux options side-by-side.
- Mention and support cross-platform modules or tools (such as Azure CLI) where possible, not just PowerShell/Az modules.
- Clarify any limitations or differences for Linux users up front, and provide guidance for achieving parity.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-compile.md
...lob/main/articles/automation/automation-dsc-compile.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows and PowerShell-based workflows for compiling DSC configurations in Azure Automation. All code examples use PowerShell, and there is no mention or example of using Linux-based tools or workflows. Windows-specific modules, cmdlets, and file paths are referenced throughout, and Linux alternatives or cross-platform approaches are not discussed. The documentation assumes a Windows environment and does not address Linux users' needs.
Recommendations
- Add examples using cross-platform PowerShell Core (pwsh) and clarify compatibility with Linux/macOS.
- Explicitly state whether DSC compilation and management is supported on Linux, and if not, provide guidance or alternatives for Linux users.
- If Linux support is deprecated (as hinted by the retirement announcement), clearly highlight this at the top and provide migration paths or alternatives.
- Provide equivalent command-line or scripting examples for Linux environments where possible, or explain limitations.
- Avoid using only Windows file paths (e.g., C:\...) in examples; include Linux-style paths or note platform differences.
- Mention and link to any Linux-native tools or approaches for configuration management if applicable.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-role-based-access-control.md
...les/automation/automation-role-based-access-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and workflows for configuring Azure RBAC and managing role assignments in Azure Automation. There are no examples or instructions using cross-platform tools such as Azure CLI, and no mention of Linux-native workflows or shell environments. The exclusive use of PowerShell and lack of Linux/CLI parity may hinder users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlet instructions, including role assignment, listing, and removal.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide sample bash shell commands.
- Where scripts are shown, offer both PowerShell and bash/CLI alternatives side by side.
- Review references to 'PowerShell' in headings and text, ensuring that cross-platform options are equally visible and not presented as secondary.
- Add a section or note clarifying that Azure Automation and RBAC are fully manageable from any OS using CLI or REST API, not just Windows/PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md
...e-docs/blob/main/articles/automation/delete-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples are presented as the only scripting/automation option, and the documentation refers to 'Azure PowerShell' before mentioning the Azure CLI or REST API (which are only mentioned in passing in the introduction). There are no Linux-specific instructions or examples, and no mention of running commands in Bash or on Linux/macOS platforms.
Recommendations
- Add Azure CLI examples (az commands) alongside PowerShell for all automation and deletion tasks.
- Include Bash shell examples where appropriate, especially for cross-platform users.
- When listing options (e.g., Azure portal, PowerShell, CLI, REST API), present Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly state that all command-line examples work on Windows, Linux, and macOS where applicable, and clarify any platform-specific limitations.
- Provide links or references to documentation for using Azure Automation with Linux environments, if available.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-getting-started.md
.../articles/automation/automation-dsc-getting-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All code examples use Windows PowerShell DSC syntax and resources (such as WindowsFeature), and there are no Linux configuration examples. The only VM creation link is for Windows, and references to DSC documentation and resources are Windows-centric. Linux is only mentioned in passing, with no practical guidance or parity in examples.
Recommendations
- Provide parallel Linux examples, such as a sample DSC configuration using the nx or nxFile resource for Linux nodes.
- Include links to both Windows and Linux VM creation guides in the prerequisites.
- Reference both Windows and Linux DSC documentation in the overview and next steps.
- Clarify which features and steps apply to Linux, and note any differences or limitations.
- If Linux support is deprecated, make this explicit at the start and provide migration or alternative guidance for Linux users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/quickstarts/dsc-configuration.md
...n/articles/automation/quickstarts/dsc-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: it assumes the use of PowerShell syntax throughout, references Windows-centric tools and patterns (such as MOF documents and the PowerShell Gallery), and does not provide Linux-native alternatives or examples. Although the configuration example targets a LAMP stack (Linux), the entire workflow is described using PowerShell DSC constructs, and the documentation explicitly notes that Azure Automation DSC for Linux has been retired, further marginalizing Linux users. There are no Bash or Linux-native configuration examples, and next steps reference Chocolatey, a Windows package manager.
Recommendations
- Provide parity for Linux users by including examples using native Linux configuration management tools (such as Ansible, Chef, or native Azure Policy Guest Configuration for Linux).
- Offer Bash or shell script equivalents for steps currently described only in PowerShell.
- Clarify the current support status for Linux and direct users to up-to-date, supported alternatives for Linux VM configuration.
- When referencing tools like Chocolatey, also mention Linux package managers (e.g., apt, yum) or cross-platform solutions.
- Reorganize the documentation to avoid assuming PowerShell as the default, and explicitly state when steps are Windows-only.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-dsc-overview.md
...ob/main/articles/automation/automation-dsc-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows and PowerShell bias. PowerShell DSC is the only configuration language discussed, and examples or references are almost exclusively Windows-centric. Windows operating systems are listed first and in detail, while Linux support is referenced generically and with less detail. Windows-specific tools and patterns (e.g., WinRM, WMF, PowerShell cmdlets, Chocolatey) are mentioned without Linux equivalents or examples. There are no Linux-specific walkthroughs or examples, and Linux support is often described as an afterthought.
Recommendations
- Provide Linux-specific examples for onboarding, configuration, and troubleshooting, including sample commands and scripts.
- List Linux operating systems and their requirements with the same level of detail as Windows.
- Include references to Linux-native configuration tools or patterns where appropriate (e.g., systemd, shell scripts, or integration with Linux package managers).
- Offer parity in documentation structure: for every Windows/PowerShell example or tool mentioned, provide the Linux equivalent or clearly state limitations.
- Highlight any differences or limitations in Linux support up front, and keep Linux-specific retirement or deprecation notices clearly separated from general documentation.
- Add a Linux-focused 'Next steps' or quickstart guide, similar to the Windows/PowerShell guidance.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-managing-data.md
...b/main/articles/automation/automation-managing-data.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by providing more detailed and prominent guidance for Windows users, especially around TLS configuration and data backup. Windows-specific tools (PowerShell cmdlets) are referenced repeatedly, often without Linux or cross-platform equivalents. Linux guidance is present but less detailed and sometimes appears after Windows instructions. Several examples and instructions are Windows-centric, with Linux alternatives either missing or less emphasized.
Recommendations
- Provide Linux command-line (bash, shell) examples alongside or before Windows/PowerShell examples for all relevant operations (e.g., exporting runbooks, managing DSC nodes).
- Reference cross-platform tools (such as Azure CLI or REST API) where possible, rather than only PowerShell cmdlets.
- Ensure Linux-specific instructions are as detailed and actionable as Windows instructions (e.g., for TLS configuration, provide distro-specific guidance and verification steps).
- Balance the order of presentation: alternate between Windows and Linux, or group by platform, rather than always listing Windows first.
- Where Windows registry or PowerShell is referenced, provide equivalent Linux file or command references (e.g., for confirming TLS settings).
- Explicitly mention if a feature or operation is not available or differs on Linux, to avoid ambiguity.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/change-tracking/enable-change-tracking-at-scale-policy.md
...nge-tracking/enable-change-tracking-at-scale-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation claims support for both Windows and Linux VMs, but throughout the page, there is a clear Windows-first bias. Windows-specific features (like Registry and Software tracking) are highlighted in the introduction, and the policy breakdown lists 'Configure ChangeTracking Extension for Windows virtual machines' before the Linux equivalent. There are no Linux-specific examples, screenshots, or mentions of Linux-specific tracked items (e.g., Linux packages or configuration files), and all screenshots and UI references are generic or Windows-centric. No Linux command-line or configuration examples are provided.
Recommendations
- Include explicit Linux examples, such as tracking Linux package changes or configuration files.
- Balance the order of presentation: alternate or group Windows and Linux instructions equally, or start with Linux in some sections.
- Add screenshots or UI references that show Linux-specific tracking (e.g., tracking /etc files or installed packages).
- Mention Linux-specific tracked items and clarify parity or differences in feature support.
- If command-line or scripting examples are provided, ensure both PowerShell (Windows) and Bash (Linux) examples are included.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for creating and managing connections use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. The section for creating a new connection specifically references 'Windows PowerShell' and provides only PowerShell examples. There is no guidance or example for users working from Linux or macOS environments. The documentation also refers to Windows-centric patterns and tools (e.g., PowerShell cmdlets, DSC configurations) before mentioning Python, and does not provide parity for Linux/CLI workflows.
Recommendations
- Add Azure CLI examples for creating and managing connections, suitable for Linux/macOS users.
- Include Bash script examples where appropriate, especially for automation scenarios.
- Clarify that PowerShell examples can be run cross-platform (if true), or provide equivalent instructions for non-Windows environments.
- Mention and link to any Linux-compatible tools or modules for Azure Automation.
- Rephrase headings and instructions to be OS-neutral (e.g., 'Create a new connection with the command line' instead of 'with Windows PowerShell').
- Ensure that all workflows (creation, management, retrieval of connections) have both PowerShell and CLI/Bash examples.
- Explicitly state platform support and any limitations for Linux/macOS users.