222
Pages Scanned
48
Pages Flagged
222
Changed Pages
21.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-02-12 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 222
Files Completed: 222
Problematic Pages
48 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 oriented toward Windows environments, with all onboarding scripts and examples provided exclusively in PowerShell (.ps1) format. Prerequisites reference Windows-specific tools like 'winget', and there are no Bash, shell, or Linux/macOS equivalents or instructions. The instructions assume the user is running a PowerShell terminal, and there is no mention of how to perform these tasks on Linux or macOS, nor are there alternative script formats or guidance for non-Windows users.
Recommendations
- Provide Bash or shell script equivalents for onboarding tasks, or document how to run the PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
- Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
- Explicitly state whether the scripts are supported on Linux/macOS, and if not, provide guidance or workarounds for non-Windows users.
- Include example commands and terminal output for Linux/macOS environments.
- Clarify any Windows-only requirements up front if the scripts are not intended for cross-platform use.
Create Pull Request
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 both Windows and Linux instructions for uninstalling the Arc agent, but the deboarding script section is heavily Windows/PowerShell-centric. Only Windows/PowerShell instructions are given for running the deboarding script, with no mention of how to run it on Linux or macOS. Additionally, Windows instructions are presented first and in greater detail.
Recommendations
- Provide explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any OS-specific considerations.
- Clarify whether the deboarding script is cross-platform or Windows-only. If it is cross-platform, include sample commands for Linux/macOS users.
- If the script is Windows-only, state this clearly and offer alternative manual steps for Linux/macOS users.
- Consider presenting Windows and Linux instructions in parallel sections or tables for parity and clarity.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command examples for connecting to the SQL Server pod using PowerShell syntax (e.g., `kubectl exec ...` with PowerShell prompt and formatting), and does not offer equivalent Linux/macOS shell examples. The use of PowerShell formatting and prompts may create friction for Linux/macOS users, even though the underlying commands are cross-platform. Additionally, PowerShell examples are presented first and exclusively, suggesting a Windows-first bias.
Recommendations
- Provide Linux/macOS shell (bash) examples alongside PowerShell examples for commands such as `kubectl exec` and SQL queries.
- Use generic shell prompts (e.g., `$`) instead of PowerShell-specific prompts (e.g., `PS C:\>`), or clarify that the commands work in any shell.
- Explicitly state that the commands are cross-platform and can be run from any OS with kubectl and sqlcmd installed.
- Add notes or sections for Linux/macOS users, including any OS-specific considerations for decoding secrets or connecting to the pod.
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) and PowerShell-style commands for Linux node configuration. There are no native Linux shell (bash/ssh) examples for critical sysctl configuration steps, which may confuse or hinder Linux users.
Recommendations
- Provide native Linux command-line examples (e.g., using ssh, bash, or direct sysctl commands) for configuring Linux nodes.
- Clarify when Windows tools (like Invoke-AksEdgeNodeCommand) are required, and offer Linux alternatives or explain their availability on Linux.
- Ensure all steps can be completed using standard Linux administration tools, not just Windows/PowerShell-based tools.
- Show both Windows and Linux command examples side-by-side where cross-platform support is intended.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides several examples and instructions that assume a Windows environment, such as backup paths using Windows-style (C:\Backupfiles\...), and references to Windows tools like SQL Server Management Studio (SSMS) and Notepad. There are no explicit Linux/macOS equivalents or examples for backup file creation, file paths, or alternative tools, which may create friction for users on non-Windows platforms.
Recommendations
- Include Linux/macOS examples for backup file creation, such as using '/home/user/backup/test.bak' or '/tmp/test.bak' as file paths.
- Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and provide instructions for using these tools on Linux/macOS.
- When referencing text editors (e.g., Notepad), suggest platform-agnostic options like VS Code, nano, or TextEdit.
- Clarify that the backup and restore SQL commands work identically on Linux-based SQL Server installations, and provide sample commands with Linux file paths.
- Add notes or sections highlighting any platform-specific considerations 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
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_authentication
Summary
The documentation references Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and features (Windows Authentication, PowerShell scripting support) without providing Linux/macOS alternatives or clarifying cross-platform support. PowerShell scripting is highlighted as a manageability feature, but Azure PowerShell is marked as 'No' in the tools table, which may confuse Linux users. Windows Authentication is listed as supported, but Microsoft Entra authentication (cross-platform) is not. There are no explicit Linux/macOS examples or guidance.
Recommendations
- Clarify which tools are cross-platform (e.g., Azure CLI, VS Code extension) and which are Windows-only.
- Add Linux/macOS alternatives for manageability and scripting (e.g., Bash, sqlcmd, Azure CLI).
- Explicitly state platform support for authentication methods (e.g., Entra ID, Windows Authentication).
- Provide guidance or links for Linux/macOS users to manage SQL Managed Instance enabled by Azure Arc.
- Mention limitations or workarounds for Linux/macOS users where Windows-only tools/features are referenced.
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 is presented as the primary (and only) deployment method, which may create friction for Linux/macOS users who prefer CLI or Bash. Windows-style file paths are used in examples, and PowerShell is referenced before any mention of CLI alternatives (which are only linked in 'Related content').
Recommendations
- Add Azure CLI deployment command examples alongside PowerShell for template deployment (e.g., az deployment group create ...).
- Include Bash or shell script snippets for Linux/macOS users where relevant.
- Use platform-neutral file path examples (e.g., ./AzureMonitorAgent.json) or show both Windows and Linux path styles.
- Explicitly mention that both PowerShell and CLI can be used, and link to CLI instructions earlier in the article.
- Consider a section or callout for Linux/macOS users explaining how to install and use Azure PowerShell or CLI.
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 and instructs users to run it in PowerShell, with no mention of Bash, Linux shell alternatives, or cross-platform scripting. This creates friction for Linux/macOS users, as PowerShell is not natively available and may require additional setup.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users.
- Document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core).
- Clarify whether the script is cross-platform and, if so, provide explicit instructions for Linux/macOS environments.
- Mention any prerequisites for running PowerShell on non-Windows systems.
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 issues, which is a cross-platform feature. However, there are several instances of Windows bias: Windows/PowerShell examples are given for network troubleshooting (e.g., Invoke-WebRequest), Windows paths are referenced in error messages, and Windows tools (RDP, PowerShell) are mentioned for remote access. Linux equivalents (such as curl, SSH, or Linux CLI commands) are not provided, and in some cases, Windows-specific troubleshooting steps are listed before or instead of Linux alternatives.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., use curl or wget for HTTP troubleshooting, SSH for remote access).
- Include Linux/macOS-specific troubleshooting steps where relevant (e.g., file permissions, SSH folder access).
- Mention Linux/macOS tools and patterns alongside Windows tools, not after or instead of them.
- Ensure error messages and paths reference both Windows and Linux conventions where applicable.
- Add explicit guidance for Linux users in sections about Azure CLI installation, proxy configuration, and network troubleshooting.
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 downloadable script exclusively for Windows, using PowerShell. There are no Linux/macOS examples, nor is there mention of equivalent recovery steps or scripts for non-Windows platforms. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternative is offered.
Recommendations
- Provide equivalent recovery instructions for Linux/macOS, including a Bash or Python script if possible.
- Clarify whether the recovery process can be performed from non-Windows machines, or explicitly state if Windows is required.
- If the script is Windows-only, explain why and offer guidance for Linux users (e.g., using a Windows VM or container).
- Add a section titled 'Recover Arc resource bridge from a Linux/macOS machine' if feasible.
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 exhibits notable Windows bias. The primary automation script is PowerShell-based, with instructions to use Windows Task Scheduler for cron jobs, and references to Windows tools and patterns (e.g., Group Policy, Configuration Manager). Linux-specific guidance is minimal and secondary, with only a brief mention of Ansible playbooks and a sudo configuration note for Linux VMs. Windows examples and tools are presented first and in greater detail, while Linux equivalents are not equally covered.
Recommendations
- Provide a Bash or Python-based automation script for Linux/macOS users, with equivalent functionality to the PowerShell script.
- Include examples for scheduling automation on Linux (e.g., using cron) alongside Windows Task Scheduler instructions.
- Expand documentation for Linux tools and patterns (e.g., using Ansible, shell scripts) for Arc agent installation at scale.
- Ensure parity in example commands and step-by-step instructions for both Windows and Linux environments.
- Mention cross-platform Azure CLI usage explicitly and provide sample commands for both OS types.
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 Azure CLI commands, and references PowerShell scripts (.ps1) for automation, without providing equivalent Bash or shell script examples. There is no mention of Linux/macOS-specific instructions or examples, and the PowerShell syntax is used even though Azure CLI is cross-platform. This creates friction for Linux/macOS users, who may not be familiar with PowerShell or .ps1 scripts.
Recommendations
- Provide Azure CLI command examples in Bash syntax (e.g., using $ variables and shell quoting) alongside PowerShell examples.
- Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or note how to run the PowerShell scripts on Linux/macOS (e.g., via pwsh).
- Clarify that Azure CLI commands can be run on any platform, and avoid using PowerShell-specific syntax unless the task is Windows-only.
- Add notes or tabs for Linux/macOS users, highlighting any platform-specific considerations.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page provides only PowerShell examples and instructions for running and editing the onboarding script, with no mention of Bash, shell, or cross-platform alternatives. The script usage and editing steps are presented in a Windows-centric manner, assuming the user is on Windows or using PowerShell. There is no guidance for Linux/macOS users, and PowerShell is shown as the default/only option.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
- Explicitly state platform requirements for the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS).
- Add instructions for running the onboarding script on Linux/macOS, including any prerequisites or installation steps.
- Mention any limitations or required adaptations for non-Windows environments.
- If the onboarding script is Windows-only, clearly indicate this limitation at the start of the article.
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 a PowerShell script (RGCleanScript.ps1) and only shows PowerShell commands for resource clean-up. There are no Bash, shell, or cross-platform script examples, nor any mention of how Linux or macOS users can perform the same clean-up tasks. The script and instructions are Windows-centric, which may hinder non-Windows users.
Recommendations
- Provide a Bash or shell script equivalent (e.g., RGCleanScript.sh) for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core (pwsh) on non-Windows platforms.
- Include explicit instructions or examples for running the script on Linux/macOS (e.g., using pwsh, or adapting the script for Bash).
- Mention any prerequisites for non-Windows users, such as installing PowerShell Core, and provide installation links.
- If the script is truly Windows-only, clearly state this limitation and suggest alternative manual clean-up steps for Linux/macOS users.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page provides extensive PowerShell examples and scripts for diagnostics and log collection, with no equivalent Bash or Linux shell examples. Paths in JSON templates and scripts use Windows-style (e.g., C:\, E:\), and PowerShell is the only scripting language shown for orchestration tasks. There is no mention of Linux/macOS alternatives, and Windows tools/patterns (PowerShell, Windows file paths) are referenced exclusively and before any Linux equivalents.
Recommendations
- Provide Bash or Linux shell equivalents for all PowerShell commands and scripts, especially for az CLI usage.
- Use cross-platform file path examples in JSON templates (e.g., /home/user/config.yaml) or clarify how to adapt for Linux/macOS.
- Explicitly state if PowerShell scripts are required, or offer alternatives using Bash or Python for Linux/macOS users.
- Add notes or sections for Linux/macOS users, highlighting any differences or requirements.
- Ensure that az CLI commands are shown in a cross-platform way (without PowerShell-specific syntax like backticks or variables).
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses Windows-only tooling (winget), with no Linux/macOS alternative. The file extraction example under the Bash tab incorrectly uses PowerShell's Expand-Archive, which is not available on Linux/macOS Bash shells. Throughout, Windows-centric tools and patterns are presented first or exclusively, and Linux/macOS users are left to infer their own equivalents.
Recommendations
- Provide Linux/macOS alternatives for installing kubectl (e.g., using curl or package managers like apt, brew, or snap).
- Correct the Bash example for extracting ZIP files to use native Bash/Linux commands (e.g., unzip, tar) instead of PowerShell's Expand-Archive.
- Ensure that examples under Bash tabs use commands available on Linux/macOS, not Windows-only tools.
- Where Windows-specific instructions are given, add equivalent steps for Linux/macOS users.
- Consider listing Linux/macOS examples before or alongside Windows/PowerShell examples to avoid implicit prioritization.
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 release notes for Workload Orchestration in Azure Arc generally use cross-platform Azure CLI commands and reference features available in both portal and CLI. However, in the May 2025 release, CLI examples are provided exclusively in PowerShell syntax (with backticks for line continuation), which is Windows-centric. Bash examples are used elsewhere, but PowerShell appears first and is the only example for some CLI tasks. There are no Linux-specific tools or commands mentioned, but the exclusive use of PowerShell in some sections may create friction for Linux/macOS users.
Recommendations
- Provide Bash equivalents for all CLI examples, especially where only PowerShell syntax is shown.
- Ensure CLI instructions are platform-neutral and avoid using Windows-specific line continuation (backticks) in examples.
- Add a note clarifying that Azure CLI is cross-platform and can be used on Linux/macOS, with examples for those environments.
- Where possible, show Bash and PowerShell examples side-by-side for parity.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most command examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). Linux/Bash equivalents are missing for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, where both Bash and PowerShell tabs are provided. This creates friction for Linux/macOS users, who must translate PowerShell-specific commands and scripting patterns to their environment.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and kubectl commands.
- Avoid using PowerShell-specific scripting constructs (e.g., variable assignment, ConvertTo-Json, Out-File) without offering a Bash alternative.
- Ensure cross-platform parity by showing Bash examples first or side-by-side with PowerShell.
- Clarify when a command is Windows-only or cross-platform.
- Review and update sections where only PowerShell is used for tasks that are not Windows-specific.
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
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is consistently featured alongside CLI, and sometimes appears first in tables and sections. There is a notable emphasis on PowerShell usage, and the CLI examples use Windows-style environment variable syntax in some places. Linux/macOS equivalents are present but not always highlighted or explained with parity. The documentation also refers to the Docker daemon and CLI, which are cross-platform, but does not explicitly mention Linux/macOS shell usage or differences. The alternative container tool section does mention 'podman', which is more common on Linux, but this is a minor mention.
Recommendations
- Ensure that Azure CLI examples are always presented first, as it is cross-platform, and clarify that PowerShell is optional and primarily for Windows users.
- Add explicit Linux/macOS shell command examples (e.g., using export instead of set for environment variables, or using bash syntax for variables).
- Where PowerShell is mentioned, add a note that it is available cross-platform, but is most commonly used on Windows.
- In the table of authentication methods, list Azure CLI before PowerShell to reflect cross-platform parity.
- Add a brief section or note clarifying that all CLI commands are supported on Linux/macOS, and provide links to platform-specific installation guides for Docker, Azure CLI, and PowerShell.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows instructions for base64 encoding files, but the Linux example is presented first and is more concise. The Windows section uses certutil and findstr, which are Windows-specific tools, and requires manual steps to remove headers. There is no PowerShell bias, and all other examples (openssl, Azure CLI, kubectl) are cross-platform. The bias is minor and limited to the base64 encoding step.
Recommendations
- Add PowerShell examples for base64 encoding on Windows, as PowerShell is available by default and more modern than certutil.
- Clarify that certutil is available only on certain Windows editions and provide alternatives for Windows users (e.g., PowerShell).
- Consider presenting Linux and Windows instructions side-by-side for parity.
- Explicitly mention that Azure CLI and kubectl commands are cross-platform and provide links to installation instructions for Windows, Linux, and macOS.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, listing both in separate, equally detailed tables. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and Linux-specific tools/examples are not missing. No critical Linux functionality is omitted.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to emphasize equal support.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Add a brief introductory note highlighting Linux support to reinforce parity.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell, which is a minor form of ordering bias ('windows_first' or 'linux_first'). No evidence of Windows-only tools, missing Linux examples, or exclusive Windows patterns is found.
Recommendations
- Maintain the current parity of examples for both Bash and PowerShell.
- Consider alternating the order of Bash and PowerShell tabs in different sections, or clarify that Bash is shown first for consistency, not preference.
- Explicitly state that both Linux/macOS and Windows environments are supported, if not already clear.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are always shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider clarifying that Bash examples are suitable for Linux/macOS and Windows users using WSL or Git Bash, while PowerShell is native to Windows.
- If possible, add a note at the top explaining which environments each example is intended for.
- Ensure that any future updates continue to provide equivalent examples for both platforms.
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 page 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 listed first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The documentation does not provide parity in client tool recommendations or examples for Linux/macOS users.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide example connection instructions for at least one Linux-native GUI client.
- Consider listing sqlcmd (which is cross-platform) before SSMS, or equally, to avoid Windows-first bias.
- Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides installation instructions for client tools across platforms, but there is a noticeable Windows bias. Windows installation links are listed first in several places, and PowerShell/cmd.exe usage is specifically called out for Windows users. The explanation about 'curl' in PowerShell is Windows-centric, and Linux installation instructions for 'curl' are less explicit. While Linux and macOS are mentioned, Windows tools and patterns are prioritized or described in more detail.
Recommendations
- List Linux and macOS installation instructions before or alongside Windows, not after.
- Provide explicit Linux installation instructions for 'curl' (e.g., 'sudo apt install curl') rather than just 'install curl package'.
- Clarify PowerShell-specific notes as Windows-only, and provide equivalent Linux/macOS guidance where relevant.
- Ensure examples and explanations are balanced across platforms, not favoring Windows terminology or tools.
- Add macOS installation instructions for 'curl' if missing.
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 and tools (e.g., 'time.windows.com', 'sts.windows.net', 'servicebus.windows.net'), and Windows NTP is mentioned as the default in the context of Hyper-V. Windows-related endpoints are listed alongside general endpoints, sometimes before Linux equivalents. However, Linux-specific endpoints (e.g., 'packages.microsoft.com', 'linuxgeneva-microsoft.azurecr.io') are also included, and SSH is referenced as a connectivity requirement, which is cross-platform. No PowerShell-only examples or Windows-only commands are present.
Recommendations
- Clarify when Windows-specific endpoints (e.g., 'time.windows.com') are only required for Windows deployments, and provide Linux alternatives (e.g., 'ntp.ubuntu.com') if applicable.
- Where Windows tools or services are mentioned (such as NTP), explicitly note Linux equivalents or provide guidance for Linux users.
- Ensure that Linux-related endpoints and requirements are given equal prominence and explanation as Windows ones.
- Consider grouping Windows-specific and Linux-specific requirements separately for clarity.
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 consistently refers to Azure CLI installation using links and examples that default to Windows (e.g., 'Azure CLI x64' links to the Windows install page). There are no explicit Linux/macOS installation instructions or examples, and the management machine requirements do not clarify cross-platform compatibility. However, the overall content is generic and does not rely on Windows-only tools or patterns.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside Windows.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide cross-platform examples where relevant.
- Ensure CLI commands and file paths are shown in a cross-platform manner (e.g., using generic paths or showing both Windows and Linux/macOS examples).
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
powershell_heavy
windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in most features and fixes. However, Windows download links and version numbers are consistently listed first, and Windows-specific installer instructions (e.g., PowerShell, msiexec, GUI) are emphasized. Known issues and troubleshooting focus on Windows installer behaviors, with no equivalent Linux guidance. Windows tools and patterns (e.g., PowerShell, msiexec, GUI) are mentioned without Linux alternatives (such as shell commands or package managers).
Recommendations
- Alternate the order of Windows and Linux download links and version numbers, or present them side-by-side to avoid implicit prioritization.
- Provide Linux-specific troubleshooting guidance and known issues, such as common installer problems or commands for resolving issues.
- When referencing Windows tools (e.g., PowerShell, msiexec), also mention Linux equivalents (e.g., bash, rpm, dpkg, systemctl) where relevant.
- Ensure that any instructions or recommendations for installation, upgrades, or configuration are mirrored for Linux users, including command-line examples.
- Add a section summarizing Linux-specific improvements, known issues, and workarounds, similar to the Windows installer guidance.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides parity for both Windows and Linux platforms, with clear sections and examples for each. However, there is a mild Windows bias: Windows instructions and tools (such as PowerShell, Group Policy, Microsoft Update, and Control Panel) are often described in greater detail and appear first in several sections. The cleanup script for removing stale resources is only provided in PowerShell, with no Linux shell equivalent. References to Windows-specific tools (e.g., Msiexec, Registry Editor) are prominent, while Linux instructions are more concise and rely on standard package managers.
Recommendations
- Provide Linux shell (bash) equivalents for resource cleanup scripts, or at least mention how Linux users can achieve similar results using Azure CLI.
- Ensure Linux examples are given equal prominence and detail as Windows examples, especially for advanced tasks (e.g., scripting, automation).
- Where possible, avoid listing Windows instructions first unless there is a clear reason (e.g., user base statistics). Consider alternating or grouping by OS.
- Expand Linux sections to include troubleshooting tips and automation methods similar to those provided for Windows.
- Mention cross-platform tools (Azure CLI) as the primary method where applicable, and clarify PowerShell is optional for Windows users.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation gives Windows-specific authentication options (interactive browser login and certificate store usage) before Linux equivalents, and references Windows tools (PowerShell's Get-AzAccessToken) without mentioning Linux alternatives. However, Linux authentication methods are described, and most examples are cross-platform.
Recommendations
- Reorder authentication options so Linux-default methods (device code, Azure CLI) are presented before Windows-only options.
- For access token acquisition, mention Linux/macOS alternatives (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
- Clarify which authentication options are cross-platform and which are Windows-only, ideally in a table or with clear labels.
- Add explicit Linux/macOS example commands where Windows-specific instructions are given (e.g., certificate store usage).
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 with managed identity on Azure Arc-enabled servers. However, Windows/PowerShell instructions and examples are presented first, and PowerShell is referenced more prominently in related content. There is minor Windows-first ordering and emphasis, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Ensure related content links reference Azure CLI and Bash examples equally alongside PowerShell.
- Explicitly state that both Windows and Linux are supported at the start of technical sections.
- Where possible, provide cross-platform scripting guidance (e.g., Python, .NET Core) in addition to OS-specific shell examples.
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
powershell_heavy
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but Windows examples and references are often presented first. PowerShell/Windows-specific command syntax is shown before Linux equivalents, and Windows file paths and tools (e.g., `%ProgramData%`, PowerShell syntax) are mentioned more prominently. Linux examples are present but sometimes secondary.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Provide Linux-specific troubleshooting steps and file paths with equal prominence to Windows.
- Where possible, use cross-platform command syntax or clarify differences for each OS.
- Ensure Linux log file locations and commands are referenced alongside Windows equivalents in all sections.
- Add explicit notes when remediation steps differ between Windows and Linux (e.g., service management, file permissions).
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there is a slight Windows bias: Windows tools (PowerShell) are mentioned before Linux equivalents, and some links and examples default to Windows tabs or Windows-specific scenarios. PowerShell is referenced as a primary automation tool, while Bash or Linux shell examples are not explicitly mentioned. The 'next steps' section and some linked guides also default to Windows-focused instructions.
Recommendations
- Explicitly mention Bash or Linux shell options alongside PowerShell in automation sections.
- Ensure linked guides and quickstarts provide Linux/macOS instructions or examples where applicable.
- Where possible, present Windows and Linux options equally (e.g., 'PowerShell or Bash' instead of just 'PowerShell').
- Review links and tabs to ensure Linux parity (e.g., not defaulting to Windows tabs in linked documentation).
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, and in some sections, the PowerShell tab appears before Bash. There are no Windows-specific tools or patterns used, and all commands are based on the Azure CLI, which is cross-platform. No Linux-specific examples (e.g., zsh, fish shell) are missing, but the documentation does not explicitly mention macOS compatibility. The only minor bias is the ordering of PowerShell and Bash examples, with PowerShell sometimes appearing first.
Recommendations
- Ensure Bash examples are always shown before PowerShell to reinforce Linux/macOS parity.
- Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding a note about Azure CLI compatibility across platforms.
- Optionally, provide a generic shell example (sh/zsh/fish) or clarify that Bash commands work on macOS as well.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell examples are given equal prominence and detail as Bash, and the tab order presents Bash first, then PowerShell. There is no evidence of Windows-only tools or patterns, and all commands use the cross-platform Azure CLI. However, the inclusion of PowerShell examples may suggest a slight Windows bias, as Linux/macOS users are less likely to use PowerShell. No Linux-specific tools or shell scripting patterns are highlighted.
Recommendations
- Clarify that PowerShell examples are for users who prefer PowerShell, and Bash is recommended for Linux/macOS.
- Consider adding a note that Azure CLI commands work identically on Linux, macOS, and Windows.
- If possible, provide a third tab for macOS/Linux terminal usage, or explicitly mention that Bash examples are suitable for both Linux and macOS.
- Ensure that any file path or environment variable usage is compatible with Linux/macOS conventions.
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 every command, ensuring parity for Linux and Windows users. However, PowerShell examples are consistently shown immediately after Bash, which may indicate a minor 'windows_first' bias in ordering, but no critical bias is present.
Recommendations
- Consider alternating the order of Bash and PowerShell examples or clarifying that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note at the start explaining which shell is recommended for each OS.
- Ensure that all CLI commands are tested and work identically in both Bash and PowerShell environments.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias toward Linux/macOS users. There are no Windows-only tools or patterns, and all commands use cross-platform tools (Azure CLI, Docker, kubectl). No critical steps are Windows-only, and Linux users can complete all tasks without friction.
Recommendations
- Maintain the current structure, as both Bash and PowerShell examples are provided for every step.
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid perceived bias.
- Explicitly state that all commands are cross-platform and supported on both Linux/macOS and Windows.
- Ensure that any future additions continue to provide parity between Bash and PowerShell examples.
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 every CLI operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all commands are cross-platform (Azure CLI). There are no missing Linux examples or Windows-only instructions.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add a brief note clarifying that Azure CLI commands work on all platforms and that Bash examples are suitable for Linux/macOS users.
- Ensure any future additions (e.g., troubleshooting, file editing) include Linux/macOS equivalents if Windows-specific tools are mentioned.
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 for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell, which is a minor 'windows_first' bias in ordering. No Windows-only tools, patterns, or missing Linux examples are present. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that Bash is shown first for consistency, not platform preference.
- Ensure that any future additions maintain parity and do not introduce Windows-only tools or instructions unless the feature is Windows-specific.
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 programmatic access, but PowerShell is consistently mentioned first and receives slightly more prominence. There are no explicit Linux/macOS examples or screenshots, and the use of PowerShell as the primary example may subtly favor Windows users, though Azure CLI is cross-platform and included. No Windows-only tools or patterns are used, and Linux users can complete all tasks described.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions to avoid Windows-first bias.
- Explicitly note that Azure CLI works on Linux/macOS and provide links or brief instructions for installation/use on those platforms.
- Include a screenshot or example showing Azure CLI usage in a terminal (not just PowerShell).
- Clarify that copying IDs in the portal works identically across platforms.
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
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell is given equal prominence throughout. In some sections, PowerShell examples are shown immediately after Bash, and the PowerShell syntax is used for variable assignment and command chaining. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, the presence of PowerShell examples may suggest a slight Windows bias, as Linux/macOS users are unlikely to use PowerShell.
Recommendations
- Consider making Bash the default or primary example, with PowerShell as an optional tab for Windows users.
- Clarify that Bash examples are recommended for Linux/macOS users, and PowerShell for Windows users.
- Ensure that Bash examples are shown first in all code blocks.
- Add a note explaining that all commands are cross-platform and can be run in Bash on Windows (WSL) or in macOS/Linux terminals.
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for Azure dashboards using three methods: Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is included and described in detail, which may be seen as Windows-centric. Additionally, PowerShell examples are given after CLI, but no explicit Linux/macOS shell examples (such as Bash or shell scripting) are provided. The documentation mentions Azure PowerShell alongside Azure CLI and REST API in the overview, but does not provide Linux-specific guidance or examples. The order of examples (CLI before PowerShell) reduces bias, but the presence of PowerShell-specific instructions without Linux/macOS shell equivalents is a minor bias.
Recommendations
- Clarify that Azure CLI commands work equally well on Windows, Linux, and macOS.
- Add explicit Bash or shell scripting examples for deploying dashboards, or note that Azure CLI commands can be run in Bash or other shells on Linux/macOS.
- Consider mentioning cross-platform compatibility of Azure PowerShell (it runs on Linux/macOS via .NET Core), or link to installation instructions for non-Windows platforms.
- Ensure that all instructions are clear for users on Linux/macOS, not just Windows.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is not strictly Windows-only, PowerShell is more commonly associated with Windows environments, and its mention before Bash or Linux shell scripting may create a subtle Windows bias. No explicit Linux/macOS examples or tools are referenced, and the documentation does not clarify parity between PowerShell and Bash or other Linux shells.
Recommendations
- Explicitly mention Bash or Linux shell scripting alongside PowerShell and CLI in the capabilities section.
- Provide examples or clarify that Azure Copilot can generate scripts for Bash, Linux shells, and macOS environments, not just PowerShell.
- Consider listing CLI and Bash before PowerShell to avoid subtle Windows-first ordering.
- Add a note about cross-platform support for generated code snippets and scripts.
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 tasks (such as changing registry SKU and showing registry usage), but consistently lists PowerShell examples alongside or after CLI, and references PowerShell cmdlets in the text. There are no explicit Linux/macOS-specific instructions or examples (e.g., Bash, shell scripting, or CLI-only workflows), and the CLI examples do not clarify their cross-platform compatibility. The documentation does not mention Linux tools or patterns, nor does it highlight CLI as the preferred cross-platform method. This creates minor friction for Linux/macOS users, though all tasks can be completed using Azure CLI, which is cross-platform.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Provide Bash/shell scripting examples or clarify CLI usage in Linux/macOS environments.
- List Azure CLI examples before PowerShell examples, or group them under clear cross-platform and Windows sections.
- Add a note indicating that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
- Consider including links to Azure CLI installation and usage guides for Linux/macOS.
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, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is not exclusive to Windows but is most commonly associated with Windows environments. The documentation does not reference Windows-only tools, but the order and parity of examples may subtly favor Windows users.
Recommendations
- Add explicit Bash or Linux shell examples for image import, especially since Azure CLI is cross-platform and commonly used on Linux/macOS.
- Clarify that Azure PowerShell is available cross-platform, but highlight Azure CLI as the primary tool for Linux/macOS users.
- Consider showing Azure CLI examples first and labeling PowerShell as an alternative for Windows users.
- Mention that Azure Cloud Shell supports both CLI and PowerShell, but Bash is the default for Linux/macOS users.
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 is largely cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: (1) The environment variable setup uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'), and (2) the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal. No explicit Linux/macOS examples are given for environment variable setup, and no Linux-specific tools or shell patterns are shown.
Recommendations
- Add Linux/macOS equivalents for environment variable setup, e.g., 'export ACR_NAME=<container-registry-name>' alongside 'set'.
- When listing options for Kubernetes cluster creation, consider mentioning Azure CLI and Portal first, or clarify PowerShell is Windows-specific.
- Review all shell command examples to ensure both Windows and Linux/macOS users are supported, especially for environment variables and file operations.
- Explicitly state that all commands are cross-platform unless otherwise noted, and link to platform-specific installation guides for Helm and Azure CLI.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Azure CLI and Azure PowerShell throughout, but consistently presents Azure PowerShell examples alongside Azure CLI, and sometimes references PowerShell-specific patterns (e.g., cmdlets, module installation). However, both tools are cross-platform and supported on Linux/macOS as well as Windows. No Windows-only tools or Windows-specific instructions are given. There are no missing Linux/macOS examples, but Azure PowerShell is often associated with Windows in user perception, and its inclusion may create a minor bias.
Recommendations
- Clarify that both Azure CLI and Azure PowerShell are fully supported on Linux and macOS, not just Windows.
- Consider adding a brief note at the start of the article indicating that all examples work on Linux/macOS as well as Windows.
- If possible, include a Bash shell example for Azure CLI to reinforce Linux parity.
- Explicitly mention that Azure PowerShell can be used on Linux/macOS, and link to installation instructions for those platforms.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is presented first. All other command-line instructions use Azure CLI or kubectl, which are cross-platform and not Windows-specific. No Windows-only tools or patterns are used, and Linux/macOS users are fully supported.
Recommendations
- Continue to provide both Bash and PowerShell examples for steps involving scripting.
- Consider explicitly stating that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
- If possible, alternate the order of Bash and PowerShell tabs across similar docs to avoid consistent 'windows_first' or 'linux_first' bias.