Azure Arc
465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2334 issues found
Showing 951-975 of 2334 flagged pages
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for managing the Azure Connected Machine agent, including installation, upgrade, uninstall, and proxy configuration. However, Windows examples and tools (PowerShell, Control Panel, Group Policy, Microsoft Update, WSUS, Configuration Manager) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no Linux shell equivalent. Some sections (like Microsoft Update configuration) are inherently Windows-specific, but overall, Linux parity is good, though Windows-centric tools and scripting are emphasized.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for resource cleanup and stale server removal, not just PowerShell.
- Where possible, present Windows and Linux instructions side-by-side or in parallel, rather than Windows-first.
- Expand Linux uninstall instructions to include removal of residual folders/files, similar to Windows guidance.
- Clarify when a tool or method is Windows-only, and offer Linux alternatives where feasible.
- Consider including examples for macOS where relevant (e.g., Azure CLI usage).
Create Pull Request
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Linux and Windows ARM template examples for each extension, ensuring parity in template content. However, all deployment instructions and command-line examples exclusively use Azure PowerShell, with no Azure CLI or Bash equivalents shown. Additionally, PowerShell commands and Windows-style file paths are presented first and throughout, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. The documentation does mention Azure CLI in the 'Related content' section, but does not provide CLI examples inline.
Recommendations
- Add Azure CLI deployment command examples alongside PowerShell for each extension.
- Include Bash-style file paths and instructions for Linux/macOS users.
- Consider presenting CLI and PowerShell examples together, or alternate which is shown first.
- Clarify that PowerShell commands can be run cross-platform, but provide CLI alternatives for users who prefer them.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides disaster recovery steps for Azure Arc resource bridge in VMware vSphere environments, but all script examples and instructions are exclusively in PowerShell (.ps1), with no mention of Bash, shell, or cross-platform alternatives. The onboarding script and its usage are presented only in Windows/PowerShell context, and there is no guidance for Linux/macOS users on how to perform equivalent operations.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements for running the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS).
- Add instructions or examples for Linux/macOS users, including how to install prerequisites and run the script.
- Mention any limitations or workarounds for non-Windows environments.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy steps and script invocation, but does not offer equivalent Linux/macOS guidance. The script section is labeled 'Windows' and omits instructions for running the script on Linux or macOS, despite the Azure Arc agent supporting both platforms. This creates friction for non-Windows users, who must infer how to run the script or whether it is compatible. Additionally, Windows instructions are presented first and in greater detail.
Recommendations
- Add explicit instructions for running the deboarding script on Linux and macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any differences in behavior.
- Clarify script compatibility (e.g., if the script is PowerShell-only, note if PowerShell Core is required and how to install/run it on Linux/macOS).
- Present Windows and Linux/macOS instructions in parallel sections, or note any limitations for non-Windows platforms.
- Include troubleshooting or caveats for Linux/macOS users (e.g., file permissions, execution policy differences).
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation displays notable Windows bias in several areas. The example for installing kubectl uses Windows-specific tooling (winget) with no Linux/macOS alternative. The archive extraction example under the Bash tab uses Expand-Archive, which is a PowerShell/Windows command, not a native Bash/Linux command. There are no Linux/macOS-specific instructions for these steps, and Windows paths are used throughout. While Azure CLI and kubectl are cross-platform, the documentation assumes Windows environments and tools, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS alternatives for installing kubectl (e.g., using curl or package managers like apt, yum, brew).
- Replace Expand-Archive in Bash examples with native Linux commands (e.g., unzip or tar).
- Use generic or platform-neutral file paths in examples, or provide both Windows and Linux/macOS path examples.
- Explicitly mention cross-platform support and clarify any Windows-specific steps.
- Add a Linux/macOS tab for critical steps where the Bash tab is actually Windows-specific.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown first and exclusively in some cases. There are no explicit Linux-specific examples or mentions of Linux tools, and the Azure CLI is cross-platform, but the use of PowerShell syntax can create friction for Linux/macOS users.
Recommendations
- Provide both Bash and PowerShell examples for CLI commands, especially in sections where only PowerShell is shown.
- Clarify that Azure CLI commands work on all platforms and note any OS-specific syntax differences.
- Consider showing Bash examples first or side-by-side with PowerShell to improve Linux parity.
- Add explicit notes or links for Linux/macOS users regarding CLI usage and file path conventions.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively provides instructions for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. All examples and guidance are Windows/PowerShell-centric, with no mention of Linux/macOS alternatives or cross-platform scripting options. The script appears to require PowerShell, and there are no Bash or shell script equivalents or instructions for running PowerShell Core on Linux/macOS.
Recommendations
- Provide instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux/macOS, including any prerequisites or compatibility notes.
- Offer a Bash or shell script equivalent for Linux users, or clarify if the PowerShell script is cross-platform.
- Explicitly state whether the script is Windows-only or can be used on other operating systems.
- Include example commands for Linux/macOS environments, such as using ./RGCleanScript.ps1 in pwsh, or provide guidance for installing PowerShell Core.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is generally Linux-focused, but it relies on the Windows-specific PowerShell cmdlet Invoke-AksEdgeNodeCommand for critical configuration steps on Linux nodes. No direct Linux shell (bash/SSH) alternatives are provided for checking or setting sysctl parameters, which may hinder Linux/macOS users who do not have access to PowerShell or the Azure AKS Edge Essentials PowerShell module.
Recommendations
- Provide equivalent Linux shell (bash/SSH) commands for checking and setting sysctl parameters, such as 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
- Clarify whether Invoke-AksEdgeNodeCommand is available cross-platform or only via Windows/PowerShell, and offer guidance for Linux-only environments.
- Ensure all critical steps can be completed using native Linux tools and commands, not just PowerShell cmdlets.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides command-line examples for interacting with the SQL Server instance inside a Kubernetes pod, but consistently uses PowerShell syntax for these examples (e.g., 'kubectl exec ...' blocks are labeled as 'powershell'). There are no Linux/macOS shell (bash) equivalents or explicit mention that the commands work cross-platform. The use of PowerShell syntax and labeling may create confusion or friction for Linux/macOS users, even though the underlying commands are compatible.
Recommendations
- Replace 'powershell' code block labels with 'console' or 'bash' where appropriate, since 'kubectl' and 'sqlcmd' commands are cross-platform.
- Add explicit bash examples or clarify that the commands work on Linux/macOS terminals as well.
- Include notes or sections addressing Linux/macOS users, especially for decoding base64 secrets (e.g., 'echo <base64> | base64 -d' for bash).
- Ensure that any references to tools or steps are not Windows-specific unless required by the scenario.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) in the 'Tools' section, and explicitly mentions PowerShell scripting support as a manageability feature. While Azure PowerShell is marked as 'No', SQL Server PowerShell is marked as 'Yes', and PowerShell scripting is highlighted as a supported feature. There are no Linux-specific tools (such as sqlcmd, mssql-cli, or Azure Data Studio) mentioned, nor are cross-platform scripting alternatives (like Bash or Python) referenced. However, the page does not provide step-by-step examples, so the bias is mostly in tool listing and feature emphasis.
Recommendations
- Add Linux/macOS-compatible tools such as Azure Data Studio, sqlcmd, and mssql-cli to the 'Tools' section.
- Mention Bash scripting or Python as alternative scripting options for manageability.
- Clarify that PowerShell scripting support refers to cross-platform PowerShell Core, if applicable.
- Provide guidance or links for Linux/macOS users to manage SQL Managed Instance enabled by Azure Arc.
- Ensure parity in tool recommendations by listing cross-platform options alongside Windows tools.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for client tools across platforms, but Windows links are often listed first and some instructions are Windows-centric. For example, the kubectl installation section references Windows first and includes a note about using cmd.exe instead of PowerShell for curl, but does not provide equivalent Linux/macOS command guidance. The curl section gives a Windows link and only mentions 'Linux: install curl package' without a link or explicit command. There is also a PowerShell-specific note about curl aliases, but no similar notes for Linux/macOS shells.
Recommendations
- List Linux/macOS installation links before or alongside Windows links, rather than Windows first.
- Provide explicit Linux/macOS installation commands for tools like curl (e.g., 'sudo apt install curl' or 'brew install curl').
- Add shell-specific notes for Linux/macOS users (e.g., bash/zsh differences) where relevant, not just PowerShell.
- Ensure all tool installation instructions are equally detailed for all platforms.
- Where possible, provide cross-platform command examples, not just Windows-specific guidance.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as using Windows file paths (e.g., C:\Backupfiles\test.bak), referencing tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives, and showing Windows paths and examples before Linux equivalents. There are no explicit Linux/macOS examples for creating backups or copying files, and Linux file paths are only shown in restore commands, not in backup steps.
Recommendations
- Provide Linux/macOS examples for backing up SQL Server databases (e.g., using /home/user/Backupfiles/test.bak or /tmp/test.bak).
- Mention cross-platform tools such as Azure Data Studio or sqlcmd for database backup and restore, alongside SSMS.
- Show kubectl cp examples using Linux/macOS source file paths (e.g., /home/user/test.bak) in addition to Windows paths.
- Clarify that the steps and tools are applicable on both Windows and Linux, and highlight any OS-specific requirements.
- Add notes or sections for Linux/macOS users, including any differences in procedure or prerequisites.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Azure CLI installation with links that default to Windows instructions and does not specify Linux/macOS equivalents. There are no explicit Linux/macOS examples or guidance for management machine requirements, CLI installation, or file paths. Azure CLI is cross-platform, but the documentation does not acknowledge or provide parity for Linux/macOS users.
Recommendations
- Add explicit guidance and links for installing Azure CLI on Linux and macOS, not just Windows.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any OS-specific requirements or caveats.
- Include example file paths and CLI usage for Linux/macOS environments.
- Ensure all CLI commands are shown in a cross-platform manner (e.g., avoiding Windows-specific syntax or assumptions about directory structure).
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting HTTP2 errors, and Windows-specific tools (e.g., Remote PowerShell, RDP) are mentioned. In some cases, Windows command-line patterns (e.g., 'C:\Program Files...') are used in error messages. Linux-specific troubleshooting steps are limited, and Linux commands (such as nslookup, ldd) are referenced but not consistently provided as examples. Windows tools and patterns are often mentioned first or exclusively, with Linux equivalents missing or less detailed.
Recommendations
- Provide Linux/macOS equivalents for PowerShell troubleshooting steps (e.g., using curl or wget with HTTP2).
- Include Linux/macOS command examples alongside Windows commands for DNS resolution, file permissions, and proxy configuration.
- Avoid referencing Windows paths (e.g., 'C:\Program Files...') exclusively; include Linux paths where applicable.
- Clarify when steps are platform-specific and provide parity in guidance for both Windows and Linux management machines.
- Expand troubleshooting sections to explicitly address Linux/macOS scenarios, especially for CLI errors, SSH folder permissions, and proxy issues.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation for `azcmagent connect` shows evidence of Windows bias in several areas. The authentication options section lists 'Interactive browser login (Windows only)' first, and describes its default behavior on Windows before mentioning Linux defaults. Windows certificate store usage is detailed, while Linux equivalents are not. The access token section references the Windows PowerShell cmdlet `Get-AzAccessToken` as the primary example, without mentioning Linux/macOS alternatives. Overall, Linux is supported and mentioned, but Windows-specific tools and workflows are prioritized or exclusively described in some sections.
Recommendations
- Reorder authentication options so that cross-platform or Linux-default methods (e.g., device code, Azure CLI) are listed first or equally.
- When referencing access token acquisition, include Linux/macOS methods (e.g., Azure CLI: `az account get-access-token`) alongside PowerShell.
- For certificate-based authentication, clarify Linux/macOS certificate storage and usage, and provide examples for both platforms.
- Where Windows-specific tools (like certificate stores or PowerShell) are mentioned, add equivalent Linux/macOS guidance or explicitly state if not applicable.
- Ensure all examples and instructions are platform-neutral or provide both Windows and Linux/macOS variants.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux instructions for all major agent lifecycle tasks (install, upgrade, uninstall, proxy configuration). However, Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Registry Editor, Msiexec) are often presented first or in greater detail. The cleanup script for stale resources is PowerShell-only, with no Linux/bash equivalent. Windows-specific tools and patterns are described extensively, while Linux instructions are concise and rely on standard package managers.
Recommendations
- Where possible, present Linux and Windows instructions in parallel or with equal prominence.
- Provide a bash or Azure CLI equivalent for the PowerShell cleanup script to enable Linux users to automate stale resource removal.
- Include more detailed Linux automation examples (e.g., using cron, systemd, or shell scripts) for tasks like upgrades and uninstalls.
- Consider adding troubleshooting tips for Linux environments, similar to the Windows-specific guidance.
- For proxy configuration, clarify any OS-specific nuances and provide examples for both Windows and Linux in each section.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment instructions and sample commands are exclusively given in Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands and Windows-style file paths are shown first and throughout, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does mention that extensions can be deployed to Linux or Windows machines, but the actual deployment workflow is Windows/PowerShell-centric.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands for ARM template deployment.
- Include Bash shell examples for Linux/macOS users, especially for editing and deploying templates.
- Use platform-neutral file paths in examples (e.g., './AzureMonitorAgent.json') or provide both Windows and Linux path formats.
- Explicitly state that Azure CLI and Bash can be used for deployment, and link to relevant CLI documentation.
- Consider alternating the order of Linux and Windows examples to avoid Windows-first bias.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page presents a notable Windows bias, especially in the 'Auto Arc-enablement script' section, which exclusively provides PowerShell examples and references Windows Task Scheduler for automation. The script usage instructions are Windows-centric, with no Linux/macOS equivalents or guidance. Windows tools and automation patterns are mentioned first and in detail, while Linux approaches are only briefly referenced or omitted. Although the out-of-band methods mention Ansible playbooks, no Linux-specific example or parity is provided for the main scripted method.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, including instructions for running the helper script in those environments.
- Include guidance for automating the script via cron jobs on Linux, not just Windows Task Scheduler.
- Clarify whether the helper script can run on Linux/macOS, and if not, offer a Linux-compatible alternative.
- Ensure that both Windows and Linux automation patterns (e.g., PowerShell vs. Bash, Task Scheduler vs. cron) are covered equally.
- Add Linux/macOS-specific troubleshooting and prerequisites, such as handling sudo privileges and script execution permissions.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides only PowerShell script examples and instructions, with no mention of Bash, Linux, or macOS equivalents. The onboarding and recovery steps are centered around editing and running a PowerShell (.ps1) script, and all code samples are PowerShell-based. There is no guidance for Linux/macOS users, nor are cross-platform alternatives discussed.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements for running the onboarding script (e.g., Windows-only, or if PowerShell Core is supported on Linux/macOS).
- If possible, offer instructions for running the onboarding script using PowerShell Core on Linux/macOS, or provide alternative methods for Linux users.
- Add a note about platform compatibility and any prerequisites for non-Windows environments.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page consistently uses PowerShell syntax for all CLI command examples and references PowerShell scripts (.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor is there guidance for running the Azure CLI commands on Linux/macOS. The use of PowerShell and Windows script files is presented as the default, which may create friction for Linux/macOS users.
Recommendations
- Provide Azure CLI command examples in Bash syntax, or clarify that the CLI commands work identically on Linux/macOS terminals.
- Offer equivalent Bash scripts for bulk deployment and workflow deletion, or explain how Linux/macOS users can run the PowerShell scripts (e.g., via PowerShell Core or alternative methods).
- Add notes or sections indicating cross-platform compatibility of the Azure CLI commands.
- Explicitly mention any platform-specific requirements or limitations for scripts, and provide alternatives where possible.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy guidance and script invocation. There are no equivalent instructions or examples for running the script on Linux/macOS, nor is it clarified whether the script can be run cross-platform. Windows instructions are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
- Clarify whether the deboarding script can be run on Linux/macOS (e.g., with PowerShell Core or Azure CLI).
- If supported, provide explicit Linux/macOS instructions for downloading and running the script, including any prerequisites (such as PowerShell Core installation or using Bash/Azure CLI).
- If the script is Windows-only, state this clearly and provide alternative manual steps or scripts for Linux/macOS users.
- Present both Windows and Linux/macOS instructions in parallel, or at least mention Linux/macOS options before or alongside Windows guidance.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for all orchestration, onboarding, and log collection tasks. File paths in JSON templates and scripts use Windows conventions (e.g., C:\, E:\), and there are no Bash, Linux shell, or cross-platform CLI examples. The onboarding and diagnostic scripts are referenced as PowerShell (.ps1) files, with no mention of Linux/macOS equivalents or how to run these tasks on non-Windows systems. This creates friction for Linux/macOS users, who may not be able to follow the steps directly.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell (.ps1) scripts, or clarify if cross-platform support exists.
- Use generic or cross-platform file paths in JSON templates (e.g., /home/user/... instead of C:\Users\...).
- Add explicit instructions for Linux/macOS users, including how to run Azure CLI commands in Bash and how to handle onboarding if PowerShell scripts are not available.
- Mention any limitations or requirements for running orchestration scripts on Linux/macOS, and provide alternatives if possible.
- Where possible, show Azure CLI commands in Bash syntax (with line continuations using \) alongside PowerShell examples.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script (WOGAMigration.ps1) for migration, with instructions to run it in PowerShell. There are no Bash, Linux shell, or cross-platform alternatives mentioned, and no guidance for Linux/macOS users on how to perform the migration.
Recommendations
- Provide a Bash or cross-platform script for Linux/macOS users.
- Document how to run the PowerShell script using PowerShell Core (pwsh) on Linux/macOS, if applicable.
- Explicitly state platform requirements and offer alternatives or workarounds for non-Windows environments.
- Add Linux/macOS-specific instructions or examples alongside Windows/PowerShell guidance.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas: Windows-specific tools (winget) are used for kubectl installation without Linux/macOS alternatives; file extraction instructions use Windows paths and PowerShell/Bash examples, but Bash is shown with Windows-centric commands; Windows paths and patterns are used throughout, and Linux/macOS users are not provided with equivalent instructions for key steps (e.g., kubectl install, file extraction).
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using curl or package managers like apt, yum, brew).
- For file extraction, include Linux/macOS Bash commands (e.g., unzip or tar) alongside Windows Expand-Archive.
- Show Bash examples with POSIX-style paths (e.g., /home/user/archive.zip) and clarify when Windows paths are used.
- Add explicit notes or tabs for Linux/macOS users where commands or tools differ.
- Ensure parity in all setup steps, including global variable definitions and file manipulations.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most command-line examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). There are no Bash or Linux shell equivalents for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, which uses Bash/PowerShell tabs. This creates friction for Linux/macOS users, as they must translate PowerShell-specific commands and patterns to their environment.
Recommendations
- Provide Bash/Linux shell equivalents for all Azure CLI, Docker, and kubectl commands.
- Avoid using PowerShell-specific syntax (e.g., variables like $var, ConvertTo-Json, Out-File) in cross-platform scenarios; use generic CLI syntax or provide both PowerShell and Bash versions.
- Clearly indicate when a command is Windows-only, and offer alternative instructions for Linux/macOS users.
- Use tabs or sections to separate Windows/PowerShell and Linux/Bash examples throughout the troubleshooting steps, not just in the 'service groups' section.