230
Pages Scanned
58
Pages Flagged
230
Changed Pages
25.2%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-02 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 230
Files Completed: 230
Problematic Pages
57 issues found
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows environments: all onboarding scripts and instructions are provided exclusively as PowerShell scripts (.ps1), and users are instructed to use Windows-specific tools such as 'winget' for installing dependencies. There are no Bash/shell script equivalents, nor are there instructions for Linux/macOS users to run the onboarding process. All examples and command snippets assume a Windows/PowerShell context, and Linux alternatives are not mentioned.
Recommendations
- Provide equivalent onboarding scripts in Bash or shell for Linux/macOS users, or document how to run the PowerShell scripts cross-platform (e.g., using PowerShell Core on Linux/macOS).
- Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., 'apt', 'yum', 'brew', or direct download links) for installing Azure CLI and kubectl.
- Explicitly state whether the onboarding scripts are supported on Linux/macOS (e.g., via PowerShell Core), and if not, provide a roadmap or workaround.
- Include Linux/macOS command examples and terminal instructions alongside PowerShell/Windows examples.
- Clarify any Windows-only requirements up front, so non-Windows users can plan accordingly.
Create Pull Request
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash or Linux shell examples. While the Azure CLI is cross-platform, the use of PowerShell-specific syntax (backticks for line continuation, variables with $) may confuse Linux/macOS users. Most other CLI instructions use generic Bash syntax, but the PowerShell examples are shown first and exclusively in some sections.
Recommendations
- Provide Bash/Linux shell examples alongside PowerShell examples for CLI commands, especially where PowerShell syntax is used.
- Clarify that Azure CLI commands work on all platforms and note any OS-specific syntax differences.
- Use platform-neutral syntax (e.g., avoid PowerShell line continuations and variables in generic CLI documentation) or show both variants.
- Add a note explaining how to adapt PowerShell examples for Bash users.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is intended for configuring a Linux-based AKS Edge Essentials cluster, but it relies heavily on the Windows-specific PowerShell cmdlet 'Invoke-AksEdgeNodeCommand' for Linux node configuration. There are no native Linux shell examples for checking or setting sysctl parameters, and the text editor example references Notepad, a Windows tool, instead of a Linux editor.
Recommendations
- Provide native Linux shell commands for checking and setting sysctl parameters (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee ...').
- Replace or supplement 'Notepad' with Linux text editors like 'nano', 'vim', or 'gedit' when editing configuration files.
- Clarify whether 'Invoke-AksEdgeNodeCommand' is available cross-platform or provide Linux alternatives if not.
- Ensure all critical steps can be completed using Linux-native tools and commands.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation instructions for client tools across platforms, but Windows links are often listed first, and there is a notable emphasis on Windows-specific behaviors (e.g., PowerShell alias for curl, cmd.exe usage). Linux installation instructions are less explicit, sometimes only referenced as 'install curl package' without a link or detailed guidance. There are no explicit Linux/macOS command examples or troubleshooting notes, and Windows-specific notes are more prominent.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions for tools like curl, including package manager commands (e.g., 'sudo apt install curl', 'brew install curl').
- Add Linux/macOS-specific troubleshooting notes (e.g., for curl or kubectl usage) similar to the PowerShell alias note.
- Include example commands for checking versions or installing tools on Linux/macOS, not just Windows.
- Ensure parity in detail and clarity for Linux/macOS users throughout the documentation.
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 page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are also mentioned, Windows tools are listed prominently and PowerShell is referenced as a core scripting method. There are no Linux-specific examples, tools, or scripting alternatives provided, and Windows authentication is listed as a supported security feature without mention of Linux/macOS equivalents.
Recommendations
- Add examples or references for Linux/macOS-compatible tools (e.g., sqlcmd, Azure Data Studio, mssql-cli).
- Clarify cross-platform support for scripting (e.g., Bash, Python, or Azure CLI usage for manageability tasks).
- Mention authentication options suitable for Linux/macOS environments (e.g., Microsoft Entra ID, if supported, or other cross-platform authentication methods).
- Balance tool listings by including Linux/macOS-friendly options alongside Windows tools, rather than focusing on Windows tools first.
- If PowerShell is referenced, also mention Bash or other scripting alternatives for Linux/macOS users.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using PowerShell syntax and references the use of sqlcmd, which is often associated with Windows environments. The examples for verifying connectivity and executing SQL commands are given in PowerShell format, and no explicit Linux/macOS shell alternatives (such as Bash or sh) are provided. The documentation does not mention Linux-specific tools or provide parity examples for Linux/macOS users, even though the context is Kubernetes and Azure Arc, which are cross-platform.
Recommendations
- Provide Bash/sh examples alongside PowerShell for kubectl exec and sqlcmd usage, ensuring Linux/macOS users can follow along easily.
- Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links for those platforms.
- Use generic shell syntax (e.g., $ kubectl ...) instead of PowerShell-specific formatting where possible.
- Explicitly mention that all commands are cross-platform unless otherwise noted, and highlight any OS-specific caveats.
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 examples and instructions that prioritize Windows tools and file paths, such as using SQL Server Management Studio (SSMS), Visual Studio Code, and Windows-style paths (e.g., C:\Backupfiles\test.bak). There are no explicit Linux/macOS examples for creating backups or copying files, and Linux file paths are only used in restore commands, not in backup steps. The instructions for copying files into pods with kubectl cp only show Windows source paths, and do not mention Linux/macOS equivalents.
Recommendations
- Add explicit Linux/macOS examples for backup commands, using typical Linux file paths (e.g., /home/user/backup/test.bak).
- Mention cross-platform tools for connecting to SQL Server, such as Azure Data Studio, in addition to SSMS and Visual Studio Code.
- Provide kubectl cp examples using Linux/macOS source paths (e.g., /home/user/backup/test.bak) and clarify that the command works on all platforms.
- Clarify that Azure Storage Explorer and Visual Studio Code are cross-platform, and provide installation links for Linux/macOS where applicable.
- Include notes or sections for Linux/macOS users, highlighting any differences or additional steps.
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, referencing Azure CLI and supporting both Windows and Linux management machines. However, there are several areas of Windows bias: PowerShell is used for troubleshooting (e.g., HTTP2 errors, DNS resolution), Windows-specific terminology (e.g., 'Remote PowerShell', 'RDP'), and Windows examples are sometimes given before Linux equivalents. Some CLI troubleshooting steps (e.g., downgrading Azure CLI with pip) mention Linux, but PowerShell commands are used for network validation and DNS resolution, with no equivalent Linux commands provided. Additionally, folder permission errors reference 'SSH folder' generically, but troubleshooting steps are not platform-specific. The documentation could be improved by providing Linux/macOS equivalents for PowerShell commands and ensuring parity in troubleshooting steps.
Recommendations
- For every PowerShell command, provide a Bash/Linux equivalent (e.g., use curl or wget for HTTP2 troubleshooting, dig/nslookup for DNS resolution).
- When referencing Windows tools (e.g., RDP, PowerShell), clarify Linux/macOS alternatives (e.g., SSH, terminal access).
- Ensure troubleshooting steps for folder permissions, network connectivity, and CLI errors include Linux/macOS-specific guidance.
- Where CLI commands are shown, explicitly state they are cross-platform and provide any OS-specific caveats.
- Review the order of examples to avoid consistently showing Windows-first patterns.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally provides both Windows and Linux release notes and download links, but there is a notable bias in troubleshooting and known issues sections, where only Windows-specific commands and tools (e.g., attrib, PowerShell) are provided. Windows examples and instructions are often presented first, and Linux equivalents for troubleshooting are missing. Some improvements and bug fixes are described only for Windows tools (e.g., MSI installer, PowerShell scripts), with no Linux alternatives or guidance.
Recommendations
- For every troubleshooting or known issue section that provides Windows command-line or PowerShell instructions, add equivalent Linux shell commands or guidance if the issue could affect Linux users.
- When listing download links or examples, alternate the order or provide a neutral presentation (e.g., 'Download for Linux or Windows').
- If a fix or improvement is Windows-only, clearly label it as such, and ensure Linux users are not left without guidance for similar scenarios.
- Where possible, provide parity in scripting examples (e.g., show both PowerShell and Bash commands for common tasks).
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation presents several onboarding methods for the Azure Connected Machine agent, with both Linux and Windows options. However, PowerShell-based methods are highlighted prominently, and Windows-specific tools (Windows Admin Center, Group Policy, Configuration Manager) are listed in dedicated sections. Windows methods are shown first in the 'at scale' section, and Linux-specific automation tools (e.g., Ansible) are mentioned but not emphasized equally. There is a notable focus on Windows tooling and scripting, which may create friction for Linux users.
Recommendations
- Provide Linux-specific examples and automation methods (e.g., Bash scripts, systemd, cron) alongside PowerShell.
- Ensure that Linux onboarding methods (such as Ansible, shell scripts) are given equal prominence and detail as Windows methods.
- Add links or references to Linux-native tools for at-scale deployment (e.g., Puppet, Chef, SaltStack) if supported.
- Clarify which methods are best suited for Linux environments and provide step-by-step guides for Linux users.
- Consider reordering the table or grouping methods by OS type to avoid implicit Windows-first bias.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions for all major lifecycle tasks (install, upgrade, uninstall, proxy config), using clear tabbed sections for each OS. However, there are several areas where Windows bias is evident: Windows examples and tools (PowerShell, Group Policy, Control Panel, Msiexec) are often described in greater detail, with more step-by-step guidance, and appear first in some sections. The cleanup script for stale Arc resources is PowerShell-only, with no Linux/bash equivalent. Windows-specific tools and patterns (e.g., Group Policy, WSUS, Configuration Manager) are mentioned exclusively, while Linux equivalents (e.g., automation via cron or systemd) are not discussed. Linux instructions are present and generally sufficient, but less detailed and less contextual.
Recommendations
- Provide a bash or Azure CLI script example for stale Arc resource cleanup, or at least mention how Linux users can achieve the same task.
- Where Windows tools (e.g., Group Policy, WSUS, Configuration Manager) are discussed, add notes about Linux equivalents or alternative automation approaches (e.g., using cron, systemd, or Ansible).
- Ensure Linux instructions are as detailed as Windows ones, including troubleshooting, logging, and automation tips.
- Consider alternating the order of Windows and Linux sections, or presenting them in parallel, to avoid 'windows_first' bias.
- Where PowerShell is used for Azure operations, provide Azure CLI equivalents (which are cross-platform).
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, but all deployment instructions and command-line examples use Azure PowerShell exclusively. There are no Azure CLI or Bash examples for deploying templates, and PowerShell is presented as the default/only method. Additionally, PowerShell deployment commands are shown before any mention of Azure CLI, which is only referenced in the 'Related content' section.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell, especially for template deployments (e.g., az deployment group create ...).
- Explicitly state that both PowerShell and Azure CLI can be used, and provide links or inline examples for Linux/macOS users.
- Consider showing Azure CLI examples first or in parallel with PowerShell to avoid implicit Windows-first bias.
- Clarify that the template files themselves are cross-platform, and the deployment tooling can be used from any OS.
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux context, but there is a notable Windows bias: Windows tools (Admin Center, Graphical Installer) are mentioned explicitly, and PowerShell is referenced before Bash. Linux equivalents (e.g., Linux graphical installers, Linux-specific deployment tools) are not mentioned or are less prominent. Windows deployment options are described in more detail and appear first in lists.
Recommendations
- Add explicit Linux deployment examples and tools, such as Linux graphical installers or common Linux management platforms.
- Ensure Bash and PowerShell examples are given equal prominence, possibly showing Bash first or side-by-side.
- Mention Linux-specific automation tools (e.g., Puppet, Chef) alongside Ansible and Configuration Manager.
- Clarify which steps or tools are applicable to Linux, and provide links to Linux-specific guidance where available.
- Balance the order of Windows and Linux references in lists and explanations.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples, especially in PowerShell and REST API sections, are Windows-centric. PowerShell examples dominate, and REST API examples exclusively use Windows-specific scripts (e.g., New-NetFirewallRule). There is a lack of Linux-specific script examples (e.g., using bash or Linux firewall tools), and guidance for SAS token generation only references Windows tooling (New-AzStorageBlobSASToken). The CLI section also uses a PowerShell command as its script example. Linux is only mentioned in passing, and Linux-specific scenarios are not demonstrated.
Recommendations
- Add Linux-specific script examples throughout, especially for common tasks such as configuring firewall rules (e.g., using iptables, ufw, or firewalld in bash scripts).
- In the Azure CLI section, provide at least one example using a bash script (e.g., 'echo Hello World!' or a simple shell command) instead of PowerShell syntax.
- In the REST API section, include a Linux scenario (e.g., running a bash script to configure a Linux firewall or perform a Linux-specific administrative task).
- When referencing SAS token generation, mention cross-platform tools (e.g., Azure CLI's az storage blob generate-sas) and not just PowerShell commands.
- Wherever possible, alternate or parallelize Windows and Linux examples to demonstrate parity and reduce friction for Linux users.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation exclusively provides recovery instructions for the Azure Arc resource bridge VM from a Windows machine, using a PowerShell script. There are no examples or guidance for Linux/macOS users, nor is there mention of equivalent tools or scripts for non-Windows platforms. The Windows approach is presented as the only method, creating friction for administrators who may use Linux or macOS.
Recommendations
- Provide equivalent recovery instructions for Linux/macOS, including Bash or Python scripts if available.
- Clarify if the recovery process is inherently Windows-only due to dependencies (e.g., SCVMM or PowerShell), or explicitly state platform limitations.
- If possible, offer cross-platform tools or containerized solutions to enable recovery from non-Windows environments.
- Mention any prerequisites or limitations for Linux/macOS users, and link to relevant resources if available.
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 demonstrates a moderate Windows bias. The primary automation script for Arc agent installation is a PowerShell script, with instructions and examples focused on PowerShell usage and Windows Task Scheduler for cron-like automation. Linux-specific guidance is limited to a brief sudo configuration note, and there are no Bash or Linux shell script examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents, and Linux automation options (e.g., cron, Bash) are not provided.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, alongside PowerShell scripts.
- Include instructions for running the automation script on Linux/macOS, such as using cron for scheduled tasks.
- Clarify whether the helper script can run cross-platform, or provide a Linux-specific version if not.
- Add Linux-first or Linux-parity examples in sections where Windows tools are referenced (e.g., Task Scheduler).
- Expand the out-of-band methods section to include more Linux automation approaches (e.g., systemd timers, Bash scripts).
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy and script invocation, but does not offer equivalent Linux/macOS guidance. The script is referenced as a PowerShell script, and only Windows-specific instructions are given for its execution. Linux agent removal is covered, but Linux/macOS users are left without clear steps for running the deboarding script, creating friction for non-Windows users.
Recommendations
- Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (such as PowerShell Core installation) and command-line examples.
- Clarify whether the script is cross-platform (PowerShell Core compatible) or Windows-only; if Windows-only, provide alternative manual steps or scripts for Linux/macOS users.
- Present Linux/macOS instructions alongside Windows instructions, not after or omitted.
- Mention any required tools (e.g., Azure CLI, PowerShell Core) for Linux/macOS users.
- If the script is not cross-platform, consider providing a Bash or Python equivalent.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only PowerShell-based onboarding script examples and instructions, with no mention of Bash, Linux shell, or cross-platform alternatives. All code snippets and script references assume a Windows/PowerShell environment, which may exclude or confuse Linux/macOS users managing Azure Arc-enabled VMware vSphere environments.
Recommendations
- Provide equivalent onboarding script instructions and examples for Bash or cross-platform shells if supported.
- Clarify in the prerequisites or introduction whether the onboarding script is only supported on Windows/PowerShell, or if there are Linux/macOS alternatives.
- If the onboarding script is cross-platform, include both PowerShell and Bash examples, and note any OS-specific requirements.
- Explicitly state OS requirements for running the onboarding script, so users on non-Windows platforms are aware of their options.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively provides a PowerShell script (`RGCleanScript.ps1`) and only demonstrates usage via PowerShell commands. There are no examples or instructions for running the clean-up script on Linux or macOS, nor is there mention of a cross-platform or Bash/sh alternative. This creates friction for non-Windows users who may not have access to PowerShell or cannot run `.ps1` scripts natively.
Recommendations
- Provide a Bash or shell script alternative (e.g., `RGCleanScript.sh`) for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core (pwsh) on all platforms.
- Include explicit instructions for running the script on Linux/macOS, such as using PowerShell Core (`pwsh`) if supported.
- Add example commands for Linux/macOS environments, and note any prerequisites (e.g., installing PowerShell Core).
- If the script is truly Windows-only, clearly state this limitation at the top of the documentation.
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
missing_linux_example
windows_tools
windows_first
Summary
The documentation page exhibits a notable Windows/PowerShell bias. All provided automation and scripting examples use PowerShell scripts (e.g., .ps1 files and PowerShell syntax), and file paths in JSON templates use Windows-style paths (e.g., C:\Users\...). There are no equivalent Bash/shell scripts or Linux/macOS command-line examples. The use of PowerShell is assumed throughout, and Linux users are not provided with guidance for adapting the instructions. Additionally, Windows paths and tools are referenced before any cross-platform alternatives.
Recommendations
- Provide equivalent Bash or shell script examples for all PowerShell scripts, especially for onboarding and enabling diagnostics.
- Use cross-platform file path examples (or note how to adapt them for Linux/macOS) in JSON templates and documentation.
- Explicitly state if the provided scripts are only supported on Windows, and offer guidance or references for Linux/macOS users if possible.
- Where Azure CLI commands are shown, use shell-agnostic syntax or provide both PowerShell and Bash variants.
- Add notes or sections for Linux/macOS users, clarifying any differences in setup or troubleshooting.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell migration script and example, with no mention of Linux/macOS-compatible alternatives or instructions. The script is a .ps1 file, which is traditionally Windows-centric, and there are no Bash or cross-platform options discussed.
Recommendations
- Clarify whether the PowerShell script is compatible with PowerShell Core (pwsh) on Linux/macOS, and provide instructions for running it on those platforms if applicable.
- If the script is Windows-only, offer a Bash or Python alternative for Linux/macOS users, or explicitly state that Linux/macOS users must use Windows or PowerShell Core.
- Add examples for running the migration on Linux/macOS, including any prerequisites or dependencies.
- Mention any limitations or required adaptations for non-Windows environments.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell script examples. There is no mention of Linux/macOS usage or alternative scripting approaches, and the PowerShell examples are presented as the default/only option, which may create friction for Linux/macOS users.
Recommendations
- Provide CLI examples in Bash syntax alongside PowerShell, especially for az CLI commands, which are cross-platform.
- Offer equivalent Bash or shell scripts for bulk_deployment.ps1 and workflow-delete.ps1, or explain how Linux/macOS users can achieve the same workflow.
- Explicitly state that az CLI commands work on all platforms and clarify any platform-specific requirements for scripts.
- Add notes or sections addressing Linux/macOS users, including troubleshooting or usage tips.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The kubectl installation command uses 'winget', a Windows-only tool, with no Linux/macOS alternative provided. The file extraction example in the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, rather than standard Linux/macOS tools like 'unzip'. Throughout, Windows tools and patterns are mentioned or shown first, and Linux/macOS equivalents are missing or not prioritized. This creates friction for non-Windows users, especially in initial setup steps.
Recommendations
- Provide Linux/macOS-specific instructions for installing kubectl (e.g., using 'curl' or 'apt', 'brew').
- Replace or supplement 'Expand-Archive' in Bash examples with 'unzip' or 'tar' commands for Linux/macOS users.
- Ensure Bash examples use cross-platform commands and avoid Windows-specific paths and tools.
- Clearly indicate which commands are Windows-only and provide parity for Linux/macOS wherever possible.
- Review the ordering of examples so that Linux/macOS instructions are not always secondary or omitted.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions using both Azure CLI and PowerShell, but PowerShell is mentioned alongside Azure CLI as a primary option, and the instructions for opening the terminal reference Visual Studio Code shortcuts that are Windows-centric. There are no Linux-specific examples or terminal instructions, and PowerShell is not natively available on most Linux/macOS systems, potentially creating friction for non-Windows users.
Recommendations
- Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Provide Linux/macOS-specific instructions for opening a terminal (e.g., using Terminal app or shell commands).
- Clarify that PowerShell is optional and primarily for Windows users, or provide guidance for installing PowerShell Core on Linux/macOS if desired.
- Consider showing Azure CLI examples first, as it is the most universally available tool.
- Add a note that Visual Studio Code is cross-platform, and provide alternative editor suggestions for Linux/macOS users.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward PowerShell and Windows-style command usage. Most examples, including those for az CLI, kubectl, and Docker, are presented in PowerShell syntax (with variables like $var and PowerShell-specific constructs), and there are no equivalent Bash/Linux shell examples for the majority of the troubleshooting steps. Only in the 'Troubleshoot service groups' section are both Bash and PowerShell examples provided. This creates friction for Linux/macOS users, who may not be familiar with PowerShell syntax or variable usage.
Recommendations
- For all az CLI, kubectl, and Docker command examples, provide both Bash and PowerShell versions, using appropriate variable syntax for each shell.
- Where PowerShell-specific constructs are used (e.g., ConvertTo-Json, Out-File, [Convert]::ToBase64String), provide equivalent Bash/Linux commands (e.g., jq, echo, base64, etc.).
- Avoid using PowerShell variable syntax ($var) in generic CLI examples; instead, use placeholders or Bash-style variables where appropriate.
- Clearly indicate which commands are for Windows/PowerShell and which are for Bash/Linux/macOS, using tabbed sections as done in the 'Troubleshoot service groups' section.
- Review all troubleshooting steps to ensure Linux/macOS users can follow them without needing to translate PowerShell commands.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command examples for Helm and Azure CLI, which are cross-platform tools. However, there is evidence of Windows bias: the environment variable is set using 'set' (a Windows command) without a Linux/macOS equivalent ('export'), and the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-only) mentioned before Portal. There are no explicit Linux/macOS-specific examples or notes for shell commands, and some commands (like 'set') may confuse Linux/macOS users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') variants when setting environment variables.
- Clarify that Azure CLI and Helm commands are cross-platform, and provide explicit shell examples for Bash/zsh where appropriate.
- When listing options for creating AKS clusters, mention Azure CLI and Portal first, and note that PowerShell is Windows-only.
- Review all command snippets to ensure they work on both Windows and Linux/macOS, and add notes where syntax differs.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides authentication instructions for Azure Container Registry using both Azure CLI and Azure PowerShell, but PowerShell examples and references are prominent throughout, and PowerShell is presented alongside Azure CLI in nearly every authentication method. There are no explicit Linux/macOS-specific examples or shell commands (e.g., Bash), and the CLI examples do not clarify cross-platform compatibility. Windows tools (PowerShell) are given equal or greater prominence compared to Azure CLI, which is cross-platform, but Linux-native workflows (such as Bash scripting or Linux-specific environment variable usage) are not addressed. The 'Next steps' section only links to Azure CLI and PowerShell guides, omitting Linux/macOS-specific workflows.
Recommendations
- Add explicit Bash/Linux/macOS shell examples alongside PowerShell and Azure CLI, especially for authentication and scripting scenarios.
- Clarify that Azure CLI commands are cross-platform and provide notes or examples for Linux/macOS users (e.g., environment variable syntax differences).
- Include links to Linux/macOS-specific getting started guides in the 'Next steps' section.
- Balance PowerShell references by including Bash or shell scripting alternatives where appropriate.
- Mention that Azure CLI and Docker commands work on Linux/macOS, and provide troubleshooting tips for those platforms.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere, with some bias toward Windows. Windows-specific features (e.g., customizing guest OS settings for Windows VMs, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) are mentioned, but these are not flagged as bias due to their inherent Windows focus. However, in sections describing tooling, Azure PowerShell is listed alongside Azure CLI and REST APIs, and Windows tools (System Center Configuration Manager, Group Policy) are mentioned before Linux equivalents (Ansible). PowerShell is referenced as a management option, and Windows-centric tools are listed first in out-of-band agent installation methods.
Recommendations
- When listing management tools, alternate the order so Linux tools (e.g., Ansible) are not always last.
- Provide explicit Linux/macOS command examples (e.g., Bash, SSH) where PowerShell is referenced.
- Clarify which features are cross-platform and which are Windows-only to help Linux/macOS users quickly identify relevant content.
- Include links to Linux-focused documentation or examples where possible.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for each command, 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 mentioned, and Linux examples are not missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
- Explicitly state that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows, to clarify cross-platform applicability.
- If possible, provide a brief note about using Azure CLI in both environments, highlighting any OS-specific nuances.
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 throughout, but PowerShell examples are consistently shown after Bash examples. There are no Windows-exclusive tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Windows-specific tools or terminology are prioritized. The only minor bias is that Bash (Linux/macOS) examples are always shown first, with PowerShell (Windows) examples following.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections, or clarify that Bash is shown first for consistency but both are equally supported.
- Explicitly state at the top that all commands are cross-platform and that both Bash and PowerShell are supported.
- If possible, provide a note about how to run PowerShell on Linux/macOS for users who prefer it.
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 or patterns are mentioned exclusively, and Linux examples are not missing.
Recommendations
- Maintain the current parity of examples for both Bash and PowerShell.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
- If possible, add a note clarifying that all commands are cross-platform via Azure CLI, and users should select their preferred shell.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering, but no critical bias in content or functionality.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that both are equally supported.
- Ensure that any referenced tooling (e.g., az, helm) is cross-platform and clarify installation instructions for Linux/macOS if not already covered elsewhere.
- Add a note confirming that all steps are fully supported on Linux/macOS and Windows, to reassure users.
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 before sqlcmd and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The documentation does not provide parity in GUI client recommendations for Linux/macOS users, and the overall tone suggests Windows as the default environment.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit examples for connecting from Linux/macOS using GUI tools, not just sqlcmd.
- When listing tools, avoid always mentioning Windows-only tools first; alternate or group by platform.
- Clarify that sqlcmd is available on both Windows and Linux, and provide installation guidance if needed.
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_example
linux_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files when creating Kubernetes secrets. The Linux example (using 'base64') is presented first, and the Windows example (using 'certutil' and 'findstr') is given immediately after. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and does not show significant Windows bias. However, the Windows-specific tool (certutil) is mentioned, and Windows users are given extra instructions for removing headers, which could be seen as a minor bias.
Recommendations
- Explicitly state that all Azure CLI and kubectl commands work on both Windows and Linux.
- Provide equivalent Linux/macOS commands for removing certificate headers (e.g., 'grep -v CERTIFICATE b64-encoded.txt > updated-b64.txt') alongside the Windows 'findstr' example.
- Clarify that OpenSSL, Azure CLI, and kubectl are cross-platform and provide installation links for Windows, Linux, and macOS.
- Consider grouping Windows and Linux instructions together, or using tabs to switch between OS-specific examples for improved clarity.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently presents Azure PowerShell (a Windows-centric tool) examples alongside or immediately after Azure CLI. There is no explicit Linux/macOS example or mention of Bash scripting, and PowerShell is presented as an equal alternative, despite its primary association with Windows. However, Azure CLI is cross-platform and the examples use standard environment variables for proxy configuration, which are compatible with Linux/macOS. No Windows-only tools or patterns are used, and Linux users can complete all tasks.
Recommendations
- Explicitly state that Azure CLI commands and environment variable examples are compatible with Linux/macOS.
- Add notes or examples showing Bash shell usage for Linux/macOS users, especially for environment variable setup.
- Clarify that Azure PowerShell can be used cross-platform, but is most familiar to Windows users.
- Consider showing Azure CLI (Linux/macOS-friendly) examples first, or labeling them as recommended for Linux/macOS.
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 for `azcmagent connect` displays mild Windows bias. Windows authentication options (interactive browser login, certificate store usage) are described first and in more detail, with explicit 'Windows only' labeling. Windows-specific tooling (PowerShell's Get-AzAccessToken) is mentioned for access token acquisition, while Linux alternatives are not referenced. However, Linux authentication methods (device code, Azure CLI) are documented and examples are generally cross-platform.
Recommendations
- Reorder authentication options so cross-platform methods (device code, Azure CLI, service principal) appear before Windows-only options.
- When referencing access token acquisition, mention Linux/macOS alternatives (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
- Clarify which examples and flags are cross-platform, and explicitly state Linux/macOS compatibility where relevant.
- Add a brief section or table summarizing authentication methods by OS/platform for quick reference.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page lists both Windows and Linux-related endpoints and requirements, but there is a mild bias toward Windows: Windows NTP server ('time.windows.com') is mentioned as the default, and several endpoints (e.g., 'login.windows.net', 'sts.windows.net', 'servicebus.windows.net') use Windows branding. The table includes a Linux-specific endpoint ('linuxgeneva-microsoft.azurecr.io') and references to Linux package sources, but Windows tools and URLs are mentioned first or exclusively in some cases. There are no OS-specific command examples or instructions, so the bias is limited to endpoint naming and notes.
Recommendations
- Clarify that NTP can use Linux NTP servers as well, and provide guidance for Linux environments.
- Where Windows-branded endpoints are mentioned (e.g., 'login.windows.net', 'sts.windows.net'), note if these are required for Linux as well, or provide Linux alternatives if applicable.
- Ensure that any references to default behaviors (such as NTP) include both Windows and Linux defaults.
- If management machines can be Linux, explicitly state so and provide any Linux-specific considerations.
- Review notes and examples for implicit Windows-first language and update for parity.
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 page for Azure Arc resource bridge system requirements shows minor Windows bias by linking to the Windows Azure CLI installation page first and referencing Azure CLI x64/32-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-only examples or tools, and the Azure CLI is cross-platform. No critical Linux/macOS information is missing, but Linux parity could be improved.
Recommendations
- Explicitly state that Azure CLI is supported on Linux and macOS, not just Windows.
- Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link.
- Clarify that the management machine can be Linux, macOS, or Windows, and note any OS-specific requirements (if any).
- If referencing CLI directory paths, mention typical Linux/macOS paths as well as Windows.
- Add a brief note that all CLI commands and configuration steps apply equally to Linux/macOS unless otherwise specified.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is consistently included alongside CLI. In several sections, PowerShell examples are shown after CLI, but the CLI syntax uses backticks (`) for line continuation, which is a Windows/PowerShell convention and not standard for Linux shells. There is a minor tendency to mention Windows tools (PowerShell, Windows Admin Center) and Windows-specific scenarios first. However, Linux parity is generally maintained, with explicit Linux instructions for log locations and onboarding, and the Azure CLI is cross-platform.
Recommendations
- Use standard Bash line continuation (\) in CLI examples instead of backticks to improve Linux usability.
- Explicitly state that Azure CLI commands work on Linux/macOS and provide Bash syntax where relevant.
- Consider including Bash shell examples or clarifying that PowerShell is optional for Linux users.
- Where Windows-specific tools (like Windows Admin Center) are mentioned, balance with Linux equivalents or clarify their scope.
- Ensure that Linux log file paths and instructions are as prominent as Windows instructions.
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, but the Windows/PowerShell example is presented first and in greater detail (including a screenshot). PowerShell is referenced as the primary tool for Windows, while Bash is used for Linux. The prerequisites and related content sections mention both platforms and tools, but PowerShell is listed before Azure CLI in the related content. Overall, Linux parity is maintained, but Windows examples and tools are prioritized.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which platform is shown first.
- Provide equally detailed screenshots and explanations for both Windows and Linux examples.
- List Azure CLI and Bash examples before or alongside PowerShell in related content.
- Ensure that all steps and explanations are equally clear for both platforms.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Windows and Linux Azure Arc-enabled servers and provides parity in feature descriptions. However, there is a mild Windows bias in the ordering of examples and tools: PowerShell examples are presented after CLI, but the PowerShell section is detailed and tips about installing the module are included. The Azure CLI section does mention Linux shells, but Windows is referenced first in several places. No critical Linux functionality is missing, and all management tasks can be performed via CLI or portal, which are cross-platform.
Recommendations
- Ensure Linux and macOS are mentioned equally alongside Windows in introductory sentences.
- Consider alternating the order of CLI and PowerShell sections, or explicitly state that CLI is cross-platform and PowerShell is primarily for Windows users.
- Add explicit notes or links for macOS users where relevant (e.g., Azure CLI installation).
- Where possible, clarify that PowerShell can be used on Linux and macOS, or provide Bash examples for common tasks.
- Review screenshots and UI instructions to ensure they are not Windows-centric.
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 presents Windows VM extensions before Linux extensions, with a more extensive and detailed table for Windows. However, Linux extensions are also comprehensively covered, and deployment methods (CLI, PowerShell, portal, templates) are presented neutrally. No critical Windows-only bias is present, and Linux users can complete all tasks described.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to emphasize parity.
- Ensure that Linux extension descriptions are as detailed as their Windows counterparts, including links to supported OS and additional information.
- Explicitly mention that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux, and provide example commands for both platforms where appropriate.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations. However, there is a mild Windows bias: Windows log file paths and PowerShell-style commands are presented first in the verbose log section, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced before Linux equivalents. Linux examples and paths are included, but Windows is prioritized in ordering and detail.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid always showing Windows first.
- Ensure Linux log file paths and troubleshooting steps are as detailed as Windows.
- Where possible, provide parity in command syntax explanations (e.g., clarify sudo/elevated prompt for Linux as much as for Windows).
- Add explicit notes about Linux-specific troubleshooting (e.g., SELinux/AppArmor, systemd service management) if relevant.
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
windows_tools
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are several instances where Windows/PowerShell tools and examples are mentioned first or exclusively. PowerShell is listed before other automation tools, and Windows-specific management features are highlighted. While Linux is referenced in some scenarios, Windows tools and terminology are often prioritized, which may create minor friction for Linux/macOS users.
Recommendations
- Ensure Linux examples and tools (such as Bash, Linux CLI, and Linux-specific VM extensions) are mentioned alongside or before Windows/PowerShell equivalents.
- When listing automation options, avoid always putting PowerShell first; alternate order or explicitly mention Linux-friendly tools.
- Add explicit Linux/macOS onboarding and management examples where possible, especially in sections referencing scripts or agent installation.
- Clarify parity between Windows and Linux support for features like Azure Update Manager, Azure Automation, and VM extensions.
- Include links or references to Linux-specific documentation and best practices.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first in the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout.
Recommendations
- Present Windows and Linux instructions side-by-side or in parallel tabs to avoid implicit prioritization.
- Alternate the order of Windows and Linux instructions in sections to ensure equal visibility.
- Explicitly mention macOS compatibility if the Bash script works on macOS.
- Clarify that both scripts are functionally equivalent and supported.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and with download links, while Linux requirements (systemd, wget) are listed second and without links. Windows PowerShell is mentioned explicitly, but no Linux shell or command-line examples are provided. The overall guidance is cross-platform, but Windows examples and tools are prioritized.
Recommendations
- List Linux requirements before or alongside Windows requirements to avoid 'Windows-first' ordering.
- Provide download links or references for Linux tools (e.g., systemd, wget) similar to Windows.
- Include example Linux shell commands or scripts for onboarding, not just Windows/PowerShell references.
- Clarify parity in supported OSes and tools, and ensure Linux users have equal guidance for installation and troubleshooting.
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 directly after Bash, which is a minor 'windows_first' bias. No Windows-only tools or patterns are used, and all instructions are cross-platform via the Azure CLI. No Linux/macOS examples are missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash examples apply to Linux/macOS and PowerShell to Windows, to reinforce parity.
- Add a brief note clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and that Bash examples are for Linux/macOS users.
- If possible, provide a single CLI example with notes on shell-specific syntax differences, to reduce duplication and emphasize cross-platform support.
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, PowerShell examples are consistently presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used exclusively, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit bias.
- Explicitly mention that Bash examples are suitable for Linux and macOS users, and PowerShell for Windows users.
- Ensure that any editor instructions (e.g., changing file encoding) include cross-platform guidance (e.g., how to do this on Linux/macOS).
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 cross-platform parity. However, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all commands are based on Azure CLI and Kubernetes, which are cross-platform. There are no missing Linux/macOS examples, and no Windows tools are mentioned.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that both are equally supported.
- Add a brief note at the top clarifying that all steps are fully supported on Linux, macOS, and Windows, and that Bash and PowerShell are shown for user convenience.
- If possible, provide guidance for users who may prefer Zsh or other Unix shells, though Bash is generally sufficient.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. No Windows-specific tools or terminology are prioritized, and Linux parity is maintained throughout. However, the presence of PowerShell examples may suggest a slight bias toward Windows users, but it is mitigated by Bash examples being present and shown first.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for most Linux/macOS users.
- Consider clarifying that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- If possible, add a note at the top explaining which shell to use depending on the user's OS.
- Ensure that any future additions do not introduce Windows-only tools or terminology unless the feature is Windows-specific.
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 consistently lists Azure PowerShell after Azure CLI. While Azure PowerShell is a Windows-centric tool, no Linux-specific shell (e.g., Bash) or platform-neutral examples are given. The focus on PowerShell may create friction for Linux/macOS users, though Azure CLI is cross-platform and featured first.
Recommendations
- Explicitly clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
- Consider including Bash or shell script examples for common tasks, especially for image import, to further improve Linux parity.
- Mention that Azure PowerShell is primarily for Windows users, and direct Linux/macOS users to Azure CLI.
- Add a note about Azure Cloud Shell availability for both CLI and PowerShell, highlighting platform neutrality.
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
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, but PowerShell examples are always shown immediately after Bash, and at times the PowerShell section is more verbose. There is no evidence of Windows-only tools, Windows-specific patterns, or missing Linux/macOS equivalents. The CLI commands are cross-platform and the instructions are equally applicable to Linux/macOS users. However, the presence of PowerShell examples throughout may create a slight impression of Windows prioritization.
Recommendations
- Continue to provide both Bash and PowerShell examples, but consider alternating the order or explicitly stating that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a brief note at the top clarifying that all CLI commands are cross-platform and that Bash is recommended for Linux/macOS users.
- Ensure that any advanced scripting or troubleshooting sections also include Bash equivalents if PowerShell is used.
- If possible, provide a table or summary mapping Bash and PowerShell commands for quick reference.
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 both Azure CLI and Azure PowerShell examples for deploying dashboards, but the PowerShell section is given equal prominence to the CLI section, and PowerShell is specifically called out as a deployment method. While Azure CLI is cross-platform and shown first, the inclusion of a dedicated PowerShell section (which is most commonly used on Windows) may suggest a slight Windows bias. However, there are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks using the Azure CLI or portal. All JSON and template examples are platform-agnostic.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (Windows, macOS, Linux) if included, to avoid the impression that it is Windows-only.
- Consider explicitly stating that Azure CLI commands work on all platforms (Windows, Linux, macOS).
- Optionally, provide Bash or shell script examples for automating deployments on Linux/macOS, or mention that the CLI commands can be used in Bash scripts.
- If space allows, mention that all steps can be completed on Linux/macOS using the Azure CLI or portal, and that PowerShell is optional.
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 Azure CLI is cross-platform, PowerShell is often associated with Windows, and its mention may imply a Windows bias. No explicit Linux/macOS examples or tools are referenced, and PowerShell is listed before Linux-specific alternatives (such as Bash).
Recommendations
- Clarify that Azure Copilot can generate scripts for multiple environments, including Bash and Azure CLI, not just PowerShell.
- Provide explicit examples or mention of Bash script generation for Linux/macOS users.
- Ensure that references to PowerShell are balanced with references to cross-platform tools, and avoid listing Windows-centric tools first unless contextually appropriate.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, but PowerShell examples are given equal prominence to CLI examples, and Windows-specific PowerShell tools are mentioned alongside cross-platform options. The instructions for stopping containers reference 'Ctrl+C', which is universal but often associated with Windows. However, Docker commands themselves are cross-platform and Linux/macOS installation links are included. There are no Linux-specific examples or shell commands (e.g., Bash), and PowerShell is presented as a primary option rather than an alternative.
Recommendations
- Add explicit Bash or Linux shell examples where relevant, especially for authentication and image removal.
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider reordering examples to show Azure CLI first, then PowerShell, to reduce Windows-first bias.
- Include notes or tips for Linux/macOS users, such as alternative ways to stop containers or manage images.
- Add troubleshooting or environment-specific guidance for Linux/macOS users where appropriate.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally and sometimes first, which is a Windows-centric tool. There are no Linux/macOS-specific examples or explicit mentions of Linux tools or shell environments. The CLI examples are cross-platform, but the presence of PowerShell examples and references may create friction for Linux/macOS users. However, all critical tasks can be completed using Azure CLI, which is fully supported on Linux/macOS.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider mentioning Bash or other Linux/macOS shell environments in the prerequisites and examples.
- Add explicit notes or sections for Linux/macOS users, highlighting that Azure CLI commands work natively in Bash and other shells.
- If possible, provide Bash script examples or show CLI commands in Bash syntax (with environment variable usage, etc.).
- De-emphasize PowerShell for general-purpose scenarios unless there is a Windows-specific requirement.
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 registry usage), but consistently lists PowerShell examples alongside or after CLI, without mentioning Linux/macOS equivalents or alternatives (e.g., Bash, shell scripting). Azure CLI is cross-platform, but PowerShell is more commonly associated with Windows. No explicit Linux/macOS-specific guidance or examples are given, and PowerShell is referenced as a primary tool for scripting and management.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly mention that PowerShell examples are primarily for Windows users, and that Bash/shell scripting can be used on Linux/macOS.
- Provide Bash/shell script examples where appropriate, or note that Azure CLI commands can be run in Bash terminals.
- Consider listing Azure CLI examples first, as it is the most universal tool.
- Add a brief section or note about using Azure CLI in Linux/macOS environments.