229
Pages Scanned
50
Pages Flagged
229
Changed Pages
21.8%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:09
Scan Information
Started At: 2026-02-17 00:00:09
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 229
Files Completed: 229
Problematic Pages
50 issues found
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation is heavily biased toward Windows/PowerShell environments. All onboarding scripts and usage instructions are provided exclusively as PowerShell (.ps1) scripts, with all example commands shown in PowerShell syntax. Prerequisites reference Windows-specific tools (winget), and there are no instructions or examples for running the onboarding process on Linux or macOS (e.g., via Bash, shell scripts, or cross-platform alternatives). This creates friction for non-Windows users and may block onboarding for those unable to run PowerShell scripts.
Recommendations
- Provide equivalent onboarding scripts in Bash or other POSIX-compliant shells, or document how to run the PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
- Include Linux/macOS-specific installation instructions for prerequisites (e.g., using apt, yum, or Homebrew instead of winget).
- Add example commands for Linux/macOS terminals, or clarify if the scripts are compatible with PowerShell Core on non-Windows platforms.
- Explicitly state platform requirements and, if Windows is required, provide a rationale or workaround for Linux/macOS users.
Create Pull Request
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides recovery instructions exclusively for Windows machines, including a PowerShell script and Windows-centric steps. There are no examples or guidance for Linux/macOS users, nor is there mention of equivalent tools or scripts for non-Windows platforms.
Recommendations
- Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts.
- Clarify whether the recovery process is supported or unsupported on Linux/macOS, and if not, explain why.
- If the script is Windows-only, consider offering a cross-platform version or documenting manual steps for Linux users.
- Mention any prerequisites or limitations for Linux/macOS environments explicitly.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is focused on preparing Linux with AKS Edge Essentials, but it uses Windows-centric tools and patterns. Specifically, it relies on the PowerShell cmdlet Invoke-AksEdgeNodeCommand for Linux node configuration, without providing native Linux shell alternatives. Notepad is mentioned as a text editor, which is Windows-specific, and there are no Linux-first or Linux-native examples for editing configuration files or running sysctl commands directly on Linux.
Recommendations
- Provide native Linux shell commands for sysctl configuration, such as using 'sysctl' and editing '/etc/sysctl.conf' with 'nano', 'vim', or 'vi'.
- Replace or supplement Notepad references with Linux text editors (e.g., nano, vim, vi) when editing configuration files.
- Offer direct bash commands for steps currently using PowerShell cmdlets, so Linux users can perform tasks without needing Windows tools.
- Ensure all examples and instructions are accessible from a Linux terminal, not just via Windows/PowerShell.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for connecting to the SQL Server pod using sqlcmd, but these examples are shown exclusively as PowerShell commands. There is no mention of Linux/macOS shell equivalents (e.g., Bash), nor are Linux-specific tools or patterns referenced. The use of PowerShell syntax (e.g., command lines prefixed with 'powershell') and lack of Bash examples creates friction for Linux/macOS users, even though the underlying tools (kubectl, sqlcmd) are cross-platform.
Recommendations
- Provide Bash shell examples alongside PowerShell for commands involving kubectl and sqlcmd.
- Clarify that sqlcmd and kubectl commands can be run from any OS terminal, not just Windows/PowerShell.
- Remove PowerShell-specific notation unless the command is truly Windows-only.
- Add notes or examples for Linux/macOS users, especially for decoding base64 secrets (e.g., using 'base64 -d').
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 are Windows-centric, such as using Windows file paths (e.g., 'C:\Backupfiles\test.bak') and referencing tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives. There are no explicit Linux/macOS examples for backup file creation or copying files, and Windows paths are shown first and exclusively in critical steps.
Recommendations
- Include Linux/macOS examples for backing up databases, such as using '/home/user/Backupfiles/test.bak' or '/tmp/test.bak' as file paths.
- Mention cross-platform tools like Azure Data Studio alongside SSMS, and clarify that Visual Studio Code and Azure Storage Explorer are available on Linux/macOS.
- Provide kubectl cp examples using Linux/macOS source file paths.
- Explicitly state that the backup and restore steps can be performed on Linux/macOS, and provide any relevant command-line alternatives.
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_first
Summary
The documentation lists several Windows-centric tools (e.g., SSMS, SQL Server PowerShell, SQL Server Profiler) and highlights PowerShell scripting support as a manageability feature. While it does mention cross-platform tools like Azure CLI and Visual Studio Code, Windows tools are often listed first and in greater detail. There are no explicit Linux/macOS command-line examples or references to Linux-native management patterns, which may create friction for non-Windows users.
Recommendations
- Add explicit examples or references for managing SQL Managed Instance enabled by Azure Arc from Linux/macOS environments, such as using Azure CLI, sqlcmd, or cross-platform scripting.
- List cross-platform tools (Azure CLI, VS Code) before Windows-only tools in tables and sections.
- Clarify which tools are cross-platform and which are Windows-only, possibly with an OS compatibility column.
- Provide links to documentation for Linux/macOS equivalents where available (e.g., sqlcmd, Azure Data Studio).
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 for `azcmagent connect` shows some Windows bias, particularly in the authentication options section. The interactive browser login is described as 'Windows only' and presented first, while Linux is mentioned later for device code login. Windows certificate store options are detailed, but Linux equivalents (such as storing certificates in files) are not described with equal prominence. The access token section references PowerShell (`Get-AzAccessToken`) as a way to obtain tokens, without mentioning Linux/macOS alternatives. However, most examples and instructions are generic and applicable to both platforms.
Recommendations
- Present authentication options in a platform-neutral order, or explicitly note Linux/macOS options alongside Windows.
- For certificate-based authentication, provide equivalent Linux instructions (e.g., storing certificates in PEM/PFX files, using OpenSSL).
- For access token acquisition, mention cross-platform methods (e.g., Azure CLI `az account get-access-token`) in addition to PowerShell.
- Add explicit Linux/macOS examples where Windows-specific tools or flows are referenced.
- Clarify that device code login is default for Linux, and provide Linux-specific command examples if needed.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides deployment instructions exclusively using Azure PowerShell, with no Azure CLI or Bash examples. All deployment commands are shown in PowerShell syntax, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. Additionally, PowerShell commands are presented before any mention of alternatives, and file paths in examples use Windows-style paths (e.g., 'D:\Azure\Templates\...'), which may confuse Linux users.
Recommendations
- Add equivalent Azure CLI deployment commands alongside PowerShell examples, especially for template deployments.
- Include Bash shell examples for Linux/macOS users, or clarify that Azure CLI can be used cross-platform.
- Show file path examples using both Windows and Linux conventions (e.g., 'D:\Azure\Templates\...' and '/home/user/Azure/Templates/...').
- Explicitly state that Azure PowerShell is available cross-platform, but Azure CLI is also supported and may be preferred on Linux/macOS.
- Consider presenting Azure CLI examples first or side-by-side with PowerShell to avoid implicit Windows-first bias.
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 is generally cross-platform, but several sections show Windows bias. PowerShell is used for troubleshooting HTTP2 errors, and Windows-specific terminology (e.g., 'Remote PowerShell', 'RDP', 'time.windows.com') appears without Linux equivalents. CLI examples are mostly generic, but some troubleshooting steps (e.g., DNS resolution, proxy testing) use Windows tools or show Windows-first approaches. Linux-specific commands and troubleshooting are only occasionally mentioned (e.g., glibc error, ldd --version), and Linux CLI examples are rare.
Recommendations
- For troubleshooting steps, provide both Windows and Linux/macOS command examples (e.g., nslookup, ping, Resolve-DnsName, curl, dig).
- When referencing PowerShell, also mention Bash or shell equivalents for Linux/macOS users.
- Include Linux/macOS proxy configuration guidance alongside Windows instructions.
- Where Windows-specific endpoints (e.g., time.windows.com) are mentioned, clarify Linux alternatives (e.g., ntp.ubuntu.com, chrony).
- Add explicit notes or sections for Linux/macOS users where CLI commands or troubleshooting steps differ.
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 for disaster recovery operations of the Azure Arc resource bridge VM is heavily focused on PowerShell scripts and examples, with no mention of Linux/macOS equivalents or cross-platform alternatives. All script examples and instructions assume the use of PowerShell, which is traditionally Windows-centric, and there are no Bash or shell script alternatives provided. The onboarding script is referenced as a .ps1 file, reinforcing the Windows-first approach.
Recommendations
- Provide Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
- Explicitly state platform requirements for the onboarding script, including whether PowerShell Core (pwsh) is supported on Linux/macOS.
- If the onboarding script is Windows-only, offer guidance for Linux/macOS users (e.g., running PowerShell Core, using a Windows VM, or alternative methods).
- Mention any prerequisites or limitations for non-Windows environments early in the documentation.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs, but there is notable Windows bias. The auto-enablement script is PowerShell-based, with instructions and examples focused on Windows terminals and Windows Task Scheduler for automation. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents. While Linux is acknowledged (e.g., sudo configuration), there are no Linux shell script examples or guidance for running the helper script on Linux/macOS. Out-of-band methods mention Ansible playbooks, but Windows-centric approaches (Group Policy, Configuration Manager) are listed first.
Recommendations
- Provide equivalent Bash shell script examples for Linux/macOS users, especially for the auto-enablement script.
- Include instructions for scheduling the script as a cron job on Linux, not just Windows Task Scheduler.
- Clarify whether the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS) and provide guidance if so.
- List Linux-friendly automation methods (e.g., Ansible, Bash) before or alongside Windows methods in out-of-band approaches.
- Add explicit Linux/macOS CLI usage examples where possible.
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
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides detailed, step-by-step instructions for running the deboarding script on Windows using PowerShell, but does not mention or provide instructions for running the script on Linux or macOS. The Windows instructions are presented first and exclusively, creating friction for non-Windows users. Additionally, there is no mention of whether the deboarding script can be run on Linux/macOS, or if an alternative is available.
Recommendations
- Clarify whether the deboarding script can be run on Linux or macOS. If so, provide equivalent instructions for those platforms, including shell commands and any prerequisites.
- If the script is Windows/PowerShell-only, explicitly state this limitation and, if possible, provide a cross-platform alternative (e.g., a Bash script or Azure CLI commands).
- Present instructions for all supported platforms in parallel or in separate sections, rather than only for Windows.
- Add a note at the start of the deboarding script section indicating platform support and any requirements.
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 provides command-line examples and scripts using PowerShell syntax (e.g., .ps1 scripts, PowerShell-style CLI invocation), and references only PowerShell scripts for automation. There are no Bash or Linux shell equivalents, nor is there guidance for Linux/macOS users on running Azure CLI commands or automating bulk operations. This creates friction for non-Windows users, especially since Azure CLI is cross-platform.
Recommendations
- Provide Azure CLI command examples using Bash syntax, including how to run commands in Linux/macOS terminals.
- Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or explain how to use the provided .ps1 scripts on Linux/macOS (e.g., via PowerShell Core).
- Clarify that Azure CLI commands can be run on any OS, and avoid using PowerShell-specific syntax (e.g., parameter quoting, .ps1 script references) as the default.
- Add notes or tabs for Linux/macOS users, showing how to perform the same tasks in their environments.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The Bash section for extracting ZIP files uses the Windows-native Expand-Archive command and Windows file paths, which are not available on Linux/macOS. The kubectl installation example uses winget, a Windows-only tool, with no Linux/macOS alternative provided. Throughout, file path examples and instructions default to Windows conventions, and Linux/macOS equivalents are missing or not mentioned. While Azure CLI and kubectl are cross-platform, the initial setup steps and examples favor Windows users.
Recommendations
- Provide Linux/macOS alternatives for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/dir').
- Offer kubectl installation instructions for Linux/macOS (e.g., using 'curl' or package managers like 'apt', 'brew').
- Use generic or platform-neutral file paths in examples, or show both Windows and Linux/macOS path formats.
- Ensure that all critical steps have Linux/macOS equivalents, especially for tool installation and file operations.
- Consider adding a platform-specific tab for Linux/macOS where needed, similar to the Bash/PowerShell split.
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 PowerShell command examples for resource cleanup. There are no Bash, shell, or cross-platform script alternatives, nor any mention of how Linux/macOS users can perform the same task. The script appears to require PowerShell, which is traditionally Windows-centric, though PowerShell Core is available cross-platform. However, the documentation does not clarify compatibility or provide Linux/macOS usage guidance.
Recommendations
- Explicitly state whether RGCleanScript.ps1 is compatible with PowerShell Core on Linux/macOS.
- Provide Bash or shell script alternatives, or document how Linux/macOS users can run the PowerShell script (e.g., using PowerShell Core).
- Include Linux/macOS-specific instructions and examples, such as running PowerShell scripts from a terminal or using Azure CLI for similar cleanup tasks.
- Mention any prerequisites or limitations for non-Windows platforms.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, and file paths in JSON templates use Windows-style (backslash) paths. There are no Bash or Linux/macOS shell equivalents for any of the automation or CLI steps. The onboarding scripts are referenced as PowerShell (.ps1) scripts, with no mention of Bash or cross-platform alternatives. Windows file patterns and tools are mentioned first and exclusively, creating friction for Linux/macOS users.
Recommendations
- Provide Bash/zsh shell equivalents for all PowerShell CLI/script examples, especially for az CLI commands.
- Use cross-platform file path examples (e.g., forward slashes, or note both Windows and Linux path formats).
- Clarify whether the onboarding scripts (.ps1) are required to be run on Windows, or provide a Bash version if possible.
- Add explicit notes about Linux/macOS support and any limitations, including how Linux users can perform equivalent tasks.
- Where possible, use az CLI syntax that works identically across platforms, and avoid PowerShell-specific parameter formatting.
- Include sample Linux file paths in JSON templates, or note how to adapt them for Linux/macOS environments.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for migration, with no mention of a Bash or cross-platform alternative. The instructions exclusively reference running the script in PowerShell, which is typically a Windows tool, and do not address Linux or macOS users or provide equivalent guidance for those platforms.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Explicitly state platform compatibility for the migration script and offer installation instructions for PowerShell on non-Windows systems if applicable.
- Include Linux/macOS-specific usage examples and troubleshooting tips.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal or greater prominence than Linux-native workflows. PowerShell is not natively available on most Linux/macOS systems, and the documentation does not provide explicit Bash or shell script examples for common Linux/macOS scenarios. In several places, PowerShell is presented as a primary workflow, and Linux-native tools or shell scripting are not covered in depth. The use of 'docker' and 'az' CLI is cross-platform, but the lack of explicit Linux/macOS shell examples and the prominence of PowerShell may create friction for non-Windows users.
Recommendations
- Add explicit Bash/shell script examples for authentication workflows, especially for service principal and admin account scenarios.
- Clarify that PowerShell is not required on Linux/macOS and that all Azure CLI examples work natively in Bash or other shells.
- Reorder examples to show Azure CLI (cross-platform) first, and PowerShell second, or clearly label PowerShell as optional/alternative.
- Where PowerShell cmdlets are shown, provide equivalent Bash/CLI commands for parity.
- Add a short section or note for Linux/macOS users, confirming that all workflows are supported and linking to any OS-specific guidance if needed.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most command-line examples use PowerShell syntax and variables, with only a few Bash alternatives provided (and only in the 'service groups' section). Many steps assume PowerShell scripting, and some commands (e.g., Base64 encoding, file manipulation) are only shown in PowerShell. Linux/macOS users may struggle to adapt instructions, especially for scripting and file handling tasks.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell commands, especially for az CLI, kubectl, docker, and file manipulation steps.
- Show Bash examples first or side-by-side with PowerShell to avoid implicit Windows prioritization.
- Clarify which steps are OS-agnostic and which require adaptation, and offer guidance for Linux/macOS users.
- For scripting tasks (e.g., Base64 encoding, JSON file creation), include Linux shell commands (e.g., base64, jq, echo) and editor instructions.
- Review variable usage and syntax to ensure compatibility across platforms.
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 an access token using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed scripting and output illustration. The Linux/Bash example follows and is also complete, but the ordering and emphasis slightly favor Windows/PowerShell. The prerequisites and group membership requirements are clearly separated for Windows and Linux, and links to both Windows and Linux Key Vault access guides are provided. The 'Related content' section lists PowerShell before Azure CLI, but includes both.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
- Ensure equal detail and explanation for both Windows and Linux examples, including output illustrations.
- In related content, list Azure CLI and PowerShell together or alternate their order.
- Consider explicitly stating that both Windows and Linux are equally supported throughout the article.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first and in greater detail. The retry command section also lists Windows before Linux. There is a minor bias in ordering and depth, but Linux users are fully supported.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid implicit prioritization.
- Ensure notes and troubleshooting guidance are equally detailed for both platforms.
- Clarify that both PowerShell and Bash scripts are available and functionally equivalent.
- Consider adding macOS-specific notes if relevant, as macOS users often use Bash.
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 for every CLI step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, indicating a minor 'windows_first' bias in ordering. No Windows-specific tools, patterns, or exclusive Windows instructions are present. All commands use cross-platform Azure CLI and kubectl tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in sections, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a short note at the top clarifying that Bash examples are for Linux/macOS terminals and PowerShell for Windows, to help new users.
- Ensure future updates continue to provide both Bash and PowerShell examples for all CLI steps.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands and variable definitions, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias. There are no Windows-specific tools, patterns, or exclusive references; all instructions are cross-platform and rely on the Azure CLI, which is available on both Windows and Linux/macOS. No critical steps are Windows-only, and Linux users can complete all tasks as described.
Recommendations
- Maintain the current structure, as Linux parity is strong.
- Consider alternating the order of Bash and PowerShell examples in future updates to avoid any perceived bias.
- Explicitly mention that Azure CLI commands work on both Linux/macOS and Windows to reassure users.
- If possible, add a brief note at the start clarifying that both Bash and PowerShell are supported and users should follow the examples matching their OS.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Arc Workload Orchestration release notes is generally cross-platform, focusing on Azure CLI and portal usage. However, in the May 2025 release section, CLI examples are provided exclusively in PowerShell syntax (using backticks for line continuation and variables with $), which is Windows-centric. Bash syntax is used elsewhere, but PowerShell is shown first and exclusively in some cases, creating minor friction for Linux/macOS users.
Recommendations
- Provide CLI examples in both Bash and PowerShell syntax, or default to Bash for cross-platform parity.
- Clarify that Azure CLI commands work on all platforms and provide OS-agnostic examples.
- Avoid using Windows-specific variable syntax ($var) and line continuation (backticks) in CLI examples unless the feature is Windows-only.
- If showing PowerShell, always accompany with Bash equivalents.
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 presented as the default/favored client. There is no mention of Linux-native GUI tools (such as Azure Data Studio or DBeaver) or macOS options, and the documentation does not provide parity in client tool recommendations or usage examples beyond sqlcmd.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio (which runs on Windows, Linux, and macOS) and provide examples for connecting with them.
- List sqlcmd and other Linux/macOS-compatible tools before or alongside SSMS to avoid Windows-first bias.
- Include explicit guidance for macOS users, and highlight any differences or prerequisites for Linux/macOS environments.
- Consider providing screenshots or step-by-step instructions for at least one cross-platform GUI tool.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low 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 example (using certutil) is more detailed and includes additional steps (removing headers) not explained for Linux. The Linux example is brief and shown first, but the Windows section is longer and more prominent. No PowerShell-specific commands are used, but Windows tools are mentioned. All other steps use cross-platform tools (openssl, Azure CLI, kubectl), and the overall workflow is not Windows-specific.
Recommendations
- Expand the Linux base64 example to include instructions for removing headers, matching the detail given for Windows.
- Clarify that the base64 command on Linux does not add certificate headers, or provide a command to remove them if needed.
- Balance the explanation so both Linux and Windows users receive equally detailed guidance.
- Consider mentioning macOS explicitly, as its base64 utility behaves like Linux.
- If possible, provide a table summarizing base64 encoding/decoding commands for Linux, macOS, and Windows.
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
windows_tools
Summary
The documentation is largely cross-platform, focusing on Azure CLI and kubectl commands, which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: Windows and macOS are mentioned before Linux in the kubelogin installation section, and Azure CLI is referenced as the primary tool for role assignments and cluster management, which is often associated with Windows/PowerShell usage. Additionally, the instructions for editing files use 'vi', which is common on Linux/macOS but not on Windows, yet no explicit Windows editor alternatives are provided. The documentation does not provide PowerShell-specific examples, but Azure CLI is often used in Windows environments.
Recommendations
- In the kubelogin installation section, mention Linux first or equally alongside Windows and macOS, and provide explicit package manager installation instructions for Linux distributions (e.g., apt, yum, brew).
- Clarify that Azure CLI and kubectl commands are cross-platform and provide links or notes for Windows-specific usage (e.g., PowerShell syntax, file path conventions).
- When referencing editing files (e.g., 'sudo vi'), suggest alternatives for Windows users, such as Notepad++ or PowerShell editors.
- Ensure all examples and instructions are equally applicable to Linux, macOS, and Windows, and explicitly state cross-platform compatibility where relevant.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There is a specific note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance. The curl installation section provides a Windows link but only mentions 'install curl package' for Linux, lacking a direct link or command. There is also a PowerShell-specific note about curl aliasing, but no similar shell-specific notes for Linux/macOS.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first bias.
- Provide direct installation links or example commands for Linux (e.g., 'sudo apt install curl') and macOS (e.g., 'brew install curl') for parity.
- Add shell-specific notes for Linux/macOS (e.g., bash/zsh) if PowerShell-specific notes are included.
- Ensure all tool installation instructions are equally detailed for all platforms.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation includes references to Windows-specific services (e.g., 'time.windows.com' for NTP, 'sts.windows.net', 'servicebus.windows.net') and Windows terminology (e.g., 'Management machine & Appliance VM IPs (if Hyper-V default is Windows NTP)'). Windows NTP is mentioned explicitly, and Windows-related endpoints appear before Linux equivalents. However, Linux endpoints and tools are also referenced (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com', SSH port 22), and the requirements are generally platform-neutral. There are no PowerShell-only examples or Windows-only instructions, but Windows endpoints and tools are mentioned first or more prominently.
Recommendations
- Clarify that NTP can use Linux NTP servers as well, and provide examples or endpoint references for Linux NTP (e.g., 'pool.ntp.org').
- Where Windows-specific endpoints are mentioned (e.g., 'sts.windows.net', 'servicebus.windows.net'), clarify their relevance for Linux deployments or provide Linux alternatives if applicable.
- Ensure Linux tools and endpoints are given equal prominence and listed alongside Windows equivalents.
- Add explicit notes or examples for Linux management machines (e.g., how to configure outbound connectivity on Linux).
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 links that default to Windows, and mentions Azure CLI x64/32-bit requirements without clarifying Linux/macOS support or providing equivalent installation guidance for those platforms. The management machine requirements and CLI extension instructions are generic, but the Azure CLI install link is Windows-specific and appears first. No Linux/macOS-specific examples or guidance are provided, though the content is not strictly Windows-only.
Recommendations
- Add explicit guidance for installing Azure CLI on Linux and macOS, including links to the official installation instructions for those platforms.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any platform-specific requirements (e.g., x64 support, SSH client availability).
- Include example commands or notes for Linux/macOS users where relevant, such as file paths or CLI usage.
- Ensure that CLI extension installation instructions are platform-neutral.
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 parity in most features and fixes. However, Windows download links and version numbers are consistently listed before Linux, and Windows-specific installation instructions (e.g., using PowerShell, msiexec, GUI) are detailed, while Linux installation methods are referenced only via a link. Windows tools and patterns (PowerShell, msiexec, GUI) are mentioned explicitly, whereas Linux equivalents (shell commands, package managers) are not described in detail. Some improvements and bug fixes reference Windows tools/scripts (e.g., ExtensionCleanup.ps1, MSI signature verification), with no Linux script equivalents mentioned.
Recommendations
- Provide explicit Linux installation instructions or examples (e.g., shell commands, package manager usage) alongside Windows instructions.
- When referencing scripts or tools (e.g., ExtensionCleanup.ps1), mention or link to Linux equivalents if available.
- Consider alternating the order of Windows and Linux download links and version numbers, or presenting them side-by-side to avoid implicit prioritization.
- Include Linux-specific troubleshooting guidance where relevant, similar to the detailed Windows installer instructions.
- Clarify when a feature or fix is Windows-only or Linux-only, and ensure Linux users are not left guessing about applicability.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Windows and Linux information for Azure Arc Connected Machine agent network requirements. However, Windows-related resources and tools (e.g., Windows Admin Center, Windows installation package, Windows-specific cipher suite configuration) are often mentioned first or in more detail. Windows Admin Center and Windows-specific endpoints are highlighted, and troubleshooting links focus on Windows TLS configuration. Linux equivalents are present but sometimes secondary.
Recommendations
- Where possible, present Linux and Windows examples/resources side-by-side or in parallel, rather than listing Windows first.
- Add links to Linux-specific troubleshooting or configuration guides for TLS and networking, similar to the Windows TLS configuration issues link.
- Clarify when Windows-specific tools (e.g., Windows Admin Center) are optional or only relevant for Windows users.
- Expand Linux guidance (e.g., OpenSSL configuration, common Linux firewall/proxy patterns) to match Windows detail.
- Ensure tables and lists consistently mention Linux and Windows resources with equal prominence.
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
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there is a mild Windows bias: Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Registry Editor, Msiexec) are often presented first or in greater detail, and a PowerShell cleanup script is provided without a Linux equivalent. Linux instructions are present and clear, but Windows-specific tooling and automation are more prominent.
Recommendations
- Provide equivalent automation scripts for Linux (e.g., Bash scripts for stale resource cleanup using Azure CLI).
- Ensure Linux examples are presented with equal prominence and detail as Windows examples, possibly alternating order or grouping by task rather than OS.
- Where Windows tools (e.g., Group Policy, Configuration Manager, WSUS) are mentioned, consider referencing Linux equivalents (e.g., cron jobs, package managers, systemd timers) for update automation.
- Add more context or links for Linux users to automate agent lifecycle tasks at scale.
- Consider including a summary table at the top listing parity for Windows and Linux management approaches.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides clear parity between Windows and Linux VM extensions, listing both in separate, equally detailed tables. However, Windows extensions are presented first, which is a minor instance of 'windows_first' bias. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and Linux-specific extensions and partner tools are well covered. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or explicitly stating that both are equally supported.
- Add a brief introductory note clarifying that all listed deployment methods and extensions are available for both Windows and Linux, to reinforce parity.
- If possible, provide a combined table or summary highlighting cross-platform extensions to emphasize equal support.
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 is mentioned alongside Azure CLI as the primary example. The custom metadata (devx-track-azurepowershell) and ordering of PowerShell before REST API may indicate a Windows-first bias. However, the page explicitly states support for both Windows and Linux, and notes a Linux-specific limitation. No Linux-specific examples or tools are provided, and PowerShell is highlighted despite its Windows origins, though it is now cross-platform.
Recommendations
- Add explicit Linux shell (bash) examples alongside PowerShell and Azure CLI.
- Clarify that PowerShell examples are cross-platform, or provide Linux-specific scripting guidance.
- Ensure that Linux limitations and nuances are documented as thoroughly as Windows ones.
- Consider including a table or section comparing Windows and Linux behaviors for Run command.
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 covers troubleshooting for both Windows and Linux, but Windows examples and references are often presented first. Windows-specific tools (PowerShell, Windows environment variables, Windows log paths) are mentioned before their Linux equivalents. PowerShell syntax is used for Windows command examples, while Linux examples use bash. Some error codes reference Windows-specific concepts (e.g., PowerShell version requirements, Windows log file paths) before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Where possible, present Linux and Windows examples side-by-side for parity.
- Ensure Linux log file paths and troubleshooting steps are as prominent as Windows ones.
- Add explicit notes clarifying when a remediation step is OS-specific.
- Review error code tables for Windows-centric language and add Linux equivalents where missing.
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
missing_linux_example
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are subtle signs of Windows bias. PowerShell is mentioned as a primary automation tool, and some links and examples reference Windows-specific tabs or features before Linux equivalents. Linux tools and examples are present but often secondary or implied rather than explicit. No critical sections are Windows-only, but Linux/macOS users may experience minor friction.
Recommendations
- When listing automation tools, mention Bash/CLI and Linux SDKs equally alongside PowerShell.
- Ensure linked guides and quickstarts include both Windows and Linux instructions/examples, not just Windows tabs.
- Where runbooks or automation are discussed, provide explicit Linux examples (e.g., Bash scripts, Linux runbook tabs) in addition to PowerShell.
- Review linked pages (e.g., 'connect VMware vCenter to Azure Arc using the helper script') to ensure Linux parity in instructions.
- When referencing Azure portal tabs or guides, avoid defaulting to Windows unless the feature is Windows-only.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or exclusive Windows tools mentioned.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a brief note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples are suitable for Linux/macOS users.
- Ensure screenshots and portal instructions are platform-neutral or clarify any OS-specific nuances if relevant.
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/macOS parity. However, PowerShell examples are sometimes shown immediately after Bash, and some minor details (like base64 encoding) are explained separately for Windows and Linux. There is no evidence of Windows-only tools or missing Linux examples, but the structure sometimes places Windows/PowerShell examples before or equally with Bash, which may create minor friction for Linux users.
Recommendations
- Ensure Bash examples are always shown first in each code tab, as Bash is the default shell for most Linux/macOS users.
- Where possible, clarify any OS-specific steps (such as file encoding or base64 commands) in a single, unified note rather than splitting by shell.
- Review PowerShell-specific explanations to ensure they are not prioritized over Bash/Linux explanations.
- Consider adding explicit notes about cross-platform compatibility, especially for commands that may behave differently on Windows vs. Linux.
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 lists Bash examples before PowerShell. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. The only detectable bias is the minor ordering of Bash examples before PowerShell.
Recommendations
- Continue providing both Bash and PowerShell examples for all commands.
- Consider clarifying that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Optionally alternate the order of examples or explicitly state that both platforms are supported equally.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first. There is no evidence of missing Linux examples or exclusive use of Windows tools; all commands use the cross-platform Azure CLI. However, the presence of PowerShell examples and the explicit PowerShell tab may indicate a mild Windows bias, especially since PowerShell is less common on Linux/macOS environments compared to Bash.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for Linux/macOS users.
- Clarify in the introduction that all commands use Azure CLI, which is cross-platform.
- Optionally, add a note that PowerShell examples are provided for users who prefer PowerShell, but Bash is recommended for Linux/macOS.
- Ensure that any references to file paths, environment variables, or scripting conventions are valid for both Linux and Windows shells.
- If possible, provide a short section or FAQ for macOS users to highlight any platform-specific considerations.
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 CLI step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently shown before PowerShell, which is a minor 'windows_first' bias in ordering. No Windows-specific tools, patterns, or exclusive Windows instructions are present. All commands use the Azure CLI, which is cross-platform.
Recommendations
- Continue to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs, or clarify that Bash is shown first for consistency, not platform preference.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reassure users.
- If possible, add a short note at the top indicating cross-platform compatibility.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No exclusive Windows tools, patterns, or missing Linux examples are present.
Recommendations
- Maintain the current approach of providing both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs in different sections, or clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state that Bash examples are intended for Linux/macOS users and PowerShell for Windows users to improve clarity.
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 nearly every section, Bash (Linux/macOS) examples are presented before PowerShell (Windows) examples. There are no Windows-specific tools, patterns, or references that would disadvantage Linux users. The Azure CLI and Helm are cross-platform tools, and no steps require Windows-only features. The only minor bias is the ordering of Bash before PowerShell, which may slightly favor Linux users in terms of visibility.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to ensure equal visibility.
- Explicitly state that both Bash and PowerShell are supported on Windows, Linux, and macOS, and that users can choose either based on their preference.
- If possible, add a note clarifying that the Azure CLI and Helm commands work identically across platforms.
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. While PowerShell is primarily associated with Windows, CLI (Azure CLI) is cross-platform. However, PowerShell is mentioned before any Linux-specific shell (such as Bash), and there are no explicit Linux/macOS shell examples or references. No actual script examples are given, so the bias is limited to the order and naming.
Recommendations
- Clarify that Azure Copilot can generate scripts for both PowerShell and Bash (or other Linux shells), not just PowerShell.
- Explicitly mention Bash or Linux/macOS shell support alongside PowerShell and CLI.
- If examples are added in the future, ensure parity by providing both PowerShell and Bash examples.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used exclusively, and all commands are cross-platform (using Azure CLI and Helm).
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections, or explicitly state that both are equally supported.
- Add a note clarifying that all commands are cross-platform and can be run on Linux, macOS, and Windows.
- If possible, provide guidance for users running Azure CLI and Helm on macOS, such as installation links or troubleshooting tips.
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 the PowerShell examples are always shown after Bash. There is no evidence of Windows-only tools or patterns being used, and all commands are based on the Azure CLI and Helm, which are cross-platform. However, the PowerShell examples are extensive and use Windows-style syntax, which may create a slight bias toward Windows users. There are no missing Linux examples, and Linux users can complete all tasks without friction.
Recommendations
- Consider adding a note clarifying that both Bash and PowerShell are fully supported and that the Azure CLI and Helm commands work identically on Linux, macOS, and Windows.
- If possible, provide a brief summary or table at the top indicating that users can choose either Bash or PowerShell, depending on their OS.
- Ensure that the Bash and PowerShell tabs are equally prominent and that Bash is not always shown first by default, or randomize the order to avoid subtle bias.
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. There is no explicit Linux/macOS example or mention of Bash scripting, and PowerShell is primarily a Windows-centric tool, though it is available cross-platform. The documentation does not reference Linux-specific tools or workflows, and the order of examples could imply Windows/PowerShell parity or priority.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Provide Bash shell scripting examples or clarify that Azure CLI commands work natively in Bash and other Unix shells.
- Consider placing Azure CLI examples before PowerShell examples, or labeling PowerShell as 'for Windows users' if appropriate.
- Add a note that PowerShell is available cross-platform but is more commonly used on Windows.
- Include links or references to Linux/macOS-specific guidance for Azure Container Registry operations.
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 tools. However, there is evidence of Windows bias in the use of the 'set' command for environment variables and the lack of explicit Linux/macOS equivalents. The environment variable setup uses 'set', which is Windows-specific, and does not mention 'export' for Linux/macOS. Most other commands are generic and applicable to all platforms, but the initial environment variable example may confuse Linux/macOS users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') commands for setting environment variables.
- Add a note clarifying that Azure CLI and Helm commands are cross-platform and can be run on Windows, Linux, or macOS.
- Where shell commands are shown, specify the shell context (e.g., Bash, PowerShell) or provide alternatives.
- Review all examples for platform-specific syntax and ensure parity.
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 and showing usage), but consistently lists PowerShell examples alongside or after CLI examples without mentioning Linux/macOS shell equivalents (e.g., Bash). There are no explicit Linux/macOS-specific instructions or examples, and PowerShell is referenced without clarifying its cross-platform availability. The documentation does not reference Windows-only tools, but the example pattern may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the preferred cross-platform option.
- Explicitly mention Bash or shell environments for Linux/macOS users when referencing Azure CLI.
- Consider providing Bash example blocks for Azure CLI commands, or note that the CLI syntax is identical across platforms.
- When referencing PowerShell, note its cross-platform nature or indicate that it is optional for Windows users.
- List Azure CLI examples first, as it is the most platform-neutral tool.