226
Pages Scanned
50
Pages Flagged
226
Changed Pages
22.1%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:30
Scan Information
Started At: 2026-02-14 00:00:30
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 226
Files Completed: 226
Problematic Pages
53 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
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased toward Windows environments: all onboarding scripts and examples are provided only for PowerShell, Windows-specific tools like 'winget' are used for prerequisites, and there are no Bash, Linux, or macOS equivalents or instructions. Linux/macOS users are left without clear guidance for running the onboarding scripts or installing dependencies.
Recommendations
- Provide Bash or shell script equivalents for onboarding (e.g., infra_onboarding.sh, cm_onboarding.sh) or document how to run the .ps1 scripts cross-platform (e.g., with PowerShell Core on Linux/macOS).
- Replace or supplement 'winget' install commands with platform-agnostic alternatives (e.g., apt, yum, brew, or direct download instructions for Azure CLI and kubectl).
- Clearly state platform requirements and, if Windows is required, explain why. If not, add explicit instructions for Linux/macOS users.
- Add example commands and screenshots for Linux/macOS terminals where appropriate.
- Mention the need for PowerShell Core (pwsh) if the scripts are intended to be cross-platform, and provide installation instructions.
Create Pull Request
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides 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 presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The template examples themselves are balanced, but the deployment instructions are Windows-centric.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell, e.g., 'az deployment group create' commands.
- Explicitly mention that Azure CLI can be used from Linux/macOS and provide sample Bash scripts.
- Consider showing CLI examples before or alongside PowerShell to avoid Windows-first bias.
- Clarify that PowerShell is cross-platform, but also provide CLI alternatives for users who do not use PowerShell.
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
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to perform clean-up operations. There are no references to Linux/macOS shell equivalents, nor are there instructions for running the script in cross-platform environments (e.g., PowerShell Core, Bash). The documentation assumes the user is on Windows and using Windows PowerShell, which may create friction for Linux/macOS users.
Recommendations
- Clarify whether RGCleanScript.ps1 is compatible with PowerShell Core (pwsh) on Linux/macOS. If so, provide example commands for running the script on those platforms.
- If the script is Windows PowerShell-only, consider providing a cross-platform version or a Bash alternative for Linux/macOS users.
- Explicitly mention prerequisites for Linux/macOS users, such as installing PowerShell Core, and provide installation instructions or links.
- Add notes or troubleshooting tips for common issues encountered when running PowerShell scripts on non-Windows platforms.
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 intended for configuring AKS Edge Essentials on Linux, but it uses Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration and does not provide native Linux shell equivalents. This creates friction for Linux users who may not have access to Windows tools or PowerShell, and there are missing examples for performing the same tasks directly on Linux.
Recommendations
- Provide native Linux shell (bash) commands for checking and setting sysctl parameters, e.g., 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
- Clarify whether Invoke-AksEdgeNodeCommand is available on Linux or only via Windows/PowerShell, and offer alternatives if not.
- Ensure all steps for Linux node configuration can be completed from a Linux environment without requiring Windows tools.
- Add explicit Linux command-line examples alongside any PowerShell/Windows-centric instructions.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation instructions for client tools across platforms, but Windows-specific guidance is often mentioned first or in greater detail. For example, 'kubectl' installation links list Windows first, and the note about installing via curl specifically references Windows cmd.exe and PowerShell, without equivalent Linux/macOS instructions. The curl section gives a Windows link and only mentions 'Linux: install curl package' without a link or command. PowerShell-specific behavior for curl is noted, but no Linux/macOS shell nuances are discussed.
Recommendations
- Present installation instructions for all platforms (Windows, Linux, macOS) in parallel, not Windows-first.
- Provide explicit Linux/macOS installation links and example commands for tools like curl, not just a brief mention.
- Include shell-specific notes for Linux/macOS (e.g., bash/zsh) where PowerShell-specific notes are given.
- Balance platform-specific guidance and troubleshooting tips.
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 frequently presents Windows-centric tools and file paths first (e.g., SSMS, C:\ paths), and does not provide equivalent Linux/macOS examples for key steps such as creating backups or copying files. This may cause friction for users on non-Windows platforms.
Recommendations
- Provide parallel examples using Linux/macOS tools (e.g., Azure Data Studio, sqlcmd, or VS Code on Linux/macOS) for connecting to SQL Server and running backup/restore commands.
- Show backup file paths using both Windows (C:\Backupfiles\test.bak) and Linux (/home/user/backup/test.bak) formats.
- When referencing tools like SSMS, mention cross-platform alternatives such as Azure Data Studio.
- In kubectl cp examples, include a Linux/macOS source path (e.g., ~/Backupfiles/test.bak) alongside the Windows example.
- Clarify that all steps can be performed from Linux/macOS where supported, and note any Windows-only requirements.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using sqlcmd, but these examples are shown exclusively with PowerShell syntax (e.g., kubectl exec ...), and the sqlcmd usage is presented in a way that assumes Windows/PowerShell familiarity. There are no explicit Linux/macOS shell examples, nor is there guidance for Linux users on connecting to the SQL Server pod or decoding secrets. The use of PowerShell syntax and lack of Linux/macOS parity creates friction for non-Windows users.
Recommendations
- Provide equivalent Linux/macOS shell examples (e.g., using bash) for connecting to the SQL Server pod, running sqlcmd, and decoding base64 secrets.
- Clarify that sqlcmd is cross-platform and provide installation instructions for Linux/macOS if needed.
- Show both Windows (PowerShell) and Linux/macOS (bash) command variants side-by-side where applicable.
- Explicitly mention that kubectl and sqlcmd commands can be run from any OS, and note any OS-specific differences.
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 methods for base64 encoding files, but the Windows instructions are more detailed and appear after the Linux example. The Windows section references Windows-specific tools (certutil, findstr) and requires manual header removal, while the Linux example is simpler. There is no PowerShell bias, but the Windows instructions are more prominent and lack parity in automation compared to Linux. All other steps use cross-platform tools (OpenSSL, Azure CLI, kubectl), but the Windows base64 encoding process is less streamlined.
Recommendations
- Provide a more streamlined Windows example for base64 encoding, possibly using PowerShell's built-in Base64 capabilities for parity with Linux simplicity.
- Mention cross-platform alternatives (e.g., using OpenSSL for base64 on Windows, or PowerShell's [Convert]::ToBase64String) to avoid reliance on certutil/findstr.
- Ensure Linux and Windows instructions are equally detailed and placed side-by-side for clarity.
- Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
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: Windows/PowerShell examples are given (e.g., PowerShell cmdlets for troubleshooting HTTP2 errors), Windows paths and error messages are shown first, and Linux-specific troubleshooting steps are sometimes missing or less detailed (e.g., SSH folder access, proxy configuration, and CLI usage). While Linux is mentioned (e.g., glibc errors, Azure Linux OS), Linux/macOS users may encounter friction due to the lack of parity in examples and troubleshooting steps.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows-specific troubleshooting steps (e.g., use curl or wget for HTTP2 troubleshooting instead of PowerShell).
- Include Linux/macOS CLI examples for commands such as az arcappliance, pip installation, and SSH folder permission troubleshooting.
- Ensure proxy and DNS troubleshooting steps are platform-agnostic, or provide separate sections for Windows and Linux/macOS.
- When referencing file paths or error messages, include both Windows and Linux/macOS formats.
- Review all troubleshooting steps for assumptions about Windows environments and add Linux/macOS guidance where missing.
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 managing the Azure Connected Machine agent, but Windows examples and tools (such as PowerShell scripts, Microsoft Update, Group Policy, and 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 tools and patterns (e.g., Control Panel, Registry Editor, Group Policy) are described in depth, while Linux instructions are more concise and rely on standard package managers. Overall, Linux parity is good for core agent operations, but automation and scripting examples favor Windows.
Recommendations
- Provide equivalent bash or shell scripts for Linux users, especially for tasks like cleaning up stale Arc-enabled server resources.
- Where possible, present Linux and Windows instructions side-by-side or in parallel, rather than Windows-first.
- Expand Linux sections to include troubleshooting tips and automation examples similar to those provided for Windows.
- Include references to Linux-native tools for managing updates and configuration (e.g., cron jobs, systemd services) where relevant.
- Clarify when a method is Windows-only and offer Linux alternatives if available.
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 and examples for both Windows and Linux, but there is a notable Windows-first bias in the ordering and phrasing. The 'Interactive browser login' is described as Windows-only and appears first, while Linux is mentioned secondarily. Windows certificate store options are detailed, but Linux equivalents (such as using PEM/PFX files) are not given equal prominence. The access token example references a Windows PowerShell cmdlet ('Get-AzAccessToken') without mentioning a Linux alternative. Overall, Linux users can complete the task, but Windows-specific tools and patterns are mentioned first or exclusively in some cases.
Recommendations
- Reorder authentication options so Linux-relevant methods (device code, Azure CLI) are not always secondary to Windows methods.
- Provide Linux-specific guidance or examples for certificate-based authentication, such as storing PEM/PFX files in typical Linux locations and using Linux file permissions.
- For access token acquisition, mention cross-platform methods (e.g., Azure CLI 'az account get-access-token') alongside PowerShell.
- Clarify that all examples and flags are cross-platform unless stated otherwise, and explicitly note any Windows-only features.
- Add explicit Linux/macOS example commands where possible, especially for authentication and certificate handling.
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 only a Windows/PowerShell-based recovery script and instructions, with no mention of Linux or cross-platform alternatives. All recovery steps assume the administrator is using a Windows machine, and the provided script is a PowerShell script. There are no Bash, Linux, or macOS instructions or scripts.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, ideally using Bash or cross-platform scripting languages.
- Explicitly state if the recovery process is only supported on Windows, and clarify any platform limitations.
- If possible, offer a cross-platform CLI or Azure CLI-based solution.
- Add a note in the prerequisites about supported operating systems for the recovery process.
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
missing_linux_example
windows_tools
Summary
The documentation page exhibits notable Windows bias, especially in the 'Auto Arc-enablement script' section, where only PowerShell and Windows Task Scheduler examples are provided. The script usage instructions assume a Windows environment, with no mention of Linux/macOS equivalents (e.g., Bash, cron). Additionally, Windows tools and patterns (PowerShell, Task Scheduler) are referenced exclusively or before Linux alternatives. While there is a brief note about sudo configuration for Linux, there are no Linux-specific automation examples or guidance for running the helper script on Linux/macOS.
Recommendations
- Provide Bash or shell script examples for Linux/macOS users, including instructions for running the helper script in a Linux environment.
- Include guidance for scheduling the script via cron on Linux, not just Windows Task Scheduler.
- Clarify whether the helper script is cross-platform or Windows-only; if cross-platform, add Linux/macOS usage instructions.
- Where PowerShell is used, offer equivalent Bash commands or note limitations for non-Windows users.
- Ensure automation approaches (e.g., Ansible, Azure CLI) are presented with parity for both Windows and Linux environments.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page for Azure Arc-enabled VMware vSphere is generally cross-platform, but there are several areas where Windows bias is evident. PowerShell is mentioned as a primary automation tool, and Windows examples or references (such as Windows Server management, Windows registry, and Windows-specific tabs in links) are often listed before Linux equivalents. Linux is supported in many features, but Linux-specific examples, tools, or guidance are less prominent or missing, especially in automation and configuration sections.
Recommendations
- Provide Linux-specific examples and guidance alongside Windows examples, especially for automation tasks (e.g., using Bash, shell scripts, or Linux-native tools).
- Mention Linux tools and patterns (such as systemd, cron, or Linux daemons) equally with Windows tools (like PowerShell and Windows registry).
- Ensure links and documentation tabs are balanced, offering both Windows and Linux instructions where applicable.
- Highlight cross-platform SDKs and CLI usage with explicit Linux/macOS compatibility notes.
- When referencing Azure Automation, include examples for Python and Bash runbooks, not just PowerShell.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exclusively provides PowerShell examples and references the onboarding script as a PowerShell (.ps1) script, with no mention of Bash, Linux shell, or cross-platform alternatives. All scripting and command-line instructions are Windows-centric, and there are no Linux/macOS equivalents or guidance for non-Windows users. This creates friction for Linux/macOS administrators attempting disaster recovery operations.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements for running the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS).
- Add examples and instructions for running the onboarding script on Linux/macOS, including installation prerequisites and command syntax.
- Mention any Azure CLI alternatives if available, or clarify if only PowerShell is supported.
- Ensure documentation is clear about platform support and limitations for disaster recovery operations.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page consistently uses PowerShell syntax for all CLI examples and references only PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor are Linux-friendly scripts or instructions provided. The use of PowerShell and .ps1 scripts is presented as the default, with no mention of cross-platform alternatives or guidance for Linux/macOS users.
Recommendations
- Provide CLI command examples in Bash syntax alongside PowerShell, or clarify that Azure CLI commands are cross-platform and can be run in Bash, Zsh, etc.
- Offer equivalent Bash scripts for bulk deployment and workflow deletion, or provide instructions for running the PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
- Explicitly state that Azure CLI commands are not limited to Windows and can be executed on any supported OS.
- Add notes or sections for Linux/macOS users, including any prerequisites or differences in file paths, script execution, or environment setup.
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, step-by-step instructions and script usage for Windows/PowerShell, including explicit PowerShell commands and environment-specific notes, while omitting equivalent instructions or scripts for Linux/macOS users. The deboarding script section is Windows/PowerShell-centric, with no mention of how to run the script on Linux/macOS, or whether a cross-platform version exists. Linux instructions are only provided for agent uninstallation, not for the main deboarding workflow.
Recommendations
- Provide instructions for running the deboarding script on Linux/macOS, or clarify if it is Windows-only.
- If a cross-platform (e.g., Bash or Python) version of the deboarding script exists, link to it and provide usage examples.
- If the script is PowerShell Core compatible, document how to run it on Linux/macOS using pwsh.
- Reorder sections or provide parallel instructions so Linux/macOS users are not left behind in critical workflows.
- Explicitly state OS requirements and alternatives for all scripts and commands.
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, with no Bash or Linux shell equivalents. Paths in JSON templates use Windows-style backslashes and drive letters. The onboarding scripts are referenced as PowerShell (.ps1) only, with no mention of Bash or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools/patterns (PowerShell, Windows file paths) are used throughout.
Recommendations
- Provide Bash or cross-platform shell examples alongside PowerShell for all CLI/script instructions.
- Use platform-neutral file path examples in JSON templates, or provide both Windows and Linux versions.
- Clarify whether the onboarding scripts (.ps1) are supported on Linux/macOS (via PowerShell Core), and provide guidance for Linux users.
- Mention any prerequisites or limitations for Linux/macOS users explicitly.
- Where possible, use Azure CLI commands in Bash syntax, or note that the commands work in both PowerShell and Bash.
- Add Linux/macOS-specific troubleshooting or log collection guidance if applicable.
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 example for installing kubectl uses 'winget', a Windows-only package manager, with no Linux/macOS alternative. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a native Bash/Linux tool. There are no Linux/macOS-specific instructions for these steps, and Windows-centric tools and paths (e.g., 'C:\path\to\archive.zip') are used throughout. While Azure CLI and kubectl are cross-platform, the documentation does not provide parity for Linux/macOS users in critical setup steps.
Recommendations
- Provide Linux/macOS alternatives for installing kubectl, such as 'curl' or 'apt/yum/brew' commands.
- Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' commands for Linux/macOS users.
- Use generic file paths (e.g., '/home/user/archive.zip') in Bash examples instead of Windows-style paths.
- Clearly indicate which commands are Windows-specific and provide equivalent commands for other platforms.
- Add a section or tab for Linux/macOS users where needed, especially for installation and file extraction steps.
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 page provides CLI examples using PowerShell syntax (backticks for line continuation, $variable notation), which is Windows-centric. Bash examples are present for az extension installation/update, but configuration examples are only shown in PowerShell. There is no mention of Linux/macOS shell equivalents or usage patterns, and PowerShell examples appear before any Bash alternatives.
Recommendations
- Provide equivalent Bash examples for all CLI commands, especially for configuration set/download tasks.
- Clarify that the Azure CLI works cross-platform and show both Windows (PowerShell) and Linux/macOS (Bash) command syntax where relevant.
- Use generic CLI syntax in documentation examples, or alternate between Bash and PowerShell to avoid implicit platform prioritization.
- Add notes or links for Linux/macOS users about line continuation and variable usage differences.
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides only a PowerShell script for migration, with no mention of Linux/macOS-compatible alternatives or instructions. The script is referenced as a .ps1 file, which is traditionally Windows-centric, and the usage example is exclusively PowerShell. There is no guidance for users on Linux or macOS platforms, nor any mention of Bash or cross-platform scripting.
Recommendations
- Provide instructions for running the migration script on Linux/macOS, such as using PowerShell Core (pwsh), if supported.
- Clarify whether the script is compatible with PowerShell Core on non-Windows platforms. If not, offer an alternative Bash or Python script for Linux/macOS users.
- Include explicit Linux/macOS usage examples and troubleshooting notes.
- Mention prerequisites for running PowerShell scripts on non-Windows systems (e.g., installing PowerShell Core).
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 PowerShell and Windows-style command usage. Most examples, including those for Azure CLI, Docker, and Kubernetes, are provided only in PowerShell syntax or with Windows-specific command patterns. Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service group' section, which does provide both Bash and PowerShell tabs. This creates friction for Linux/macOS users, especially in sections where only PowerShell commands are given and Windows-style variable usage is assumed.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
- Use cross-platform variable syntax (e.g., $VAR for PowerShell, $VAR for Bash) and clarify which shell is expected.
- Add notes or tabs indicating which commands are for Windows/PowerShell and which are for Bash/Linux.
- Ensure Docker and kubectl examples are shown in Bash syntax as well, since these tools are widely used on Linux/macOS.
- Review and update file encoding instructions to clarify cross-platform editors and encoding differences.
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 generally presents Windows download links and version numbers before Linux, and occasionally references Windows-specific tools (e.g., PowerShell, msiexec) and issues. However, Linux is well-represented with dedicated download links, release notes, and Linux-specific improvements. There are a few minor instances where Windows tools or patterns are mentioned without Linux equivalents, but Linux users are not blocked from completing tasks.
Recommendations
- Alternate the order of Windows and Linux download links or present them together to avoid a 'Windows-first' impression.
- Where Windows-specific installation instructions or troubleshooting steps are given (e.g., using msiexec or PowerShell), consider providing equivalent Linux instructions or explicitly stating when an issue is Windows-only.
- When referencing scripts or tools (e.g., ExtensionCleanup.ps1), clarify if a Linux equivalent exists or note that it is Windows-only.
- Continue to highlight Linux-specific improvements and fixes to reinforce parity.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for setting up workload orchestration, but the Bash tab is presented first, followed by PowerShell. There are no Windows-specific tools or patterns used; all commands rely on the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and there is no exclusive mention of Windows tools. The PowerShell examples are provided for parity, but the Bash examples are shown first, which is a minor bias in favor of Linux/macOS users rather than Windows.
Recommendations
- Ensure that both Bash and PowerShell examples are equally accessible, perhaps by defaulting to the user's OS or by providing clear guidance for both platforms.
- Consider adding a note clarifying that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
- If possible, provide a brief section explaining how to install Azure CLI on all supported platforms.
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 are presented first in each relevant section. All critical steps and commands are available for Linux users, and Linux parity is maintained throughout. The only minor bias is the ordering of Windows instructions before Linux.
Recommendations
- Present Windows and Linux instructions in parallel (side-by-side tabs or columns) or alternate which OS is shown first.
- Explicitly mention macOS compatibility if the Bash script works on macOS.
- Clarify that both PowerShell and Bash scripts are functionally equivalent and supported.
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 shown after Bash examples. There are no Windows-only tools or patterns; all commands use cross-platform Azure CLI and kubectl. No critical steps are Windows-only, and Linux parity is maintained. The only minor bias is that Bash (Linux/macOS) examples are always presented first, with PowerShell (Windows) second.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell are supported on Windows, Linux, and macOS, and that users can choose either based on their environment.
- Add a short note at the top clarifying that all commands are cross-platform and that PowerShell Core is available on Linux/macOS.
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 first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI, which is cross-platform. No critical steps are Windows-only, and Linux users can fully complete the tutorial.
Recommendations
- Maintain Bash-first ordering, as it is inclusive for Linux/macOS users.
- Continue providing both Bash and PowerShell examples for all steps.
- If possible, clarify that Azure CLI commands are cross-platform and can be run on any OS.
- Consider adding a brief note at the top indicating that both Linux/macOS and Windows environments are supported.
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 SKU), but consistently lists PowerShell examples after CLI and does not provide explicit Linux/macOS shell examples (e.g., Bash). The CLI examples are cross-platform, but the PowerShell examples are Windows-centric. There is no mention of Linux-specific tools or patterns, and no explicit guidance for Linux/macOS users. REST API references are included, but no curl or Bash examples are provided.
Recommendations
- Clarify that Azure CLI commands are cross-platform and work on Linux/macOS as well as Windows.
- Add Bash/curl examples for REST API operations to demonstrate Linux usage.
- Explicitly mention Linux/macOS compatibility where relevant, especially in sections referencing Azure CLI.
- Consider including Linux/macOS shell screenshots or terminal prompts to reinforce parity.
- If PowerShell is referenced, note that PowerShell Core is available cross-platform, but most Linux users will use Bash or Zsh.
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-compatible example is provided, SSMS is presented as the default/favored client. There is no mention of other cross-platform or Linux-native SQL clients (e.g., DBeaver, Azure Data Studio). The documentation does not provide PowerShell examples, but the Windows bias is evident in tool selection and ordering.
Recommendations
- Mention cross-platform SQL clients such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit examples for connecting from Linux/macOS using GUI tools (e.g., Azure Data Studio) in addition to sqlcmd.
- Reorder examples so that cross-platform tools are listed first or equally with SSMS.
- Clarify that SSMS is Windows-only and suggest alternatives for 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
Low 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 Profiler, SQL Server PowerShell) and mentions PowerShell scripting support as a manageability feature. However, it also lists cross-platform tools (Azure CLI, VS Code extension) and notes that Azure PowerShell is not supported. No explicit Linux/macOS examples or tools are provided, but the page does not prioritize Windows tools over Linux equivalents in critical workflows.
Recommendations
- Add explicit mention of Linux/macOS-compatible management tools (e.g., Azure Data Studio, sqlcmd, mssql-cli).
- Provide examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments.
- Clarify which tools are cross-platform and which are Windows-only.
- Include sample workflows for Linux users (e.g., using Azure CLI or VS Code extension on Linux).
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 connectivity requirements for Azure Arc Resource Bridge, including both Windows and Linux-related endpoints. However, there is a mild bias toward Windows: Windows NTP server ('time.windows.com') is mentioned explicitly, and several endpoints reference 'windows.net' and 'windows.com'. Windows-specific notes (e.g., Hyper-V default NTP) are present, but Linux equivalents (such as ntp.org or chrony) are not mentioned. The Azure CLI installation section references downloading the installer but does not clarify Linux/macOS installation differences. Windows-related endpoints are listed before Linux endpoints in some cases.
Recommendations
- Add Linux/macOS NTP server examples (e.g., ntp.org, pool.ntp.org) alongside 'time.windows.com', and clarify when Windows NTP is relevant.
- Clarify Azure CLI installation requirements for Linux/macOS, including relevant URLs or package managers (apt, yum, brew).
- Ensure Linux-specific endpoints (such as 'packages.microsoft.com') are given equal prominence and explanation.
- Where Windows-specific notes are given (e.g., Hyper-V default NTP), add Linux-specific notes (e.g., default NTP behavior on Ubuntu/CentOS).
- Consider listing Linux and Windows endpoints/examples together, rather than Windows-first.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is generally cross-platform, but there are subtle signs of Windows bias. Azure CLI is used throughout, which is available on all platforms, but installation instructions and links often mention Windows or Mac first, with Linux instructions appearing later or being less detailed. In the section on Azure kubelogin, Windows/Mac installation instructions are mentioned before Linux, and Linux instructions are less explicit. There are no PowerShell-specific commands, but Azure CLI is sometimes associated with Windows usage. No Linux-specific tools or patterns are mentioned, and some steps (such as SSH into master nodes, editing files, and using kubectl) are generic, but could benefit from more explicit Linux guidance. Overall, Linux users can complete all tasks, but may encounter minor friction.
Recommendations
- Ensure Linux installation instructions are as prominent and detailed as Windows/Mac instructions, especially for tools like Azure kubelogin.
- Provide explicit Linux command examples for common tasks (e.g., editing files with nano as well as vi, handling file permissions, SSH usage).
- When referencing Azure CLI, clarify that it is fully supported on Linux and provide links to Linux-specific installation guides.
- Avoid mentioning Windows/Mac first in tool installation sections; present all platforms equally or start with Linux.
- Add troubleshooting tips for Linux environments where relevant (e.g., file permissions, sudo usage).
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 with a link that defaults to Windows instructions and mentions Azure CLI x64/32-bit requirements, but does not specify Linux/macOS equivalents or provide parity in example links. No explicit Windows-only tools or PowerShell commands are used, and the CLI commands are cross-platform. However, the documentation could be improved by clarifying Linux/macOS support and providing relevant links.
Recommendations
- Add explicit mention that Azure CLI is cross-platform and supported on Windows, Linux, and macOS.
- Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link.
- Clarify that management machine requirements (such as Azure CLI x64) apply equally to Linux/macOS, or specify any OS-specific caveats.
- Include example CLI commands run on Linux/macOS, or note that the commands are identical across platforms.
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 comprehensive coverage for both Windows and Linux VM extensions, including separate tables for each OS and partner extensions. However, Windows extensions are listed first, which may subtly reinforce Windows as the default or primary platform. All deployment methods (CLI, PowerShell, portal, ARM templates) are mentioned equally, and Linux examples are not missing. No critical sections are Windows-only.
Recommendations
- Consider alternating the order of Windows and Linux sections, or explicitly state that both are equally supported.
- Add a brief introductory note clarifying that Azure Arc-enabled servers support both Windows and Linux extensions equally.
- Ensure that linked deployment guides (e.g., CLI, PowerShell) provide parity in Linux and Windows examples.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page presents Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell (a Windows-centric tool) is highlighted equally alongside Azure CLI. No explicit Linux shell examples (e.g., Bash) are shown, and PowerShell is mentioned before Linux-native tools. The page does state Run command supports both Windows and Linux, but the examples and tooling focus on Windows/PowerShell, creating mild friction for Linux/macOS users.
Recommendations
- Add explicit Bash or Linux shell examples alongside PowerShell examples.
- Clarify that Azure CLI is cross-platform and provide Linux-specific usage notes where relevant.
- Ensure Linux and Windows are mentioned equally in examples and tool recommendations.
- Consider linking to Linux-specific documentation or best practices for script execution.
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 covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations. However, there are minor signs of Windows bias: Windows log file paths and PowerShell/Windows command examples are presented before Linux equivalents, and Windows-specific tools (e.g., PowerShell version requirements, Windows environment variables) are referenced. Linux examples and paths are present, but Windows is often shown first or in more detail.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which OS is shown first to avoid implicit prioritization.
- Ensure Linux-specific troubleshooting steps and log file locations are as clearly described as Windows equivalents.
- Where Windows-specific tools (e.g., PowerShell) are mentioned, also reference Linux alternatives (e.g., Bash, shell commands) if applicable.
- Explicitly state parity between Windows and Linux where possible, and clarify any OS-specific limitations.
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 greater detail (including a screenshot). The Linux example is present and functional, but the ordering and emphasis slightly favor Windows. References to Azure portal, PowerShell, and Azure CLI for related tasks are balanced, but PowerShell is mentioned before Azure CLI.
Recommendations
- Present Windows and Linux examples in parallel or alternate their order to avoid implicit prioritization.
- Ensure screenshots and example outputs are provided for both Windows and Linux, not just Windows.
- Where possible, mention Azure CLI alongside PowerShell for cross-platform parity.
- Explicitly state that both Windows and Linux are fully supported and provide links to Linux-specific tutorials before or alongside Windows equivalents.
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is intentionally Windows-focused, as System Center Virtual Machine Manager (SCVMM) is a Windows-only product. The support matrix and requirements are centered around Windows Server environments, with references to Windows-specific tools (WinRM, Windows Management Framework, OpenSSH for Windows, SCVMM admin accounts, etc.). Linux is mentioned only in passing, mainly for running helper scripts or installing Arc agents in Linux VMs, but the primary examples and guidance are for Windows. Windows examples and tools are presented first and in detail, while Linux requirements are brief and secondary.
Recommendations
- Clarify early in the documentation that SCVMM is a Windows-only management platform and that the documentation is intentionally Windows-focused.
- Where Linux is supported (e.g., for running helper scripts or installing Arc agents in Linux VMs), provide more detailed Linux-specific guidance, troubleshooting tips, and performance recommendations.
- If Linux workstations are supported for deployment scripts, offer parity in examples and address known issues or limitations.
- Explicitly state any limitations or differences for Linux users to reduce confusion.
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. While most features are platform-neutral or mention both Windows and Linux, Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned explicitly, and Windows tools (like Azure PowerShell) are listed alongside cross-platform tools. However, Linux-specific examples are present (e.g., Arc agent installation on Linux via SSH), and cross-platform SDKs and tools are included. There is a minor bias in mentioning Windows features and tools before Linux equivalents in some sections.
Recommendations
- Ensure parity by explicitly mentioning Linux/macOS support where relevant (e.g., guest OS customization for Linux VMs).
- When listing tools (Azure CLI, PowerShell), clarify platform compatibility and provide Linux/macOS usage examples if available.
- Avoid listing Windows-specific tools or features before Linux equivalents unless there is a technical reason.
- Add links or references to Linux/macOS documentation where appropriate.
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 major steps, ensuring Linux and Windows users are supported. However, in most sections, PowerShell examples are presented after Bash, and some PowerShell-specific nuances (like base64 encoding) are explained. There is a slight Windows-first bias in the order of examples and some minor PowerShell-specific notes, but Linux parity is generally maintained.
Recommendations
- Ensure that Bash and PowerShell tabs are presented with equal prominence, possibly randomizing or alternating their order.
- Where platform-specific nuances exist (e.g., encoding differences), clarify both Linux and Windows approaches in the main text, not just in code comments.
- Consider adding a brief note at the top clarifying that all steps are supported on both Linux and Windows, and that Bash examples are for Linux/macOS while PowerShell is for Windows.
- Review PowerShell examples for unnecessary Windows-specific tools (e.g., 'armclient') and suggest cross-platform alternatives if possible.
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 first. There are no Windows-specific tools or patterns mentioned, and Linux parity is maintained throughout. No critical sections are Windows-only.
Recommendations
- Maintain the current structure, as Bash examples are shown first and Linux parity is upheld.
- Consider clarifying that both Bash and PowerShell examples are equivalent and supported on all platforms.
- If possible, add a note about cross-platform compatibility of Azure CLI and variable syntax differences.
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 every CLI operation, ensuring parity for Linux/macOS and Windows users. However, in most sections, PowerShell examples are presented after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No Linux/macOS examples are missing.
Recommendations
- Continue to provide both Bash and PowerShell examples for all CLI operations.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to reinforce parity.
- Add a brief note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples are intended 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 throughout, but consistently presents Bash examples before PowerShell. There are no Windows-specific tools or patterns, and all CLI commands are cross-platform (az CLI). No Linux examples are missing, and no Windows-only tools are referenced.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is shown first for consistency.
- Clarify that all az CLI commands work equally on Linux, macOS, and Windows.
- Add a brief note at the start indicating cross-platform compatibility to reassure Linux/macOS users.
Azure Arc
Create a Basic Solution with Common Configurations with Workload Orchestration
...ation/quickstart-solution-with-common-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently lists Bash examples before PowerShell. There are no Windows-only tools or patterns, and Linux/macOS users are fully supported via Bash and Azure CLI. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in sections to avoid perceived prioritization.
- Explicitly state that both Bash (Linux/macOS) and PowerShell (Windows) are supported and equivalent for these tasks.
- Add a short note clarifying that all CLI commands work on Linux, macOS, and Windows, and users can choose their preferred shell.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, with Bash (Linux/macOS) examples consistently shown before PowerShell (Windows) examples. There are no Windows-only tools or patterns, and all commands use the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows-specific tools are required.
Recommendations
- No action needed. The documentation already provides parity between Linux/macOS (Bash) and Windows (PowerShell) users.
- Continue to ensure that both Bash and PowerShell examples are kept up to date and equivalent.
- If possible, clarify in the prerequisites that Azure CLI and Helm are cross-platform tools, to reassure users on all OSes.
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 parity between Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell examples, which is a minor bias in favor of Linux/macOS users rather than Windows. No evidence of Windows bias such as PowerShell-only instructions, Windows tools, or missing Linux examples is found.
Recommendations
- No changes needed for Linux parity. Both Bash and PowerShell instructions are provided throughout.
- If desired, alternate the order of Bash and PowerShell tabs in some sections to balance presentation for both user groups.
- Ensure that any referenced scripts or files (e.g., .json, .yaml) are accessible and usable from both Linux and Windows environments.
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 alongside CLI. PowerShell is primarily associated with Windows, while CLI (Azure CLI) is cross-platform. However, there are no explicit examples or instructions favoring Windows tools, nor are Linux/macOS equivalents omitted. The mention of PowerShell is not exclusive or prioritized above CLI, but its inclusion without clarification may subtly suggest Windows bias.
Recommendations
- Clarify that Azure Copilot can generate scripts for both Azure CLI (cross-platform) and PowerShell (primarily Windows, but also available on Linux/macOS).
- Consider mentioning Bash or shell scripts as additional options for Linux/macOS users if supported.
- Provide examples or links that demonstrate script generation for both CLI and PowerShell, ensuring parity.
- Explicitly state that Azure CLI is cross-platform and PowerShell is available on multiple OSes, to avoid assumptions of Windows-only usage.
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 consistently lists Bash instructions first. There is no evidence of Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. However, the PowerShell examples are present throughout, which may be unnecessary for Linux/macOS users, and could be perceived as a mild Windows bias.
Recommendations
- Consider making Bash the default example and PowerShell an optional tab, as Bash is more universally supported across Linux/macOS and Windows (via WSL or Git Bash).
- Clarify that PowerShell examples are primarily for Windows users, and Bash for Linux/macOS.
- Ensure all CLI commands are tested and work identically on Linux/macOS.
- If possible, provide a brief note about cross-platform compatibility of Azure CLI and Helm.
- If Bash is the most common scenario, consider listing it first in the tab order.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatically retrieving subscription and tenant IDs. However, PowerShell is consistently mentioned first, and the examples reference PowerShell modules and cmdlets before CLI equivalents. There are no Windows-only tools or patterns, but the ordering and emphasis may subtly favor Windows users. All instructions for using the Azure portal are platform-neutral.
Recommendations
- Alternate the order in which PowerShell and CLI options are presented, or explicitly state that both are cross-platform.
- Clarify that Azure CLI works on Windows, Linux, and macOS, and provide links or notes to installation guides for non-Windows platforms.
- Consider including brief example commands for both PowerShell and CLI inline, rather than only linking out.
- Ensure parity in depth and visibility between PowerShell and CLI guidance.
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 to Azure Container Registry. However, the PowerShell example is given equal prominence and appears immediately after the CLI example, which may create friction for Linux/macOS users. The mention of Azure PowerShell as a primary tool, without explicit reference to Bash or Linux-native alternatives, suggests a mild Windows bias. All examples are cross-platform (Azure CLI and PowerShell both run on Linux/macOS), but the documentation does not highlight this fact or provide Bash shell-specific guidance.
Recommendations
- Clarify that Azure PowerShell and Azure CLI are both cross-platform, and explicitly mention their availability on Linux/macOS.
- Provide Bash shell or Linux-native command examples (e.g., using Docker CLI directly) where relevant.
- Consider listing Azure CLI examples first, as it is more commonly used on Linux/macOS.
- Add a note for Linux/macOS users about running Azure CLI and PowerShell in their environments.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
minor_windows_tools
Summary
The documentation provides authentication examples for Azure Container Registry using both Azure CLI and Azure PowerShell, with PowerShell examples and references appearing throughout. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, though it is available on Linux/macOS. The documentation sometimes presents PowerShell examples alongside or after CLI examples, and references to PowerShell cmdlets are frequent. There is a minor tendency to mention Windows-associated tools (PowerShell) and patterns, but Linux/macOS users can complete all tasks using Azure CLI and Docker. The documentation also acknowledges alternative container tools (like podman) and provides guidance for their use, which improves parity.
Recommendations
- Clearly indicate that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Where PowerShell examples are given, explicitly note that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for those platforms.
- Consider providing bash shell script examples for common authentication flows, especially for scenarios involving scripting or CI/CD on Linux.
- When listing authentication methods or examples, consistently present Azure CLI (cross-platform) before PowerShell (Windows-associated).
- Add a brief note in the 'Next steps' section about Linux/macOS parity, e.g., 'All Azure CLI examples work on Linux/macOS as well as Windows.'
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 both Azure CLI and Azure PowerShell examples for all import scenarios. However, PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI throughout the page may create a perception of Windows bias. Additionally, in some sections, PowerShell examples or references appear before or alongside Azure CLI, which can subtly reinforce Windows-first patterns. There are no explicit Windows-only tools or missing Linux/macOS examples, since Azure CLI is fully cross-platform and all commands are shown for both tools.
Recommendations
- Make it clear that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
- Consider showing Azure CLI examples first in each section, or grouping CLI and PowerShell examples so CLI is the default.
- Add a brief note at the top clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell examples are optional for users on Windows.
- If possible, provide Bash shell scripting examples for advanced scenarios, or link to Linux/macOS-specific guidance.
- Ensure that references to installing Azure CLI and PowerShell include links for Linux/macOS installation.
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 up Helm client' section, the environment variable is set using the Windows-style 'set' command without a Linux/macOS equivalent. Additionally, the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal. There are no explicit Linux/macOS-specific examples or notes, and the only environment variable example is Windows-first.
Recommendations
- For environment variable setup, provide both Windows ('set') and Linux/macOS ('export') examples, e.g., 'export ACR_NAME=<container-registry-name>' for Bash.
- When listing options for creating AKS clusters, mention cross-platform tools (Azure CLI) first, then platform-specific tools (PowerShell), and clarify their OS compatibility.
- Add a note clarifying that all CLI commands (Helm, Azure CLI) work on Linux/macOS, and provide explicit Bash examples where relevant.
- Review all command snippets to ensure they are OS-neutral or provide alternatives for both Windows and Linux/macOS users.