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 1876-1900 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/authenticate-with-entra-id-namespaces.md
...es/event-grid/authenticate-with-entra-id-namespaces.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias by referencing Windows-specific resources first (e.g., enabling managed identities on a VM links to a Windows VM guide), and by omitting explicit Linux or cross-platform command-line examples for authentication or role assignment. All code samples are in C#/.NET, which is cross-platform but traditionally associated with Windows. There are no PowerShell-specific commands, but there is a lack of parity in showing Linux or CLI-based workflows.
Recommendations
- When referencing enabling managed identities on VMs, provide both Windows and Linux VM links, or a neutral overview page.
- Include Azure CLI examples for authentication and role assignment, as these are cross-platform and widely used on Linux.
- Provide at least one code sample in a language commonly used on Linux (e.g., Python or JavaScript), or explicitly mention that the SDKs and code samples work on Linux as well.
- If environment variable setup is shown, clarify how to do this on both Windows (setx, PowerShell) and Linux (export in Bash).
- Review all links and ensure that Linux and cross-platform documentation is referenced alongside or before Windows-specific resources.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/mpa-request-ownership.md
...ost-management-billing/manage/mpa-request-ownership.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes procedures using the Azure portal web interface, with all screenshots and instructions reflecting a Windows-centric user experience. There are no command-line examples (e.g., Azure CLI, PowerShell, Bash) or references to cross-platform tools, nor is there any mention of Linux or macOS environments. This implicitly prioritizes Windows workflows and may leave Linux/macOS users without clear guidance for automation or non-GUI scenarios.
Recommendations
- Provide equivalent instructions using Azure CLI, which is cross-platform and works on Windows, Linux, and macOS.
- Include example commands for common transfer operations using Azure CLI or REST API, enabling automation and non-GUI workflows.
- Explicitly state that the Azure portal is web-based and accessible from any OS, but also offer links to documentation for CLI-based management.
- Add a section or note addressing how Linux/macOS users can perform these tasks, referencing relevant tools or scripts.
- Where possible, avoid screenshots or instructions that assume a specific OS or browser, or clarify that the steps are OS-agnostic.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/blob-event-quickstart-template.md
.../articles/event-grid/blob-event-quickstart-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by primarily referencing the Azure Portal and mentioning Azure PowerShell before Azure CLI when discussing alternative deployment methods. There are no explicit Linux or cross-platform command-line examples, and the only detailed deployment instructions use the Azure Portal, which is platform-agnostic but often associated with Windows workflows. The mention of PowerShell before CLI in the deployment section further reinforces a subtle Windows-first bias. No Linux-specific tools or shell examples are provided.
Recommendations
- Provide explicit Azure CLI examples for template deployment, including command-line instructions that work on Linux, macOS, and Windows.
- When listing alternative deployment methods, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
- Include a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
- Add sample shell commands (bash) for uploading files to Blob storage, such as using 'az storage blob upload' or 'curl', to demonstrate parity with PowerShell examples.
- Ensure that all screenshots and instructions are clearly cross-platform or provide platform-specific guidance where necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/understand-ea-roles.md
.../cost-management-billing/manage/understand-ea-roles.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively references the Azure portal and web-based workflows for managing Enterprise Agreement roles, with no mention of command-line tools or automation options. There are no examples or references to Windows-specific tools like PowerShell, but there is also a complete absence of Linux or cross-platform CLI (such as Azure CLI) instructions. The documentation implicitly assumes a GUI/web workflow, which is more common in Windows-centric environments, and does not provide parity for users who prefer or require Linux or command-line automation.
Recommendations
- Add examples and instructions for managing EA roles using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- If PowerShell examples are added in the future, ensure equivalent Azure CLI examples are provided.
- Explicitly mention that all administrative tasks can be performed via the Azure CLI or REST API, and link to relevant documentation.
- Include a section or callout for automation and scripting options, highlighting tools available on Linux.
- Review the documentation for any implicit assumptions about the user's operating system or interface, and clarify when tasks are cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/reservations/calculate-ea-reservations-savings.md
...ling/reservations/calculate-ea-reservations-savings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Excel-first bias by exclusively providing step-by-step instructions and screenshots for Microsoft Excel, a Windows-centric tool, without offering equivalent examples or guidance for Linux users or alternative spreadsheet tools. There are no command-line or open-source alternatives (e.g., LibreOffice Calc, csvkit, pandas) mentioned or demonstrated, and all workflow descriptions assume use of Excel's GUI, which is not universally available or preferred, especially on Linux systems.
Recommendations
- Add parallel instructions and screenshots for at least one popular cross-platform or Linux-native spreadsheet tool, such as LibreOffice Calc or Google Sheets.
- Include a section or callout on how to perform the calculations using command-line tools (e.g., csvkit, awk, pandas) for users who prefer or require non-GUI workflows.
- When referencing Excel, clarify that any spreadsheet application can be used, and provide at least brief guidance for alternatives.
- Consider providing downloadable example scripts (e.g., Python, bash) that automate the calculation process for users on Linux or macOS.
- Ensure that all steps that reference Excel-specific features (like 'Format as Table') are either generalized or have alternative instructions for other tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/reservations/reservation-apis.md
...st-management-billing/reservations/reservation-apis.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell as a method for managing reservations (e.g., splitting reservations), and lists the PowerShell method before the Azure CLI method in the section on role assignments. There are no explicit Linux-only examples or tools, and the CLI is mentioned after PowerShell, which may suggest a Windows-first approach. However, most API examples are platform-neutral, and there are no overtly missing Linux examples.
Recommendations
- When listing command-line tools, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
- Provide explicit Azure CLI examples for all operations where PowerShell is mentioned, especially for tasks like splitting reservations.
- Where possible, include bash or shell script examples to demonstrate parity for Linux users.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide links to installation/use instructions for both on Windows, Linux, and macOS.
- Audit linked articles (such as those for splitting reservations) to ensure they contain CLI and Linux-friendly instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/savings-plan/calculate-ea-savings-plan-savings.md
...ling/savings-plan/calculate-ea-savings-plan-savings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references Excel for data preparation and formula calculation, with all screenshots and instructions tailored to the Excel interface (a Windows-centric tool). There are no examples or guidance for users on Linux or macOS, nor are alternative spreadsheet tools (such as LibreOffice Calc, Google Sheets, or command-line CSV tools) demonstrated. This creates a Windows-first bias and omits Linux-friendly workflows.
Recommendations
- Explicitly mention and provide examples for alternative spreadsheet tools such as LibreOffice Calc (Linux/macOS/Windows), Google Sheets (web-based), or Numbers (macOS).
- Include screenshots or step-by-step instructions for at least one non-Excel tool to demonstrate parity.
- Add a section or note on how to perform the calculations using command-line tools (e.g., awk, csvkit, pandas in Python) for users who prefer or require scriptable, non-GUI workflows.
- Rephrase instructions to use more generic spreadsheet terminology (e.g., 'spreadsheet application' instead of 'Excel'), and avoid referencing Excel-specific UI elements unless alternatives are also described.
- Where possible, provide downloadable sample scripts (e.g., Python, bash) that automate the calculations for users on Linux or in headless environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/savings-plan/manage-savings-plan.md
...management-billing/savings-plan/manage-savings-plan.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively describes management of Azure savings plans using the Azure Portal (a web-based GUI), with no mention of command-line tools or automation methods. There are no examples or references to CLI tools such as Azure CLI or Azure PowerShell, nor are there any Linux-native instructions or scripts. While PowerShell is not explicitly mentioned, the absence of Azure CLI or Linux command-line examples constitutes a bias towards Windows-centric or GUI-based workflows, which are more familiar to Windows users.
Recommendations
- Add equivalent Azure CLI command examples for all major tasks (e.g., changing scope, viewing details, delegating roles), as Azure CLI is cross-platform and widely used on Linux.
- Where relevant, provide Azure PowerShell examples alongside Azure CLI, but do not prioritize PowerShell over CLI.
- Explicitly mention that all tasks can be performed from Linux, macOS, or Windows using the Azure CLI.
- Include links to official Azure CLI documentation for managing savings plans.
- Consider adding automation examples (e.g., shell scripts) for common scenarios to support Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/troubleshoot-subscription/troubleshoot-sign-in-issue.md
...roubleshoot-subscription/troubleshoot-sign-in-issue.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides browser troubleshooting steps with detailed instructions for Edge (a Microsoft browser) and Chrome, and to a lesser extent Safari, but omits explicit instructions for Firefox and does not address Linux-specific browser workflows. Additionally, all examples and UI paths are described using Windows-centric terminology (e.g., Edge settings), with no mention of Linux or its common browsers and tools.
Recommendations
- Include instructions for Firefox, which is widely used on Linux platforms.
- Add Linux-specific guidance for clearing browser cache and cookies, including command-line options where appropriate.
- When listing browsers, avoid always listing Edge first; consider rotating or grouping browsers by platform.
- Explicitly mention that the steps apply to all platforms, and note any platform-specific differences.
- Provide parity in troubleshooting steps for Linux users, such as referencing Linux desktop environments or common Linux browsers.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/scope-level/sql-server-hadr-licenses.md
...gement-billing/scope-level/sql-server-hadr-licenses.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on SQL Server HADR configuration within the Azure portal, referencing concepts and tools (such as Always On availability groups and SQL Server roles) that are traditionally associated with Windows environments. There are no examples or mentions of Linux-based SQL Server deployments, nor are there instructions or screenshots relevant to Linux users. The documentation implicitly assumes a Windows-centric context.
Recommendations
- Include explicit mention that SQL Server HADR is supported on both Windows and Linux platforms, if applicable.
- Provide parallel instructions or screenshots for configuring HADR on SQL Server running on Linux VMs in Azure.
- Reference Linux-specific tools or command-line methods (such as az CLI or bash scripts) for managing HADR settings, in addition to or instead of GUI-based instructions.
- Clarify any platform-specific differences in HADR benefit selection or licensing behavior between Windows and Linux SQL Server deployments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/troubleshoot-billing/troubleshoot-ea-billing-issues-usage-file-pivot-tables.md
...troubleshoot-ea-billing-issues-usage-file-pivot-tables.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Microsoft Excel for all examples and screenshots, and all step-by-step instructions assume the use of Excel on Windows. There is no mention of Linux-compatible spreadsheet tools (such as LibreOffice Calc), nor are there alternative instructions or screenshots for non-Windows platforms. This creates a bias toward Windows users and may exclude or confuse Linux users.
Recommendations
- Include alternative instructions and screenshots for popular Linux spreadsheet applications, such as LibreOffice Calc or Gnumeric.
- Explicitly mention that the CSV files can be opened and manipulated in any spreadsheet software, and provide links to cross-platform or Linux-native tools.
- Where keyboard shortcuts or menu paths are given, provide equivalents for Linux and macOS environments.
- Add a section or note addressing Linux users, outlining any differences in workflow or UI they might encounter.
- Avoid using Excel-specific terminology or features unless they are also available in other spreadsheet applications, or clearly indicate when a feature is Excel-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/troubleshoot-billing/billing-troubleshoot-azure-payment-issues.md
...t-billing/billing-troubleshoot-azure-payment-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Microsoft Edge and Internet Explorer explicitly when suggesting private browsing for troubleshooting, without mentioning Linux browsers or providing equivalent instructions for Linux users. No Linux-specific tools, browsers, or troubleshooting steps are mentioned, and all browser-related guidance is Windows-centric. There are no command-line examples, but the only browser guidance assumes a Windows environment.
Recommendations
- When suggesting private browsing, include instructions for popular Linux browsers such as Firefox and Chromium (e.g., 'Open a private/incognito window in your browser, such as Firefox, Chrome, or Edge').
- Avoid referencing only Microsoft Edge or Internet Explorer; instead, provide cross-platform browser instructions or mention that the steps apply to any modern browser.
- If browser cache/cookie clearing is recommended, provide generic steps or link to documentation for multiple browsers and platforms.
- Review the documentation for any other implicit Windows assumptions and ensure parity for Linux and macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/understand/download-azure-daily-usage.md
...ement-billing/understand/download-azure-daily-usage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes how to view and download Azure usage and charges using the Azure portal, with all screenshots and instructions reflecting the web interface, which is platform-agnostic. However, in the section on using the Azure CLI to automate data export, there are no examples or notes about running the CLI on Linux or macOS, nor are there any shell-specific considerations or examples. There is also no mention of PowerShell or Windows-specific tools, but the absence of Linux/macOS-specific guidance or examples constitutes a subtle Windows/portal-first bias.
Recommendations
- Explicitly mention that the Azure CLI commands work on Windows, Linux, and macOS, and provide example commands in both Bash (for Linux/macOS) and PowerShell (for Windows), if relevant.
- Add notes or links about installing and using the Azure CLI on Linux and macOS, including any OS-specific prerequisites or troubleshooting tips.
- If screenshots are used for command-line operations, include examples from both Windows (e.g., Command Prompt or PowerShell) and Linux/macOS (e.g., Bash terminal).
- Clarify that the Azure portal is accessible from any modern browser on any OS, to reinforce platform neutrality.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/troubleshoot-billing/troubleshoot-csp-billing-issues-usage-file-pivot-tables.md
...roubleshoot-csp-billing-issues-usage-file-pivot-tables.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Microsoft Excel for all examples and screenshots, and all instructions are written with Excel-specific terminology and keyboard shortcuts (e.g., Ctrl+Shift+Arrow), which are Windows-centric. There are no examples or guidance for Linux users or for alternative spreadsheet tools (such as LibreOffice Calc, Google Sheets, or command-line CSV tools), nor are there any references to how to perform similar tasks outside of Excel/Windows environments.
Recommendations
- Provide equivalent instructions and screenshots for at least one popular Linux-compatible spreadsheet application, such as LibreOffice Calc.
- Mention and briefly describe how to use open-source or cross-platform tools (e.g., LibreOffice Calc, Google Sheets, csvkit, pandas) to manipulate large CSV files and create pivot tables.
- Replace or supplement Excel-specific keyboard shortcuts and menu paths with generic or cross-platform alternatives.
- Add a section or callout noting that the steps can be performed on Linux/macOS using alternative tools, and link to relevant resources or documentation.
- Where possible, provide command-line examples (e.g., using csvkit or pandas) for users who prefer not to use GUI spreadsheet applications.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/understand/review-enterprise-agreement-bill.md
...billing/understand/review-enterprise-agreement-bill.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Excel for CSV report handling and troubleshooting, without mentioning or providing guidance for Linux or cross-platform alternatives. There are no examples or instructions for viewing or manipulating CSV files using Linux tools (such as LibreOffice Calc, csvkit, or command-line utilities), nor is there mention of how to address CSV formatting issues outside of Excel. All portal navigation and examples assume the use of the Azure web portal, which is cross-platform, but the only tooling guidance is Windows-centric.
Recommendations
- Add instructions for opening and formatting CSV reports using Linux-compatible tools such as LibreOffice Calc, OpenOffice, or command-line utilities (e.g., csvkit, awk, sed).
- Include troubleshooting tips for CSV formatting issues in non-Windows environments, such as using locale-aware import options in LibreOffice or specifying delimiters with command-line tools.
- Provide at least one example of downloading and viewing reports using Linux or macOS tools, or reference cross-platform solutions.
- Consider mentioning that the Azure portal is accessible from any modern browser on Windows, Linux, or macOS, to reinforce cross-platform compatibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/common-issues/staging-resources.md
...articles/cyclecloud/common-issues/staging-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing the Azure portal's graphical interface (commonly associated with Windows workflows) for checking storage account settings, without providing equivalent command-line instructions (such as Azure CLI or PowerShell) that would be more cross-platform. There are no Linux-specific or CLI-based examples or guidance, which may disadvantage users on Linux or those preferring automation.
Recommendations
- Add Azure CLI examples for checking if Hierarchical namespace is enabled, e.g., using 'az storage account show'.
- Provide PowerShell and Azure CLI command examples for granting permissions, not just portal-based instructions.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows using CLI tools.
- Include links to relevant Azure CLI and PowerShell documentation for managing storage accounts and permissions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/add-disk.md
...docs/blob/main//articles/cyclecloud/how-to/add-disk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Links
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows documentation links before Linux equivalents in the disk types section, even though the product is cross-platform. There are no explicit Windows-only examples or tools, but the ordering and linking pattern subtly prioritizes Windows.
Recommendations
- Ensure that documentation links reference Linux documentation first or provide both Linux and Windows links side by side, especially since Azure CycleCloud is often used for Linux HPC workloads.
- Review all external links to ensure parity between Linux and Windows documentation, or use neutral, platform-agnostic links where possible.
- Explicitly mention that the instructions and options apply equally to both Linux and Windows VMs, or clarify any platform-specific differences.
- Consider adding a short section or note confirming Linux compatibility and providing direct links to Linux disk documentation for clarity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/download-cluster-templates.md
...ain//articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists Microsoft HPC Pack—a Windows-specific scheduler—prominently among cluster template types, and links to Windows PowerShell documentation for it. This gives Windows tools visibility equal to or greater than Linux-native schedulers. There are no explicit Linux command-line or shell examples, but the CLI example is cross-platform. However, the inclusion and linking of Windows tools and documentation before or alongside Linux equivalents may indicate a subtle Windows bias.
Recommendations
- Ensure Linux-native tools (e.g., Slurm, OpenPBS, HTCondor) are described with equal detail and prominence as Windows tools.
- Avoid linking to Windows/PowerShell documentation (e.g., for HPC Pack) without providing equivalent Linux-focused documentation for other schedulers.
- Add explicit Linux shell (bash) examples where possible, or clarify that the CLI commands are cross-platform.
- Consider ordering the template types so that Linux-native schedulers are not overshadowed by Windows-specific options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/ccws/configure-open-ondemand.md
...cles/cyclecloud/how-to/ccws/configure-open-ondemand.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of the Azure CycleCloud web portal and Microsoft Entra ID (both Microsoft-centric tools), without providing command-line or Linux-native alternatives. There are no Linux shell or CLI examples, and the workflow is described entirely through a GUI that is typical of Windows environments. No mention is made of how to perform these steps on Linux or via cross-platform tools.
Recommendations
- Provide equivalent command-line instructions using Azure CLI or REST API, which are cross-platform and can be run from Linux.
- Include examples or references for configuring Open OnDemand authentication using Linux shell commands or scripts.
- Clarify whether the CycleCloud web portal is accessible and fully functional from Linux systems, and mention any Linux-specific considerations.
- Where possible, avoid assuming a GUI workflow and offer text-based alternatives for automation and scripting.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/ccws/open-ondemand-add-users.md
...cles/cyclecloud/how-to/ccws/open-ondemand-add-users.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation focuses exclusively on user management through the CycleCloud web portal, a Microsoft-centric tool, without mentioning or providing examples for Linux-native tools or command-line methods. There are no Linux or POSIX command-line instructions, and the workflow is tightly coupled to Microsoft Entra ID and CycleCloud, which are more common in Windows-centric environments.
Recommendations
- Include instructions or examples for adding users via Linux command-line tools (e.g., useradd, adduser) for environments where CycleCloud is not used or for advanced users.
- Mention how user management integrates with standard Linux authentication and user management systems (e.g., /etc/passwd, LDAP).
- Provide parity by referencing or linking to Linux-native user management documentation.
- Clarify whether CycleCloud is required, or if there are alternative workflows for non-Windows or hybrid environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/managed-identities.md
...main//articles/cyclecloud/how-to/managed-identities.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation references Managed Identity configuration using Azure portal links that specifically mention Windows VMs, and does not provide any Linux-specific examples or guidance. There are no command-line examples for Linux users, nor are there references to Linux VM configuration or parity in the instructions.
Recommendations
- Include links to Azure documentation for configuring Managed Identities on Linux VMs, not just Windows VMs.
- Provide example workflows or screenshots for both Windows and Linux VM scenarios.
- Add Azure CLI examples for assigning Managed Identities to Linux VMs, as this is the primary method for Linux users.
- Ensure that all references to portal workflows or quickstarts are platform-neutral or provide both Windows and Linux variants where differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/install-cyclecloud-cli.md
...//articles/cyclecloud/how-to/install-cyclecloud-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally presents Windows-specific instructions and tools (such as PowerShell scripts and right-click extraction) before or with more detail than Linux equivalents. The Windows installation section is more prescriptive about using PowerShell and GUI actions, while the Linux section assumes more familiarity and omits some details. The prerequisite section also links only to Windows Python installation, despite mentioning Linux and Mac.
Recommendations
- Provide equal prominence and detail for Linux and Windows instructions, including explicit Linux/Mac Python installation links in the prerequisites.
- Include command-line alternatives for Windows users (e.g., using PowerShell or Command Prompt to unzip and run the installer, not just GUI steps).
- Ensure that Linux and Mac instructions are as detailed as Windows instructions, including troubleshooting tips and environment setup.
- Consider grouping platform-specific instructions under clear headings, and avoid always listing Windows first.
- Add a Mac-specific section if the CLI supports macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/install-arm.md
...s/blob/main//articles/cyclecloud/how-to/install-arm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by mentioning Windows users and their shell options before Linux users, and by not providing Linux-specific command examples or guidance beyond a link for SSH key generation. The instructions are generally cross-platform, but Linux-specific nuances and examples are underrepresented.
Recommendations
- Present instructions for Linux and Windows users in parallel, rather than listing Windows first.
- Provide explicit Linux command examples and troubleshooting tips, not just links.
- Clarify any differences in Azure CLI usage or environment setup between Windows, Linux, and macOS.
- Include notes on where files (like SSH keys) are stored on different platforms.
- Add a section or callouts for common Linux/macOS issues or best practices when using CycleCloud.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/images.md
...cs/azure-docs/blob/main//articles/cyclecloud/images.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by providing only Windows-based examples for specifying images (e.g., 'cycle.image.win2022', 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-g2:latest', 'Windows 2022 DataCenter'). No Linux-based examples are shown in the configuration snippets, despite Linux images being supported and listed in the table. This may lead Linux users to feel less supported or unsure about the correct syntax for their use case.
Recommendations
- Add Linux-based examples alongside Windows examples in all configuration snippets. For example, show how to specify an Ubuntu or CentOS image using ImageName, URN, and Image label.
- Alternate the order of examples or provide both Windows and Linux examples together to avoid the impression of Windows being the default or preferred platform.
- Explicitly mention that the same configuration patterns apply to Linux images, and provide at least one full Linux example for each method of specifying images.
- If possible, include a note or section highlighting Linux-specific considerations or best practices, to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/htcondor.md
.../azure-docs/blob/main//articles/cyclecloud/htcondor.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows configuration options for HTCondor, but in several places, Windows paths and settings are mentioned alongside or before Linux equivalents. Some configuration options are marked as '(Windows only)', and Windows paths (e.g., C:\condor) are given equal or earlier prominence to Linux paths. However, all code and usage examples (such as cluster definitions and CLI commands) use Linux images and tools, and there are no PowerShell or Windows command-line examples.
Recommendations
- Ensure Linux paths and configuration options are always listed first, as Linux is the primary platform for HTCondor.
- Where Windows-specific options are mentioned, clearly separate them into a dedicated subsection or table row, rather than mixing them with Linux defaults.
- If Windows support is secondary, clarify this in the introduction and focus examples on Linux.
- Provide explicit Linux and Windows examples side-by-side if Windows is a supported platform, or otherwise minimize Windows references to avoid confusion.
- For configuration tables, group Linux and Windows defaults in separate columns or rows for clarity.