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 676-700 of 2334 flagged pages
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a generally cross-platform overview but exhibits some Windows bias. Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly, while Linux equivalents (such as Cockpit, cloud-init, or Linux package managers) are not. PowerShell is referenced as a deployment method, but Bash is only mentioned generically, with no concrete Linux command-line examples. There are no Linux-specific deployment walkthroughs or examples, and Windows deployment options are listed before Linux ones.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, cloud-init, or Ansible for onboarding Linux servers.
- Mention Linux-native tools (e.g., Cockpit, systemd, package managers) where appropriate, especially in the 'Deploying Azure Arc' section.
- Provide concrete Bash or shell command examples alongside PowerShell, not just generic references.
- Balance the order of presentation so that Linux and Windows deployment options are given equal prominence.
- Clarify that all major features and workflows are supported on both Windows and Linux, or call out any exceptions.
Create Pull Request
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples (especially in PowerShell and REST API sections) are Windows-centric. PowerShell examples use Windows-style scripts and paths, and REST API examples exclusively show Windows-specific commands (e.g., New-NetFirewallRule). There is a lack of Linux-specific script examples (e.g., using bash or Linux firewall commands), and Windows tools (like New-AzStorageBlobSASToken) are referenced without Linux equivalents. The Azure CLI section also defaults to PowerShell syntax in its script example. Linux is only mentioned in passing, and Linux users are left to infer how to adapt the examples.
Recommendations
- Provide parallel Linux-focused examples for each scenario, using bash scripts, Linux shell commands, and Linux file paths.
- In PowerShell sections, clarify cross-platform usage or provide bash alternatives where possible.
- In REST API examples, include at least one Linux scenario (e.g., using iptables or ufw for firewall configuration).
- When referencing tools like New-AzStorageBlobSASToken, mention cross-platform alternatives or CLI equivalents.
- In all sections, alternate or balance the order of Windows and Linux examples, or clearly label which OS each example targets.
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 exhibits moderate Windows bias. The primary automation script is PowerShell-based, with instructions to use Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents. Linux-specific guidance is limited to a brief sudo configuration note, and there are no Linux shell or cron examples for running the automation script. Out-of-band methods mention Ansible, but most scripted examples and automation focus on Windows environments.
Recommendations
- Provide equivalent Bash/shell script examples for Linux/macOS users, including instructions for running the automation script in a Linux environment.
- Add guidance for scheduling the automation script using Linux cron jobs, not just Windows Task Scheduler.
- Ensure that all PowerShell scripts are accompanied by Linux-compatible alternatives or clarify if the script is Windows-only.
- Mention Linux tools and patterns (e.g., systemd timers, cron) alongside Windows tools.
- Expand Linux-specific prerequisites and troubleshooting sections.
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 exclusively provides PowerShell examples and references the onboarding script as a PowerShell (.ps1) script, with no mention of Bash, Linux shell, or cross-platform alternatives. All command-line instructions and code snippets are PowerShell-based, and there is no guidance for Linux or macOS users on how to perform equivalent operations or run the script. This creates friction for non-Windows users attempting disaster recovery operations.
Recommendations
- Provide explicit instructions for running the onboarding script on Linux/macOS, including prerequisites (such as PowerShell Core installation) and any differences in usage.
- Offer Bash or shell script alternatives if available, or clarify if the onboarding script is cross-platform and how to execute it on non-Windows systems.
- Add notes about required tools for Linux/macOS users (e.g., PowerShell Core, Azure CLI) and any potential limitations.
- Include Linux/macOS-specific examples or highlight any OS-specific steps.
- Clarify if the onboarding script is Windows-only; if so, suggest workarounds or alternatives for Linux/macOS users.
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
Summary
The documentation provides detailed instructions and examples for Windows users, especially when running the deboarding script, with PowerShell-specific guidance and notes. Linux users are not given equivalent instructions or examples for running the script, and Windows steps are presented first and in greater detail. However, Linux uninstall instructions for the agent are included, and the overall process is not Windows-exclusive.
Recommendations
- Add explicit instructions and examples for running the deboarding script on Linux/macOS, including shell commands and prerequisites.
- Clarify whether the deboarding script can be run cross-platform (e.g., with PowerShell Core or Azure CLI), and provide guidance for Linux users.
- Present Windows and Linux instructions in parallel or clearly labeled sections to improve parity.
- Include troubleshooting notes for Linux/macOS environments similar to the PowerShell ISE note for Windows.
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 consistently uses PowerShell syntax for Azure CLI commands and references a PowerShell script (bulk_deployment.ps1) for bulk deployment automation. There are no explicit Linux/macOS shell examples (e.g., Bash), and the script provided is Windows-specific, creating friction for non-Windows users. Azure CLI is cross-platform, but the documentation's examples and automation focus on Windows tools and syntax.
Recommendations
- Provide Azure CLI command examples in Bash syntax, or clarify that the CLI commands work identically on all platforms.
- Offer a Bash shell script equivalent to bulk_deployment.ps1, or provide guidance for Linux/macOS users on how to perform bulk deployment automation.
- Explicitly state platform compatibility for the Azure CLI commands and scripts.
- Mention any prerequisites or limitations for Linux/macOS users, such as the lack of a PowerShell script equivalent.
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 and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. All usage examples are PowerShell-based, with no mention of Linux/macOS-compatible alternatives (such as Bash scripts or cross-platform instructions). The script is referenced as a .ps1 file, which is traditionally associated with Windows environments, and there is no guidance for Linux users on how to run the script (e.g., using PowerShell Core on Linux/macOS or alternative approaches).
Recommendations
- Add instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux and macOS, including any prerequisites or installation steps.
- Provide explicit examples for Linux/macOS users, such as running './RGCleanScript.ps1' in pwsh, and clarify any differences in syntax or behavior.
- Mention whether the script is compatible with cross-platform PowerShell (PowerShell Core), or provide a Bash equivalent if possible.
- Include troubleshooting tips for Linux/macOS users (e.g., file permissions, execution policy).
- Clearly state if the script is Windows-only, or highlight cross-platform support if available.
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 all CLI and scripting examples using PowerShell syntax and Windows-style file paths. There are no Bash, Linux, or macOS shell examples, and file path references (e.g., C:\, E:\) are Windows-specific. The onboarding scripts are referenced as PowerShell (.ps1) only, with no mention of Bash or cross-platform alternatives. This creates friction for Linux/macOS users, who must translate commands and paths themselves.
Recommendations
- Provide Bash/zsh equivalents for all PowerShell CLI examples, using Linux/macOS file path conventions.
- Clarify whether the onboarding scripts (.ps1) are cross-platform (e.g., can be run with PowerShell Core on Linux/macOS) or provide Bash alternatives.
- Use generic file path placeholders or show both Windows and Linux/macOS path formats in JSON templates.
- Explicitly mention any OS requirements for scripts and tools, and link to cross-platform installation instructions for Azure CLI and PowerShell Core.
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. The extraction instructions for the ZIP file use Windows-specific paths and tools (e.g., Expand-Archive with Windows-style paths, winget for kubectl installation), and do not provide Linux/macOS equivalents. Bash examples are shown, but often with Windows paths or commands that are not cross-platform. There is no guidance for Linux/macOS users on extracting ZIP files or installing kubectl. The documentation assumes a Windows environment in several places, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS equivalents for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/workspace').
- Use cross-platform paths in Bash examples (e.g., '/home/user/cm/workspace' instead of 'C:\path\to\cm\workspace').
- Add instructions for installing kubectl on Linux/macOS (e.g., 'curl -LO ...', 'sudo apt install kubectl', or 'brew install kubectl').
- Clarify which commands are Windows-only and offer alternatives for other platforms.
- Ensure Bash examples are truly cross-platform and not just Windows paths in Bash syntax.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows/PowerShell environments. All onboarding scripts and usage examples are provided only for PowerShell, with no mention of Bash, Linux, or macOS equivalents. Windows-specific tools like 'winget' are used for prerequisites, and there are no instructions for installing dependencies on Linux/macOS. This creates friction for non-Windows users and may prevent them from following the onboarding process without significant adaptation.
Recommendations
- Provide Bash (or generic shell) equivalents for all PowerShell script invocations, or clarify if the scripts are truly Windows-only.
- List Linux/macOS installation commands for prerequisites (e.g., using apt, yum, brew for Azure CLI and kubectl) alongside or before Windows/winget commands.
- Indicate script compatibility (e.g., if .ps1 scripts are cross-platform via PowerShell Core, state this explicitly; if not, provide alternative scripts or guidance for Linux/macOS users).
- Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
- Reorder examples or provide tabs for Windows, Linux, and macOS to ensure parity.
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 in Bash, but the May 2025 release section includes only PowerShell syntax for configuration commands, which may create friction for Linux/macOS users. Otherwise, the documentation is largely cross-platform, focusing on Azure CLI and portal usage, with no exclusive mention of Windows tools or patterns.
Recommendations
- Add equivalent Bash examples for CLI commands shown in PowerShell syntax, especially in the May 2025 release section.
- Clarify that Azure CLI commands can be run on any OS and provide OS-neutral syntax where possible.
- Ensure future examples consistently include both Bash and PowerShell variants, or use OS-neutral command formatting.
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 examples, including those for Azure CLI, Kubernetes, Docker, and file manipulation, are provided in PowerShell syntax only, with no equivalent Bash or Linux shell examples. Windows-specific scripting patterns (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding via .NET) are used throughout. Bash/Linux examples are only provided in the 'Troubleshoot service groups' section, and even there, PowerShell is shown first or equally. This creates friction for Linux/macOS users, who must translate Windows-centric instructions to their environments.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and Kubernetes operations.
- Use cross-platform variable assignment and scripting patterns (e.g., environment variables, jq for JSON manipulation, base64 for encoding) instead of PowerShell-specific constructs.
- Where file encoding or manipulation is required, offer Linux/macOS-compatible instructions (e.g., using iconv, cat, jq, etc.).
- Ensure Bash examples are presented before or alongside PowerShell, not after.
- Review all troubleshooting steps for Windows-centric language and tools, and add Linux/macOS guidance as needed.
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 file path and backup examples using Windows-style paths (e.g., C:\Backupfiles\test.bak) and tools (e.g., SQL Server Management Studio) without offering equivalent Linux/macOS examples or guidance. The order and examples assume a Windows environment, which may create friction for Linux/macOS users.
Recommendations
- Add Linux/macOS file path examples (e.g., /home/user/backup/test.bak) alongside Windows paths in backup and kubectl cp commands.
- Explicitly mention that SQL Server Management Studio (SSMS) is Windows-only and suggest cross-platform alternatives like Azure Data Studio or sqlcmd for Linux/macOS users.
- Provide example commands for creating backups on Linux-based SQL Server instances, including sample backup file paths.
- Clarify that Visual Studio Code is cross-platform and can be used on Windows, Linux, and macOS.
- Where possible, show both Windows and Linux/macOS variants for commands involving local file system operations.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of detailed examples and scripts are PowerShell-centric, with Windows tools and patterns (e.g., New-AzStorageBlobSASToken, New-NetFirewallRule, .ps1 scripts) used throughout. Linux-specific examples are largely absent, and REST API scenarios exclusively target Windows (e.g., configuring Windows Firewall with PowerShell). Even in CLI sections, the sample scripts use PowerShell syntax (Write-Host), and there are no bash/sh examples. Guidance for Linux users is minimal, and Linux is often mentioned only in passing or in notes.
Recommendations
- Add Linux-specific examples for all major scenarios (e.g., using bash/sh scripts, configuring Linux firewall with iptables or firewalld, using .sh files in scriptUri).
- In CLI and REST API sections, provide parallel Linux examples (e.g., show how to run a bash script, not just PowerShell).
- When referencing tools like New-AzStorageBlobSASToken, also mention az CLI equivalents for generating SAS tokens.
- In parameter passing sections, show explicit Linux script parameter usage, not just describe it in prose.
- Balance the order of presentation so Linux and Windows are equally represented, or alternate which comes first.
- Where possible, clarify any OS-specific limitations or behaviors.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, with no Bash or Linux shell equivalents. Paths in JSON templates are Windows-style (e.g., C:\Users\...), and the recommended automation script is a PowerShell (.ps1) file. There are no instructions or examples for Linux/macOS users, even though Azure CLI and Kubernetes are cross-platform. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell CLI examples, especially for az CLI commands.
- Use cross-platform path examples in JSON templates (e.g., /home/user/...), or clarify how to adapt them for Linux/macOS.
- Offer a Bash version of the automation script (infra_onboarding.sh) or document how Linux/macOS users can run the workflow.
- Explicitly state OS requirements for scripts, and link to cross-platform alternatives where available.
- Ensure that instructions for collecting logs and enabling extensions are not Windows-centric, and clarify any OS-specific steps.
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
While the documentation is focused on preparing Linux with AKS Edge Essentials, it uses the Windows-specific PowerShell cmdlet 'Invoke-AksEdgeNodeCommand' to run Linux system commands, without providing direct Linux-native shell command equivalents. This assumes the user is operating from a Windows environment, which may not be the case for all Linux administrators. There are no examples of running the sysctl commands directly on a Linux shell, and the documentation does not clarify how to perform these steps from a native Linux terminal.
Recommendations
- Provide native Linux shell command examples for checking and setting sysctl parameters, such as 'sysctl fs.inotify.max_user_instances' and 'echo ... | sudo tee ...'.
- Clarify when and why 'Invoke-AksEdgeNodeCommand' is required, and offer alternative instructions for users managing the node directly from a Linux environment.
- Ensure that all steps can be completed from a Linux host without requiring Windows tools or PowerShell.
- Consider adding a note or section for Linux-only workflows, especially for administrators who do not have access to Windows or PowerShell.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides command examples for connecting to the SQL Server instance using PowerShell syntax and references the use of sqlcmd, which is typically associated with Windows environments. All connection examples use PowerShell, and no Linux/macOS shell (bash) equivalents are provided. The documentation does not mention Linux tools or patterns, nor does it provide Linux-first or cross-platform examples for connecting to the SQL Server pod.
Recommendations
- Provide equivalent bash shell examples for connecting to the SQL Server pod, using sqlcmd or other cross-platform tools.
- Explicitly mention that sqlcmd is available on Linux/macOS and provide installation instructions or links if needed.
- Use generic shell syntax (e.g., $ kubectl exec ...) instead of PowerShell-specific syntax where possible.
- Ensure that all steps are described in a way that is platform-agnostic, or provide separate sections/examples for Windows and Linux/macOS users.
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 references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly lists PowerShell scripting support as a manageability feature. However, Azure PowerShell is marked as 'No' in the tools table, and the page does mention cross-platform tools like Azure CLI and Visual Studio Code. There are no explicit Linux/macOS examples or mentions of Linux-native tools, and Windows tools are referenced without Linux alternatives.
Recommendations
- Add examples or references for Linux/macOS management tools (e.g., sqlcmd, Azure Data Studio, Bash scripting).
- Clarify which features and tools are cross-platform and which are Windows-only.
- Provide guidance for Linux/macOS users on how to accomplish equivalent tasks (e.g., scripting, management) without Windows-specific tools.
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS.
- Include sample commands using Bash or Azure CLI for common management tasks.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there is evidence of Windows bias: PowerShell is referenced for troubleshooting HTTP2 issues, Windows paths are shown in error messages, and Windows tools (e.g., Remote PowerShell, RDP) are mentioned. Linux-specific troubleshooting commands and examples are largely absent, and Linux CLI usage is not demonstrated equivalently. The order of examples and troubleshooting steps often assumes Windows as the default environment.
Recommendations
- Add Linux/macOS equivalents for PowerShell troubleshooting steps (e.g., using curl or wget with HTTP2 for network validation).
- Provide Linux/macOS-specific commands for DNS resolution (e.g., dig, nslookup, host) alongside Windows commands.
- Include examples of managing Azure CLI and extensions on Linux/macOS, such as installation, downgrade, and log collection.
- Mention Linux/macOS file permission troubleshooting for SSH folder access.
- Ensure error messages and troubleshooting steps reference both Windows and Linux paths/tools where applicable.
- Where PowerShell is used, offer a Bash or shell alternative for Linux/macOS users.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with feature parity and clear versioning for both platforms. However, there is a notable Windows-first bias in several areas: download links for Windows are always listed before Linux; known issue troubleshooting steps provide only Windows/PowerShell commands with no Linux equivalents; and some improvements reference Windows tools/scripts (e.g., PowerShell, .msi, Windows installer) without mentioning or linking to Linux alternatives. This creates friction for Linux users, especially when troubleshooting, as they must seek out Linux-specific instructions elsewhere.
Recommendations
- When providing troubleshooting steps (e.g., editing agent configuration file permissions), include Linux command examples (such as chmod/chown) alongside Windows/PowerShell commands.
- Where Windows tools or scripts are referenced (e.g., .msi installer, PowerShell scripts), mention or link to the equivalent Linux tools or scripts (e.g., .deb/.rpm packages, shell scripts).
- Consider alternating the order of Windows and Linux download links or presenting them side-by-side to avoid implicit prioritization.
- For known issues or common tasks, ensure both Windows and Linux remediation steps are documented, or explicitly state if an issue is Windows-only.
- Where possible, provide parity in the level of detail for both platforms, especially in troubleshooting and installation guidance.
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 moderate Windows bias. The authentication section describes Windows-specific interactive browser login first, and references Windows certificate stores for certificate-based authentication. Access token acquisition is demonstrated with a PowerShell cmdlet (`Get-AzAccessToken`), with no Linux/macOS equivalent. Windows-specific certificate store options are detailed, while Linux approaches are not mentioned. However, device code login and Azure CLI authentication are described as defaults for Linux, and most examples are generic and cross-platform.
Recommendations
- Add Linux/macOS-specific guidance for access token acquisition (e.g., using Azure CLI: `az account get-access-token`).
- Provide parity for certificate-based authentication on Linux/macOS, such as instructions for storing and referencing PEM/PFX files.
- When listing authentication options, avoid presenting Windows-only methods first unless they are universally recommended.
- Clarify cross-platform differences for certificate handling, and explicitly mention Linux/macOS approaches.
- Include example commands for Linux/macOS where Windows-specific tools or stores are referenced.
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 comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration instructions. However, Windows examples and tools (such as PowerShell scripts, Microsoft Update, Group Policy, and Control Panel) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no equivalent Bash or Azure CLI example for Linux users. Windows-specific tools and patterns (e.g., Msiexec, Registry Editor, Group Policy) are described in depth, while Linux instructions are more succinct and rely on standard package managers.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for resource cleanup tasks, especially for stale server removal.
- Ensure Linux examples are given equal prominence and detail, possibly by alternating the order of Windows and Linux sections.
- Expand Linux uninstall instructions to include troubleshooting steps or advanced scenarios, similar to Windows.
- Where possible, mention cross-platform alternatives to Windows-specific tools (e.g., provide Azure CLI or REST API examples alongside PowerShell).
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 requirements, but links and examples are Windows-centric (e.g., linking to Azure CLI Windows install page and specifying x64/32-bit requirements without mentioning Linux/macOS equivalents). No Linux/macOS installation instructions or examples are provided for management machine setup, despite Azure CLI being cross-platform. The CLI commands shown are generic, but the management machine requirements and links focus on Windows.
Recommendations
- Add explicit guidance for Linux and macOS management machines, including links to their Azure CLI installation instructions.
- Clarify that Azure CLI is supported on Linux/macOS and provide minimum requirements for those platforms.
- Show example CLI commands and file paths for Linux/macOS (e.g., where configuration files are generated).
- Mention any OS-specific considerations for Linux/macOS (such as SSH, file permissions, etc.).
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Linux and Windows onboarding options, but PowerShell (a Windows-centric tool) is highlighted as a primary method for both platforms, and Windows-specific methods are listed in detail after the cross-platform options. PowerShell-based onboarding is mentioned before Linux-native automation tools (like Ansible), and there are several Windows-only onboarding methods, but no Linux-only equivalents.
Recommendations
- Clarify in the PowerShell onboarding method whether Linux users are expected to use PowerShell Core or if there are Bash/CLI equivalents.
- Add explicit Bash or shell script examples for Linux users, or link to Linux-specific onboarding guides if available.
- If PowerShell is truly cross-platform in this context, state this clearly and provide Linux usage instructions.
- Consider listing truly cross-platform methods (e.g., Ansible, service principal with Bash) before Windows-specific methods.
- If there are Linux-native automation tools (e.g., cloud-init, shell scripts), mention them alongside Ansible.
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 commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are shown first and are the only method described for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. Windows file paths are used in sample commands, further reinforcing Windows-first patterns.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell, e.g., 'az deployment group create --resource-group <name> --template-file <file> --parameters <params>'.
- Mention that ARM template deployment can be performed from any OS, and clarify that PowerShell is not required.
- Provide sample Bash commands for Linux users where relevant.
- Use generic file paths (e.g., './Templates/Template.json') in examples, or show both Windows and Linux path formats.
- Consider listing CLI/Bash examples before or alongside PowerShell to avoid Windows-first ordering.