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 576-600 of 982 flagged pages
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 and PowerShell bias. All error handling concepts and examples are presented exclusively in terms of PowerShell cmdlets and Windows-centric tools (e.g., Write-Warning, Start-AzVM, Get-AutomationVariable). There is no mention of Linux runbooks, Bash, or cross-platform scripting. The terminology and examples assume the user is working in a Windows/PowerShell environment, with no Linux or cross-platform parity.
Recommendations
- Include examples and explanations for error handling in Linux-based runbooks, such as using Bash or Python activities.
- Mention and demonstrate how error handling works in graphical runbooks that target Linux hybrid workers or use cross-platform scripting languages.
- Provide equivalent Linux tool or command examples (e.g., using shell scripts or Python for error handling and notifications).
- Clarify in the introduction that the guidance is PowerShell-specific, or restructure the documentation to present both Windows/PowerShell and Linux/Bash/Python approaches side by side.
- Reference Azure Automation support for Linux hybrid workers and how error handling differs or is implemented in those scenarios.
Create Pull Request
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 demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric technology) in both order and depth of coverage, providing only PowerShell code examples (with Windows file paths), and referencing Windows-specific tools and environment variables. Linux support is mentioned but not illustrated with examples, and Linux-specific considerations are minimal or absent.
Recommendations
- Provide Linux-specific examples for PowerShell runbooks, including file paths and environment variables relevant to Linux (e.g., /home/user/modules instead of C:\modules).
- Include explicit guidance and troubleshooting steps for running PowerShell and Python runbooks on Linux Hybrid Runbook Workers, not just Windows.
- Balance the order of presentation so that Python and Linux scenarios are not always after PowerShell/Windows; consider parallel sections or tables.
- Where Windows-specific tools or patterns are discussed (e.g., environment variables, file paths), provide Linux equivalents or note differences.
- Add sample Python runbooks that demonstrate both Windows and Linux compatibility, and clarify any OS-specific limitations.
- Highlight any differences in module/package management between Windows and Linux Hybrid Runbook Workers.
- Explicitly state when a feature or limitation applies only to Windows, Linux, or both, to avoid ambiguity.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively uses PowerShell-based examples and workflows, referencing the AWS PowerShell module, PowerShell Gallery, and PowerShell ISE. There are no examples or instructions for using Linux-native tools (such as AWS CLI with Bash or Python scripts), nor is there mention of cross-platform scripting options. The documentation assumes a Windows-centric workflow and does not address Linux users or provide parity in tooling or examples.
Recommendations
- Provide equivalent instructions and examples using the AWS CLI in Bash or Python scripts for Linux users.
- Include steps for importing and using AWS CLI modules in Azure Automation, highlighting cross-platform compatibility.
- Mention and demonstrate how to author runbooks using Python or Bash, not just PowerShell.
- Avoid referencing Windows-specific tools (e.g., PowerShell ISE) as the only option; suggest alternatives like VS Code or cloud-based editors.
- Reorder sections or provide parallel instructions so that Linux and cross-platform options are presented alongside or before Windows-specific ones.
- Explicitly state that Azure Automation supports multiple scripting languages and link to relevant documentation for non-PowerShell options.
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 and PowerShell bias. All command-line examples are provided exclusively using Azure PowerShell cmdlets, with no equivalent examples for Azure CLI, Bash, or other cross-platform tools. The PowerShell sections are always presented first and in detail, while Linux-native or cross-platform approaches are either omitted or only briefly mentioned (e.g., Azure CLI is only referenced in passing for revocation). The documentation assumes the user is familiar with PowerShell and Windows tooling, and there is no guidance for users working on Linux or macOS environments.
Recommendations
- Provide Azure CLI examples for all PowerShell command sequences, including creating and assigning managed identities, configuring Key Vault access policies, and updating Automation account encryption settings.
- Include Bash shell script examples where appropriate, especially for REST API calls using curl.
- Explicitly mention cross-platform compatibility and note any differences in behavior or prerequisites between Windows and Linux/macOS environments.
- Reorganize sections to present PowerShell and CLI examples side-by-side, or clearly label them as 'Windows/PowerShell' and 'Linux/macOS/CLI' to improve discoverability for non-Windows users.
- Expand the 'Revocation of access' section to include full Azure CLI command examples, not just a reference link.
- Add a note early in the document clarifying that all operations can be performed from any OS using Azure CLI or REST, not just PowerShell.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards Windows environments, with exclusive use of PowerShell scripts, Windows-style file paths (e.g., D:\examplefiles), and instructions that assume the use of Windows tools and conventions. There are no examples or guidance for Linux-based Hybrid Runbook Workers, nor are Bash or Linux shell equivalents provided. The only method shown for creating test files is via PowerShell, and all directory references use Windows syntax.
Recommendations
- Include parallel Linux/Bash examples for all PowerShell commands, such as using 'touch' to create files.
- Mention and show Linux file path formats (e.g., /home/user/examplefiles) alongside Windows paths.
- Clarify that Hybrid Runbook Workers can run on Linux, and provide setup and usage instructions for Linux environments.
- Ensure that documentation steps and screenshots are not exclusively Windows-centric; add Linux equivalents where applicable.
- Reference both PowerShell and Bash (or other relevant shells) in runbook authoring and testing sections.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-security-guidelines.md
.../articles/automation/automation-security-guidelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias in its guidance for installing and managing Hybrid Runbook Workers. All referenced installation and management links explicitly use the 'windows' tab, and there is no mention of Linux equivalents or examples. The documentation refers to VM Contributor roles and domain controllers, which are more relevant to Windows environments, and does not provide parity for Linux-based automation scenarios.
Recommendations
- Include explicit instructions and examples for installing and managing Hybrid Runbook Workers on Linux machines, using the appropriate tabs and links.
- Ensure that all referenced links (such as installation guides) provide both Windows and Linux options, and do not default to the Windows tab.
- Mention Linux-specific security considerations (e.g., avoiding installation on critical Linux servers, using sudoers for least privilege) alongside Windows-specific advice.
- Provide examples of runbook execution and authentication for both Windows and Linux Hybrid Workers.
- Review all sections for references to Windows-only tools or concepts and add Linux equivalents where applicable.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/graphical-runbook-sdk.md
...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell, with all examples and terminology referencing PowerShell commands, workflows, and concepts. There is no mention of Linux, Bash, or cross-platform scripting, and the SDK and its usage are described exclusively in the context of PowerShell and Windows-centric workflows.
Recommendations
- Explicitly state whether the SDK and graphical runbooks support Linux Hybrid Runbook Workers or cross-platform execution.
- Provide examples or guidance for authoring graphical runbooks that invoke Bash scripts or Linux commands, if supported.
- Clarify whether the .dll and SDK can be used on non-Windows platforms (e.g., via .NET Core/5/6+ on Linux/macOS), and provide instructions for those environments if possible.
- If Linux is not supported, clearly state this limitation at the top of the documentation.
- Include a table or section comparing Windows/PowerShell and Linux/Bash support for graphical runbooks, so users understand platform compatibility.
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 exhibits a Windows bias by referencing PowerShell cmdlets as the primary method for automation, mentioning Azure Resource Manager and PowerShell together, and omitting equivalent Linux/CLI examples or tools. There is no mention of Bash, Azure CLI, or Linux-specific automation patterns. The language and examples assume a Windows-centric environment, with no guidance for users operating from Linux or cross-platform environments.
Recommendations
- Include equivalent examples using Azure CLI (az) commands alongside PowerShell cmdlets.
- Explicitly mention that runbooks can be authored in Python or Bash, and provide examples for these languages.
- Reference cross-platform tools and patterns, such as Bash scripting or Linux cron integration, where applicable.
- Ensure that instructions for authentication and permissions are not tied exclusively to Windows tools or terminology.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
- Review and update terminology to be platform-neutral (e.g., refer to 'command-line tools' instead of only 'PowerShell').
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-send-email.md
...blob/main/articles/automation/automation-send-email.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All code examples, setup instructions, and tool references are exclusively for PowerShell, with no mention of Bash, Azure CLI, or Linux-based approaches. Windows/PowerShell tools and patterns are presented as the default and only option, with no Linux or cross-platform alternatives provided.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
- Mention that Azure Automation runbooks can also be authored in Python and provide a Python example for sending email via SendGrid.
- Include instructions for installing and using the Azure CLI on Linux/macOS, and show how to perform prerequisite steps (e.g., Key Vault creation, secret management, role assignment) using CLI commands.
- Clarify that the PowerShell examples work cross-platform (if true), or specify any platform limitations.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
- Balance the order of presentation so that Windows/PowerShell and Linux/CLI approaches are given equal prominence.
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, invoking, and managing webhooks use PowerShell cmdlets or scripts, with no equivalent examples for Linux-native tools (such as Bash, curl, or Azure CLI). Even REST API examples are shown using PowerShell's Invoke-RestMethod. There are no Bash, curl, or Azure CLI examples, and the only scripting language shown for interacting with Azure Automation is PowerShell. This makes the documentation less accessible for Linux or cross-platform users.
Recommendations
- Add equivalent examples using Azure CLI for all PowerShell-based operations (creating, updating, deleting webhooks, invoking webhooks, retrieving job output, etc.).
- Provide REST API examples using curl or HTTPie in Bash, not just PowerShell's Invoke-RestMethod.
- Include sample scripts in Bash for preparing JSON payloads and invoking webhooks.
- When showing code tabs, present Azure CLI or Bash/curl examples before or alongside PowerShell, not only after.
- Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
- Where possible, use neutral language (e.g., 'command line' instead of 'PowerShell prompt') and avoid assuming a Windows environment.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/enable-managed-identity-for-automation.md
...s/automation/enable-managed-identity-for-automation.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 and PowerShell usage. All code examples for enabling and using managed identities (including REST API, ARM templates, authentication, and resource access) are provided exclusively in PowerShell, with only a single Python example (and no Bash/CLI/Linux shell examples). Windows tools and paths are referenced first or exclusively in several places, and Linux equivalents are either missing, less detailed, or mentioned after Windows. There are no Azure CLI, Bash, or Linux-native scripting examples for the main workflows, and the documentation assumes PowerShell as the default automation and scripting environment.
Recommendations
- Provide Azure CLI examples for all major workflows (enabling managed identity, assigning roles, authenticating, accessing resources) alongside PowerShell.
- Include Bash/shell script examples for REST API calls and token retrieval, especially for Linux-based Automation accounts.
- When referencing file paths or commands for both Windows and Linux Hybrid Runbook Workers, present them in parallel and with equal detail.
- Add Python and/or Bash examples for accessing Azure Key Vault, SQL Database, and other resources using managed identity, not just PowerShell.
- Avoid assuming PowerShell as the default; explicitly state when an example is PowerShell and offer alternatives for Linux users.
- Where possible, use cross-platform tools (e.g., Azure CLI, REST via curl) in examples to ensure parity.
- Review and update all sections to ensure Linux and cross-platform users can follow the documentation without needing to translate PowerShell to their environment.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/extension-based-hybrid-runbook-worker-install.md
...ation/extension-based-hybrid-runbook-worker-install.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. PowerShell is used as the primary scripting example throughout, including for Linux scenarios, rather than native Linux tools or shell scripts. Windows-specific tools, paths, and patterns (such as C:\ paths, Windows PowerShell, .NET Framework, and registry keys) are referenced frequently and often before or instead of Linux equivalents. The Bicep and ARM template examples are exclusively for Windows VMs, with no Linux VM deployment examples. Linux-specific guidance is minimal or absent in several sections, especially for automation and extension management.
Recommendations
- Provide native Linux shell (bash) examples for all automation and extension installation steps, especially where PowerShell is currently used for Linux.
- Include Bicep and ARM template examples for deploying Hybrid Runbook Worker extensions to Linux VMs, not just Windows.
- When listing requirements, tools, or commands, present Linux and Windows options side-by-side, or alternate which platform is shown first.
- Reference Linux file paths, permissions, and troubleshooting steps wherever Windows equivalents are given (e.g., folder permissions, uninstall instructions, proxy settings).
- Clarify when PowerShell Core is required on Linux, and provide installation and usage guidance for bash or Python where possible.
- Expand troubleshooting and management sections to include Linux-specific issues, logs, and commands.
- Ensure all code samples, especially in REST, CLI, and scripting, show both Windows and Linux extension types and relevant settings.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-runbooks.md
...-docs/blob/main/articles/automation/manage-runbooks.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 code examples are provided exclusively in PowerShell, with no Bash, Python, or cross-platform CLI equivalents. File paths and script references use Windows conventions (e.g., C:\Runbooks\), and there is no mention of Linux shell environments or tools. The documentation assumes the use of Windows tooling and patterns throughout, omitting guidance for Linux users or those preferring cross-platform automation approaches.
Recommendations
- Provide equivalent examples using Azure CLI (az), Bash, or Python where possible, especially for common tasks such as creating, importing, publishing, and retrieving runbooks.
- Include Linux-friendly file path examples and clarify that runbooks can be authored and managed from Linux/macOS environments.
- Mention and demonstrate cross-platform tools and workflows (e.g., using az CLI, REST API, or SDKs) alongside PowerShell.
- Explicitly state platform requirements or limitations, and offer guidance for users working from Linux or macOS.
- Balance the order of presentation so that Windows/PowerShell and Linux/CLI approaches are given equal prominence.
- Add notes or links to resources for Linux users, such as how to install and use Azure CLI or Python SDK for automation tasks.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/manage-sql-server-in-automation.md
...articles/automation/manage-sql-server-in-automation.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 automation and scripting examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. Instructions for module installation and hybrid worker setup are PowerShell-specific, and there are no Linux or cross-platform alternatives provided. The documentation assumes a Windows-centric workflow throughout.
Recommendations
- Provide equivalent examples using Azure CLI (az) and Bash scripts for connecting and managing Azure SQL databases.
- Include instructions for installing required modules or packages on Linux-based Hybrid Runbook Workers, not just via PowerShell.
- Mention and demonstrate how to use Azure Automation with Python runbooks, which are supported and cross-platform.
- Explicitly state cross-platform compatibility where applicable, and clarify any Windows-specific requirements.
- Reorder or balance the presentation so that Linux and cross-platform methods are given equal prominence to PowerShell/Windows approaches.
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 demonstrates a clear bias towards Windows and PowerShell environments. Most examples, especially for creating and managing runbooks and runtime environments, focus on PowerShell, with detailed steps and REST API payloads referencing PowerShell modules (e.g., Az PowerShell, Get-Module). Windows/PowerShell-specific packaging (.zip, PowerShell Gallery) is emphasized, while Linux/Python equivalents are only briefly mentioned or relegated to notes. There are no concrete Linux shell or Python-centric examples, and Windows tools and conventions are referenced before or instead of Linux alternatives.
Recommendations
- Provide equivalent, detailed examples for Python runbooks, including REST API payloads and portal workflows.
- Include explicit Linux/Python packaging instructions and examples (e.g., using .whl files, pip, or Linux shell commands) alongside PowerShell/Windows instructions.
- Balance the documentation by presenting Python/Linux options before or alongside PowerShell/Windows options, rather than as afterthoughts or notes.
- Add screenshots and walkthroughs for Python runbooks and Linux-based runtime environments, not just PowerShell.
- Reference Linux/Python package repositories (e.g., PyPI) and tools (e.g., pip) where appropriate, not just PowerShell Gallery.
- Clarify when instructions or features are platform-specific, and provide parity where possible.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/migrate-run-as-accounts-managed-identity.md
...automation/migrate-run-as-accounts-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a strong bias toward Windows and PowerShell environments. All code samples, migration steps, and runbook examples exclusively use PowerShell cmdlets and scripts, with no mention of Linux shell (Bash), Python, or cross-platform automation approaches. The documentation assumes the use of Windows-centric tools and workflows, such as PowerShell modules (Az, AzureRM), and does not provide equivalent guidance or examples for Linux-based Automation accounts or hybrid workers running on Linux. The order and language also assume PowerShell as the default, reinforcing a Windows-first perspective.
Recommendations
- Add equivalent examples using Azure CLI (az) and/or Python SDK for runbook authentication and resource management, demonstrating how to migrate from Run As accounts to managed identities in Linux-based runbooks.
- Include sample scripts for Bash and Python runbooks, showing how to authenticate with managed identities and perform common automation tasks.
- Explicitly mention support for Linux hybrid runbook workers, and provide migration guidance and troubleshooting steps specific to Linux environments.
- Clarify in prerequisites and migration steps that both Windows and Linux runbook environments are supported, and link to platform-specific documentation where appropriate.
- Balance the order of presentation so that cross-platform or Linux-native tools (e.g., Azure CLI, Python) are mentioned alongside or before PowerShell, to avoid reinforcing a Windows-first mindset.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/overview.md
...s/azure-docs/blob/main/articles/automation/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-centric tools (such as DSC) are mentioned more frequently and in greater detail than their Linux equivalents. PowerShell is referenced as the primary automation language, with only secondary mention of Python. The configuration management section focuses exclusively on PowerShell DSC, with no mention of Linux-native configuration management tools or approaches. Examples and scenarios often reference Windows-specific technologies (e.g., Active Directory, SQL Server, SharePoint) before or instead of Linux alternatives. There is a lack of explicit Linux-focused examples, tools, or guidance, despite claims of heterogeneous support.
Recommendations
- Provide equal prominence to Linux automation tools and scripting languages (e.g., Bash, Python) alongside PowerShell.
- Include Linux-native configuration management options or clarify how DSC applies to Linux systems.
- Add Linux-specific examples and scenarios, such as automating package management, service management, or configuration on Linux VMs.
- Mention Linux equivalents to Windows technologies referenced (e.g., reference LDAP or Samba alongside Active Directory, PostgreSQL/MySQL alongside SQL Server).
- Ensure that documentation for modules, galleries, and shared resources includes Linux-relevant content and examples.
- Clarify any limitations or differences in feature support between Windows and Linux environments.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/remove-user-assigned-identity.md
...n/articles/automation/remove-user-assigned-identity.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/Powershell bias. All command-line examples use Powershell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. Even REST API usage is shown via Powershell's Invoke-RestMethod, and variable paths use Windows-style backslashes. There are no Linux or cross-platform command-line examples, and Powershell is assumed as the default scripting environment throughout.
Recommendations
- Add equivalent Azure CLI examples for all operations, including authentication, resource modification, and verification.
- Provide Bash shell examples for REST API calls using curl, including how to obtain an access token with Azure CLI.
- Use platform-neutral variable naming and file path conventions, or show both Windows and Linux path styles.
- Explicitly mention that Powershell examples are for Windows (and optionally for cross-platform Powershell Core), and provide Linux/macOS alternatives.
- In sections where Powershell is used to verify results, also show how to do this with Azure CLI (e.g., az automation account show).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-3-packages.md
...ocs/blob/main/articles/automation/python-3-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, particularly in the sections on preparing wheel files for Python 3.8, where only Windows instructions are provided initially and in more detail. PowerShell cmdlets are heavily featured for package management, with no equivalent CLI or bash examples for Linux users. Windows-specific terminology and tools are referenced before Linux equivalents, and Linux guidance is only provided for the Python 3.10 (preview) scenario. There are no Linux/CLI examples for managing packages, and the PowerShell-centric approach may alienate Linux users.
Recommendations
- Provide equivalent Linux (bash/CLI) instructions for preparing wheel files for Python 3.8, not just for Python 3.10.
- Include Azure CLI examples for all package management tasks currently shown only with PowerShell cmdlets.
- When describing architecture or platform requirements, mention both Windows and Linux environments together, rather than prioritizing Windows.
- Add explicit Linux-based examples for Hybrid Runbook Worker scenarios, including how to prepare and upload packages from Linux.
- Where possible, use cross-platform tools (e.g., Azure CLI, REST API) in examples, or provide both PowerShell and bash/CLI alternatives.
- Review and balance screenshots and terminology to ensure Linux users are equally represented.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/python-packages.md
...-docs/blob/main/articles/automation/python-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates Windows bias by providing explicit instructions and command-line examples only for Windows environments (e.g., using Windows 64-bit machine and Windows-style pip invocation), while omitting equivalent Linux or cross-platform instructions. There are no Linux or macOS examples or notes, and Windows tools and paths are mentioned exclusively.
Recommendations
- Include Linux/macOS equivalents for all command-line instructions, such as pip usage and file paths.
- Provide cross-platform guidance or clarify when steps are Windows-specific.
- Add a note or section addressing how to perform the same tasks on Linux (e.g., using 'pip download' on Linux/Mac, and where to find the downloaded files).
- Avoid using only Windows-style paths (e.g., C:\Python27\Scripts\pip2.7.exe); instead, show both Windows and Unix-style commands.
- Mention any platform-specific requirements or differences explicitly to help non-Windows users.
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 demonstrates a Windows bias in several ways: Windows examples and tools (such as PowerShell and Windows-specific registry paths) are presented first or exclusively in key sections, especially in the Bicep and ARM template examples, which only show Windows VM creation and extension installation. PowerShell is heavily featured, while Linux command-line or scripting examples are minimal or absent for core tasks. Some operational steps (like folder permissions and extension installation) reference only Windows paths or tools, and Linux equivalents are either missing or less detailed.
Recommendations
- Provide parallel Linux examples for all automation, scripting, and deployment scenarios (e.g., show how to deploy the Hybrid Worker extension to a Linux VM using Bicep/ARM templates, Azure CLI, REST API, and PowerShell).
- In code samples and step-by-step instructions, present both Windows and Linux paths, commands, and configuration details side-by-side or in clearly separated tabs.
- Include Linux-specific operational guidance, such as required folder permissions, service management, and troubleshooting steps, matching the detail provided for Windows.
- When listing tools or onboarding channels (e.g., PowerShell, Azure CLI), ensure Linux-friendly tools and workflows are given equal prominence and detail.
- Avoid presenting Windows instructions or tools before Linux equivalents unless there is a technical reason; strive for parity in ordering and depth.
- Expand the 'Remove agent-based Hybrid Worker' and other operational sections to provide more comprehensive Linux removal and cleanup steps, including agent uninstallation and configuration file cleanup.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/whats-new.md
.../azure-docs/blob/main/articles/automation/whats-new.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell by consistently prioritizing PowerShell runbooks, mentioning PowerShell versions and features before Python or Linux equivalents, and providing examples and feature announcements that focus on PowerShell and Windows-centric tools. Linux and Python support are mentioned, but often as secondary or afterthoughts, and there are few, if any, Linux-specific examples or guidance.
Recommendations
- Ensure that all feature announcements and examples include both PowerShell and Python (or Bash) runbook scenarios, with equal prominence.
- When discussing runbook support, mention Python and Linux support alongside PowerShell and Windows, not after.
- Provide Linux-specific guidance, examples, and migration paths where appropriate (e.g., for Hybrid Runbook Workers, show both Windows and Linux installation/migration steps).
- Highlight cross-platform capabilities and tools (such as Azure CLI in Bash) equally with PowerShell.
- Where scripts or GitHub resources are referenced, include both PowerShell and Python/Bash versions, or clarify cross-platform compatibility.
- Audit the documentation for sections that implicitly assume a Windows/PowerShell environment and revise to be OS-agnostic or to provide Linux parity.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/runtime-environment-overview.md
...in/articles/automation/runtime-environment-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. PowerShell is consistently mentioned first and in greater detail than Python, with specific focus on PowerShell versions and features. The Azure CLI is only discussed in the context of PowerShell 7.4, with no mention of Bash or Linux-native scripting environments. There are no examples or references for Linux shell scripting, and the only default packages highlighted are Az PowerShell and Azure CLI (as used from PowerShell). The documentation does not provide parity for Linux users or those using Bash or other Unix shells.
Recommendations
- Include examples and explanations for using Azure CLI in Bash or Linux-native environments, not just PowerShell.
- List Bash or shell scripting as a supported language if applicable, or clarify its support status.
- Provide Linux-centric package examples (e.g., pip for Python, apt/yum for system packages) alongside PowerShell examples.
- Mention and document any Linux-specific runtime environments or limitations, if they exist.
- Ensure that references and links are balanced between PowerShell and Python, and add links to Bash or Linux scripting documentation where relevant.
- Explicitly state if certain features are Windows/PowerShell-only, and suggest Linux alternatives if available.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/source-control-integration.md
...main/articles/automation/source-control-integration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. The prerequisites and configuration steps assume the use of PowerShell consoles, and references to file encoding issues point to PowerShell/VSCode documentation. There are no Linux or cross-platform command-line examples, and the documentation does not address how users on Linux or macOS systems might perform equivalent tasks.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, especially for assigning roles and configuring source control.
- Include explicit instructions and examples for Linux/macOS users, such as using Bash or cross-platform shells.
- Reference cross-platform tools and workflows (e.g., Azure CLI, REST API via curl) alongside PowerShell.
- When discussing file encoding issues, link to general encoding best practices or Linux/macOS-specific guidance, not just PowerShell/VSCode.
- Ensure that screenshots and UI walkthroughs do not assume a Windows environment where not necessary.
- Clearly state platform compatibility and any limitations for Linux/macOS users at the start of the documentation.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/tutorial-configure-servers-desired-state.md
...automation/tutorial-configure-servers-desired-state.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All code examples use PowerShell cmdlets and Windows-specific DSC resources (e.g., WindowsFeature IIS). The prerequisites and instructions focus exclusively on Windows VMs, with no Linux-specific examples or guidance. References and links are also Windows/PowerShell-centric, and there is no demonstration of managing Linux nodes or using Linux-compatible DSC resources.
Recommendations
- Add parallel examples for onboarding and configuring Linux VMs, including sample configurations using Linux DSC resources (e.g., nxFile, nxPackage).
- Include prerequisites and instructions for Linux VMs, such as supported distributions and required packages.
- Provide Bash/CLI examples where possible, or at least reference how Linux users can interact with Azure Automation State Configuration.
- Clarify in the introduction and throughout the document whether Linux is still supported, especially in light of the included retirement announcement.
- Link to documentation specifically about managing Linux nodes with Azure Automation State Configuration, if still supported.