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 201-225 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/tutorial-autoscale-ps.md
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All examples and instructions are provided exclusively using Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux-compatible alternatives. File paths and certificate creation steps assume a Windows environment. There are no Linux or cross-platform instructions or examples, making it difficult for Linux users to follow the tutorial.
Recommendations
- Provide equivalent Azure CLI (az) commands for all resource creation and management steps, as Azure CLI is cross-platform and widely used on Linux.
- Include instructions for creating self-signed certificates using OpenSSL, which is available on Linux and macOS, alongside the PowerShell example.
- Use platform-neutral file paths or clarify path differences for Windows and Linux (e.g., c:\appgwcert.pfx vs. ~/appgwcert.pfx).
- Explicitly state that the tutorial can be followed from Linux, macOS, or Windows, and provide guidance for each platform where steps differ.
- Add a section or callouts highlighting any platform-specific prerequisites or differences, such as installing Azure CLI or PowerShell Core on Linux.
- Consider reordering or parallelizing examples so that Linux and Windows approaches are presented side-by-side, rather than Windows-first or Windows-only.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/troubleshoot-network-connectivity.md
...ticles/event-grid/troubleshoot-network-connectivity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell/Windows command-line examples (psping.exe) first and in greater detail, mentioning Windows-specific tools (psping.exe, tcpping.exe) without clear Linux alternatives, and only briefly referencing a Linux example (telnet) without parity in explanation or troubleshooting depth. Linux users are left with less guidance and fewer tool recommendations for network troubleshooting.
Recommendations
- Provide Linux-native command examples (e.g., nc, nmap, curl) alongside or before Windows examples for all troubleshooting steps.
- List cross-platform tools (e.g., hping3, nmap, netcat) and explain their usage for Linux environments.
- Ensure that troubleshooting commands and tool recommendations are presented in a platform-neutral order or grouped by OS, rather than Windows-first.
- Expand Linux sections to match the detail and troubleshooting depth given to Windows users, including equivalent explanations and output interpretation.
- Include notes or tables summarizing equivalent tools/commands for Windows, Linux, and macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/ssl-overview.md
...lob/main//articles/application-gateway/ssl-overview.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 by referencing Windows-specific tools and APIs (such as the PFXImportCertStore function), providing configuration guidance and next steps only for PowerShell (a Windows-centric tool), and omitting Linux or cross-platform alternatives for certificate management and Application Gateway configuration. There are no examples or instructions for Linux users, and Windows terminology and tools are mentioned before or instead of platform-neutral or Linux equivalents.
Recommendations
- Provide parallel instructions and examples for configuring end-to-end TLS using Azure CLI and/or Azure Portal, which are cross-platform and accessible from Linux, macOS, and Windows.
- When referencing certificate formats and tools, include Linux/OpenSSL equivalents (e.g., how to generate and convert certificates using OpenSSL commands).
- Avoid linking exclusively to Windows API documentation (such as PFXImportCertStore); instead, link to Azure documentation or platform-neutral resources.
- In the 'Next steps' section, include links to guides for configuring Application Gateway with end-to-end TLS using Azure CLI and Azure Portal, not just PowerShell.
- Explicitly mention that all configuration steps can be performed from any OS using cross-platform tools, and provide examples or links for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/ingress-controller-install-existing.md
...ication-gateway/ingress-controller-install-existing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing several PowerShell-based command examples (using variables and scripting patterns specific to PowerShell), especially for Azure CLI operations and Kubernetes resource management. These examples are not accompanied by equivalent Bash/Linux shell commands, and PowerShell is used in contexts where Bash would be more universally applicable. Additionally, PowerShell examples are presented before or instead of Bash alternatives, and there are no explicit Linux/Bash examples for key steps such as role assignment and resource querying.
Recommendations
- Provide Bash/Linux shell equivalents for every PowerShell example, especially for Azure CLI and Kubernetes operations.
- When presenting command-line examples, default to Bash syntax or present Bash first, as it is more universally applicable across platforms (including Cloud Shell, Linux, and macOS).
- Clearly indicate which examples are platform-specific, and offer guidance for users on both Windows (PowerShell) and Linux/macOS (Bash).
- Avoid using PowerShell-specific variable syntax (e.g., $variable) in generic Azure CLI or kubectl command examples; use environment variables or inline values for cross-platform compatibility.
- Review all scripting sections to ensure Linux users can follow the documentation without needing to translate PowerShell to Bash themselves.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/proxy-buffers.md
...ob/main//articles/application-gateway/proxy-buffers.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples (a Windows-centric tool) for both creating and updating Application Gateway resources, while not offering equivalent Bash or Linux shell scripting examples. The PowerShell method is given a dedicated section, and the Azure CLI examples are not explicitly shown in a Linux context (e.g., Bash scripting or Linux shell). There is also a reference to the Azure SDK for .NET, another Windows-centric technology, without mention of cross-platform SDKs. No Linux-specific guidance or examples are present.
Recommendations
- Add explicit Bash/Linux shell scripting examples for the Azure CLI method, demonstrating usage in a Linux terminal.
- Include cross-platform scripting examples (e.g., using Bash, Python SDK, or REST API with curl) to ensure Linux users are equally supported.
- Mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, and provide sample command lines for each where relevant.
- If referencing SDKs, include links or examples for Python, Java, or other cross-platform SDKs, not just .NET.
- Reorder sections so that cross-platform methods (Azure CLI, ARM template) appear before Windows-specific tools like PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/renew-certificates.md
...in//articles/application-gateway/renew-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, and by providing a detailed PowerShell script without any equivalent Bash or Linux-native scripting example. The Azure CLI example is present but is less detailed and appears after the PowerShell example. There are no Linux-specific instructions or examples (e.g., Bash scripting, Linux file paths), and the PowerShell example assumes a Windows environment.
Recommendations
- Provide Bash/Linux shell scripting examples for certificate renewal using Azure CLI, including handling certificate files and passwords in a Linux environment.
- Present Azure CLI examples before or alongside PowerShell examples to avoid implying Windows as the default platform.
- Include notes or sections for Linux/macOS users, such as how to generate or handle PFX files, and how to securely store and use passwords in scripts.
- Clarify that Azure CLI is cross-platform and highlight any differences in usage between Windows and Linux, if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/redirect-http-to-https-portal.md
...s/application-gateway/redirect-http-to-https-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell, including certificate creation and IIS installation. The tutorial assumes the use of Windows Server as the backend OS, and there are no examples or instructions for Linux-based VMs, certificate generation on Linux, or using Bash/Azure CLI. Windows tools and paths (e.g., c:\appgwcert.pfx) are used exclusively, and Windows is the default/only option presented for the scale set OS.
Recommendations
- Provide equivalent examples using Azure CLI and Bash for certificate creation and VM configuration.
- Include instructions for generating self-signed certificates on Linux (e.g., using OpenSSL).
- Offer a Linux-based backend VMSS example (e.g., Ubuntu with NGINX or Apache).
- Use platform-neutral file paths and terminology where possible.
- Present both Windows and Linux options side-by-side, or clearly indicate how to adapt steps for Linux users.
- Mention that IIS is Windows-specific and suggest alternatives (e.g., NGINX/Apache) for Linux.
- Ensure that portal-based steps do not assume Windows-specific file formats or tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/self-signed-certificates.md
...ticles/application-gateway/self-signed-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows and Windows-specific tools (IIS, PowerShell, Windows hosts file editing) are often mentioned first or exclusively, while Linux equivalents are less emphasized or omitted. The Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example. References to editing the hosts file and importing certificates are Windows-centric, and the 'devx-track-azurepowershell' metadata further highlights a Windows/PowerShell focus.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell examples for certificate upload and Application Gateway configuration, as Azure CLI is cross-platform.
- When referencing hosts file editing, include instructions or links for both Windows and Linux/macOS.
- For web server configuration, ensure parity in detail and links for Apache, NGINX, and IIS, and avoid listing IIS first by default.
- Mention OpenSSL installation instructions or package names for both Windows and Linux, not just a general statement.
- Where screenshots or walkthroughs are provided for Windows tools (e.g., IIS), provide equivalent Linux examples (e.g., Apache/NGINX certificate import).
- Review metadata and custom tags to ensure they do not signal a Windows/PowerShell-only focus if the content is intended to be cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/retirement-faq.md
...b/main//articles/application-gateway/retirement-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing Azure PowerShell scripts for migration, without mentioning or providing examples for cross-platform alternatives such as Azure CLI or REST API. There are no Linux-specific instructions or examples, and the only automation tooling discussed is PowerShell, which is traditionally associated with Windows environments. This may disadvantage users who primarily use Linux or prefer non-PowerShell tooling.
Recommendations
- Provide equivalent Azure CLI examples and instructions for migration tasks, ensuring parity with PowerShell guidance.
- Mention REST API options for migration where applicable, to support automation from any platform.
- Explicitly state that PowerShell Core is cross-platform if PowerShell must be used, and provide installation guidance for Linux users.
- Include Linux shell (bash) command examples for common migration and troubleshooting scenarios.
- Balance references to PowerShell with Azure CLI throughout the documentation, especially in FAQs and migration steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/migrate-v1-v2.md
...ob/main//articles/application-gateway/migrate-v1-v2.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 migration instructions, examples, and scripts are provided exclusively in PowerShell, with no mention or examples for Bash, Azure CLI, or Linux-native tooling. The prerequisites and guidance assume the use of PowerShell modules and cmdlets, and there is no discussion of how to perform the migration from a Linux or cross-platform environment. The PowerShell Gallery and Windows-centric patterns (e.g., .ps1 scripts, NuGet package extraction, use of ConvertTo-SecureString, etc.) are referenced throughout, with no alternatives for Linux users.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all major steps, including authentication, resource discovery, and migration.
- Include Bash shell examples for script execution and parameter handling, especially for certificate management and file operations.
- Reference the Azure Cloud Shell as a cross-platform, browser-based alternative, and clarify that it supports both PowerShell and Bash/CLI.
- Document how Linux and macOS users can run the migration (e.g., using Azure CLI, Python scripts, or PowerShell Core on Linux), and note any prerequisites or differences.
- If the migration script is only available in PowerShell, explicitly state this limitation and provide guidance for installing PowerShell Core on Linux/macOS, or offer a roadmap for CLI support.
- Reorder or balance examples so that Linux/CLI alternatives are presented alongside or before Windows/PowerShell examples where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/automanage-arc.md
...-docs/blob/main//articles/automanage/automanage-arc.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation lists Windows Server versions first in the supported OS section and includes a Windows-only service (Microsoft Antimalware) in the participating services table, with no Linux equivalent or alternative mentioned. There are no Linux-specific examples, tools, or guidance provided, despite the page being tagged for Linux. The documentation does not provide parity in examples or service descriptions for Linux users.
Recommendations
- List supported Linux distributions before or alongside Windows Server versions to avoid a 'Windows-first' impression.
- For services like Microsoft Antimalware that are Windows-only, explicitly mention recommended or supported Linux alternatives (e.g., integration with third-party Linux antivirus solutions or note the absence of built-in antimalware for Linux).
- Include Linux-specific examples, tools, or configuration notes where relevant, especially in sections describing onboarding, monitoring, or compliance.
- Add guidance or links for Linux users regarding best practices for security, update management, and monitoring, ensuring Linux parity in documentation.
- Where a service is not available for Linux, clearly state this and suggest alternative approaches or tools for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/automanage-smb-over-quic.md
.../main//articles/automanage/automanage-smb-over-quic.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition as the required OS for SMB over QUIC with Automanage best practices. All instructions, prerequisites, and linked resources are Windows-centric, with no mention of Linux support, alternatives, or examples. The only referenced tools and features are specific to Windows Server, and the documentation does not clarify whether Linux is unsupported or simply omitted.
Recommendations
- Explicitly state whether SMB over QUIC with Automanage is supported on Linux VMs. If not supported, clarify this early in the documentation.
- If Linux support exists or is planned, provide equivalent instructions and examples for deploying and managing SMB over QUIC on Linux-based Azure VMs.
- Include references to Linux-compatible tools or alternatives for certificate management and SMB configuration.
- Ensure that links and 'Next steps' sections include Linux documentation or note platform-specific differences.
- If Windows-only features are being described, clearly label sections as 'Windows Server only' to avoid confusion for cross-platform administrators.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-cache-for-redis/cache-best-practices-scale.md
...es/azure-cache-for-redis/cache-best-practices-scale.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions PowerShell cmdlets as a primary method for programmatically scaling Azure Cache for Redis, listing it before Azure CLI and REST API. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific tools or workflows. This ordering and lack of Linux examples suggest a subtle Windows-first and PowerShell-heavy bias.
Recommendations
- Provide explicit Bash/Azure CLI examples alongside or before PowerShell examples to ensure Linux parity.
- Mention cross-platform tools (e.g., Azure CLI) before platform-specific tools (e.g., PowerShell) when listing programmatic options.
- Include sample commands for both Windows (PowerShell) and Linux (Bash/CLI) environments.
- Clarify that Azure CLI and REST API are fully cross-platform and suitable for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/add-user-assigned-identity.md
...ain//articles/automation/add-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 and PowerShell bias. All command-line examples are provided exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native shell equivalents. The use of Windows-style paths (e.g., 'path\file.json'), reliance on PowerShell-specific cmdlets (e.g., Connect-AzAccount, Invoke-RestMethod), and the absence of Linux or cross-platform CLI examples make it difficult for Linux users to follow the instructions. Even REST API and ARM template deployment steps are shown only with PowerShell, and there is no mention of Azure CLI or Bash scripting. The only non-PowerShell example is a Python snippet, but it is limited and does not cover the full workflow.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands for all PowerShell cmdlets, especially for authentication, resource management, and REST API invocation.
- Include Bash shell script examples for Linux users, particularly for file paths and environment variable usage.
- Use cross-platform file path conventions (e.g., forward slashes or environment-agnostic variables) in examples.
- Explicitly mention that all PowerShell examples can be run on PowerShell Core (pwsh) on Linux/macOS, or provide alternatives where necessary.
- For REST API and ARM template deployment, show how to use curl or az deployment group create in addition to PowerShell.
- Add a section or callouts for Linux/macOS users, highlighting any differences or prerequisites.
- Ensure that the documentation does not assume a Windows environment by default, and balance the order of examples (e.g., present Azure CLI or Bash before or alongside PowerShell).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-services.md
.../blob/main//articles/automation/automation-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a notable bias toward Windows and PowerShell-centric automation. Azure Automation is repeatedly described in terms of PowerShell runbooks, with frequent references to the PowerShell Gallery and the use of PowerShell modules for integration. Windows-centric tools and concepts (e.g., registry, Active Directory, SQL Server) are mentioned as primary automation targets. While Python is mentioned as an alternative scripting language, Linux-specific tools, shells, or automation patterns are largely absent. There are few, if any, explicit Linux examples or references to Linux-native scripting or management approaches. The documentation also tends to mention Windows/PowerShell approaches before any Linux alternatives, reinforcing a Windows-first perspective.
Recommendations
- Include explicit Linux examples for automation scenarios, such as using Bash scripts or Linux-native tools (e.g., systemd, cron) in Azure Automation.
- Highlight Linux-specific automation targets (e.g., managing Linux services, configuration files, or package managers) alongside Windows examples.
- Reference Linux scripting languages (e.g., Bash, Python) and demonstrate how to use them in Azure Automation, with links to relevant documentation.
- Balance mentions of PowerShell with equivalent Linux shell or scripting approaches, and clarify cross-platform capabilities where available.
- When listing supported platforms or features (e.g., in Azure Automanage), provide parity in detail for both Windows and Linux, including any limitations or differences.
- Add guidance or links for Linux administrators on integrating their existing automation scripts and tools with Azure services.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/compose-configurationwithcompositeresources.md
...omation/compose-configurationwithcompositeresources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell Desired State Configuration (DSC), with all examples and terminology centered on PowerShell and Windows-centric tools. There are no Linux-specific examples, tools, or workflows mentioned, and the only reference to Linux is a retirement announcement. The documentation assumes the use of PowerShell objects and patterns (e.g., [PSCredential]), and references to tools like Chocolatey further reinforce a Windows-first perspective.
Recommendations
- Include explicit examples or notes for Linux DSC scenarios, if still supported, or clarify the current support status for Linux.
- Provide equivalent Linux workflows or tools where possible, or direct users to Linux-native configuration management alternatives.
- Balance references to Windows-specific tools (such as Chocolatey and PowerShell cmdlets) with Linux equivalents (such as apt, yum, or shell scripts) or explain the lack of parity.
- If Linux support is deprecated, make this clear at the start and suggest migration paths or alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/virtual-machines-custom-profile.md
...articles/automanage/virtual-machines-custom-profile.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific features (such as Windows Admin Center and Windows-only audit modes) without mentioning Linux equivalents or clarifying Linux support. There are no Linux-specific examples or guidance, and Windows tools are referenced without parity for Linux users.
Recommendations
- Explicitly state which features and settings apply to Linux VMs, and provide equivalent Linux guidance where possible.
- Include Linux-specific examples or notes, especially for features that are Windows-only (e.g., clarify if and how security baselines or antimalware settings apply to Linux).
- If a feature is Windows-only (e.g., Windows Admin Center), clearly indicate this and, if possible, suggest Linux alternatives or clarify the Linux experience.
- Provide ARM template examples or configuration settings tailored for Linux VMs, or at least highlight differences in configuration between Windows and Linux.
- Review and update documentation to ensure Linux users are not left out or confused about feature applicability.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-create-alert-triggered-runbook.md
...utomation/automation-create-alert-triggered-runbook.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 throughout. All code examples, including those for assigning permissions and the main runbook, are exclusively in PowerShell. The prerequisites and links reference Windows and PowerShell-specific tools and modules, with no mention of Bash, Azure CLI, or Linux-based automation. The only VM creation link points to a Windows VM via PowerShell. There are no examples or guidance for users working from Linux or using cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) examples for all PowerShell scripts, especially for assigning permissions and managing Automation accounts.
- Include Bash or cross-platform shell script examples where applicable.
- Update the prerequisites to mention both Windows and Linux environments, and link to both Windows and Linux VM creation guides.
- Offer guidance on how to use the Azure portal and Azure CLI for users who do not use PowerShell.
- Ensure that runbook examples are provided in both PowerShell and Python (supported in Azure Automation), or at least mention Python as an option.
- Explicitly state that the instructions are cross-platform where possible, or provide platform-specific sections for Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-dsc-getting-started.md
.../articles/automation/automation-dsc-getting-started.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell DSC. All configuration examples use PowerShell syntax and Windows-specific resources (e.g., WindowsFeature IIS). The only VM creation link is for Windows, and there are no Linux configuration examples or references to Linux DSC resources. The documentation repeatedly references Windows PowerShell DSC and Windows tools, with no parity for Linux users. Although there is a mention of Linux support retirement, there is no guidance or examples for Linux scenarios.
Recommendations
- Add Linux-specific configuration examples, such as using nxFile or nxPackage resources in DSC for Linux.
- Include links to creating Linux VMs in Azure alongside Windows VM instructions.
- Provide guidance or references for managing Linux nodes with Azure Automation State Configuration (even if deprecated, for historical parity).
- Clarify the current support status for Linux and direct users to alternatives or migration paths if Linux support is retired.
- Balance references to Windows and Linux in both prerequisites and next steps, ensuring both platforms are addressed where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/repair-automanage-account.md
...main//articles/automanage/repair-automanage-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell is mentioned explicitly and equally alongside Azure CLI, despite Azure CLI being cross-platform and PowerShell being primarily associated with Windows. There are no explicit Linux or Bash shell examples, and the PowerShell module is referenced before any mention of Linux-native tools or workflows. The documentation does not clarify that PowerShell Core is available on Linux, nor does it provide Bash or shell script equivalents for Linux users.
Recommendations
- Prioritize Azure CLI examples, as it is cross-platform and works natively on Linux, macOS, and Windows.
- If mentioning PowerShell, clarify that PowerShell Core is available on Linux and macOS, or provide a Bash/shell equivalent for Linux users.
- Add explicit Bash or shell script examples for Linux users, especially for ARM template deployments and role assignments.
- When listing options, mention Azure CLI before PowerShell to reflect its broader platform compatibility.
- Include a note or section on Linux-specific considerations or workflows, if any exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-connections.md
...ob/main//articles/automation/automation-connections.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing primarily on PowerShell cmdlets and workflows, with detailed examples and step-by-step instructions for Windows PowerShell. The creation and management of connections are described almost exclusively using PowerShell and the Az modules, which are most commonly used on Windows. There is no mention of Linux shell (bash/CLI) equivalents for managing connections, nor are there any examples using Azure CLI or other cross-platform tools. The Python section is present but limited to runbook scripting, not connection management. There are no Linux-specific instructions or examples for creating or managing connections outside the Azure portal.
Recommendations
- Add Azure CLI examples for creating, retrieving, and managing Automation connections, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include bash shell script examples for interacting with Azure Automation via REST API or Azure CLI.
- Reorganize sections so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell examples, rather than PowerShell-first.
- Explicitly mention Linux/macOS compatibility and provide guidance for non-Windows users, including any prerequisites or differences in workflow.
- Where PowerShell is referenced, clarify that PowerShell Core is cross-platform and provide examples for both Windows PowerShell and PowerShell Core on Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/move-automanaged-configuration-profile.md
...s/automanage/move-automanaged-configuration-profile.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell variables, and operators) for all examples and workflows. There are no equivalent examples for Linux users (e.g., using Bash, curl, or Azure CLI), and the documentation assumes familiarity with Windows scripting patterns. This creates a clear bias towards Windows environments and leaves Linux users without guidance.
Recommendations
- Provide equivalent Linux/Bash examples using curl or Azure CLI for all PowerShell commands.
- Introduce cross-platform Azure CLI examples, which are supported on both Windows and Linux.
- Explicitly mention that the steps can be performed from any OS, and clarify any OS-specific requirements.
- Structure example sections so that both Windows (PowerShell) and Linux (Bash/CLI) users can easily find relevant instructions.
- Avoid using Windows-specific operators (such as -replace) without showing the equivalent in Bash or other shells.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-config-aws-account.md
...//articles/automation/automation-config-aws-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking to AWS credential documentation specifically for PowerShell, referencing Windows-centric credential management patterns, and omitting any Linux or cross-platform examples or guidance. There is no mention of Linux tools, shell environments, or how to perform equivalent tasks outside of Windows/PowerShell.
Recommendations
- Include links to AWS CLI documentation for credential management, which is cross-platform and widely used on Linux.
- Provide examples or references for storing and retrieving AWS credentials using Linux tools or scripts (e.g., Bash, Python).
- Mention that Azure Automation runbooks can be authored in Python as well as PowerShell, and provide parity in examples.
- Avoid referencing only PowerShell-specific AWS documentation; instead, offer both PowerShell and CLI/SDK options.
- Clarify that the instructions apply regardless of the underlying OS, or explicitly call out differences where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-create-standalone-account.md
...les/automation/automation-create-standalone-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for key management and runbook creation, referencing PowerShell runbooks and cmdlets predominantly, and omitting equivalent instructions or examples for Linux users (such as Azure CLI or Bash). The 'Next steps' section also prioritizes PowerShell tutorials and references, with Python mentioned only after multiple PowerShell links. No Linux-native tools or workflows are discussed.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets shown, especially for access key management and Automation account operations.
- Include Bash shell examples where appropriate, particularly for Linux users.
- In 'Next steps', provide parity by listing Python and Azure CLI tutorials alongside PowerShell, not after.
- Reference cross-platform tools and workflows (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
- Mention that Automation runbooks can be authored in Python and Bash, and provide links or examples for these.
- Ensure screenshots and UI instructions are not Windows-centric and clarify that the Azure portal is cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-disaster-recovery.md
...n//articles/automation/automation-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All migration scripts and automation examples are provided exclusively in PowerShell or PowerShell Workflow, with no mention of Bash, Python, or other Linux-native scripting options. The prerequisites and module requirements are all PowerShell/Az.* focused, and the runbook import/execution steps assume PowerShell as the only supported language. While the page claims applicability to both Linux and Windows VMs, Linux-specific tools, scripts, or examples are entirely absent. Additionally, links and installation steps for Hybrid Runbook Workers default to Windows tabs and instructions.
Recommendations
- Provide equivalent migration scripts and runbook examples using Bash and/or Python, which are native to Linux environments.
- Document the use of Azure CLI (az) commands for asset migration and automation, alongside PowerShell.
- Include Linux-first or Linux-parity tabs/examples in all step-by-step sections, especially for Hybrid Runbook Worker installation and runbook execution.
- List both Windows and Linux options equally in all instructions, rather than defaulting to Windows or PowerShell.
- Clarify any limitations or differences in Linux support for automation account disaster recovery, and offer workarounds or alternatives where PowerShell is not available.