Automation
232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
365 issues found
Showing 101-125 of 365 flagged pages
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/credentials.md
...in/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 page exhibits a strong Windows bias, primarily focusing on PowerShell cmdlets and workflows. All command-line examples are given in PowerShell, with no mention of Linux shell equivalents or cross-platform CLI tools. Windows-specific tools and patterns (e.g., PSCredential, PowerShell modules) are referenced exclusively and before Python alternatives. There are no bash, Azure CLI, or Linux-native examples for credential management, and the documentation does not address Linux automation scenarios.
Recommendations
- Add equivalent examples using Azure CLI (az) for credential management, which is cross-platform and works on Linux.
- Include bash or shell script examples for common credential operations, such as retrieving secrets from Azure Key Vault.
- Clarify which features and cmdlets are available or not available on Linux-based hybrid workers, and provide guidance for Linux users.
- Mention Python and other cross-platform SDKs earlier in the documentation, not only after extensive PowerShell coverage.
- Provide a comparison table of credential management approaches for Windows (PowerShell), Linux (bash/Azure CLI), and Python.
- Explicitly state any platform limitations or differences in credential asset usage between Windows and Linux environments.
Create Pull Request
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 bias by exclusively using PowerShell and Az PowerShell cmdlets for all automation and database management examples. There are no references to Linux-native tools, Bash, or cross-platform scripting alternatives. Instructions for installing modules and configuring Hybrid Runbook Workers assume a Windows environment (elevated PowerShell prompt), and no Linux-specific guidance or examples are provided. The documentation also references Windows environment variables and patterns before any mention of Linux equivalents.
Recommendations
- Include equivalent Bash or Azure CLI examples for connecting and managing Azure SQL databases, especially for runbooks that can run on Linux Hybrid Workers.
- Provide instructions for installing required modules and configuring Hybrid Runbook Workers on Linux systems, including package manager commands and environment setup.
- Reference cross-platform scripting options (e.g., Python, Azure CLI) where possible, and clarify which steps or modules are Windows-specific.
- Add notes or sections highlighting Linux compatibility and differences, such as environment variables, shell commands, and module installation.
- Ensure that all code samples and instructions are clearly marked as Windows-specific if they do not apply to Linux, and provide Linux alternatives where feasible.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation shows evidence of Windows bias. Windows tools and patterns (such as PowerShell cmdlets) are heavily featured for managing Python 3.8 packages, with no equivalent Linux CLI or Bash examples provided. In the section on building wheel files, the Windows workflow is described in detail for Python 3.8, while the Linux workflow is only described for Python 3.10. PowerShell cmdlets are used exclusively for package management tasks, and there are no examples using Azure CLI, Bash, or cross-platform tools. This may disadvantage Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent Linux/Bash/Azure CLI examples for all PowerShell cmdlets shown, especially for common tasks like adding, listing, updating, and removing Python packages.
- When describing workflows (such as building wheel files), always present both Windows and Linux instructions side by side, or clearly indicate platform-specific differences.
- Avoid using Windows-specific terminology or tools as the default or only option; introduce cross-platform or Linux-first alternatives where possible.
- Explicitly mention when a feature or workflow is only available on Windows, and provide guidance for Linux users.
- Add a section summarizing cross-platform support and recommended tools for both Windows and Linux users.
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
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses PowerShell scripts and cmdlets (Connect-AzAccount, Get-AzResourceGroup, etc.) for all examples and migration steps, which are native to Windows and commonly used in Windows environments. There is no mention of Linux shell equivalents (such as Azure CLI/bash), nor are there examples for Linux-based automation workers. All tooling and migration scripts referenced are PowerShell-based, and the workflow assumes familiarity with Windows/PowerShell patterns. No Linux-first or cross-platform guidance is provided.
Recommendations
- Add equivalent Azure CLI (az) examples for authentication and resource management using managed identities, suitable for Linux and cross-platform environments.
- Include guidance and sample scripts for runbooks written in Python or Bash, which are supported in Azure Automation and commonly used on Linux.
- Explicitly mention how Linux-based hybrid runbook workers can authenticate using managed identities, with step-by-step instructions.
- Reference cross-platform tools and patterns (such as az CLI, REST API usage) alongside PowerShell, and avoid assuming PowerShell as the default.
- Reorder examples or provide tabs for both Windows/PowerShell and Linux/CLI approaches, ensuring parity and discoverability 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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias by exclusively using PowerShell syntax and DSC modules (e.g., nx), referencing the PowerShell Gallery, and relying on Windows-centric tools and workflows. Although the configuration example targets a LAMP stack (Linux), all instructions and code are written in PowerShell, and there is no mention of Linux-native tools or workflows. The documentation also notes that Azure Automation DSC for Linux has been retired, further marginalizing Linux users.
Recommendations
- Provide equivalent examples using Linux-native configuration management tools (e.g., Ansible, Chef, or native shell scripts) where possible.
- Include instructions for configuring Linux VMs using the recommended Azure Guest Configuration feature, with Linux-specific workflows and code samples.
- Clarify in the prerequisites and introduction that the documented approach is now Windows-centric due to the retirement of Linux DSC, and direct Linux users to supported alternatives.
- If PowerShell is still recommended for Linux, provide explicit instructions for installing and using PowerShell Core on Linux, and clarify any limitations.
- Update the 'Next steps' section to include Linux-relevant resources or migration guides for users affected by the retirement of Linux DSC.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell cmdlets, which are native to Windows and not commonly used on Linux. There are no examples using Azure CLI, Bash, or other Linux-native tools. Even REST API usage is shown via PowerShell scripts. Windows tools and patterns are mentioned exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
- Add equivalent Azure CLI examples for all operations, as Azure CLI is cross-platform and commonly used on Linux.
- Provide Bash shell script examples for REST API calls using curl or similar tools.
- Mention and demonstrate how to perform these tasks on Linux/macOS environments, including authentication and file handling.
- Where PowerShell is used, clarify that it is available cross-platform, but also offer alternatives for users who prefer native Linux tools.
- Ensure that verification steps (such as checking identity type) are shown using Azure CLI as well as PowerShell.
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 bias by prioritizing PowerShell as the primary scripting language, referencing multiple PowerShell versions, and focusing on Windows-centric tools such as PowerShell and Azure CLI in the context of PowerShell. There is a lack of Linux-specific examples, tools, or guidance, and the documentation does not mention Bash, shell scripting, or Linux package management, nor does it provide parity in examples or instructions for Linux environments.
Recommendations
- Include Linux-specific scripting examples, such as Bash or shell scripts, alongside PowerShell examples.
- Mention Linux-native tools (e.g., Bash, sh, or Linux CLI utilities) and how they can be used in Azure Automation runbooks.
- Provide guidance on package management for Python in Linux environments, including pip and system packages.
- Clarify cross-platform compatibility and explicitly state how runbooks can be authored and executed on Linux-based environments.
- Add documentation links and examples for Linux users, such as references to Bash scripting documentation or Linux automation best practices.
- Ensure that examples and instructions are presented in a platform-neutral order or provide parallel examples for both Windows and Linux.
Automation
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
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell-based instructions and tools, especially for unregistering nodes and deleting configurations. Windows/PowerShell methods are described in detail and given before Linux equivalents, with Linux instructions often relegated to brief manual steps or optional sections. Linux-specific examples and parity in tooling are limited, and the use of Windows-centric cmdlets (e.g., Remove-DscConfigurationDocument) is emphasized.
Recommendations
- Provide Linux-specific command-line examples for unregistering nodes, such as using OMI or DSC agent commands, if available.
- Include parity in step-by-step instructions for Linux, not just manual file deletion (e.g., scripts or commands to unregister nodes from Linux CLI).
- Present Windows and Linux instructions side-by-side or in parallel tabs, rather than Windows/PowerShell first.
- Reference Linux-native tools or automation methods where possible, and avoid assuming PowerShell is the default for all platforms.
- Expand Linux sections with troubleshooting, verification, and re-registration steps, matching the detail given to Windows/PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/shared-resources/schedules.md
...main/articles/automation/shared-resources/schedules.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and cmdlets for schedule management in Azure Automation. All CLI instructions use PowerShell syntax, and there is no mention of Bash, Azure CLI, or Linux-native tooling. Windows/PowerShell tools are referenced first and exclusively, with no Linux or cross-platform alternatives provided.
Recommendations
- Add equivalent Azure CLI examples for all schedule management tasks, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Include Bash script examples where appropriate, especially for automation scenarios.
- Explicitly mention that PowerShell Core is available cross-platform, but clarify any differences in usage or prerequisites for Linux/macOS users.
- Reference Linux-native tools or patterns where applicable, such as cron integration or using REST API calls from Bash.
- Reorder sections so that cross-platform options (Azure CLI, REST API) are presented before or alongside PowerShell examples.
- Add notes or links for Linux users regarding installation and usage of PowerShell Core, if PowerShell is required.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/collect-data-microsoft-azure-automation-case.md
...eshoot/collect-data-microsoft-azure-automation-case.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides separate sections for Linux and Windows, but the Windows section includes more detailed instructions (e.g., specific event logs to export and their formats), while the Linux section is less detailed and lacks equivalent log collection specifics. Windows tools (EVTX format, event logs) are mentioned explicitly, whereas Linux log collection is referenced only via a third-party tool and folder compression. Some general troubleshooting steps (e.g., job and module issues) do not specify Linux or Windows differences, potentially assuming Windows defaults.
Recommendations
- Provide equally detailed Linux instructions, such as which log files to collect and their formats, analogous to the Windows event logs.
- List Linux tools and commands for log collection (e.g., journalctl, /var/log/syslog) alongside Windows tools.
- Ensure that general troubleshooting steps clarify any OS-specific differences, rather than assuming Windows-centric workflows.
- Where screenshots or UI instructions are given, note any differences for Linux users (if applicable).
- Review referenced KB articles to ensure Linux parity in examples and instructions.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/desired-state-configuration.md
...automation/troubleshoot/desired-state-configuration.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 bias. Troubleshooting steps, examples, and tools are almost exclusively presented in terms of PowerShell DSC, Windows event logs, and Windows-specific cmdlets. Windows tools (e.g., xDscDiagnostics, w32tm) and Azure portal workflows are described in detail, while Linux troubleshooting is only briefly mentioned in a single scenario. Linux-specific errors, logs, and remediation steps are largely absent, and Linux onboarding is referenced only as a link, not with explicit examples or guidance.
Recommendations
- Provide Linux-specific troubleshooting steps and examples for common scenarios, including log locations, error messages, and remediation commands.
- Include parity for Linux onboarding, configuration, and agent registration, with explicit instructions and sample commands (e.g., shell commands, systemd service checks, certificate management on Linux).
- Reference Linux equivalents for Windows tools (e.g., show how to check time sync on Linux, parse DSC logs, manage certificates).
- Ensure that Linux scenarios are presented alongside Windows scenarios, not only as afterthoughts or links.
- Where PowerShell is used, clarify if and how PowerShell Core can be used on Linux, or provide alternative native Linux approaches.
- Expand documentation for Linux retirement and alternatives, given the end-of-life announcements.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/managed-identity.md
...n/articles/automation/troubleshoot/managed-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 bias. All troubleshooting examples and code snippets use PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM), which are Windows-centric and do not mention or provide equivalent Bash/CLI commands for Linux users. The troubleshooting steps and error messages reference Windows tools and patterns exclusively, and there is no guidance for Linux-based automation environments or hybrid scenarios. This may hinder Linux users from effectively troubleshooting managed identity issues in Azure Automation.
Recommendations
- Add equivalent troubleshooting examples using Azure CLI (az) and Bash scripts for each scenario.
- Include error messages and resolution steps relevant to Linux-based Hybrid Runbook Workers.
- Explicitly mention cross-platform options and clarify when PowerShell is required versus when CLI/Bash can be used.
- Provide links to Linux-specific documentation or guides for Azure Automation managed identities.
- Ensure screenshots and UI instructions are not Windows-specific, or provide Linux alternatives where applicable.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/start-runbooks.md
...e-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 clear Windows bias by exclusively providing examples and instructions for starting Azure Automation runbooks using Windows PowerShell. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform PowerShell Core. Windows tools and patterns are mentioned first and exclusively, with no parity for Linux or macOS environments.
Recommendations
- Add equivalent examples for starting runbooks using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Include instructions and sample code for PowerShell Core (pwsh), clarifying its cross-platform compatibility.
- Explicitly mention that PowerShell cmdlets can be used on Linux/macOS with PowerShell Core, and provide any necessary setup steps.
- Provide Bash or REST API curl examples for starting runbooks, especially in the section discussing the Azure Automation API.
- Reorder or balance the presentation so that Windows-specific tools are not always mentioned first, and ensure Linux/macOS methods are equally visible.
- Add troubleshooting and next steps resources relevant to Linux/macOS users.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/troubleshoot/shared-resources.md
...n/articles/automation/troubleshoot/shared-resources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias, with all troubleshooting steps and code examples provided exclusively in PowerShell. Windows-centric tools and patterns (such as PowerShell cmdlets and references to DLLs) are mentioned throughout, with no equivalent guidance or examples for Linux environments or cross-platform automation. The documentation assumes the use of Windows-based tooling and does not address Linux scenarios or provide bash/CLI alternatives.
Recommendations
- Provide equivalent troubleshooting steps and code examples using Azure CLI, bash, or Python for Linux users.
- Explicitly mention cross-platform compatibility and note any differences in behavior or requirements between Windows and Linux environments.
- Include references to Linux tools and patterns where applicable (e.g., handling modules, authentication, error messages).
- Add a section or notes for users running Azure Automation from Linux, including common issues and resolutions.
- Where DLLs or Windows-specific components are referenced, clarify their relevance (or irrelevance) to Linux users and suggest alternatives if available.
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 focused on Windows environments and PowerShell tooling. All code examples use PowerShell and target Windows VMs, specifically referencing IIS installation. Prerequisites and links are Windows-centric, and there is no example or guidance for Linux machines. Although Linux support is mentioned in passing, there are no Linux-specific instructions, examples, or parity in tooling.
Recommendations
- Add equivalent examples for onboarding and configuring Linux VMs, including sample DSC configurations for common Linux packages/services.
- Include instructions and code samples using cross-platform tools (such as Azure CLI or bash scripts) where possible, not just PowerShell.
- Update prerequisites to reference both Windows and Linux VM creation guides, and clarify current support status for Linux.
- Provide guidance on managing Linux nodes, including any differences in configuration, onboarding, and compliance checking.
- If Linux support is deprecated, make this clear at the start and provide migration or alternative recommendations for Linux users.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its heavy emphasis on PowerShell runbooks and Windows-centric tooling. Most examples and feature announcements focus on PowerShell versions, with Python support mentioned but less frequently and often as a secondary note. Windows tools and patterns, such as PowerShell modules (AzureRM, Az) and VS Code extensions for PowerShell, are highlighted more prominently than their Linux or cross-platform equivalents. There is a lack of explicit Linux shell (bash) examples, and Windows/PowerShell features are often mentioned first or exclusively, with Linux support referenced only in passing or as an afterthought.
Recommendations
- Provide equivalent Linux/bash examples alongside PowerShell examples for runbook creation and management.
- Highlight cross-platform capabilities and ensure announcements mention Linux support explicitly and equally.
- Include references to Linux-native tools and scripting environments (e.g., bash, sh, cron) where relevant.
- Balance documentation of PowerShell and Python runbooks with examples and migration guides for both.
- When describing new features, avoid listing Windows/PowerShell options first unless there is a technical reason; alternate ordering or group by platform.
- Add guidance for Linux users on using Azure Automation, including troubleshooting and best practices for Linux environments.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides disaster recovery guidance for Azure Automation, which applies to both Linux and Windows VMs. However, all migration scripts and automation examples are exclusively PowerShell-based, with no mention of Bash, Azure CLI, or Python alternatives. The instructions for Hybrid Runbook Worker reference both Windows and Linux, but all migration and runbook automation is presented only with PowerShell scripts and workflows, which are traditionally Windows-centric tools. This creates friction for Linux/macOS users who may prefer or require non-PowerShell solutions.
Recommendations
- Provide equivalent migration scripts or runbooks using Azure CLI and/or Python to support Linux/macOS users.
- Include explicit examples or tabs for Bash/Azure CLI where PowerShell is currently used.
- Clarify if PowerShell Core (cross-platform) is supported and provide guidance for running scripts on Linux/macOS.
- Reference or link to any existing Linux/macOS-friendly tools or documentation for Automation account asset migration.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and PowerShell cmdlets are mentioned first and more frequently. Several backup and retention operations reference Windows PowerShell cmdlets without Linux CLI or scripting equivalents, and Windows registry settings are linked before Linux OpenSSL guidance. Linux examples are present but less detailed and not always given equal prominence.
Recommendations
- Provide Azure CLI or Bash script equivalents for PowerShell cmdlet examples, especially for backup/export operations.
- Ensure Linux guidance is presented alongside Windows instructions, not after or as an afterthought.
- Add explicit instructions or links for managing Automation assets and DSC nodes from Linux/macOS environments.
- Include references to Linux tools (e.g., az CLI, shell scripts) where Windows tools (PowerShell, registry) are mentioned.
- Balance the order of platform-specific guidance so Linux and Windows are treated equally.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page heavily relies on Windows PowerShell examples and tools, such as PSCredential, Get-AutomationPSCredential, and Az modules. All code samples are in PowerShell, with no mention of Bash, Python, or Linux/macOS alternatives. The instructions for creating credential assets and managing Azure resources are exclusively PowerShell-based, and Windows terminology is used throughout. There is no guidance for Linux/macOS users or cross-platform scripting.
Recommendations
- Add equivalent Bash or Python examples for credential asset creation and Azure authentication, using Azure CLI or SDKs.
- Clarify whether Azure Automation runbooks can be authored in languages other than PowerShell and provide links or examples if so.
- Mention cross-platform tools (e.g., Azure CLI, REST API, Python SDK) where applicable, and note any limitations.
- Explicitly state if certain steps are PowerShell-only and provide guidance for Linux/macOS users on alternatives or workarounds.
- Reorder sections to avoid always presenting Windows/PowerShell solutions first.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page heavily focuses on PowerShell and Windows-centric tools and patterns, with most examples, screenshots, and workflows centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). Windows/PowerShell terminology and tools are used throughout, and PowerShell examples are presented before Python. There is minimal coverage of Python runbooks, and no mention of Bash, Linux shell, or cross-platform CLI usage. Assigning parameters and calling runbooks is almost exclusively demonstrated with PowerShell cmdlets and Windows-centric workflows.
Recommendations
- Add examples for starting runbooks and passing parameters using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
- Provide Python runbook parameter usage examples beyond referencing another tutorial, including how to pass parameters from CLI or REST API.
- Include guidance for Linux/macOS users, such as how to use Bash or shell scripts to invoke runbooks via REST API or Azure CLI.
- Clarify which features are PowerShell/Windows-specific and which are cross-platform, to help non-Windows users navigate the documentation.
- Present Python and cross-platform examples alongside PowerShell, not only after or as an afterthought.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is heavily PowerShell-centric, with all certificate management (creation, upload, and deployment) examples using PowerShell cmdlets. There are no CLI, Bash, or Linux-native examples for certificate management tasks. The only non-PowerShell examples are for retrieving certificates in Python runbooks, but all asset management and deployment workflows are shown with PowerShell. The documentation also recommends PowerShell as a workaround for portal limitations, and PowerShell examples are consistently presented first.
Recommendations
- Add Azure CLI examples for certificate creation, upload, and management to provide parity for Linux/macOS users.
- Include Bash or cross-platform scripting examples where possible, especially for tasks like uploading certificates or deploying Resource Manager templates.
- When recommending workarounds (e.g., for CSP accounts), mention Azure CLI or REST API alternatives, not just PowerShell.
- Consider reordering or parallelizing examples so that PowerShell and cross-platform approaches are presented equally.
- Clarify which steps are platform-agnostic (e.g., using the Azure portal, Resource Manager templates) and which are PowerShell-specific.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell cmdlets and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, and there is no mention of Bash, Linux shell, or cross-platform CLI alternatives. The 'Create a new credential asset' section only provides a Windows PowerShell example, with no Linux or macOS equivalent. The documentation assumes use of PowerShell and Windows tools throughout, creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for credential asset management, which are cross-platform and usable on Linux/macOS.
- Explicitly state whether PowerShell Core (pwsh) is supported and provide examples for it if so.
- Clarify if credential management is possible via REST API or SDKs, and provide relevant examples.
- Mention or link to any Linux/macOS-compatible tools or workflows for Azure Automation credential management.
- Reorder sections to present cross-platform options (Azure portal, Azure CLI, SDKs) before Windows PowerShell.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and references (including PowerShell cmdlets and registry settings) are presented first and more frequently. Backup and retention examples rely heavily on Windows PowerShell cmdlets, with no equivalent CLI or Linux-native examples. References to asset management and DSC node removal use Windows PowerShell cmdlets exclusively.
Recommendations
- Provide Azure CLI or REST API examples alongside PowerShell cmdlets for backup/export and asset management tasks.
- Include Linux/macOS-specific instructions or scripts for tasks like exporting runbooks, DSC configurations, and managing assets.
- Balance the order of presentation so Linux examples are not consistently secondary to Windows examples.
- Reference cross-platform tools and commands (e.g., az CLI, Bash scripts) where possible.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for managing certificates in Azure Automation demonstrates a notable Windows/PowerShell bias. Most examples and instructions use PowerShell cmdlets, which are traditionally associated with Windows environments. The creation and management of certificates are shown almost exclusively with PowerShell, and PowerShell examples are presented first. There is minimal mention of Linux/macOS workflows, and no CLI, Bash, or Linux-native tooling is referenced. Python examples are provided, but only for accessing certificates in runbooks, not for certificate creation or management.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to support Linux/macOS users.
- Include Bash or shell script examples where possible, especially for uploading certificates or interacting with Azure Automation.
- Clarify whether PowerShell examples are cross-platform (i.e., usable on PowerShell Core on Linux/macOS), and provide guidance for non-Windows users.
- Explicitly mention any platform limitations, and provide alternative workflows for Linux/macOS users if certain features are Windows-only.
- Consider reordering examples so that platform-neutral or cross-platform approaches are presented before Windows/PowerShell-specific ones.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with nearly all examples, code snippets, and workflows using PowerShell cmdlets and patterns. There is minimal mention of Linux/macOS workflows, and no Bash, CLI, or cross-platform examples for starting or interacting with runbooks. Python runbooks are briefly mentioned, but only in the context of parameter passing, not in terms of how to invoke or manage them from Linux/macOS environments.
Recommendations
- Add Azure CLI examples for starting runbooks and passing parameters, demonstrating usage on Linux/macOS.
- Include Bash or shell script samples for interacting with the REST API to start runbooks and assign parameters.
- Clarify which features and workflows are cross-platform and which are Windows/PowerShell-specific.
- Provide parity in examples for Python runbooks, including how to invoke them from Linux/macOS environments.
- Mention any platform-specific limitations or differences explicitly, so users know what is supported on their OS.