226
Pages Scanned
53
Pages Flagged
226
Changed Pages
23.5%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-07 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 226
Files Completed: 226
Problematic Pages
56 issues found
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation is heavily biased toward Windows/PowerShell environments. All onboarding scripts and examples are provided only as PowerShell (.ps1) scripts, and users are instructed to use PowerShell terminals. Prerequisites reference Windows-specific tools like 'winget' for installing dependencies, with no mention of Linux/macOS equivalents. There are no Bash or cross-platform script examples, and no guidance for non-Windows users.
Recommendations
- Provide equivalent Bash shell scripts or clear instructions for Linux/macOS users, or explicitly state if only Windows is supported.
- Include installation instructions for Azure CLI and kubectl using cross-platform methods (e.g., apt, yum, brew, or direct downloads) instead of only 'winget'.
- If the scripts are inherently Windows-only, add a prominent note at the top clarifying this limitation.
- If possible, refactor onboarding scripts to be cross-platform (e.g., using Python or Bash), or provide alternative manual steps for Linux/macOS users.
- Show both PowerShell and Bash command examples where applicable.
Create Pull Request
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.
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
Summary
The documentation provides both Windows and Linux context in its introduction and scope, but several sections show a Windows-first bias. Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly and before Linux equivalents. PowerShell is referenced as a primary scripting method, and Linux-specific tools (e.g., shell scripts, Ansible) are mentioned but not emphasized equally. There are no explicit Linux command examples, and the standalone agent installation section only covers Windows clients.
Recommendations
- Provide explicit Linux/Bash command examples alongside PowerShell where scripts are referenced.
- Mention Linux tools (e.g., shell scripts, systemd, Ansible) with equal prominence and detail as Windows tools.
- Include a section or link for standalone Azure Monitor Agent installation on Linux client machines, or clarify if not supported.
- When listing deployment options, alternate the order or group by OS to avoid always listing Windows tools first.
- Add Linux-specific troubleshooting or configuration notes where relevant.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides recovery instructions and a downloadable script exclusively for Windows/PowerShell environments. There are no instructions, scripts, or examples for performing the recovery from Linux or macOS systems, nor is there mention of cross-platform alternatives.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
- Clearly indicate if the recovery process is only supported from Windows, and explain why (e.g., dependencies on Windows-only tools or APIs).
- If feasible, offer a platform-agnostic solution (such as an Azure CLI or Python script) to enable recovery from non-Windows systems.
- Explicitly state OS requirements and limitations in the prerequisites section.
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 a moderate Windows bias. The primary automation script for at-scale agent installation is a PowerShell script, with instructions focused on Windows environments (e.g., PowerShell terminal usage, Windows Task Scheduler for cron jobs, and Set-ExecutionPolicy). Windows-specific tools and patterns (PowerShell, Windows Task Scheduler) are mentioned exclusively or before Linux equivalents. While Linux is referenced (e.g., sudo configuration), there are no Linux/bash script examples or guidance for running the automation at scale on Linux/macOS. Out-of-band methods mention Ansible, but Windows-centric approaches (Group Policy, Configuration Manager) are listed first and in greater detail.
Recommendations
- Provide equivalent bash or shell script examples for Linux/macOS users, including instructions for running at scale.
- Include guidance for scheduling automation on Linux (e.g., using cron) alongside Windows Task Scheduler.
- List Linux-friendly automation methods (e.g., Ansible, shell scripts) before or alongside Windows methods.
- Clarify which methods are cross-platform and which are Windows-only, and provide parity where possible.
- Add explicit examples for Linux/macOS environments (e.g., running the helper script in bash, using chmod for 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_tools
Summary
The documentation provides only PowerShell examples and instructions for running the onboarding script, with no mention of Bash, Linux shell, or cross-platform alternatives. The onboarding script is referenced with a .ps1 extension and all example code is in PowerShell, implying Windows-centric tooling and workflows. There is no guidance for Linux/macOS users or mention of how to run the onboarding script on non-Windows platforms.
Recommendations
- Add explicit instructions for running the onboarding script on Linux/macOS, including prerequisites (such as PowerShell Core or Bash alternatives).
- Provide Bash or shell script examples alongside PowerShell, or clarify if the onboarding script is cross-platform.
- Mention any required tools for Linux/macOS users (e.g., PowerShell Core, Azure CLI) and how to install them.
- State platform compatibility for the onboarding script and highlight 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 changes and script invocation, but does not offer equivalent Linux/macOS guidance. The script section is labeled 'Windows' and lacks information on running the script from Linux or macOS, despite Azure CLI and PowerShell Core being cross-platform. Manual steps are portal-based and platform-neutral, but the scripted removal is Windows-centric.
Recommendations
- Add instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any differences in handling execution policies.
- Clarify whether the deboarding script can be run on Linux/macOS, and if not, provide a Linux-compatible version or alternative.
- Present both Windows and Linux/macOS script instructions side-by-side, or note any limitations for non-Windows users.
- Explicitly mention supported platforms for the deboarding script and provide troubleshooting tips for Linux/macOS 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 consistently uses PowerShell syntax for Azure CLI commands and references a bulk deployment script in PowerShell (.ps1). There are no Bash or Linux/macOS shell examples, and the only script provided is Windows-specific. This creates friction for Linux/macOS users, who may need to adapt commands and cannot use the provided script directly.
Recommendations
- Provide Azure CLI command examples in Bash syntax (e.g., using single quotes, proper escaping) alongside PowerShell examples.
- Offer a Bash shell script equivalent to bulk_deployment.ps1, or note how Linux/macOS users can perform bulk deployment without the PowerShell script.
- Clarify that Azure CLI commands are cross-platform, and specify any OS-specific considerations.
- Mention that the .ps1 script is Windows-only and suggest alternatives for Linux/macOS users.
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 moderate Windows bias, especially in the file extraction step. The Bash tab uses Windows-specific commands (Expand-Archive, cd with Windows-style paths) and references Windows paths (e.g., C:\path\to\archive.zip), with no Linux/macOS equivalent (such as unzip or tar). The kubectl installation command uses winget, a Windows-only tool, and does not provide a Linux/macOS alternative. Throughout, examples and variable placeholders are often Windows-centric, and Linux/macOS users must infer or adapt steps. However, Azure CLI and kubectl commands are cross-platform, and most orchestration steps are generic.
Recommendations
- Provide Linux/macOS equivalents for file extraction (e.g., unzip <archive.zip> -d <folder> or tar -xf <archive.tar.gz> -C <folder>).
- Add instructions for installing kubectl on Linux/macOS (e.g., curl or apt/yum/brew commands).
- Use generic path placeholders or show both Windows and Unix-style paths in examples.
- Clarify that Bash examples are intended for both Windows (WSL/Git Bash) and Linux/macOS, and offer platform-specific notes where needed.
- Ensure all steps that reference Windows tools (winget, Expand-Archive) have Linux/macOS alternatives.
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) and only shows Windows/PowerShell command examples. There is no mention of Linux/macOS equivalents, such as Bash or cross-platform scripting, nor guidance for running the script on non-Windows platforms. The script appears to be distributed only as a .ps1 file, which is traditionally Windows-centric, and PowerShell is referenced as the primary tool.
Recommendations
- Provide instructions for running the script on Linux/macOS, including installation of PowerShell Core (pwsh) if required.
- Clarify whether the script is compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
- Offer Bash or shell script alternatives if possible, or note limitations for Linux/macOS users.
- Explicitly state platform requirements and offer guidance for Linux/macOS users to achieve equivalent functionality.
- Add examples using 'pwsh' for Linux/macOS if the script is compatible.
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, Kubernetes). Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service groups' section, which offers Bash and PowerShell tabs. This bias creates friction for Linux/macOS users, as they must translate PowerShell commands to Bash or other shells.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and Kubernetes commands.
- Use cross-platform syntax for Azure CLI commands (e.g., avoid PowerShell-specific variable assignment and piping).
- Clearly indicate when a command is Windows-only or cross-platform.
- Add notes or tabs for macOS/Linux users where file encoding or path conventions differ.
- Review and update troubleshooting steps to ensure Linux parity, especially for edge device operations.
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 migration script and example, with no mention of Linux/macOS-compatible alternatives or instructions. The script is a .ps1 file, which is traditionally associated with Windows environments, and there are no Bash or cross-platform script options provided.
Recommendations
- Provide a Bash or Python migration script for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Add explicit instructions for running the migration on Linux/macOS, including any prerequisites (e.g., PowerShell Core installation).
- Mention whether the script is cross-platform or Windows-only, and if Windows is required, state this clearly in the prerequisites.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry. However, the PowerShell example is given equal prominence and appears immediately after the CLI example, despite PowerShell being primarily a Windows-centric tool. There are no explicit Linux/macOS shell (bash) examples, nor is there mention of Linux-native tools or workflows. The documentation does not exclusively use Windows tools, but the inclusion and parity of PowerShell examples may create friction for Linux/macOS users.
Recommendations
- Add explicit bash or shell examples for Linux/macOS users, especially for image import workflows.
- Clarify that Azure CLI is cross-platform and recommend it as the primary tool for Linux/macOS users.
- Consider mentioning Docker CLI commands for users who prefer native Docker workflows.
- If PowerShell is included, note its cross-platform availability, but also highlight that Azure CLI is more commonly used on Linux/macOS.
Container Registry
Quickstart - Create Geo-Replicated Registry - ARM Template
...ontainer-registry-get-started-geo-replication-template.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation primarily demonstrates deploying the ARM template via the Azure portal, with only brief mentions of Azure PowerShell, Azure CLI, and REST API as alternative methods. No explicit Linux/macOS-specific instructions or examples are provided, and the portal-based workflow is shown first. While Azure CLI is mentioned (which is cross-platform), there are no step-by-step CLI examples, and PowerShell is referenced before CLI in the deployment methods link. The cleanup section also only describes portal-based deletion, omitting CLI or script-based approaches favored by Linux/macOS users.
Recommendations
- Add explicit Azure CLI examples for deploying the ARM template, including command-line instructions for Linux/macOS users.
- Provide cleanup instructions using Azure CLI (e.g., az group delete) alongside portal steps.
- When listing deployment methods, mention Azure CLI before PowerShell to avoid Windows-first bias.
- Include notes or links for Linux/macOS users on how to install and use Azure CLI for these tasks.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image management, but PowerShell examples are given equal prominence and detail, despite PowerShell being primarily a Windows tool. There is no explicit Linux example for Azure CLI usage, and PowerShell is presented as a recommended method alongside CLI, which may confuse Linux/macOS users. Additionally, keyboard shortcuts (Ctrl+C) are described generically, but could be clarified for macOS users.
Recommendations
- Clarify that Azure PowerShell examples are intended for Windows users, and Azure CLI is cross-platform.
- Present Azure CLI examples first, as it is the most universal and cross-platform tool.
- Add explicit notes or tabs indicating which examples are for Windows (PowerShell) and which are for Linux/macOS (CLI).
- Include a brief statement that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
- Consider adding bash shell examples for common Docker operations, or at least clarify that Docker CLI commands are identical across platforms.
- Clarify keyboard shortcuts for stopping containers (e.g., 'Ctrl+C' on Windows/Linux, 'Cmd+C' on macOS).
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command examples for Helm and Azure CLI, which are cross-platform, but in the 'Set the following environment variables' section, it uses the Windows-style 'set' command without providing the Linux/macOS equivalent ('export'). Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, then Azure PowerShell, then Azure Portal, which is a minor 'windows_first' bias. Most other commands use cross-platform syntax, but the omission of Linux/macOS environment variable examples creates friction for non-Windows users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') environment variable examples wherever environment variables are set.
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux/macOS.
- When listing options for creating resources (e.g., AKS clusters), consider listing Linux/macOS-friendly tools (Azure CLI) first, but clarify their cross-platform nature.
- Review all command blocks to ensure they are not using Windows-only syntax unless the section is explicitly Windows-specific.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and lists it before sqlcmd (which is cross-platform). However, it does provide a sqlcmd example for both Linux and Windows, and does not rely on Windows-only tools or PowerShell. The overall guidance is mostly platform-neutral, but the ordering and emphasis on SSMS may create minor bias.
Recommendations
- Explicitly mention cross-platform GUI clients (such as Azure Data Studio) alongside SSMS.
- Provide example connection instructions for Azure Data Studio or other Linux/macOS-compatible tools.
- Clarify that sqlcmd works on Linux, macOS, and Windows, and show examples for each platform if there are differences.
- Consider listing cross-platform tools first, or at least equally with Windows-only tools.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, with dedicated tables for each OS and clear links to usage and supported OS information. However, Windows extensions are presented first, which may subtly reinforce a Windows-centric perspective. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and partner extensions are shown for both OSes. No critical Linux gaps or missing examples are evident.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side if possible, to avoid implicit Windows-first bias.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Where possible, provide example links or code snippets for both Windows and Linux in deployment guides (if not already present in linked pages).
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for each command, but consistently presents Bash examples first. There are no Windows-specific tools or patterns, and all commands use the cross-platform Azure CLI. No Linux examples are missing, and Linux parity is maintained throughout.
Recommendations
- Maintain Bash examples first, as Bash is the default shell on Linux and macOS.
- Ensure that PowerShell examples are clearly marked as cross-platform (PowerShell Core), if applicable.
- Consider adding a brief note clarifying that Azure CLI commands work on Windows, Linux, and macOS, and that Bash examples are suitable for Linux/macOS users.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, with Bash (Linux/macOS) examples consistently shown first in each section. There are no exclusive Windows tools, PowerShell-only instructions, or missing Linux examples. The only minor bias is the inclusion of PowerShell examples, which may not be needed for all users, but their presence does not disadvantage Linux/macOS users.
Recommendations
- No changes are necessary for Linux parity. The documentation already provides Bash (Linux/macOS) examples first and covers all steps for both platforms.
- Optionally, clarify that Bash examples are suitable for macOS as well as Linux, if not already clear.
- If desired, consider grouping platform-agnostic instructions together and only splitting out platform-specific syntax when necessary.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There are no Windows-only tools or patterns, and Linux parity is maintained throughout. The Azure CLI and Helm are cross-platform tools, and no Windows-specific instructions or tools are prioritized. However, the ordering of Bash before PowerShell may be considered a minor bias toward Linux/Unix environments.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that both are supported equally.
- Add a note clarifying that all commands are cross-platform and that users should select the tab matching their environment.
- Ensure that any future examples or troubleshooting steps include both Bash and PowerShell variants.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides CLI examples primarily using Bash syntax, which is cross-platform, but in the May 2025 release, PowerShell syntax is used for CLI examples. There are no Windows-specific tools or patterns mentioned, and the Azure CLI is inherently cross-platform. However, the use of PowerShell syntax in the examples may create minor friction for Linux/macOS users, as Bash is more common on those platforms.
Recommendations
- Provide CLI examples in both Bash and PowerShell syntax, or default to Bash for cross-platform parity.
- Explicitly state that Azure CLI commands work on all platforms and provide guidance for Linux/macOS users if syntax differs.
- Avoid using platform-specific shell syntax unless the feature is Windows-only.
Low 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 examples and notes are presented first or more prominently. For 'curl', Linux installation instructions are less explicit than Windows. The kubectl section includes a Windows-specific note about using cmd.exe instead of PowerShell, but does not offer comparable Linux/macOS guidance. There is a PowerShell-specific explanation for curl, but no equivalent for Linux shells. Overall, Linux and macOS users may experience minor friction due to Windows-first ordering and less detailed Linux instructions.
Recommendations
- Ensure installation instructions for Linux and macOS are as explicit and accessible as Windows instructions.
- Provide shell-specific notes for Linux/macOS (e.g., bash/zsh) where PowerShell-specific guidance is given.
- Present platform options in parallel (Windows, Linux, macOS) rather than Windows-first ordering.
- Clarify Linux installation steps for tools like curl (e.g., 'sudo apt install curl' or 'yum install curl').
- Add notes for Linux/macOS users where Windows-specific caveats are mentioned (e.g., shell differences for curl).
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation provides both Linux and Windows approaches for base64 encoding files, but the Windows section is more detailed, mentioning certutil and findstr commands, while the Linux section only briefly references base64. The Linux example is minimal, and there is no explicit macOS guidance. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl), but Windows-specific tools are mentioned without equivalent macOS instructions.
Recommendations
- Expand the Linux/macOS section to include decoding as well as encoding, and clarify that the base64 command works on macOS.
- Provide a macOS-specific note or example for base64 usage.
- Mention that certutil and findstr are Windows-only, and suggest alternatives for Linux/macOS (e.g., grep for findstr).
- Ensure parity in detail between Windows and Linux/macOS instructions for file encoding/decoding.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical steps, but consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and sometimes before or equally with CLI. There are no Linux-specific command-line examples (e.g., Bash scripts), but the CLI examples are cross-platform. The PowerShell examples use Windows-style environment variable syntax and commands, which may confuse Linux/macOS users. The documentation does not mention Linux/macOS tools or patterns, and does not clarify that Azure PowerShell can be used cross-platform, potentially leading to a Windows bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure PowerShell can run on Linux/macOS, or provide Bash shell equivalents for environment variable setting.
- Show Azure CLI examples first, as it is the most universal tool.
- Add notes or examples for Linux/macOS users, especially for environment variable syntax (e.g., export vs $Env:).
- Consider including Bash script snippets for common tasks where relevant.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page lists both Windows and Linux-related endpoints and requirements, but there is a mild bias towards Windows in the ordering and terminology. Windows-specific services (e.g., 'time.windows.com', 'sts.windows.net', 'servicebus.windows.net') are mentioned, and Windows NTP is referenced before any Linux alternatives. The Azure CLI installer is mentioned, but no explicit Linux installation instructions or package managers (other than 'packages.microsoft.com') are referenced. However, Linux endpoints and requirements (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com', SSH usage) are present, and the documentation is not Windows-exclusive.
Recommendations
- Explicitly mention Linux NTP alternatives (e.g., 'ntp.ubuntu.com', 'pool.ntp.org') alongside 'time.windows.com', clarifying when each is used.
- Provide examples or references for Linux Azure CLI installation (e.g., apt, yum, zypper) in addition to the generic 'Azure CLI Installer' endpoint.
- Ensure that Linux-related endpoints and requirements are given equal prominence and ordering as Windows-specific ones.
- Clarify that SSH and Kubernetes API server ports are relevant for both Windows and Linux management machines, and provide guidance for both OS types where applicable.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are consistently shown alongside CLI, and some CLI examples use backtick (`) line continuation, which is a Windows/PowerShell convention. Portal instructions are platform-agnostic, but CLI and PowerShell are presented as equivalent, with PowerShell sometimes shown after CLI. There is a minor bias in log file locations, with Windows mentioned first. The documentation references both Linux and Windows endpoints and installation packages, and explicitly includes Linux log file locations and onboarding instructions. Overall, Linux parity is good, but minor Windows-first ordering and Windows conventions are present.
Recommendations
- Use platform-neutral CLI syntax (avoid Windows-style backticks for line continuation; use standard Bash line continuation with \ for Linux/macOS examples).
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and provide Bash-style examples where appropriate.
- Alternate the order of Windows and Linux log file locations, or present them together for parity.
- Where PowerShell is presented, clarify its applicability (Windows only, or cross-platform if using PowerShell Core).
- Consider providing Linux/macOS onboarding script examples if there are platform-specific steps.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Linux and Windows information for Azure Arc-enabled server connectivity, but there are minor signs of Windows bias. Windows installation package URLs are listed before Linux equivalents, and Windows Admin Center is referenced as a management tool without mentioning Linux alternatives. Cipher suite configuration details are given for Windows first, with Linux relegated to a general OpenSSL note. However, Linux requirements and URLs are present, and critical tasks can be completed on Linux.
Recommendations
- List Linux and Windows installation package URLs in parallel or alternate order to avoid Windows-first bias.
- When referencing Windows Admin Center, mention Linux management alternatives (such as Azure CLI, SSH, or other tools) if applicable.
- Provide more explicit Linux configuration guidance for cryptographic protocols (e.g., OpenSSL configuration examples) alongside Windows-specific instructions.
- Ensure that troubleshooting links and sections for TLS issues include Linux-specific guidance, not just Windows.
- Where possible, add Linux command-line examples or references for endpoint lookups and network configuration.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, including error/exit codes and log file locations for each OS. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell-specific syntax (& operator, environment variables), while Linux examples follow. The log file paths and troubleshooting steps reference Windows locations before Linux equivalents. There is a minor bias toward Windows in ordering and tool references, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Where possible, provide generic command syntax before OS-specific examples.
- Ensure Linux log file paths and troubleshooting steps are as prominent as Windows equivalents.
- Clarify that both Windows and Linux are equally supported, perhaps with a summary table or section.
- Use neutral language and avoid referencing Windows tools (e.g., PowerShell) unless necessary for the task.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Windows and Linux Arc-enabled servers and provides parity in feature descriptions. However, there is mild bias in the ordering of examples: Azure PowerShell is presented after Azure CLI, and PowerShell-specific instructions are included, which may be less relevant for Linux users. The CLI section does clarify Linux compatibility, but PowerShell is still given a dedicated section and tip, which could be seen as slightly favoring Windows users. All critical tasks can be completed on Linux via Azure CLI, so Linux users are not blocked.
Recommendations
- Continue to emphasize Azure CLI as the cross-platform tool, and consider listing CLI instructions before PowerShell in all sections.
- Add explicit notes that Azure PowerShell is primarily for Windows, and recommend CLI for Linux/macOS users.
- Where possible, clarify that all CLI commands work identically on Linux, macOS, and Windows.
- Consider adding bash/zsh shell script examples for common extension management tasks to further support Linux users.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed, including error handling and output formatting. The Linux/Bash example is present and functional, but less detailed and is shown after the Windows example. The 'Related content' section mentions PowerShell before Azure CLI, which may reinforce Windows-first patterns.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which is shown first to avoid Windows-first bias.
- Ensure parity in script detail and error handling between PowerShell and Bash examples.
- In 'Related content', list Azure CLI and PowerShell equally or alternate their order.
- Add clarifying notes that both Windows and Linux are fully supported and provide links to OS-specific tutorials where relevant.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first and in greater detail. The Windows section includes additional troubleshooting guidance (e.g., avoiding PowerShell ISE), while the Linux section is more concise. The retry commands for failed deployments are also shown with Windows first. No Linux functionality is missing, but Windows is prioritized in ordering and depth.
Recommendations
- Present Windows and Linux instructions in parallel or in a more balanced order (e.g., side-by-side or alternating which comes first).
- Add any Linux-specific troubleshooting notes if relevant, similar to the PowerShell ISE warning for Windows.
- Ensure that both PowerShell and Bash script download instructions are equally detailed.
- Consider using generic language (e.g., 'On Windows, do X. On Linux, do Y.') instead of always starting with Windows.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there is a mild Windows bias: Windows-related features (such as Windows Server management, Extended Security Updates, and Windows registry/file monitoring) are mentioned more prominently and often before Linux equivalents. PowerShell is listed as a primary automation tool, with Linux alternatives (like Bash or shell scripting) not explicitly mentioned. Some links and examples default to Windows tabs or Windows-specific guidance, even when Linux is supported.
Recommendations
- Ensure Linux examples and tools (such as Bash, shell scripting, and Linux-specific agent installation) are presented alongside PowerShell and Windows examples.
- When listing supported automation tools, explicitly mention Bash/shell scripting for Linux users.
- Where links default to Windows tabs, add equivalent Linux tabs or links.
- In sections describing monitoring, configuration, and update management, clarify Linux support and provide Linux-specific guidance or links.
- When describing VM extensions or agent installation, include explicit instructions for Linux VMs.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or exclusive Windows instructions are present. All instructions are cross-platform via Azure CLI.
Recommendations
- Consider alternating the order of Bash and PowerShell examples or explicitly state that both are equally supported.
- Add a brief note at the start clarifying that all CLI instructions work on Linux, macOS, and Windows.
- Ensure screenshots and portal instructions are not Windows-centric (e.g., avoid referencing Windows-only UI elements).
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the PowerShell tab is present and contains full examples, which may suggest a Windows bias. The Bash tab is shown first, but the PowerShell section is equally detailed, and no Linux-specific tools or patterns are discussed. There is no mention of Linux/macOS-specific issues, nor are there any Linux-only examples or troubleshooting tips. All commands use the Azure CLI, which is cross-platform, but the presence of PowerShell examples may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clarify that PowerShell examples are for Windows users and Bash for Linux/macOS users.
- Add explicit notes about cross-platform compatibility of Azure CLI commands.
- Provide troubleshooting tips for Linux/macOS users if there are known issues.
- Consider adding a section about using the Azure CLI in macOS/Linux environments (e.g., installation, shell differences).
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently present and sometimes shown immediately after Bash, which may create a slight Windows-first impression. There are no Windows-only tools or patterns, and all commands are cross-platform (Azure CLI and kubectl). No Linux/macOS examples are missing, and no Windows-specific tools are mentioned.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or default to Bash first for cross-platform CLI tutorials.
- Explicitly note that Azure CLI and kubectl commands work on Linux, macOS, and Windows, to reassure non-Windows users.
- If possible, add a brief section explaining how to install Azure CLI and kubectl on Linux/macOS for completeness.
- Ensure that any future additions do not introduce Windows-specific tools or patterns unless necessary.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, which could be considered a minor 'windows_first' bias if the reverse were true, but here Bash is first. No Windows-only tools or patterns are used, and all commands are cross-platform (az CLI, Helm). There are no missing Linux examples or exclusive Windows tools.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, for new users.
- If possible, add a brief note about cross-platform compatibility of az CLI and Helm.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include both Bash and PowerShell instructions.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell, which is a minor bias in favor of Linux/macOS users ('windows_first' bias would be the opposite). No evidence of Windows-only tools, Windows-first ordering, or missing Linux examples is found. All commands use the Azure CLI, which is cross-platform.
Recommendations
- No changes required for Linux parity. The documentation already provides Bash examples first and PowerShell examples second, ensuring both platforms are covered.
- If desired, clarify in the introduction that both Bash (Linux/macOS) and PowerShell (Windows) are supported, and users should select the tab appropriate for their environment.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is consistently presented as a first-class option alongside CLI, and in some sections, PowerShell is given equal or slightly more prominence than Linux-native workflows. However, Linux/macOS users are not blocked, as all critical flows are covered with Azure CLI and Docker commands, which are cross-platform. There is a minor 'windows_first' bias in the authentication options table, where PowerShell is listed before Docker-native or Linux-native alternatives in some cases.
Recommendations
- Clearly indicate that Azure PowerShell is optional and primarily for users who prefer it (typically Windows users), while Azure CLI is cross-platform and recommended for Linux/macOS.
- In tables and code blocks, list Azure CLI (cross-platform) examples before PowerShell to reinforce Linux parity.
- Add explicit notes that all CLI commands work on Linux/macOS, and clarify that Docker and Podman are supported on all platforms.
- Where PowerShell is mentioned, consider adding a short note that Bash/CLI is the default for Linux/macOS users.
- Ensure that all sections referencing PowerShell have equivalent CLI/Bash examples, and vice versa.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are always shown after Bash. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, the presence of PowerShell examples may suggest a slight Windows bias, as Linux/macOS users would not use PowerShell. No Linux-specific tools or patterns are missing, and the Bash examples are complete and functional.
Recommendations
- Consider making Bash the default or first example in each code tab, as Bash is more universal across Linux/macOS and Windows (via WSL).
- Clarify in the introduction that Bash is recommended for Linux/macOS users and PowerShell for Windows users.
- Ensure that any references to file paths or shell syntax are cross-platform (e.g., avoid Windows-style backslashes in Bash examples).
- If possible, provide a brief note on how to use Bash on Windows (e.g., via WSL or Git Bash) for users who may not have PowerShell.
- Explicitly state that all commands are cross-platform and that Azure CLI and Helm work on Linux, macOS, and Windows.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell (a Windows-centric tool) alongside CLI. While Azure CLI is cross-platform, PowerShell is often associated with Windows, and its mention before Bash or Linux shell scripting may subtly prioritize Windows users. No explicit Linux/macOS examples or tools are referenced, and no Bash or shell script generation is mentioned.
Recommendations
- Explicitly mention Bash or shell script generation as a capability, if supported.
- Clarify that Azure CLI is cross-platform and provide examples for both PowerShell and Bash where relevant.
- Ensure that any code snippet generation examples in future documentation include both PowerShell and Bash/Linux shell variants.
- Add a note about parity between Windows and Linux/macOS users for script generation, if applicable.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for both Azure CLI and PowerShell, but the introductory text mentions PowerShell first and references opening PowerShell or Azure CLI. The example for using Visual Studio Code terminal uses a Windows-centric keyboard shortcut (Ctrl + `), and PowerShell is given its own tab alongside CLI. There are no Linux-specific instructions or examples, but the Azure CLI commands are cross-platform. The documentation does not reference Windows-only tools, but the ordering and emphasis slightly favor Windows/PowerShell users.
Recommendations
- Mention Azure CLI first in deployment instructions, as it is cross-platform.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Add a note about opening terminals on Linux/macOS (e.g., use Ctrl+Shift+` in VS Code on some platforms).
- Consider including Bash shell examples or explicitly stating that Azure CLI commands can be run in Bash or other terminals.
- Balance the order of CLI and PowerShell tabs, or default to CLI.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity between Azure CLI and Azure PowerShell throughout, but consistently includes PowerShell examples alongside CLI examples, which may signal a bias toward Windows users. Azure PowerShell is a Windows-centric tool, and its inclusion may be unnecessary for Linux/macOS users, who typically use Azure CLI. Additionally, PowerShell examples are sometimes presented immediately after CLI examples, rather than offering Linux/macOS-specific guidance or alternatives. No Windows-only tools or patterns are referenced, and all commands are cross-platform via Azure CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users, while Azure PowerShell is primarily for Windows environments.
- Consider presenting Azure CLI examples first, and PowerShell examples as optional for Windows users.
- Add explicit notes indicating that Azure CLI commands work identically on Linux, macOS, and Windows.
- Remove or de-emphasize PowerShell examples in sections where Azure CLI is sufficient and more universal.
- If possible, provide shell script examples (bash/zsh) for Linux/macOS users, especially for automation scenarios.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations, but PowerShell is consistently mentioned alongside or immediately after CLI, and no explicit Linux/macOS shell examples (e.g., Bash) are provided. The CLI examples are cross-platform, but the presence of PowerShell (a Windows-centric tool for many users) without explicit mention of Bash or Linux-native tools may create a subtle Windows bias. There are no references to Linux-specific tools or workflows, and the order of examples sometimes puts PowerShell before REST API or other platform-neutral options.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and consider explicitly stating this in the documentation.
- Add Bash shell examples where appropriate, or clarify that the CLI examples are intended for cross-platform use.
- When listing programmatic options, consider listing Azure CLI (cross-platform) before PowerShell, and REST API as a platform-neutral alternative.
- If possible, provide short notes or links for Linux/macOS users on installing and using Azure CLI.