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 1026-1050 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/blob-event-quickstart-bicep.md
...in//articles/event-grid/blob-event-quickstart-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides deployment instructions for both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux or macOS environments. The CLI example is cross-platform, but the PowerShell example is Windows-centric. There are no Linux-specific instructions or notes, and no mention of Linux tools or shell environments. The 'Clean up resources' section links only to Azure Portal instructions, not CLI or shell commands, which could be more cross-platform.
Recommendations
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI as the default for cross-platform compatibility.
- Clearly indicate that the PowerShell example is primarily for Windows users, or provide instructions for PowerShell Core on Linux/macOS if applicable.
- Add a note or section for Linux/macOS users, confirming that all steps can be performed from Bash or other shells using Azure CLI.
- For resource cleanup, provide Azure CLI commands alongside portal instructions to ensure parity for users on all platforms.
- Consider reordering examples to present CLI (cross-platform) before PowerShell (Windows-centric), or default to CLI in the main flow.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/link-partner-id-power-apps-accounts.md
...-billing/manage/link-partner-id-power-apps-accounts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias by prioritizing PowerShell instructions and examples, referencing PowerShell cmdlets throughout, and mentioning PowerShell before Azure CLI in alternate approaches. While Azure CLI instructions are provided, there are no explicit Linux/macOS-specific examples or guidance, and the validation section only mentions PowerShell and the Azure portal, omitting CLI or cross-platform alternatives. There is an implicit assumption that users are familiar with PowerShell, which is primarily a Windows tool, despite its cross-platform support.
Recommendations
- Include explicit Linux/macOS examples and notes where CLI commands are shown, clarifying cross-platform compatibility.
- In validation steps, provide Azure CLI equivalents alongside PowerShell and portal instructions.
- When listing alternate approaches or tooling, alternate the order of PowerShell and Azure CLI to avoid always placing Windows tooling first.
- Add brief notes or links about installing and using PowerShell on Linux/macOS, or clarify that PowerShell Core is cross-platform.
- Where possible, highlight any differences or considerations for non-Windows environments (e.g., file paths, authentication methods).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/mca-setup-account.md
...es/cost-management-billing/manage/mca-setup-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web-based GUI), with no mention of cross-platform command-line tools such as Azure CLI or Azure PowerShell. There are no examples or instructions for Linux or macOS users, and all procedural steps assume use of the Azure portal, which is most commonly accessed via Windows environments. Additionally, there is no mention of automation or scripting options that are platform-agnostic, such as REST APIs, Azure CLI, or Terraform (except for a brief mention in the context of subscription vending, without any concrete examples).
Recommendations
- Include Azure CLI examples for all major actions (e.g., checking roles, transitioning billing, managing access), as Azure CLI is cross-platform and widely used on Linux and macOS.
- Where possible, provide REST API examples or references for automation, which are platform-independent.
- Explicitly mention that the Azure portal is accessible from any modern browser on Windows, Linux, or macOS, to clarify that the steps are not Windows-specific.
- Add PowerShell examples only alongside Azure CLI, and clarify that Azure PowerShell is available cross-platform.
- For sections involving role assignment or billing management, provide sample CLI commands (az billing, az role assignment, etc.) and links to relevant documentation.
- In the 'Changes to subscription vending using Terraform' section, provide a minimal example or link to a quickstart for Linux users.
- Add a note or section for Linux/macOS users on any prerequisites or differences (if any) in the process.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/programmatically-create-subscription-preview.md
...manage/programmatically-create-subscription-preview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides examples for REST, Azure PowerShell, and Azure CLI when creating Azure subscriptions for Enterprise Agreement (EA) accounts. PowerShell examples are given equal prominence to Azure CLI, but there is a slight Windows bias: PowerShell is highlighted as a primary scripting interface, and the instructions for PowerShell specifically mention using Azure Cloud Shell with PowerShell, which is more familiar to Windows users. The documentation does not mention Linux shells or scripting environments, nor does it provide Bash-specific guidance or note cross-platform compatibility for PowerShell. There are no explicit Linux/Bash examples or notes on how to run PowerShell commands on Linux/macOS, and the PowerShell sections assume familiarity with Windows tooling. However, Azure CLI examples are included, which are cross-platform, partially mitigating the bias.
Recommendations
- Explicitly state that Azure PowerShell is cross-platform and can be used on Linux/macOS as well as Windows.
- Add Bash shell examples or notes for users running Azure CLI in Bash environments, especially for common scripting scenarios.
- In PowerShell sections, mention how to install and use Azure PowerShell on Linux/macOS, or link to cross-platform installation guides.
- Avoid language that assumes the user is on Windows (e.g., referencing PowerShell as the default shell or omitting Bash).
- Where Cloud Shell is referenced, clarify that both Bash and PowerShell environments are available and supported.
- Consider providing parity in troubleshooting or environment setup instructions for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/cloud-event-schema.md
...s/blob/main//articles/event-grid/cloud-event-schema.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing both Azure CLI and PowerShell examples for schema configuration, with PowerShell (a Windows-centric tool) featured equally alongside the cross-platform CLI. In the Azure Functions section, development workflows are described primarily for Visual Studio and Visual Studio Code, with instructions referencing Windows-specific tooling (NuGet Package Manager Console, Solution Explorer). There are no explicit Linux or macOS-specific instructions or examples, and no mention of Linux-native tools or shell environments.
Recommendations
- Provide explicit Linux/macOS shell examples (e.g., bash/zsh) for CLI commands, including environment variable syntax differences.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS, and provide sample commands in bash syntax.
- For PowerShell, note that PowerShell Core is available cross-platform, or provide equivalent bash examples where possible.
- In the Azure Functions section, include instructions for .NET CLI usage (dotnet add package) as an alternative to Visual Studio/Windows-specific NuGet workflows.
- Mention Linux/macOS compatible editors (such as VS Code, JetBrains Rider) and provide steps for those environments.
- Add a section or callout for Linux users, highlighting any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/reservations/reservation-utilization.md
...gement-billing/reservations/reservation-utilization.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing PowerShell and the Azure portal (which is typically accessed via a browser on Windows) as primary methods for viewing reservation utilization. There is mention of APIs, PowerShell, and CLI, but no explicit Linux or cross-platform command-line examples are provided. Power BI, a Windows-centric tool, is emphasized for reporting, with no mention of Linux-compatible alternatives or usage instructions for Linux environments.
Recommendations
- Include explicit Azure CLI examples for reservation utilization queries, as Azure CLI is cross-platform and commonly used on Linux.
- Provide sample API requests using curl or other command-line tools available on Linux.
- Mention and demonstrate how to access and analyze reservation utilization data on Linux or macOS, not just via PowerShell or Power BI.
- If possible, reference cross-platform reporting tools or clarify Power BI web access for non-Windows users.
- Ensure that instructions and screenshots (if any) are not Windows-specific and clarify that the Azure portal is accessible from any OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/reservations/view-purchase-refunds.md
...nagement-billing/reservations/view-purchase-refunds.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Windows-centric tools (Azure portal, Power BI) and omitting any mention of Linux or cross-platform CLI examples. There are no instructions or examples for Linux users, such as using Azure CLI, Bash, or other cross-platform tools. The order of presentation also puts Windows GUI tools first, with no parity for Linux command-line workflows.
Recommendations
- Add examples using Azure CLI commands (az consumption reservation or similar) to retrieve reservation purchase and refund transactions, which are cross-platform and work on Linux, macOS, and Windows.
- Include sample REST API calls using curl or other command-line tools common on Linux, with example requests and responses.
- Mention and provide guidance for using cross-platform tools (such as Azure CLI and REST API) before or alongside Windows-specific tools like Power BI.
- Explicitly state that the instructions apply to all platforms where possible, and provide alternative workflows for Linux users.
- Where screenshots are provided, consider including terminal output or CLI examples in addition to GUI screenshots.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/reservations/understand-reserved-instance-usage.md
...ing/reservations/understand-reserved-instance-usage.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows-based VM examples (Standard_DS1_v2 Windows virtual machine) and discussing Windows software costs, without providing equivalent Linux VM examples or mentioning Linux-specific considerations. The focus on Windows VMs and related software costs may lead Linux users to feel unsupported or unclear about how reservations apply to Linux workloads.
Recommendations
- Include parallel examples using popular Linux VM SKUs (e.g., Standard_DS1_v2 running Ubuntu or CentOS) alongside Windows examples.
- Explicitly state how reservation usage and billing differ (or do not differ) for Linux VMs, including any software cost differences.
- Add a section or note clarifying that the reservation process applies to both Windows and Linux VMs, and highlight any Linux-specific details.
- Provide screenshots or CSV excerpts for Linux VM scenarios to ensure parity in guidance.
- Link to documentation about Linux VM licensing and reservation implications, if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/savings-plan/permission-view-manage.md
...agement-billing/savings-plan/permission-view-manage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only Azure PowerShell examples for managing and assigning roles to Azure savings plans, with no mention of equivalent Azure CLI or cross-platform scripting options. This approach assumes the use of PowerShell, which is traditionally associated with Windows environments, and omits guidance for users on Linux or macOS who may prefer or require Azure CLI or bash scripting.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell scripts provided, ensuring Linux and macOS users have clear, supported instructions.
- Explicitly state that PowerShell Core is cross-platform, if PowerShell must be used, and provide installation links for Linux/macOS.
- Where possible, provide REST API examples using curl or similar tools to support automation from any OS.
- Review the documentation for other areas where Windows-centric tools or terminology are used and provide Linux/macOS alternatives.
- Consider a section or note at the start of the scripting section indicating which tools are cross-platform and which are Windows-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/savings-plan/software-costs-not-included.md
...nt-billing/savings-plan/software-costs-not-included.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on Windows software costs and meters, with no mention of Linux or other operating system equivalents. All examples and tables are about Windows Server licensing, and there is no discussion of how savings plans apply to Linux VMs or their software costs. This creates a Windows-first perspective and omits information relevant to Linux users.
Recommendations
- Add a section explicitly addressing Linux VM software costs, clarifying whether there are any software meters or additional charges for Linux VMs under savings plans.
- Include comparative tables or notes for both Windows and Linux, highlighting differences in how savings plans apply to each.
- If there are no software costs for Linux VMs, state this clearly to provide parity and transparency for Linux users.
- Review related links and ensure at least one covers Linux-specific considerations for Azure savings plans.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/scope-level/transition-existing.md
...-management-billing/scope-level/transition-existing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell scripts for usage analysis, without providing equivalent examples or guidance for Linux users. There is no mention of Bash, Azure CLI, or cross-platform scripting alternatives, and the only automation tool highlighted is PowerShell, which is primarily associated with Windows environments.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux and cross-platform users.
- Explicitly mention that PowerShell Core is cross-platform, if recommending PowerShell, and provide installation instructions for Linux.
- Include links to Linux-compatible tools or scripts for managing and analyzing Azure Hybrid Benefit usage.
- Ensure that automation and scripting guidance is not limited to Windows-centric tools; present Linux and cross-platform options alongside Windows examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/reservations/view-reservations.md
...t-management-billing/reservations/view-reservations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong bias towards Windows by exclusively providing Azure PowerShell examples and instructions for managing Azure reservations. There are no examples or references to cross-platform tools such as Azure CLI, nor are there any Bash or Linux shell script equivalents. The use of PowerShell as the only automation/scripting method implicitly assumes a Windows environment or familiarity with PowerShell, which is less common among Linux users.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell scripts and management tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Provide Bash shell script examples alongside PowerShell scripts for automation scenarios.
- Explicitly state that PowerShell Core is available cross-platform, but clarify whether the provided scripts are compatible with PowerShell Core on Linux/macOS.
- Include guidance or links for installing and using Azure CLI and/or PowerShell Core on non-Windows platforms.
- Review all sections to ensure Linux users are not excluded from management workflows, and mention any platform-specific caveats.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/scope-level/tutorial-azure-hybrid-benefits-sql.md
...ling/scope-level/tutorial-azure-hybrid-benefits-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based registration instructions for SQL Server VMs and only mentioning the PowerShell script for license usage analysis. There are no Linux-specific examples, instructions, or references to Linux tooling for managing or registering SQL Server VMs, despite SQL Server being supported on Linux in Azure.
Recommendations
- Add links and instructions for registering SQL Server VMs running on Linux, such as referencing the appropriate Azure documentation for Linux VM registration with the SQL IaaS Agent Extension.
- Provide Linux command-line examples (e.g., Bash, Azure CLI) alongside or in place of PowerShell scripts for gathering license usage and availability details.
- Mention and link to any Linux-compatible tools or scripts for license management and monitoring, or clarify if such tools are not available.
- Ensure that all steps and walkthroughs explicitly note any differences or additional steps required for Linux-based SQL Server deployments.
- Review the documentation for assumptions that all SQL Server workloads are Windows-based and update language to be inclusive of Linux scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/scope-level/sql-iaas-extension-registration.md
...billing/scope-level/sql-iaas-extension-registration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by only providing PowerShell script examples for registration checks and automation, referencing the Azure portal (which is platform-agnostic but often illustrated with Windows-centric workflows), and linking to a Windows-specific SQL IaaS Agent extension registration guide. There are no Linux CLI (e.g., Azure CLI, Bash) examples or explicit mention of Linux-based workflows, despite SQL Server being supported on Linux VMs in Azure.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for registration checks and automation, alongside PowerShell.
- Include explicit instructions or links for registering SQL IaaS Agent extension on Linux-based Azure VMs.
- Reference both Windows and Linux documentation for SQL IaaS Agent extension registration, not just the Windows-specific page.
- Clarify that the registration process and tools are applicable to both Windows and Linux SQL Server VMs, and highlight any differences.
- Add screenshots or walkthroughs that show Linux VM scenarios in addition to Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/troubleshoot-billing/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables.md
...tomer-agreement-billing-issues-usage-file-pivot-tables.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Microsoft Excel for all examples and instructions, with no mention of Linux-compatible spreadsheet tools (such as LibreOffice Calc or Google Sheets) or command-line alternatives. Keyboard shortcuts and menu navigation are tailored to Excel on Windows, and there are no Linux-specific instructions or screenshots. This may alienate users on Linux or macOS platforms.
Recommendations
- Include alternative instructions for opening and manipulating CSV files using Linux-compatible spreadsheet applications such as LibreOffice Calc or Google Sheets.
- Provide command-line examples for basic CSV analysis using tools like awk, csvkit, or pandas for users who prefer or require non-GUI solutions.
- Mention that the steps can be performed in other spreadsheet tools and, where possible, provide equivalent menu paths and shortcuts for those tools.
- Add screenshots or textual descriptions for at least one non-Windows spreadsheet application to improve inclusivity.
- Explicitly state that the process is cross-platform and highlight any differences or limitations users might encounter on Linux or macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/understand/plan-manage-costs.md
...ost-management-billing/understand/plan-manage-costs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows terminology and examples are prioritized (e.g., referencing 'Windows VM' specifically and showing screenshots of Windows VM sizing), while Linux is only mentioned in passing or as a secondary consideration. There are no Linux-specific examples or screenshots, and no mention of Linux command-line tools or workflows for cost management. The documentation assumes usage of the Azure Portal UI, which is platform-agnostic, but when OS-specific references are made, Windows is foregrounded.
Recommendations
- Include examples and screenshots for both Windows and Linux VMs when discussing cost estimation and management.
- When referencing VM sizes or features (such as auto-shutdown), provide parallel information for Linux VMs, not just Windows VMs.
- If mentioning OS-specific workflows (e.g., shutting down VMs from within the OS), clarify the process for both Windows and Linux.
- Where possible, mention or link to command-line tools (such as Azure CLI or Bash scripts) that are commonly used on Linux, in addition to portal-based workflows.
- Ensure that references to downloadable files (e.g., Excel price sheets) are accompanied by notes on how they can be used on Linux (e.g., with LibreOffice or CSV viewers).
- Review all screenshots and examples to ensure Linux parity, not just Windows-centric illustrations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/understand/mosp-new-customer-experience.md
...ent-billing/understand/mosp-new-customer-experience.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references PowerShell and APIs/SDKs for automation and management tasks but does not mention or provide examples for Linux/Unix command-line tools, Azure CLI, or scripting environments. There are no Linux-specific instructions or parity in automation tooling, and the only automation examples are PowerShell-focused, which is more common on Windows. This may make Linux users feel unsupported or require them to infer how to use equivalent tools.
Recommendations
- Include Azure CLI examples alongside PowerShell for all automation and scripting instructions, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that APIs and SDKs are available for use from Linux environments, and provide examples or links to relevant documentation.
- When referencing automation, list Azure CLI before or alongside PowerShell to avoid Windows-first bias.
- Add troubleshooting and operational instructions that are relevant to Linux users, such as using bash scripts or Linux-based authentication flows.
- Where screenshots or UI instructions are given, clarify that the Azure portal is accessible from any OS, and provide CLI alternatives where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/common-issues/updating-scalesets.md
...rticles/cyclecloud/common-issues/updating-scalesets.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing GUI-based navigation patterns (e.g., gear icon, Azure portal), which are more familiar to Windows users. There are no command-line examples (such as Azure CLI or PowerShell), and no Linux-specific guidance or parity is provided for checking quotas or resolving the issue.
Recommendations
- Add Azure CLI examples for checking VM quotas, as the CLI is cross-platform and widely used on Linux.
- Include PowerShell examples if desired, but ensure CLI examples are presented first or alongside them.
- Explicitly mention that the Azure portal and GUI navigation are platform-agnostic, but provide command-line alternatives for users on Linux or those who prefer automation.
- Consider adding a section titled 'Using the Azure CLI' with step-by-step instructions for Linux/macOS/WSL users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/cluster-templates.md
.../main//articles/cyclecloud/how-to/cluster-templates.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias by referencing Windows-specific Azure documentation (e.g., Spot VMs link points to /azure/virtual-machines/windows/spot-vms), using Windows-centric machine types (Standard_D4v3, H16r) in examples, and omitting explicit Linux or cross-platform command-line examples. There are no PowerShell commands, but the lack of Linux-specific examples or references, and the use of Windows terminology and links, indicate a Windows-first approach.
Recommendations
- Provide links to both Windows and Linux versions of Azure documentation (e.g., Spot VMs for Linux).
- Include Linux-specific or cross-platform examples where relevant, such as referencing Linux VM images or using Linux-friendly machine types.
- Balance terminology and examples to reflect both Windows and Linux environments, especially in areas like custom images, machine types, and configuration.
- Explicitly mention Linux support and provide sample configurations or commands for Linux-based clusters.
- Avoid using only Windows-centric documentation links or examples when the product is cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/ccws/plan-your-deployment.md
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows/Azure-centric bias by exclusively referencing Azure-native tools and patterns (such as Azure Bastion, VPN Gateway, and Microsoft Entra ID) without mentioning or providing parity for Linux-native or cross-platform alternatives. There are no Linux-specific examples, and the guidance assumes the use of Azure's ecosystem, which is more familiar to Windows administrators. No Linux command-line or open-source VPN/Bastion alternatives are discussed.
Recommendations
- Include examples or references for connecting to CycleCloud Workspace for Slurm from Linux environments, such as using OpenSSH, OpenVPN, or WireGuard for secure access.
- Mention open-source or cross-platform alternatives to Azure Bastion (e.g., SSH jump hosts) and provide guidance for their configuration.
- Provide Linux command-line examples for any required setup steps, such as configuring VPN connections or accessing resources.
- Clarify that while Azure-native tools are recommended, Linux-native and open-source options are also supported and can be integrated.
- Add a section or callout specifically addressing Linux users and their typical workflows for accessing and managing the Slurm environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/connect-to-node.md
...ob/main//articles/cyclecloud/how-to/connect-to-node.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides more detailed and explicit instructions for connecting to Windows nodes (e.g., RDP tunneling, launching the Microsoft RDP client) than for Linux nodes. While SSH is mentioned for Linux, there are no concrete Linux-specific examples or troubleshooting tips. Windows tools and workflows (RDP, Microsoft RDP client) are called out by name, and Windows scenarios are sometimes described before or more thoroughly than Linux equivalents.
Recommendations
- Add explicit, step-by-step examples for connecting to Linux nodes using SSH, including sample commands for common Linux SSH clients (e.g., OpenSSH on Linux/macOS).
- Provide parity in troubleshooting tips and workflow details for Linux users, such as how to use SSH agent forwarding on Linux and macOS.
- When describing connection methods, present Linux and Windows instructions side-by-side or in parallel sections to avoid the impression of Windows-first bias.
- Mention and provide examples for Linux-native RDP clients (e.g., Remmina, rdesktop, FreeRDP) when discussing RDP access to Windows nodes from non-Windows systems.
- Clarify any OS-specific steps or requirements for both Linux and Windows users, ensuring both are equally represented.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/scheduled-events.md
...b/main//articles/cyclecloud/how-to/scheduled-events.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides both Linux and Windows paths and script examples, but Windows is often mentioned first (e.g., script directories), and Windows-specific file paths and script extensions are given equal or slightly more prominence. There is no explicit Linux command-line or shell example, and the documentation refers to Windows batch scripts (.bat) alongside Linux shell scripts (.sh), but does not provide parity in terms of example commands or troubleshooting for Linux users.
Recommendations
- Alternate the order of Linux and Windows references throughout the documentation, or list Linux first to match the Azure VM Linux scheduled events link.
- Provide explicit Linux shell command examples (e.g., example contents of an onPreempt.sh script or how to make it executable with chmod).
- Include troubleshooting tips or common patterns for both Linux and Windows users.
- Clarify that both .sh and .bat scripts are supported, and provide a brief example for each.
- Where possible, link to Linux-specific documentation or tools, not just general or Windows-centric resources.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/user-authentication.md
...ain//articles/cyclecloud/how-to/user-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing examples and terminology specific to Windows (e.g., DOMAIN\user), and omitting Linux-specific authentication examples or tools. While LDAP is mentioned, no Linux-focused examples or guidance are provided, and the only explicit mention of Linux is in the context of SSH keys for cluster nodes, not authentication setup.
Recommendations
- Add Linux-focused authentication examples, such as integrating with OpenLDAP or other common Linux directory services, including example configurations.
- Provide sample user login formats for both Windows (DOMAIN\user) and Linux (uid=user,ou=People,dc=example,dc=com) environments.
- Include references to Linux-native tools and commands (e.g., ldapsearch, kinit, or PAM configuration) where relevant.
- Balance the order of sections by presenting generic LDAP or Linux-compatible authentication options before or alongside Active Directory.
- Clarify that Active Directory is not the only enterprise authentication option, and provide parity in troubleshooting and configuration guidance for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/use-spot-instances.md
...main//articles/cyclecloud/how-to/use-spot-instances.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently linking to Windows-specific Azure documentation (e.g., /azure/virtual-machines/windows/spot-vms) as the primary or only reference for Spot VM concepts, pricing, and eviction policy. Linux equivalents are only mentioned in passing or as secondary references. There are no Linux-specific configuration examples or command-line instructions, and the documentation does not provide parity in examples or references for Linux users.
Recommendations
- Provide equal prominence to Linux documentation links (e.g., /azure/virtual-machines/linux/spot-vms) alongside or before Windows links when discussing Spot VM concepts, pricing, and eviction policy.
- Include Linux-specific configuration examples or command-line instructions where relevant, especially in sections discussing VM configuration, eviction notification, and event handling.
- Ensure that references to Azure features (such as Scheduled Events) include both Windows and Linux documentation and usage patterns.
- Review all cross-references to ensure Linux users are not required to interpret Windows-centric instructions or adapt from Windows-first documentation.
- Consider adding a dedicated section or callouts for Linux users to clarify any differences or additional steps required for Linux-based clusters.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/hpcpack.md
...s/azure-docs/blob/main//articles/cyclecloud/hpcpack.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Server technologies, Active Directory, and Windows-based tools (such as PowerShell scripts and Windows Scheduled Tasks). There is no mention of Linux support, Linux-based configuration, or cross-platform parity. All examples, prerequisites, and operational details assume a Windows environment, and Linux compute nodes are explicitly not supported.
Recommendations
- Clearly state the lack of Linux support at the top of the documentation to set expectations.
- If/when Linux support is planned, provide equivalent Linux examples, tools, and workflows alongside Windows instructions.
- Reference Linux alternatives for cluster management, autoscaling, and credential handling where possible (e.g., cloud-init, Linux-based domain join, Linux CLI tools).
- Include a roadmap or links to Linux-compatible HPC solutions in Azure CycleCloud for users seeking cross-platform options.
- Avoid using only Windows/PowerShell terminology in CLI and automation sections; provide Bash or cross-platform CLI examples if/when Linux support is added.