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 276-300 of 2185 flagged pages
Azure Docs
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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows and PowerShell examples are consistently presented first or exclusively, especially in code samples, Bicep, and ARM template sections. PowerShell is the primary automation language shown, with little to no equivalent Bash or Linux-native scripting. The Bicep and ARM template examples only provision Windows VMs, and the documentation for extension installation and management focuses on Windows tools and paths, with Linux guidance often minimal or missing. Linux-specific instructions are less detailed, and Linux examples are sometimes absent or only mentioned as alternatives.
Recommendations
- Provide Linux-first or parallel Linux examples alongside Windows examples in all sections, including code, Bicep, and ARM templates.
- Include Bash or shell script examples for Linux, not just PowerShell.
- Expand Bicep and ARM template samples to show how to deploy Linux VMs and install the Hybrid Worker extension for Linux.
- Ensure that Linux-specific requirements, troubleshooting, and operational steps are as detailed as those for Windows.
- Where PowerShell is used for both platforms, clarify cross-platform compatibility or provide native alternatives.
- List Linux tools, paths, and configuration steps with the same prominence as Windows equivalents.
- Review all 'how-to' steps and ensure Linux parity in portal, CLI, and API instructions.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/quickstarts/create-azure-automation-account-portal.md
.../quickstarts/create-azure-automation-account-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal UI to create an Automation account and does not provide any command-line examples. The only 'Next steps' link is to a PowerShell runbook tutorial, which is Windows-centric. There are no references to Linux tools, Bash, or cross-platform scripting, and no mention of Linux or macOS workflows. This creates a subtle Windows bias by implying PowerShell is the default or only automation method, and by omitting Linux alternatives.
Recommendations
- Include links to both PowerShell and Bash/Azure CLI tutorials for next steps, ensuring parity for Linux users.
- Mention that Automation runbooks can be authored in multiple languages (PowerShell, Python, etc.), and provide links to Linux-friendly examples.
- Add a 'Next steps' section with links to creating Python runbooks or using the Azure CLI to manage Automation accounts.
- Explicitly state that the Azure portal is cross-platform and accessible from any OS, and provide guidance for users who prefer command-line tools on Linux/macOS.
- Balance references to PowerShell with equivalent Linux-native tools or scripts where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/context-switching.md
...cs/blob/main//articles/automation/context-switching.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page is heavily focused on Azure PowerShell cmdlets and provides only PowerShell-based examples and recommendations. It exclusively references Windows-centric tools and patterns (such as PowerShell cmdlets like Add-AzAccount, Disable-AzContextAutosave, and Get-AzVM) without mentioning or providing equivalent guidance for Linux users or those using Azure CLI, Python SDK, or other cross-platform tools. There are no Bash, Azure CLI, or non-Windows scripting examples, and the terminology assumes a PowerShell context throughout.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for context management and resource access, showing how to handle context switching in Bash or other shells.
- Include a section or code snippets for Python SDK or REST API usage to demonstrate cross-platform automation approaches.
- Explicitly mention that the guidance applies to PowerShell and provide links or references to Linux or cross-platform alternatives.
- Rephrase sections to use neutral terminology (e.g., 'script' instead of 'runbook' where appropriate) and clarify when a step is PowerShell-specific.
- Ensure that troubleshooting and error messages include examples that could be encountered when using non-PowerShell tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-troubleshoot-repair-dev-box.md
...articles/dev-box/how-to-troubleshoot-repair-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exclusively discusses troubleshooting Remote Desktop Protocol (RDP) connectivity to dev boxes, referencing Windows-specific concepts such as 'Windows Guest OS readiness' and RDP. There are no examples or guidance for Linux-based dev boxes, nor are alternative remote access protocols (e.g., SSH) mentioned. All troubleshooting steps, checks, and screenshots are tailored to Windows environments, with no Linux parity.
Recommendations
- Include troubleshooting steps and examples for Linux-based dev boxes, such as SSH connectivity issues.
- Mention and document checks relevant to Linux guest OS readiness alongside Windows checks.
- Provide parity in screenshots and instructions for Linux dev boxes, if supported.
- Clarify in the prerequisites or introduction whether the tool and documentation apply only to Windows dev boxes, or expand coverage to include Linux scenarios.
- If the Troubleshoot & Repair tool does not support Linux, explicitly state this and provide alternative troubleshooting guidance for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/graphical-runbook-sdk.md
...lob/main//articles/automation/graphical-runbook-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows and PowerShell. All examples and terminology are based on PowerShell cmdlets and workflows, with no mention of Linux, Bash, or cross-platform scripting. The SDK and its usage are described exclusively in the context of Windows-centric technologies, and there are no Linux or cross-platform alternatives or examples provided.
Recommendations
- Add explicit statements about platform support, clarifying whether the SDK and graphical runbooks are Windows-only or cross-platform.
- If Linux or cross-platform support exists, provide equivalent examples using Bash, Python, or other relevant scripting languages.
- Mention Linux automation tools or patterns (such as Bash scripts, cron jobs, or Azure Automation Hybrid Workers on Linux) where appropriate.
- If the SDK is Windows-only, clearly state this limitation at the beginning of the documentation.
- Include a section comparing Windows and Linux automation capabilities in Azure Automation, and link to Linux-specific documentation if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/how-to/private-link-security.md
...n//articles/automation/how-to/private-link-security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripting examples for configuring Automation account network access, referencing Windows tools and patterns (such as PowerShell Desired State Configuration), and omitting equivalent Linux CLI (e.g., Azure CLI, Bash) or Linux-native configuration examples. While Linux is mentioned as supported in some features, practical Linux usage guidance is missing.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for all resource management tasks, especially for setting properties like publicNetworkAccess.
- Include Bash shell scripting examples where appropriate to complement PowerShell scripts.
- When discussing configuration management (e.g., DSC), clarify Linux support and provide Linux-specific configuration steps or references.
- Ensure that all step-by-step instructions and code snippets are available for both Windows and Linux environments.
- Explicitly mention any differences or limitations for Linux users, and link to Linux-specific documentation where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-webhooks.md
.../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 samples and walkthroughs use PowerShell cmdlets, Windows-style file paths, and Windows-centric tooling (e.g., Az PowerShell module, Invoke-WebRequest, Get-Content). There are no examples using Linux-native tools (such as curl, wget, or bash scripting), nor are there any references to cross-platform or Linux command-line environments. REST API examples are also shown only via PowerShell, not with curl or other common Linux tools. The documentation assumes the user is on Windows or using PowerShell Core, and does not provide parity for Linux users.
Recommendations
- Add equivalent examples using curl or wget for invoking webhooks and REST APIs from Linux/macOS.
- Provide bash or shell script samples for preparing JSON payloads and handling responses.
- Show how to authenticate and interact with Azure using Azure CLI (az) instead of only PowerShell Az module.
- Use platform-agnostic file paths (e.g., forward slashes) or clarify path differences for Windows vs. Linux.
- Explicitly mention that all examples are shown in PowerShell and provide links or tabs for Linux/bash alternatives.
- Include at least one full end-to-end example using only Linux-native tools to demonstrate parity.
Azure Docs
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 demonstrates a strong Windows and PowerShell bias. All code examples use PowerShell cmdlets, with file paths and patterns (e.g., C:\Runbooks\Sample_TestRunbook.ps1) that are Windows-centric. There are no examples using Bash, Azure CLI, or Linux shell scripting. The documentation refers exclusively to PowerShell tools and workflows, and does not mention or provide parity for Linux-native tools or scripting environments. Even when Python is mentioned, it is only in the context of runbook types, not in management or operational examples.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for all PowerShell-based operations, including creating, importing, publishing, and managing runbooks.
- Include Linux-compatible file path examples (e.g., /home/user/Runbooks/Sample_TestRunbook.py) alongside Windows paths.
- Provide Bash or shell script examples for relevant automation tasks, especially for resource checks, job status retrieval, and error handling.
- Explicitly mention and demonstrate how Linux users can author, import, and manage Python runbooks, including using the Azure CLI or REST API.
- Balance the order of presentation so that Linux and cross-platform tools are introduced alongside or before Windows/PowerShell tools.
- Reference Linux-specific considerations (such as permissions, environment variables, and shell differences) where relevant.
- Clarify which features or steps are platform-agnostic versus Windows/PowerShell-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/manage-office-365.md
...cs/blob/main//articles/automation/manage-office-365.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 using Windows PowerShell and related tooling. There are explicit notes that certain cmdlets must be run from Windows PowerShell (not PowerShell Core, which is cross-platform), and no Linux or cross-platform alternatives are provided. The workflow assumes a Windows environment throughout.
Recommendations
- Provide equivalent examples using PowerShell Core (pwsh), and clarify which modules/cmdlets are supported cross-platform.
- Explicitly state any limitations or lack of support for Linux/macOS, and suggest workarounds or alternatives where possible.
- Include instructions for installing and using Microsoft Graph PowerShell on Linux/macOS, or note if it is not supported.
- If Azure Automation supports Python or other cross-platform scripting languages, mention and provide examples.
- Avoid language such as 'Windows PowerShell command prompt' unless the functionality is truly unavailable elsewhere; otherwise, use 'PowerShell' generically.
- Add a section or callout for Linux/macOS users, even if only to clarify current limitations and future roadmap.
Azure Docs
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 is heavily focused on PowerShell-based automation, with all code samples and migration steps provided exclusively in PowerShell. There are no examples or guidance for users who may use Python, Bash, or other scripting languages commonly found in Linux environments. The documentation assumes the use of Windows-centric tools and patterns (such as PowerShell cmdlets and the Azure PowerShell modules), and does not mention or prioritize cross-platform or Linux-native alternatives. This creates a Windows-first bias and may exclude or confuse Linux users.
Recommendations
- Provide equivalent sample scripts for Bash (using Azure CLI) and Python (using Azure SDK), especially for authentication and resource management tasks.
- Explicitly mention that Azure Automation supports Python runbooks and Linux Hybrid Runbook Workers, and provide migration guidance for those scenarios.
- Include references to cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and not just as an afterthought.
- When describing steps or tools, avoid assuming PowerShell as the default; instead, offer parallel instructions for Linux/CLI users.
- Add a section or callout for Linux users, highlighting any differences or additional considerations when migrating from Run As accounts to managed identities.
Azure Docs
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 exclusively uses PowerShell cmdlets and Windows-centric tools (e.g., Az PowerShell, Invoke-Sqlcmd, Hybrid Runbook Worker setup via PowerShell) for all examples and instructions. There are no references to Linux-based automation, Bash, Azure CLI, or cross-platform scripting. The guidance and code samples assume a Windows environment, with no mention of Linux equivalents or how to achieve the same tasks on non-Windows platforms.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for connecting and managing Azure SQL Database, alongside PowerShell examples.
- Explicitly mention that Azure Automation supports Python and Bash runbooks, and provide sample code for those environments.
- Document how to install and use required modules/tools on Linux-based Hybrid Runbook Workers, not just via PowerShell.
- Include notes or sections on differences and considerations for Linux-based automation, such as authentication, environment variables, and module installation.
- Reorder or parallelize examples so that Linux and cross-platform approaches are presented alongside Windows/PowerShell methods, rather than only after or not at all.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/manage-runtime-environment.md
...ain//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 clear bias towards Windows and PowerShell environments. PowerShell is the primary scripting language discussed, with detailed examples and default package support. Windows/PowerShell-specific tools and patterns (such as PowerShell Gallery, Az PowerShell module, and Get-Module cmdlet) are mentioned and exemplified, while Linux or cross-platform alternatives are either referenced only in passing or omitted. Python (the main cross-platform alternative) is mentioned, but with far less detail, and there are no concrete Linux shell or CLI examples. The documentation assumes familiarity with Windows-centric workflows and tools, and Linux-specific guidance is minimal or missing.
Recommendations
- Provide equivalent Linux/bash examples for all operations, especially where PowerShell commands or modules are shown.
- Include examples using Azure CLI (az) in bash, not just PowerShell, and clarify cross-platform compatibility.
- When referencing package uploads, give equal detail for Python (.whl) and Linux-specific packaging, not just PowerShell modules.
- Mention and demonstrate how to manage and inspect Python packages (e.g., using pip or python -m pip list) in runbooks, similar to the Get-Module example for PowerShell.
- Clarify which features and packages are available or behave differently on Linux-based runtime environments.
- Avoid defaulting to PowerShell/Windows terminology (e.g., 'PowerShell Gallery') without also referencing PyPI or other Linux-friendly sources.
- Explicitly state when examples are Windows/PowerShell-specific and provide parallel Linux/Python instructions where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/python-3-packages.md
...cs/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 demonstrates a Windows-first bias. In sections about preparing wheel files for Python 3.8, only Windows instructions are provided first and in detail, while Linux instructions are only given for Python 3.10 (preview). The PowerShell cmdlets for managing Python packages are presented without Linux CLI or Azure CLI equivalents, and there are no Bash or cross-platform examples for package management. The documentation assumes the use of Windows tools and environments in several places, with Linux parity only partially addressed for the newer Python version.
Recommendations
- Provide Linux-based instructions for generating wheel files for Python 3.8, not just for Python 3.10.
- Include Azure CLI or Bash script examples for managing Python packages, alongside or instead of PowerShell cmdlets.
- When listing tools or commands, present both Windows and Linux options, or use cross-platform tools where possible.
- Avoid assuming the user is on Windows by default; clarify when instructions are OS-specific and offer alternatives.
- Highlight any differences in package management workflows between Windows and Linux environments in Azure Automation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/overview.md
.../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 Windows bias by heavily emphasizing PowerShell and Windows-centric tools and patterns. PowerShell and DSC (Desired State Configuration, a Windows technology) are repeatedly mentioned as primary automation mechanisms, with runbook types and modules focused on PowerShell. The 'Modules gallery' section highlights PowerShell Gallery and Microsoft Script Center, both Windows-focused resources, before mentioning Python. Linux support is referenced, but concrete Linux-specific examples, tools, or patterns are missing. The documentation does not provide parity in examples or guidance for Linux users, and Windows technologies are often mentioned first or exclusively.
Recommendations
- Provide Linux-specific examples alongside or before Windows/PowerShell examples, such as Bash or Python runbooks.
- Highlight Linux-native automation tools and patterns (e.g., shell scripts, Ansible, cloud-init) where appropriate.
- Expand the 'Modules gallery' section to include Linux-relevant repositories or resources, not just PowerShell Gallery.
- Clarify that DSC is primarily a Windows technology and provide equivalent Linux configuration management options (e.g., Ansible, Chef, Puppet).
- Ensure all features and scenarios explicitly mention Linux compatibility and provide guidance for Linux environments.
- Balance the order of presentation so that Linux and Windows are given equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/remove-user-assigned-identity.md
...//articles/automation/remove-user-assigned-identity.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-based CLI examples for scripting and REST API calls, referencing Windows-specific tools and cmdlets (e.g., Set-AzAutomationAccount, Invoke-RestMethod), and omitting equivalent examples for Linux users (such as Azure CLI or curl). There are no bash, Azure CLI, or cross-platform scripting examples, and PowerShell is the only automation language shown for command-line operations.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all command-line operations, including removing managed identities and making REST API calls.
- Provide bash/curl examples for REST API interactions to support Linux/macOS users.
- When referencing scripting, present both PowerShell and bash/Azure CLI options, or clearly indicate cross-platform alternatives.
- Avoid assuming the use of PowerShell for verification steps; show how to verify results using Azure CLI or the portal.
- Explicitly mention that PowerShell examples can be run on Linux/macOS with PowerShell Core, or provide native Linux shell alternatives.
Azure Docs
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows and PowerShell are prioritized in examples and tooling, with detailed Bicep and ARM template samples focused exclusively on Windows VMs. PowerShell is heavily featured, and Windows-specific tools and paths are referenced more often and in greater detail than their Linux counterparts. Linux examples are minimal or missing in key sections, such as Bicep/ARM templates and PowerShell/CLI instructions, and Linux-specific nuances are not addressed with the same depth.
Recommendations
- Provide parallel Bicep and ARM template examples for Linux VMs, not just Windows.
- Include Linux-specific PowerShell/CLI commands and examples where applicable, such as using 'HybridWorkerForLinux' in extension installation.
- Ensure that all PowerShell and Azure CLI instructions have Linux equivalents, including any differences in parameters or prerequisites.
- When referencing file paths, permissions, or system requirements, provide both Windows and Linux details side by side.
- Avoid always listing Windows first in tables and instructions; alternate or present both platforms equally.
- Expand the 'Remove agent-based Hybrid Worker' section to include more detailed Linux removal steps, matching the depth of the Windows instructions.
- Explicitly call out any differences or caveats for Linux users in each step, not just in summary tables.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/quickstarts/install-hybrid-worker-extension.md
...omation/quickstarts/install-hybrid-worker-extension.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension selection options reference 'Windows Hybrid Worker' only, with no parallel instructions or visuals for Linux VMs. The prerequisites specifically mention a Windows VM, and there are no Linux-specific examples or guidance provided. Linux support is only mentioned in passing, without actionable steps.
Recommendations
- Add parallel step-by-step instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
- Update the prerequisites section to include both Windows and Linux VMs, or provide separate lists for each platform.
- When listing extension options, mention both 'Windows Hybrid Worker' and 'Linux Hybrid Worker' (if available), and clarify selection for each OS.
- Ensure all configuration and deployment steps are described for both Windows and Linux, including any OS-specific considerations.
- Provide links to Linux-specific troubleshooting and management documentation where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/guest/security.md
...munication-services/concepts/interop/guest/security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing the Microsoft Teams admin center and PowerShell as the primary or sole tools for managing Teams external user policies, without mentioning or providing Linux or cross-platform alternatives. The focus on Microsoft-specific tools and patterns, such as PowerShell and the Teams admin center, implicitly assumes a Windows environment and omits guidance for Linux users.
Recommendations
- Include equivalent command-line or scripting examples for Linux environments, such as using Azure CLI or REST APIs where possible.
- Explicitly mention whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation and usage instructions for non-Windows systems.
- Reference cross-platform management tools (e.g., Azure CLI, web-based portals) alongside or before Windows-specific tools.
- Add a section or note clarifying the options available to Linux users for managing Teams and Azure Communication Services security settings.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/quickstarts/dsc-configuration.md
...//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 exhibits a Windows-centric bias: it uses PowerShell syntax and patterns throughout, references Windows DSC concepts and tooling (such as MOF compilation and PowerShell Gallery), and does not provide Linux-native examples or alternatives. While the example configures a LAMP stack (Linux), the entire workflow is presented through Windows/PowerShell paradigms. Additionally, the documentation explicitly notes that Azure Automation DSC for Linux is retired, but does not offer guidance or parity for Linux users, nor does it mention Linux-native configuration management tools.
Recommendations
- Provide clear guidance for Linux users, including alternatives now that Azure Automation DSC for Linux is retired (e.g., using Azure Policy Guest Configuration, Ansible, or native Linux configuration management tools).
- Include Linux-native examples and workflows, such as using shell scripts, cloud-init, or Ansible playbooks, especially for scenarios like LAMP stack deployment.
- Clarify the limitations and supported platforms for each step, and avoid presenting PowerShell/Windows-centric workflows as the only or primary method.
- Reference and link to Linux-specific documentation or migration guides for users affected by the retirement of Linux DSC.
- Consider restructuring the quickstart to either focus solely on Windows, or to provide parallel instructions for both Windows and Linux users, with clear distinctions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/shared-resources/certificates.md
...//articles/automation/shared-resources/certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All command-line examples for certificate management use PowerShell cmdlets, with no equivalent Bash, Azure CLI, or Linux-native instructions. Windows/PowerShell tools and patterns (e.g., .pfx, ConvertTo-SecureString, X509Certificate2) are referenced exclusively, and PowerShell is presented before Python in both explanations and examples. There are no Linux shell or cross-platform CLI examples for certificate creation, upload, or retrieval.
Recommendations
- Provide Azure CLI examples for certificate management tasks (creation, upload, retrieval) alongside PowerShell examples.
- Include Bash or shell script examples for common certificate operations, especially for Linux users.
- Mention Linux-compatible certificate formats and tools (e.g., OpenSSL) and show how to prepare/upload certificates from Linux environments.
- Reorder or parallelize sections so that PowerShell and cross-platform (CLI, Python) examples are presented with equal prominence.
- Clarify that the PowerShell cmdlets can be used on Linux/macOS via PowerShell Core, if applicable, or provide alternatives.
- Reference Linux-native certificate stores and how to use certificates managed by Azure Automation in Linux-based runbooks or DSC configurations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/start-runbooks.md
...-docs/blob/main//articles/automation/start-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 bias by exclusively providing examples and instructions using Windows PowerShell cmdlets and patterns. There are no examples or guidance for starting runbooks using cross-platform tools such as Azure CLI, Bash, or Python SDKs. The PowerShell approach is presented as the primary or only command-line method, and there is no mention of Linux or macOS environments, nor are Linux-native tools or shell examples provided.
Recommendations
- Add equivalent Azure CLI examples for starting and managing runbooks, including parameter passing and job status retrieval.
- Include Bash shell script examples for Linux/macOS users, especially for API calls using curl or similar tools.
- Mention and provide examples for using the Azure SDKs (e.g., Python, .NET, Java) to start runbooks programmatically from non-Windows environments.
- Clarify that PowerShell Core (pwsh) is cross-platform, and if supported, provide examples that work on Linux/macOS as well as Windows.
- Reorganize sections so that cross-platform or platform-neutral methods (e.g., Azure CLI, REST API) are presented before or alongside Windows-specific tools.
- Explicitly state the platform requirements and alternatives for each method, helping users on Linux or macOS identify suitable options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/runtime-environment-overview.md
...n//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 as the primary or first scripting language, with multiple runtime versions detailed. Azure CLI support is discussed only in the context of PowerShell runbooks, and there are no explicit Linux/bash examples or references. The documentation refers to Windows-centric tools and patterns (PowerShell, .dll files, modules), with little to no mention of Linux-native scripting environments or package types.
Recommendations
- Include examples and explicit support statements for bash/shell scripting in Azure Automation, if supported.
- When listing scripting languages, alternate the order or mention Python/bash first in some sections to avoid 'windows_first' bias.
- Discuss package types and dependencies relevant to Linux environments (e.g., .so files, Linux-native packages) alongside .dll files.
- Clarify whether Azure CLI can be used in Python or bash runbooks, not just PowerShell.
- Provide Linux-specific guidance or examples for managing runtime environments and packages.
- Reference both PowerShell and Python documentation equally in the 'Next steps' section, and consider linking to bash/shell scripting resources if supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/state-configuration/remove-node-and-configuration-package.md
...configuration/remove-node-and-configuration-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Windows-centric tools and workflows. PowerShell cmdlets are mentioned and described in detail, while Linux instructions are more generic and less detailed. Windows methods are often presented first, and Linux steps are sometimes relegated to brief file deletion instructions without equivalent command-line examples or context.
Recommendations
- Provide Linux command-line examples (e.g., using rm for file deletion) alongside PowerShell examples for parity.
- Present Windows and Linux instructions in parallel sections or tabs, rather than listing Windows/PowerShell first.
- Include more detailed Linux-specific guidance, such as commands to unregister nodes or manage configurations, not just file paths.
- Reference Linux-native tools or scripts where applicable, not only PowerShell cmdlets.
- Ensure that Linux instructions are as comprehensive and actionable as their Windows counterparts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/source-control-integration.md
...ain//articles/automation/source-control-integration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows and PowerShell bias. All command-line examples use PowerShell, and there are no Bash, CLI, or Linux-native instructions. The documentation assumes the use of Windows tools (e.g., PowerShell console, PowerShell cmdlets) and does not provide parity for Linux or cross-platform users. Even when discussing prerequisites and troubleshooting, references are made to PowerShell scripting and Windows-centric workflows, with no mention of Linux alternatives or Azure CLI equivalents.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for role assignment and source control configuration.
- Include Bash shell examples for Linux/macOS users, or clarify that the process is cross-platform if applicable.
- Explicitly state platform requirements or limitations (e.g., if PowerShell 7+ or Azure CLI is supported on Linux/macOS).
- Reference Linux/macOS tools and editors in sections discussing encoding or editing runbooks.
- Add a section or note for Linux/macOS users outlining any differences or additional steps required.
- Ensure that screenshots and UI instructions are not Windows-specific where possible, or provide Linux/macOS equivalents if the Azure portal experience differs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/shared-resources/credentials.md
...n//articles/automation/shared-resources/credentials.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows and PowerShell usage. All command-line examples for managing credentials use PowerShell cmdlets, with no mention of Bash, CLI, or Linux-native tools. The workflow and terminology (e.g., PSCredential, cmdlet) are Windows-centric. The only non-Windows examples are for Python runbooks, but there are no Linux shell or cross-platform CLI examples for credential management. The documentation refers to 'Windows PowerShell' explicitly and does not address Linux automation scenarios or tools.
Recommendations
- Add Azure CLI examples for credential asset management, including creation, retrieval, and deletion, to provide parity for Linux and cross-platform users.
- Include Bash shell script examples where applicable, especially for retrieving credentials in runbooks or automation tasks.
- Clarify whether credential management is possible from non-Windows environments and, if so, document the process.
- Avoid using 'Windows PowerShell' as the default terminology; instead, use 'PowerShell' or specify when examples are cross-platform.
- Mention any limitations or differences in credential management when using Linux Hybrid Runbook Workers or cross-platform agents.
- Provide links or references to Linux or cross-platform documentation where available.