231
Pages Scanned
51
Pages Flagged
231
Changed Pages
22.1%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:09
Scan Information
Started At: 2026-02-26 00:00:09
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 231
Files Completed: 231
Problematic Pages
52 issues found
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
Summary
The documentation provides authentication options for both Windows and Linux, but the 'Interactive browser login' is described as Windows-only and presented first. Windows certificate store usage is detailed, while Linux equivalents are not mentioned. The access token example references a Windows PowerShell cmdlet ('Get-AzAccessToken') without Linux alternatives. However, the overall command syntax and most examples are cross-platform.
Recommendations
- Present authentication options in a platform-neutral order or clarify platform defaults for each.
- For certificate-based authentication, mention Linux certificate storage options (e.g., file paths, permissions) and provide Linux-specific guidance.
- For access token acquisition, include Linux/macOS alternatives (such as using Azure CLI: 'az account get-access-token') alongside PowerShell examples.
- Explicitly state which authentication methods are available on Linux/macOS and provide parity in examples.
- Where Windows-specific tools or stores are mentioned, add equivalent Linux/macOS instructions or links.
Create Pull Request
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for migration, with instructions to run it in PowerShell. No Linux/macOS shell or cross-platform alternatives are mentioned, nor is there guidance for users who do not have access to PowerShell (e.g., Linux users). The page assumes PowerShell availability, which is a Windows-centric tool.
Recommendations
- Provide a Bash or cross-platform script for migration, or clarify if PowerShell Core (pwsh) can be used on Linux/macOS.
- Explicitly state PowerShell requirements and offer installation instructions for Linux/macOS if PowerShell Core is supported.
- Add Linux/macOS usage examples, including how to run the script in PowerShell Core or alternative migration methods.
- Mention any limitations or workarounds for non-Windows users.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is focused on configuring AKS Edge Essentials for Linux, but uses PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to interact with Linux nodes, rather than native Linux shell commands. There are no direct Linux shell examples for checking or setting sysctl parameters, and the text editor recommendation (Notepad) is Windows-centric.
Recommendations
- Provide native Linux shell commands for checking and setting sysctl parameters (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee -a /etc/sysctl.conf && sudo sysctl -p').
- Recommend Linux text editors (e.g., nano, vim, gedit) instead of Notepad.
- Clarify when PowerShell cmdlets are required, and offer Linux-native alternatives where possible.
- Ensure all critical steps can be completed using Linux tools without requiring Windows/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, but does not offer equivalent Linux/macOS shell examples. PowerShell is used for kubectl exec commands, and Windows-style command prompts are shown first. There is no explicit mention of Linux/macOS alternatives or parity, which may create friction for non-Windows users.
Recommendations
- Provide bash/zsh shell examples alongside PowerShell for kubectl exec and sqlcmd commands.
- Clarify that sqlcmd is cross-platform and provide installation instructions for Linux/macOS if needed.
- Use generic shell prompt (e.g., $) or indicate both Windows and Linux/macOS command syntax where relevant.
- Explicitly state that the steps are applicable to both Windows and Linux/macOS environments, unless there are OS-specific differences.
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 step-by-step instructions for migrating a SQL Server database to Azure Arc-enabled SQL Managed Instance, but several examples and instructions assume a Windows environment. For example, backup file paths and kubectl cp examples use Windows-style paths (e.g., C:\Backupfiles\test.bak) without providing Linux/macOS equivalents. Tools like SSMS are mentioned without Linux alternatives, and Visual Studio Code is referenced, which is cross-platform, but no explicit Linux/macOS instructions or screenshots are provided. This may cause friction for users on Linux or macOS.
Recommendations
- Provide equivalent examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) alongside Windows paths.
- Mention and provide examples using cross-platform or Linux-native tools for backup (e.g., sqlcmd, Azure Data Studio) where possible.
- Clarify that Visual Studio Code is cross-platform and provide any Linux/macOS-specific steps if needed.
- When referencing SSMS (which is Windows-only), suggest Azure Data Studio as an alternative for Linux/macOS users.
- For kubectl cp commands, show both Windows and Linux/macOS source path examples.
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 lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure PowerShell is marked as 'No', SQL Server PowerShell is marked as 'Yes', and PowerShell scripting is highlighted in the manageability section. There are no Linux/macOS-specific tools or scripting examples mentioned, nor is there guidance for Linux users on equivalent workflows.
Recommendations
- Add examples or mention of cross-platform tools such as Azure Data Studio, which runs on Windows, Linux, and macOS.
- Clarify that SQL Server PowerShell is primarily a Windows tool and provide alternatives for Linux/macOS users, such as Bash scripting or using sqlcmd.
- Include references to command-line tools like sqlcmd and Azure CLI, which are cross-platform, and provide sample usage.
- Explicitly state which features/tools are Windows-only and suggest Linux/macOS alternatives where possible.
- Consider adding a section or table column indicating platform compatibility for each tool.
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
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but the Windows section is more detailed and appears after the Linux example. The Linux example uses the 'base64' command, while Windows users are directed to use 'certutil' and 'findstr'. However, the Linux example is brief and lacks guidance for removing headers, which is covered for Windows. The rest of the documentation is platform-neutral, focusing on Azure CLI, kubectl, and OpenSSL, which are cross-platform tools.
Recommendations
- Add instructions for removing headers from base64 output on Linux/macOS, such as using 'grep' or 'sed'.
- Clarify that OpenSSL, Azure CLI, and kubectl commands are cross-platform and provide any necessary notes for Windows users (e.g., file path syntax differences).
- Consider providing Linux/macOS and Windows examples side-by-side for base64 encoding and header removal to ensure parity.
- Explicitly mention that the steps are applicable to both Linux and Windows unless otherwise noted.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions for all major lifecycle tasks (install, upgrade, uninstall, proxy config), but Windows examples and tools (PowerShell, Group Policy, WSUS, Configuration Manager, MSI installer, Msiexec) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no Linux/bash equivalent. Windows-specific update infrastructure is described in depth, while Linux package manager instructions are concise. Overall, Linux users can complete all tasks, but Windows-centric examples and tooling are more prominent.
Recommendations
- Provide equivalent bash scripts for resource cleanup and automation tasks, not just PowerShell.
- Balance the level of detail between Windows and Linux sections, especially for upgrade/uninstall procedures.
- Where possible, mention Linux tools (e.g., cron, systemd, Ansible) for automation alongside Windows tools (Group Policy, WSUS).
- Consider presenting Linux and Windows instructions in parallel or alternating order, rather than Windows-first.
- Add troubleshooting tips for Linux environments, similar to those for Windows (e.g., log locations, service management).
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting examples, Windows paths are referenced in error messages, and Windows tools (such as Remote PowerShell and RDP) are mentioned. Linux-specific troubleshooting commands and examples are largely absent, and Windows/PowerShell instructions are often given before or instead of Linux equivalents. Some CLI commands reference Windows paths, and Linux troubleshooting is only briefly mentioned (e.g., glibc version error).
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., use curl, wget, or openssl for network troubleshooting).
- Include Linux/macOS-specific troubleshooting steps for common errors, such as SSH folder access, DNS resolution, and proxy configuration.
- When referencing file paths or error messages, clarify if they are Windows-specific or provide Linux/macOS equivalents.
- Ensure that CLI instructions and examples are platform-neutral or include both Windows and Linux/macOS variants.
- Add troubleshooting guidance for Linux-specific issues, such as permission errors, file system differences, and environment variable configuration.
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 deployment instructions exclusively using Azure PowerShell commands, without showing Azure CLI or Bash equivalents. All deployment steps and examples use PowerShell syntax, which is native to Windows and less familiar to Linux/macOS users. While ARM templates are provided for both Linux and Windows extensions, the command-line instructions are Windows-centric, and PowerShell is presented as the primary (and only) method for template deployment.
Recommendations
- Add Azure CLI examples for deploying ARM templates, such as 'az deployment group create' commands, alongside PowerShell examples.
- Explicitly mention that Azure CLI can be used from Linux/macOS and provide equivalent CLI syntax for each deployment scenario.
- Consider showing Bash script snippets for Linux users, or at least link to Azure CLI documentation for ARM template deployment.
- If PowerShell is required (e.g., for certain advanced scenarios), clarify this and provide guidance for installing PowerShell Core on Linux/macOS.
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 provides extensive PowerShell examples and references Windows tools (such as New-AzStorageBlobSASToken and New-NetFirewallRule) throughout, with Windows-centric scripting and terminology. While the Run command feature supports both Windows and Linux, most examples (especially in PowerShell and REST API sections) are Windows-focused, and Linux-specific guidance is minimal or absent. REST API examples exclusively target Windows scenarios (firewall rule creation via New-NetFirewallRule), and PowerShell examples use Windows paths and scripts. Azure CLI examples use PowerShell syntax (Write-Host), which is not appropriate for Linux shell scripts. Linux-specific scripting, parameters, and REST API scenarios are missing.
Recommendations
- Add Linux-specific examples for PowerShell, Azure CLI, and REST API sections, such as running bash scripts, configuring iptables/firewalld, and using Linux file paths.
- In PowerShell examples, clarify how to run scripts on Linux Arc-enabled servers (e.g., using .sh files, bash commands, and relevant parameters).
- For Azure CLI, provide both Windows (PowerShell) and Linux (bash) script examples, and avoid using Write-Host in CLI examples intended for Linux.
- In REST API section, include Linux scenarios (e.g., running bash scripts to configure firewall rules with iptables or ufw) alongside Windows examples.
- Ensure documentation consistently mentions Linux support and provides parity in guidance for both OS types.
- Where referencing tools like New-AzStorageBlobSASToken, clarify alternatives or usage for Linux users.
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
windows_first
missing_linux_example
Summary
The documentation provides recovery instructions and a script exclusively for Windows, using PowerShell and referencing a Windows-specific script. There are no Linux/macOS equivalents, examples, or guidance, and the section is titled 'Recover Arc resource bridge from a Windows machine,' implying Windows is the only supported platform for this operation.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or Python.
- Clarify if recovery is only supported from Windows, and if so, explain why and mention any possible workarounds for Linux/macOS users.
- If cross-platform support is possible, add Linux/macOS-specific prerequisites, script examples, and troubleshooting steps.
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 provides multiple methods for installing Arc agents at scale for VMware VMs, but there is a notable Windows bias. The 'Auto Arc-enablement script' section exclusively uses PowerShell and references Windows Task Scheduler for automation, with no Linux shell or cron examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux equivalents, and Linux-specific guidance is limited to a brief sudo configuration note. While Ansible playbooks are mentioned as an out-of-band method, no Linux-centric automation examples or scripts are provided.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, especially for the automation script.
- Include instructions for running the automation script as a cron job on Linux, not just Windows Task Scheduler.
- Offer guidance for using Linux-native tools (e.g., systemd timers, cron) for scheduled tasks.
- Ensure parity in example commands and scripts for both Windows and Linux environments.
- 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 provides only PowerShell examples and references a .ps1 onboarding script, with no mention of Bash, Linux shell, or cross-platform alternatives. All scripting and command-line instructions are Windows-centric, and there are no Linux/macOS equivalents or guidance for non-Windows environments. This creates friction for Linux/macOS users attempting disaster recovery operations.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, if supported.
- Clarify whether the onboarding script can be run on Linux/macOS (e.g., with PowerShell Core), and provide instructions for doing so.
- Mention any prerequisites or limitations for Linux/macOS users, including supported platforms for the onboarding script.
- If the onboarding script is Windows-only, explicitly state this and suggest alternatives or workarounds 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 a PowerShell-based deboarding script for removing VMware vCenter from Azure Arc, with detailed instructions for Windows users (PowerShell). There are no equivalent Linux/macOS instructions for running the script, and Windows-specific guidance (e.g., Set-ExecutionPolicy) is given before any mention of Linux alternatives. Manual removal steps are platform-neutral, but the scripted approach is Windows-centric.
Recommendations
- Provide instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any required permission settings.
- Mention PowerShell Core as a cross-platform option and clarify if the script is compatible with it.
- If the script is Windows-only, explicitly state this and offer a Linux/macOS alternative or manual steps.
- Consider providing Bash or shell script alternatives for Linux users, or document how to use the manual removal steps as a fallback.
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. There are no Linux/macOS shell or cross-platform script alternatives, and all usage examples are PowerShell-centric. The script is referenced as a .ps1 file, which is typically not natively supported on Linux/macOS without additional setup (e.g., installing PowerShell Core). No Bash or Azure CLI equivalents are mentioned.
Recommendations
- Provide instructions for running the script using PowerShell Core on Linux/macOS, including installation guidance if needed.
- Offer a Bash or Azure CLI equivalent script for Linux/macOS users, or clarify if the PowerShell script is cross-platform.
- Explicitly state platform requirements and limitations for the script.
- Add Linux/macOS usage examples, or note if the script is intended for Windows environments only.
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 provides Azure CLI command examples in PowerShell syntax and references PowerShell scripts (.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor are Linux-friendly scripts or instructions mentioned. The use of PowerShell and .ps1 files is presented as the default, with no Linux alternatives or parity.
Recommendations
- Provide Azure CLI command examples in Bash syntax alongside PowerShell, or clarify that the CLI commands work cross-platform.
- Offer equivalent Bash shell scripts (.sh) for bulk deployment and workflow deletion, or document how Linux/macOS users can perform the same tasks.
- Explicitly state that the Azure CLI commands are cross-platform and can be run in any shell, not just PowerShell.
- Add notes or sections for Linux/macOS users, including any required adaptations for file paths, script execution, or prerequisites.
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 notable Windows bias. All CLI/script examples are provided in PowerShell syntax, including use of backticks for line continuation and explicit PowerShell script (.ps1) usage. File paths in JSON templates and scripts are Windows-style (e.g., C:\Users\...), and references to tools/scripts are exclusively PowerShell-based. There are no Bash, Linux, or macOS equivalents or guidance for users on non-Windows platforms, despite the topic being cross-platform (Azure Arc-enabled Kubernetes clusters can run on Linux). This bias may create friction for Linux/macOS users attempting to follow the instructions.
Recommendations
- Provide Bash/zsh shell equivalents for all CLI/script examples, using standard Linux/macOS conventions (e.g., line continuation with \ or newlines, no backticks).
- Include Linux-style file paths in JSON templates and scripts (e.g., /home/user/...).
- Clarify whether the infra_onboarding.ps1 script is cross-platform (e.g., can it be run with PowerShell Core on Linux/macOS?), and provide guidance for Linux/macOS users if not.
- Add explicit notes or sections for Linux/macOS users, including any prerequisites or alternative steps.
- Where possible, use platform-neutral Azure CLI commands and avoid PowerShell-specific syntax.
- Consider providing downloadable shell scripts (.sh) 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 Windows bias in several areas. The Bash example for extracting ZIP files uses the Windows-specific Expand-Archive command and Windows file paths, which are not available on Linux/macOS. The recommended installation method for kubectl uses winget, a Windows-only package manager, with no Linux/macOS alternatives provided. Throughout, file paths and command examples often default to Windows conventions, and Linux-native tools (such as unzip or tar) are not mentioned. While Azure CLI and kubectl are cross-platform, the documentation does not provide Linux/macOS-specific instructions for critical setup steps.
Recommendations
- Provide Linux/macOS equivalents for ZIP extraction, such as 'unzip' or 'tar' commands, and use POSIX-style file paths in Bash examples.
- Include kubectl installation instructions for Linux/macOS (e.g., using 'curl', 'apt', 'brew', or 'snap') alongside winget.
- Ensure Bash examples are platform-agnostic or offer separate tabs for Linux/macOS and Windows.
- Review file path conventions in Bash examples to avoid Windows-only syntax.
- Add explicit notes or sections for Linux/macOS users where Windows-specific tools are referenced.
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 towards Windows and PowerShell. All onboarding scripts and examples are provided only for PowerShell (.ps1 files), and users are instructed to use Windows-specific tools like 'winget'. There are no Bash, shell, or Linux/macOS equivalents or instructions, and no mention of how to run the scripts on non-Windows platforms. This creates friction for Linux/macOS users who may wish to automate onboarding for workload orchestration in Azure Arc.
Recommendations
- Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the PowerShell scripts cross-platform (e.g., with PowerShell Core).
- Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., 'apt', 'brew', or direct download links).
- Explicitly state platform requirements for the scripts, and if Windows is required, clarify this early in the documentation.
- Add notes or sections for Linux/macOS users, including any prerequisites, script modifications, or alternative onboarding steps.
- If PowerShell Core is supported, provide instructions for installing and running the scripts on Linux/macOS.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown first and exclusively in some cases. There are no Linux-specific tools or patterns mentioned, and the Azure CLI is inherently cross-platform, but the example bias may create friction for Linux/macOS users.
Recommendations
- Provide both Bash and PowerShell examples for CLI commands, or default to Bash syntax for cross-platform parity.
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and note any OS-specific differences if present.
- Avoid using Windows-specific line continuation (backticks) in CLI examples unless the section is Windows-only.
- Where possible, add Linux/macOS-specific notes or troubleshooting tips.
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 cross-platform tools like Azure CLI, Docker, and kubectl. Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service groups' section, which offers both Bash and PowerShell tabs. This creates friction for Linux/macOS users, as they must translate PowerShell-specific syntax and patterns to Bash or their preferred shell.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and kubectl commands.
- Avoid using PowerShell-specific constructs (e.g., variable syntax, ConvertTo-Json, Out-File) in generic cross-platform guidance; use platform-neutral syntax or offer both versions.
- Clearly indicate when a command is Windows-only, and provide alternative instructions for Linux/macOS where possible.
- Review file encoding guidance to ensure it is relevant for Linux/macOS users (e.g., UTF-8 with BOM is a Windows-specific concern).
- For scripting steps (e.g., Base64 encoding, JSON file creation), offer Bash/Linux alternatives (e.g., using echo, base64, jq, etc.).
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides authentication instructions for Azure Container Registry using both Azure CLI and Azure PowerShell, but PowerShell examples and references are prominent throughout, and often shown alongside or immediately after CLI examples. There are no explicit Linux/macOS-specific examples (e.g., shell scripting, environment variable usage, or alternative CLI patterns). Windows/PowerShell tools are mentioned in every authentication method table row, and the 'Next steps' section links to both CLI and PowerShell guides, but does not reference Linux/macOS-specific workflows. While Docker and Azure CLI are cross-platform, the documentation does not highlight Linux/macOS usage or address potential differences (such as shell syntax or environment setup).
Recommendations
- Add explicit Linux/macOS shell examples (e.g., bash/zsh) for authentication flows, especially for scripting scenarios.
- Clarify that Azure CLI and Docker commands are cross-platform, and provide guidance for Linux/macOS users (e.g., installation links, shell environment setup).
- Include troubleshooting tips for Linux/macOS environments (e.g., Docker daemon setup, file permissions, environment variables).
- Balance PowerShell references with bash or shell script equivalents, especially in tables and quickstart sections.
- Mention that Azure CLI is available on Linux/macOS and link to installation instructions for those platforms.
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 all commands, but consistently presents Bash examples before PowerShell. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There are no missing Linux examples or Windows-only instructions.
Recommendations
- Continue to provide both Bash and PowerShell examples for all commands.
- Consider clarifying that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Optionally, add a note at the top explaining the cross-platform nature of Azure CLI and the provided examples.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used, and all commands are cross-platform (Azure CLI, Helm).
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid perceived bias.
- Explicitly mention that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a brief note clarifying that Azure CLI and Helm are available on all major platforms.
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
windows_first
Summary
The documentation provides both Bash and PowerShell examples throughout, but PowerShell examples are consistently presented after Bash. There are no Windows-exclusive tools or patterns, and Linux parity is maintained for all commands. No critical steps are Windows-only, and the Azure CLI and kubectl are cross-platform.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in sections to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell are supported on Windows, Linux, and macOS to reinforce cross-platform parity.
- If possible, add a note clarifying that PowerShell Core is available on Linux/macOS, not just Windows.
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 primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux/Windows example is provided, SSMS is presented as the default client, potentially creating friction for Linux/macOS users. No Linux-native GUI tools (e.g., Azure Data Studio, DBeaver) are mentioned. Azure CLI commands are cross-platform, but the client connection guidance is slightly Windows-biased.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit examples for connecting from macOS and Linux, including GUI and CLI tools.
- Clarify that sqlcmd is available on Linux/macOS and provide installation guidance or links.
- Consider listing sqlcmd first, or equally, when describing connection options.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There are Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl), and explanations about PowerShell's curl alias, but there are no equivalent Linux/macOS-specific notes or troubleshooting tips. The Linux installation for curl is mentioned only as 'install curl package' without a link or further guidance, which is less helpful than the Windows section.
Recommendations
- Present installation links for all platforms (Windows, Linux, macOS) in parallel, rather than listing Windows first.
- Provide Linux/macOS-specific troubleshooting tips or notes, similar to the PowerShell/cmd.exe guidance for Windows.
- Add direct links or instructions for installing curl on Linux and macOS, not just a brief mention.
- Ensure parity in detail and guidance for all platforms, including version checks and command usage.
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 tasks, but consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI. In some sections, PowerShell examples are shown immediately after CLI, and environment variable examples are given for both Bash (Linux/macOS) and PowerShell (Windows). However, there are no Linux-specific command-line tools (e.g., shell scripts, curl, etc.) or explicit macOS guidance. The documentation is not Windows-only, but the presence of PowerShell throughout and the lack of Linux/macOS-specific examples creates mild Windows bias.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while Azure PowerShell is primarily for Windows users.
- Add notes or examples for Linux/macOS users where relevant (e.g., shell scripting, handling environment variables, troubleshooting).
- Consider including troubleshooting tips for Linux/macOS environments, such as proxy configuration nuances.
- Where possible, clarify that all commands (except PowerShell) are compatible with Linux/macOS.
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 includes references to Windows-specific services (e.g., 'time.windows.com', 'sts.windows.net', 'servicebus.windows.net', 'login.windows.net') and Windows NTP as a default, which may imply Windows-centric patterns. Windows NTP is mentioned as the default for Hyper-V, but Linux NTP alternatives are not discussed. Some URLs and notes reference Windows, but Linux equivalents or patterns are not always provided or explained. However, the documentation does mention Linux-specific endpoints (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com') and SSH as a connectivity requirement, which is cross-platform.
Recommendations
- Add explicit Linux NTP server examples (e.g., 'ntp.ubuntu.com', 'pool.ntp.org') and clarify when Windows NTP is required versus when Linux NTP is appropriate.
- Where Windows-specific URLs or services are mentioned, provide Linux equivalents or clarify if the requirement applies to both OS types.
- Ensure examples and notes do not default to Windows patterns unless the feature is Windows-only.
- Add clarification on management machine OS requirements and provide guidance for both Windows and Linux administrators.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation references Azure CLI installation and links to the Windows installation page first, but does not provide parity for Linux/macOS users (e.g., links to their installation instructions or mention them explicitly). All CLI examples are generic and not Windows-specific, but the management machine requirements and CLI links are Windows-centric.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside the Windows link.
- Clarify that the management machine can be Windows, Linux, or macOS, as Azure CLI is cross-platform.
- Provide example CLI commands for Linux/macOS where relevant (e.g., file paths, shell syntax differences).
- Ensure that references to 'current CLI directory' are clear for all OSes (e.g., explain how to find the working directory on Linux/macOS).
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in feature and bug fix descriptions. However, Windows download links and version numbers are consistently listed before Linux, and Windows-specific installer instructions (e.g., PowerShell, msiexec, GUI) are detailed, while Linux installation methods and troubleshooting are referenced only via links. Some improvements and bug fixes reference Windows tools (e.g., PowerShell scripts, MSI signature verification), but Linux equivalents are not always explained in the same detail.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers to avoid Windows-first bias.
- Provide explicit Linux installation and troubleshooting instructions (e.g., command-line examples for RPM/DEB, systemctl usage) alongside Windows installer guidance.
- Where Windows tools/scripts are mentioned (e.g., PowerShell, MSI), briefly note the Linux equivalent or clarify if not applicable.
- Ensure that Linux-specific improvements and bug fixes are described with equal detail as Windows items.
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 clear parity between Windows and Linux VM extensions, with dedicated tables for each OS and links to relevant usage and deployment information. However, the Windows extensions table is presented before the Linux extensions table, which is a minor 'windows_first' bias. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned equally for both OSes, and partner extensions are shown for both platforms. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to reinforce parity.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Add a brief introductory note clarifying that Azure Arc-enabled servers support both Windows and Linux equally, to reinforce cross-platform support.
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
minor_windows_tools
Summary
The documentation covers troubleshooting Azure Connected Machine agent issues for both Windows and Linux, providing parity in error codes, exit codes, and troubleshooting steps. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. There is a minor mention of Windows-specific log file locations and PowerShell requirements, but Linux equivalents are also provided. Overall, the bias is minimal and does not significantly impact Linux/macOS users.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid 'windows_first' bias.
- Where possible, provide both Windows and Linux log file paths together rather than separately.
- Explicitly mention macOS support or limitations if applicable.
- Ensure that troubleshooting steps reference both Windows and Linux commands/tools equally.
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 portal instructions. Some minor Windows-specific notes (e.g., PowerShell command syntax, log file locations) are included, but Linux equivalents are also provided. Windows examples and tools are not exclusive, but are sometimes referenced first or with more detail. The documentation is not Windows-only and covers Linux scenarios, but there is a slight tendency to mention Windows tools and patterns before Linux equivalents.
Recommendations
- Ensure Linux and macOS instructions/examples are always present and equally detailed.
- Where PowerShell is referenced, clarify that it is available on Linux/macOS as well, or provide Bash/Linux shell alternatives where appropriate.
- Alternate the order of CLI and PowerShell examples so Linux users see their preferred tools first in some sections.
- Explicitly note cross-platform compatibility for Azure CLI and agent commands.
- Review log file instructions to ensure Linux paths are shown with equal prominence to Windows paths.
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 Azure Arc-enabled servers and provides parity in feature descriptions and CLI examples. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. In some sections, Windows is mentioned before Linux (e.g., 'Windows and Linux'), and PowerShell is presented alongside CLI, which is more cross-platform. All examples are available for both platforms, but PowerShell is not natively available on most Linux systems.
Recommendations
- Emphasize Azure CLI as the primary cross-platform tool for managing extensions, and clarify that PowerShell is optional for Linux users.
- Consider listing Linux and Windows in alternating order or using 'Linux and Windows' where appropriate.
- Add a note clarifying that Azure PowerShell is available on Linux via PowerShell Core, but Azure CLI is the recommended cross-platform approach.
- Ensure that all screenshots and portal instructions are generic and not Windows-specific.
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, but the Windows/PowerShell example is presented first and in more detail, including a screenshot. The Linux example is present and functional, but the ordering and emphasis slightly favor Windows. The 'Related content' section lists PowerShell before Azure CLI, which is more cross-platform.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which comes first to avoid implicit prioritization.
- Include equal detail and screenshots for both Windows and Linux workflows.
- In 'Related content', list Azure CLI before PowerShell, or clarify CLI is cross-platform.
- Explicitly state that both Windows and Linux are fully supported and provide parity in instructions.
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 in the 'Run the script' and 'Retry command' sections. The Windows-specific note about PowerShell ISE is included, but there is no equivalent Linux-specific guidance. Both platforms are supported, and Linux parity is generally good.
Recommendations
- Present Windows and Linux instructions in parallel or alternate the order to avoid always showing Windows first.
- Add Linux-specific notes or troubleshooting tips if relevant (e.g., shell compatibility, permissions).
- Explicitly mention macOS support if the Bash script works on macOS, or clarify if it does not.
- Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
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, but there are subtle indications of Windows bias. PowerShell is mentioned as a primary automation tool alongside Azure CLI and SDKs, and some links (such as Azure Automation and AVS onboarding) default to Windows-specific tabs or examples. Windows features and tools are sometimes referenced before Linux equivalents, though Linux support is acknowledged throughout. No critical sections are Windows-only, and Linux users can complete all tasks, but Windows examples and terminology are slightly more prominent.
Recommendations
- Ensure that automation examples and links reference both PowerShell and Bash/CLI equally, or provide Linux/macOS-specific guidance where relevant.
- When listing supported tools and SDKs, avoid placing Windows-specific tools (e.g., PowerShell) before cross-platform options (e.g., Azure CLI, REST API).
- For links that default to Windows tabs (such as AVS onboarding or Azure Automation), add explicit Linux tabs or examples, or clarify Linux support.
- Consider adding a section or callout summarizing Linux/macOS parity and supported scenarios for non-Windows users.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere and includes both Windows and Linux-related updates. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned, but Linux is also referenced (Arc agent installation on Linux via SSH). However, in several places, Windows tools and technologies (e.g., System Center Configuration Manager, Group Policy, Azure PowerShell) are mentioned before or more prominently than their Linux equivalents (e.g., Ansible). Windows examples and tools tend to be listed first, and Windows-specific features are sometimes highlighted without equal Linux coverage.
Recommendations
- When listing tools or methods for agent installation at scale, ensure Linux-native options (e.g., Ansible, shell scripts) are given equal prominence and not always listed last.
- For features that apply to both Windows and Linux VMs, clarify applicability and provide examples for both platforms.
- Where PowerShell is mentioned, also reference Bash/Azure CLI equivalents if available.
- Review the order of tool listings to avoid always putting Windows tools first.
- Add links or references to Linux-specific documentation where relevant.
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, in several sections, PowerShell examples are presented immediately after Bash, which may subtly reinforce Windows as a primary platform. No Windows-specific tools or patterns are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or Windows-only tools mentioned.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note at the beginning clarifying that all Azure CLI commands are cross-platform and Bash examples are intended for Linux/macOS users.
- Ensure screenshots and portal instructions are neutral and do not reference Windows-specific UI elements.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line tasks, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash, and some PowerShell-specific nuances (like base64 encoding) are explained. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks without friction. Minor bias exists in the ordering and the presence of PowerShell-specific explanations.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
- Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- Ensure that any PowerShell-specific explanations (e.g., base64 encoding) are matched with Bash/Linux equivalents, which is already done in most cases.
- If possible, provide a brief summary at the start clarifying cross-platform support.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash (Linux/macOS) tab is presented first. All commands use the cross-platform Azure CLI, and there are no Windows-specific tools or patterns. No critical steps are Windows-only, and Linux/macOS users are fully supported.
Recommendations
- Maintain the current structure, as Bash examples are shown first and all commands are cross-platform.
- Ensure that any future additions (such as troubleshooting or advanced scenarios) continue to provide parity for Linux/macOS users.
- Consider clarifying in the introduction that all examples are cross-platform unless otherwise noted, to reassure non-Windows 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 operations, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are shown first, followed by PowerShell, which is a minor bias toward Linux/macOS users rather than Windows. There are no Windows-only tools, patterns, or terminology used, and all instructions are cross-platform. No critical sections are Windows-only, and Linux/macOS users can complete all tasks as described.
Recommendations
- Maintain the current structure of providing 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 at the top indicating that all CLI commands are cross-platform and users should select the appropriate shell for their OS.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, in each section, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users (not Windows). No Windows-specific tools, patterns, or exclusive examples are present. All commands use the Azure CLI and Helm, which are cross-platform.
Recommendations
- No action needed for Linux parity. If desired, alternate the order of Bash and PowerShell tabs in different sections to avoid perceived bias.
- Ensure that any future additions maintain parity and do not introduce Windows-only tools or instructions.
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, ensuring cross-platform parity. However, in each section, Bash examples are consistently shown first, followed by PowerShell. There are no Windows-only tools, patterns, or references, and Linux/macOS users can fully follow the tutorial without friction.
Recommendations
- Maintain the current structure, as both Bash and PowerShell examples are provided.
- Consider alternating the order of Bash and PowerShell examples in some sections to avoid implicit bias toward Bash users.
- Explicitly state at the beginning that both Linux/macOS (Bash) and Windows (PowerShell) are fully supported, to reassure users.
- If possible, add a brief note clarifying that all commands are cross-platform unless otherwise specified.
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 capability, listing PowerShell alongside CLI. While this is not strictly Windows-only, PowerShell is historically associated with Windows, and its mention alongside CLI may subtly prioritize Windows users. However, no exclusive Windows tools, examples, or patterns are given, and the documentation is focused on a cross-platform mobile app.
Recommendations
- Clarify that both Bash (Azure CLI) and PowerShell scripts are supported, and provide examples or guidance for both where relevant.
- Explicitly mention that Azure Copilot can generate scripts for Linux/macOS environments using Azure CLI.
- If showing script generation examples, alternate or balance between PowerShell and Bash/CLI examples.
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 cross-platform Azure CLI and Helm. However, the PowerShell examples are present throughout, which may slightly favor Windows users, but Linux/macOS parity is maintained.
Recommendations
- Consider explicitly stating that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a note clarifying that PowerShell Core is available on Linux and macOS, so PowerShell examples are not Windows-exclusive.
- If possible, provide a generic shell example or clarify that Bash and PowerShell are both supported on all platforms.
- Ensure that Bash and PowerShell tabs are equally prominent and clarify that users can choose either based on their environment.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. However, the PowerShell example is given equal prominence and appears immediately after the CLI example, which may signal a Windows-centric approach. There are no explicit Linux/macOS command-line examples (such as Bash scripts or references to Linux-native tools), and PowerShell is primarily a Windows tool, though it is now cross-platform. The overall workflow and guidance are platform-neutral, but the example tooling leans toward Windows/PowerShell.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for image import and authentication workflows.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS, and consider showing CLI examples first.
- Mention that PowerShell Core is available on Linux/macOS, but provide guidance for users who prefer native shell environments.
- Include references to Linux-native tools (such as Docker CLI, curl, etc.) where relevant, or note their applicability.
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 parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally and sometimes before CLI. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. There are no Linux-specific examples, and no mention of Bash or shell scripting. The documentation assumes familiarity with PowerShell, which is less common on Linux/macOS platforms.
Recommendations
- Feature Azure CLI examples first, as CLI is cross-platform and native to Linux/macOS.
- Explicitly state that Azure CLI is recommended for Linux/macOS users.
- Add notes clarifying that PowerShell is available cross-platform, but CLI is more typical for Linux/macOS.
- Consider including Bash shell scripting examples for automation scenarios.
- Clarify installation instructions for Azure CLI and PowerShell on Linux/macOS.
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, such as changing registry SKUs and showing registry usage. However, PowerShell examples are consistently given alongside CLI examples, and in some cases, PowerShell is mentioned before CLI. There are no explicit Linux/macOS shell examples (e.g., Bash), and the documentation does not clarify that Azure CLI is cross-platform. Additionally, there is no mention of Linux-native tools or workflows, and the examples do not address Linux/macOS users directly.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Provide Bash shell examples or note that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
- When listing tools, mention Azure CLI before Azure PowerShell, as CLI is more widely used and cross-platform.
- Consider adding a brief note for Linux/macOS users about installing and using Azure CLI.
- Avoid listing PowerShell examples before CLI unless the feature is Windows-specific.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command-line examples for Helm and Azure CLI, which are cross-platform, but in the 'Set the following environment variables' section, the example uses the Windows 'set' command instead of the cross-platform 'export' (Linux/macOS). Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, but also includes Azure PowerShell and Portal, which is reasonable. However, the documentation does not consistently provide Linux/macOS equivalents for environment variable setting, and the initial example may confuse non-Windows users.
Recommendations
- For environment variable examples, provide both Windows ('set') and Linux/macOS ('export') commands, or use cross-platform syntax.
- Add a note clarifying that Azure CLI and Helm commands are cross-platform and can be used on Windows, Linux, and macOS.
- Review all command snippets to ensure they are not Windows-specific and provide parity for Linux/macOS users.
- Consider listing Linux/macOS commands first or side-by-side with Windows commands for improved parity.