226
Pages Scanned
55
Pages Flagged
226
Changed Pages
24.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-09 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 226
Files Completed: 226
Problematic Pages
57 issues found
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for migration, with instructions to run it in PowerShell. There are no Linux/macOS shell (Bash) equivalents or guidance for users on non-Windows platforms. The migration script is a .ps1 file, which is natively supported only on Windows, and there is no mention of cross-platform alternatives or compatibility.
Recommendations
- Provide a Bash or cross-platform script for Linux/macOS users, or clarify if PowerShell Core (pwsh) can be used on non-Windows platforms.
- Add explicit instructions for running the migration script on Linux/macOS, including prerequisites (e.g., installing PowerShell Core).
- Mention any limitations or required adaptations for Linux/macOS users if only PowerShell is supported.
- Consider offering a platform-neutral migration tool or script if feasible.
Create Pull Request
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 towards Windows/PowerShell environments. All onboarding scripts and examples are provided only as PowerShell (.ps1) scripts, and users are instructed to use PowerShell terminals. Prerequisites reference Windows-specific tools (winget), and there are no Linux/macOS equivalents or instructions. No Bash, shell, or cross-platform script examples are provided, making it difficult for Linux/macOS users to follow the onboarding process.
Recommendations
- Provide Bash/shell script equivalents for infra_onboarding.ps1 and cm_onboarding.ps1, or document how to run these scripts on Linux/macOS (e.g., via Azure CLI, or with cross-platform scripting).
- List Linux/macOS installation commands for prerequisites (e.g., using apt, brew, or direct downloads for Azure CLI and kubectl) alongside or before Windows-specific commands.
- Clarify whether the onboarding scripts are Windows-only, or if cross-platform support is planned/available.
- If PowerShell Core (pwsh) is supported on Linux/macOS, explicitly state this and provide usage instructions.
- Reorder examples or provide parallel instructions so Linux/macOS users are not left behind.
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
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation generally provides parity between Windows and Linux in terms of feature lists and release notes. However, there is a notable Windows-first bias in several areas: download links for Windows are always listed before Linux, and known issue remediation steps are only provided for Windows (using Command Prompt and PowerShell), with no equivalent Linux troubleshooting guidance. Additionally, Windows-specific tools and patterns (e.g., PowerShell, attrib) are referenced without Linux alternatives, and some improvements reference Windows scripts without Linux equivalents.
Recommendations
- When listing download links or instructions, alternate or parallelize Windows and Linux to avoid implicit prioritization.
- For troubleshooting steps (e.g., editing permissions on config files), provide equivalent Linux commands (such as chmod/chown) and instructions.
- Where Windows-specific scripts or tools are mentioned (e.g., PowerShell, attrib), clarify if Linux users are unaffected or provide the corresponding Linux method.
- Ensure that all known issues and fixes are addressed for both platforms, or explicitly state when an issue is Windows-only.
- Consider including a summary table or section that highlights platform-specific differences, so Linux users can quickly identify relevant information.
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 gives Windows-specific authentication options (interactive browser login and certificate store usage) before Linux equivalents and references Windows tools (PowerShell's Get-AzAccessToken) without mentioning Linux alternatives. However, Linux authentication methods are described, and most examples are cross-platform.
Recommendations
- Clarify that interactive browser login is Windows-only and suggest Linux alternatives more prominently.
- When referencing PowerShell tools (e.g., Get-AzAccessToken), also mention how Linux/macOS users can obtain access tokens (e.g., Azure CLI's 'az account get-access-token').
- Present Linux authentication options (device code, Azure CLI) before or alongside Windows options to avoid Windows-first ordering.
- Add explicit Linux/macOS examples where appropriate, especially for certificate-based authentication (e.g., using PEM files).
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and mentions PowerShell scripting support as a manageability feature. However, it also lists cross-platform tools like Azure CLI and Visual Studio Code. No Linux/macOS-specific examples or tools are highlighted, and Windows tools are presented without Linux alternatives.
Recommendations
- Add examples or references for Linux/macOS-compatible tools (e.g., sqlcmd, Azure Data Studio, mssql-cli).
- Clarify which features/tools are cross-platform and which are Windows-only.
- Provide guidance for Linux/macOS users on managing SQL Managed Instance enabled by Azure Arc, including scripting and automation options.
- Mention or link to documentation for using Azure Arc SQL Managed Instance from Linux/macOS environments.
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
Summary
The documentation is focused on configuring AKS Edge Essentials on Linux, but uses PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration tasks, rather than providing native Linux shell commands. This assumes the user is operating from a Windows environment or using Windows tools to manage Linux nodes, which may not align with the experience of Linux-first administrators.
Recommendations
- Provide equivalent native Linux shell commands for tasks such as checking and setting sysctl parameters (e.g., using 'sysctl' and 'echo' directly in bash).
- Clarify when PowerShell/Invoke-AksEdgeNodeCommand is required and offer alternatives for users managing Linux nodes directly.
- Ensure that all critical configuration steps can be performed using standard Linux tools and document those workflows.
- Consider including a section or callout for users who are managing from a Linux or macOS environment, outlining the appropriate commands.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation frequently presents Windows tools and file paths first (e.g., SSMS, C:\ paths), and omits explicit Linux/macOS examples for key steps such as database backup and file copying. While the core migration process is cross-platform, the guidance assumes a Windows environment for local operations, which may create friction for Linux/macOS users.
Recommendations
- Provide parallel examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) in backup and kubectl cp steps.
- Mention and give examples for common Linux SQL tools (e.g., Azure Data Studio, sqlcmd) alongside or instead of SSMS.
- Clarify that Visual Studio Code and Azure Storage Explorer are cross-platform, and link to their Linux/macOS installation guides.
- When referencing commands or file locations, show both Windows and Linux/macOS variants side by side.
- Explicitly state that the process is platform-agnostic except for tool choice, and offer guidance for non-Windows users.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several signs of Windows bias: PowerShell is referenced for troubleshooting HTTP2 issues, Windows paths are shown in error messages, and some CLI instructions (such as proxy troubleshooting and DNS resolution) use Windows-centric tools (PowerShell, Resolve-DnsName, ping) without offering Linux equivalents. Linux-specific troubleshooting is only mentioned in passing (GLIBC error), and Linux commands (such as ldd --version, nslookup) are not consistently presented alongside Windows commands. Examples and guidance often default to Windows tools and terminology, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., curl for HTTP2 troubleshooting, dig/nslookup for DNS resolution).
- When referencing file paths or error messages, clarify if they are OS-specific and provide Linux/macOS alternatives where relevant.
- Ensure troubleshooting steps and CLI instructions include both Windows and Linux/macOS guidance, especially for proxy, DNS, and network validation.
- Add explicit notes or sections for Linux/macOS users where OS-specific issues may arise (e.g., GLIBC, SSH folder permissions).
- Review and update examples to avoid Windows-first ordering; present cross-platform instructions in parallel.
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents both Linux and Windows onboarding options, but Windows-specific tools and workflows (such as PowerShell, Windows Admin Center, Configuration Manager, and Group Policy) are listed with dedicated methods, while Linux-specific automation tools (other than Ansible) are not. PowerShell is highlighted as a cross-platform tool, but the documentation does not clarify if Linux users can use PowerShell or provide equivalent Bash/shell examples. Windows-specific methods are listed after cross-platform ones, but the presence of multiple Windows-only methods and the lack of Linux-specific automation examples (e.g., Bash scripts, cloud-init, or Linux-native configuration management tools besides Ansible) indicate a moderate Windows bias.
Recommendations
- Add explicit Bash/shell script examples or links for Linux onboarding, especially for interactive and at-scale scenarios.
- Clarify in the PowerShell method whether it is supported and tested on Linux (PowerShell Core), or provide a Linux-native alternative.
- Consider including Linux-native automation options (e.g., cloud-init, shell scripts, or other configuration management tools like Chef/Puppet) if supported.
- Balance the number of Windows-only and Linux-only methods, or clearly indicate when a method is Windows-specific.
- In the table, ensure that for every Windows-specific at-scale method, a Linux equivalent is suggested if available.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment commands and instructions exclusively use Azure PowerShell, with no Azure CLI or Bash equivalents. Additionally, PowerShell deployment commands are presented first and throughout, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Windows file paths are used in sample commands, further reinforcing a Windows-centric approach.
Recommendations
- Add Azure CLI deployment command examples alongside PowerShell, e.g., az deployment group create.
- Include Bash shell usage instructions for Linux/macOS users.
- Present deployment commands for both Windows and Linux platforms in parallel, or clarify that PowerShell is cross-platform.
- Use generic file paths (e.g., ./Templates/...) in examples instead of Windows-specific paths (e.g., D:\Azure\Templates\...).
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
windows_tools
missing_linux_example
Summary
The documentation generally presents Azure Arc and Azure Monitor Agent as cross-platform solutions for both Windows and Linux. However, there is a subtle Windows bias: Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly, while Linux equivalents (such as Cockpit, cloud-init, or Linux-native package managers) are not. PowerShell is referenced before Bash, and there are no concrete Linux-specific deployment examples or tool mentions. The 'Standalone Azure Monitor Agent installation' section only references Windows clients, with no mention of Linux client scenarios.
Recommendations
- Add explicit references to Linux-native deployment tools and methods (e.g., cloud-init, shell scripts, Ansible for Linux, Linux package managers) alongside Windows tools.
- Provide Linux-specific examples or clarify that Bash scripts are supported equally.
- In the 'Standalone Azure Monitor Agent installation' section, clarify the options (or lack thereof) for Linux client devices.
- Where Windows tools are mentioned (e.g., Windows Admin Center, Group Policy), add Linux equivalents or state if none exist.
- Ensure that PowerShell and Bash examples are presented with parity, or clarify when a method is Windows-only.
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 comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a mild Windows bias: Windows examples and tools (such as PowerShell scripts, Msiexec, Control Panel, Group Policy, WSUS, Configuration Manager) are often presented first or in greater detail, and the only cleanup script for stale resources is provided in PowerShell. Linux instructions are present and clear, but advanced automation examples (e.g., scripting for cleanup) are Windows/PowerShell-only.
Recommendations
- Add equivalent Linux shell scripts (e.g., Bash) for resource cleanup and automation tasks, or reference Azure CLI for cross-platform scripting.
- Where possible, present Windows and Linux instructions in parallel, rather than Windows-first.
- Include Linux-specific automation examples for tasks like agent removal, upgrades, and stale resource cleanup.
- Reference cross-platform tools (Azure CLI) before or alongside Windows-specific tools (PowerShell).
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of examples and guidance are heavily skewed toward Windows and PowerShell. PowerShell is used as the primary scripting language in both Azure PowerShell and Azure CLI examples, and REST API samples exclusively use Windows-specific cmdlets (e.g., New-NetFirewallRule) and reference Windows Server resources. There are no Linux shell script examples, and Windows tools (such as New-AzStorageBlobSASToken) are referenced without Linux equivalents. This creates friction for Linux users and makes it unclear how to use the feature with Linux servers.
Recommendations
- Add Linux-focused examples throughout, especially in the Azure CLI and REST API sections. For example, show how to run a Bash script (e.g., 'echo Hello World' or 'id') on a Linux Arc-enabled server.
- In REST API examples, provide at least one scenario using a Linux server (e.g., running a shell script to update packages or configure iptables).
- When referencing tools for generating SAS tokens or managing blobs, mention cross-platform or CLI alternatives (e.g., Azure CLI 'az storage blob generate-sas') and not just PowerShell cmdlets.
- When describing parameter passing, clarify the differences for Linux (e.g., how environment variables or arguments are handled in Bash scripts).
- Ensure that Linux and Windows examples are presented with parity and, where possible, alternate the order or group them together.
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
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides detailed recovery instructions and a script download specifically for Windows, using PowerShell. There are no equivalent instructions, scripts, or guidance for performing the recovery from a Linux or macOS machine. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternative is offered for non-Windows users.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
- If the recovery process is only supported on Windows, clearly state this limitation at the beginning of the article.
- If partial steps can be performed from Linux/macOS (e.g., preparing config files, interacting with Azure CLI), document those to help non-Windows users participate in the process.
- Consider offering a platform-agnostic script (e.g., written in Python or using Azure CLI) if feasible.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs. However, the primary automation script is PowerShell-based, with instructions and examples focused on Windows environments (e.g., PowerShell terminal, Windows Task Scheduler for cron jobs, Set-ExecutionPolicy). Windows tools and patterns are mentioned first and in detail, while Linux equivalents (e.g., cron, shell scripting) are missing or only briefly referenced. Although Linux is acknowledged (e.g., sudo configuration), practical Linux/macOS automation examples are absent.
Recommendations
- Provide equivalent shell script or Bash examples for Linux/macOS users, especially for the automation script.
- Include instructions for running the automation script via cron on Linux, not just Windows Task Scheduler.
- Offer guidance for using PowerShell Core on Linux/macOS, if the script is cross-platform, or clarify Windows-only limitations.
- Ensure that out-of-band methods (e.g., Ansible) are given equal prominence and example detail as Windows-centric methods.
- Add Linux/macOS-specific troubleshooting and prerequisites alongside Windows instructions.
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 provides only PowerShell examples and references, with no mention of Bash, Linux shell, or cross-platform alternatives. All script examples and instructions are PowerShell-centric, and the onboarding script is referenced as a .ps1 file, implying Windows usage. There is no guidance for Linux/macOS users, nor are alternative tools or commands provided.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements for running the onboarding script, and mention if Linux/macOS users can use Azure CLI or other tools.
- Add instructions or links for Linux/macOS users, including how to install prerequisites and run scripts.
- If the onboarding script is Windows-only, recommend using Windows containers or VMs for Linux/macOS users, and clarify this limitation.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1), with no mention of Linux/macOS-compatible alternatives or guidance. All usage examples are PowerShell-based, and there is no indication that the script can be run on Linux or with Bash, nor are cross-platform instructions provided.
Recommendations
- Clarify whether the PowerShell script is compatible with PowerShell Core (pwsh), which runs on Linux/macOS, or if it is Windows-only.
- If the script is cross-platform, provide usage examples for Linux/macOS (using pwsh) and note any prerequisites (such as installing PowerShell Core).
- If the script is Windows-only, explicitly state this limitation in the prerequisites section.
- Consider providing a Bash or Python equivalent script for Linux/macOS users, or instructions for using Azure CLI to achieve the same clean-up tasks.
- Add a note about how Linux/macOS users can perform the clean-up, even if only via Azure CLI or portal.
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 changes and script invocation, but does not offer equivalent Linux/macOS guidance. The script section is Windows-centric, and Linux users are left without clear instructions for running the script or workarounds. Additionally, Windows instructions are presented before Linux ones, and Linux removal steps are less detailed.
Recommendations
- Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any required permission changes.
- Clarify whether the deboarding script is cross-platform or Windows-only. If cross-platform, provide bash/zsh examples and note any OS-specific caveats.
- Ensure parity in detail for uninstalling agents and extensions on Linux, matching the clarity of Windows instructions.
- Consider presenting Windows and Linux instructions side-by-side or in parallel sections to avoid 'windows_first' bias.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page consistently uses PowerShell syntax for Azure CLI commands and references a PowerShell script (bulk_deployment.ps1) for bulk deployment automation. There are no Bash or Linux/macOS shell examples, and the script provided is only in PowerShell, which is natively supported on Windows. This creates friction for Linux/macOS users, who may need to adapt commands or scripts for their environment.
Recommendations
- Provide Azure CLI command examples in Bash syntax as well as PowerShell, or use generic CLI syntax that works across platforms.
- Offer a Bash shell script equivalent to bulk_deployment.ps1, or note how Linux/macOS users can run the PowerShell script (e.g., via PowerShell Core).
- Explicitly state that Azure CLI commands are cross-platform and clarify any OS-specific requirements for scripts.
- Add notes or sections for Linux/macOS users, including troubleshooting tips or alternative approaches.
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 is heavily PowerShell-centric, with nearly all code examples provided in PowerShell syntax and Windows command patterns. Linux/Bash equivalents are missing for most critical steps, except for the 'service groups' section, which offers both Bash and PowerShell tabs. This creates friction for Linux/macOS users, who must translate PowerShell commands or guess the correct Bash syntax.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
- Ensure examples are presented in both Bash and PowerShell tabs throughout the document, not just in the 'service groups' section.
- Avoid using Windows-specific PowerShell constructs (e.g., ConvertTo-Json, Out-File, [Convert]::ToBase64String) without showing how to achieve the same in Bash/Linux.
- Clarify when a command is cross-platform (e.g., az CLI, kubectl, docker) and show the syntax for both environments.
- Review file encoding instructions to ensure they are relevant for Linux/macOS users (e.g., mention how to check/save UTF-8 files in Linux editors).
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 provides nearly all CLI and scripting examples using PowerShell syntax, including backticks for line continuation and explicit PowerShell script usage (.ps1 files). Paths in JSON templates are Windows-style (e.g., C:\Users\...), and no Bash or Linux/macOS shell equivalents are given. The instructions for onboarding, enabling diagnostics, and collecting logs are all shown with PowerShell scripts, creating friction for Linux/macOS users who must adapt these steps. There is no mention of Linux tools or shell patterns, and Windows conventions (paths, PowerShell) are used throughout.
Recommendations
- Provide Bash/sh examples alongside PowerShell for all CLI commands, especially az CLI usage.
- Show Linux/macOS file path conventions in JSON templates (e.g., /home/user/...) or note that paths should be adapted.
- Clarify that .ps1 scripts can be rewritten as Bash scripts, or provide Bash versions if possible.
- Mention cross-platform compatibility for az CLI commands and highlight any Windows-only steps.
- Add notes or sections for Linux/macOS users, including troubleshooting or adaptation tips.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses the Windows-specific 'winget' tool, with no Linux/macOS equivalent provided. In the file extraction section, the Bash example incorrectly uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS, and all example paths are Windows-style. There are no Linux/macOS-specific instructions for these steps, and Windows tools/patterns are mentioned exclusively or first. The rest of the guide uses Azure CLI and PowerShell, which are cross-platform, but the initial setup steps create friction for non-Windows users.
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew', etc.).
- Correct the Bash tab to use native Linux/macOS commands for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/dir').
- Include Linux/macOS file path examples alongside Windows paths.
- Ensure all critical steps have Linux/macOS equivalents and are presented with equal prominence.
- Consider adding a note clarifying cross-platform support and linking to OS-specific guides where appropriate.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI examples primarily using PowerShell syntax, especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown first and exclusively for configuration file operations. There is no mention of Linux/macOS-specific shell usage or parity for these examples, and no explicit guidance for non-Windows users.
Recommendations
- Provide equivalent Bash examples for all CLI commands, especially those shown in PowerShell.
- Add a note clarifying that Azure CLI commands work cross-platform and can be run in Bash, PowerShell, or other shells.
- Ensure that all CLI instructions are presented in both Bash and PowerShell syntax, or use a neutral format where possible.
- Explicitly mention Linux/macOS compatibility for the Azure CLI extension and commands.
Container Registry
Quickstart - Create Geo-Replicated Registry - ARM Template
...ontainer-registry-get-started-geo-replication-template.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation primarily demonstrates deploying and managing the ARM template using the Azure portal, with only brief mentions of Azure PowerShell and Azure CLI as alternative methods. No explicit Linux/macOS-specific instructions or examples are provided, and PowerShell is mentioned before CLI. The cleanup and review steps are portal-centric, lacking command-line parity for Linux/macOS users.
Recommendations
- Add explicit Azure CLI examples for deploying the ARM template, reviewing resources, and cleaning up, as CLI is cross-platform and preferred by many Linux/macOS users.
- Mention Azure CLI before PowerShell when listing cross-platform tools.
- Provide step-by-step instructions for all tasks (deploy, review, clean up) using Azure CLI commands.
- Clarify that all steps can be completed on Linux/macOS using Azure CLI, and link to relevant CLI documentation.
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 every major step, ensuring Linux/macOS and Windows users are supported. However, PowerShell examples are consistently presented after Bash examples, indicating a minor 'windows_first' bias in ordering. There are no Windows-only tools or patterns, and Linux examples are not missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to reinforce parity.
- Ensure that any OS-specific nuances (such as file encoding or base64 commands) are clearly explained for both platforms, as is done here.
- Maintain the current approach of providing both Bash and PowerShell examples for all commands.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first, followed by PowerShell. There are no Windows-specific tools, patterns, or commands used; all orchestration is performed via the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively or before their Linux equivalents. The only minor bias is the ordering of Bash before PowerShell, which is actually favorable to Linux/macOS users.
Recommendations
- No changes needed. Both Bash and PowerShell examples are provided, ensuring parity for Linux/macOS and Windows users.
- Maintain the current approach of providing cross-platform Azure CLI examples.
- If desired, clarify in the prerequisites that Azure CLI is supported on Windows, Linux, and 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 operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash examples, rather than exclusively or before Bash. There are no Windows-specific tools or patterns used, and all commands are cross-platform (Azure CLI, kubectl). No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is achieved.
- Consider alternating the order of Bash and PowerShell tabs in future documentation to avoid minor 'windows_first' bias.
- Explicitly note that Azure CLI and kubectl commands are cross-platform and can be used on Linux, macOS, and Windows.
- If possible, add a brief note for macOS users regarding any prerequisites (e.g., installing Azure CLI, kubectl) to further improve inclusivity.
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 this does not exclude Linux/macOS users, PowerShell is a Windows-centric tool and is mentioned before Bash or other Linux-native shells. No explicit Linux/macOS examples or tools are referenced, and no Bash-specific guidance is provided.
Recommendations
- Explicitly mention Bash or shell script generation alongside PowerShell and CLI.
- Provide examples or clarify that Azure Copilot can generate scripts for Bash and other Linux/macOS shells.
- Ensure parity in script generation examples, showing both PowerShell and Bash where relevant.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring parity between 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, patterns, or terminology are used, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for CLI commands.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows, to reinforce cross-platform support.
- Ensure screenshots and portal instructions are not Windows-specific (they are not in this page).
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is largely cross-platform, as Helm and Azure CLI are available on Windows, Linux, and macOS. However, there are minor signs of Windows bias: the environment variable example uses the Windows 'set' command, and the order of Kubernetes cluster creation options lists Azure PowerShell before Linux-friendly alternatives. No Linux/macOS-specific shell examples (e.g., 'export', bash syntax) are provided alongside Windows commands, which may cause friction for non-Windows users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') environment variable examples when setting variables like ACR_NAME.
- When listing options for creating AKS clusters, mention Azure CLI (cross-platform) before Azure PowerShell (Windows-centric), or clarify platform compatibility.
- Add notes or code blocks indicating that Azure CLI and Helm commands are cross-platform, and provide explicit bash/zsh syntax where relevant.
- Review all code snippets to ensure they work as-is on Linux/macOS, or provide alternative commands where necessary.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd) and labels them as 'powershell', which may confuse Linux/macOS users. There are no explicit Linux/macOS shell examples, and PowerShell is used as the default for command snippets. However, most commands are cross-platform (kubectl, yaml, sqlcmd), but the labeling and example order suggest a Windows-first bias.
Recommendations
- Replace 'powershell' code block labels with 'console' or 'bash' where appropriate, especially for kubectl and sqlcmd commands that are cross-platform.
- Add explicit Linux/macOS shell examples or clarify that the commands work on all platforms.
- Ensure that instructions for decoding base64 secrets mention common Linux/macOS tools (e.g., 'base64 -d') alongside any Windows-specific guidance.
- Avoid labeling cross-platform commands as 'powershell' unless there is actual PowerShell-specific syntax.
- Consider showing Linux/macOS examples first or in parallel with Windows examples.
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 references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before the cross-platform sqlcmd tool. However, it does provide a sqlcmd example for both Linux and Windows, and does not exclusively use Windows tools or patterns. The bias is minor, mainly in the ordering and emphasis of Windows tools.
Recommendations
- Mention cross-platform tools (such as Azure Data Studio) alongside SSMS, and list them first or equally.
- Provide explicit examples for connecting from macOS and Linux, including GUI options.
- Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links.
- Consider adding a note about Azure Data Studio as a cross-platform alternative to SSMS.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There are Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl), and Linux installation instructions for curl are less explicit than Windows. There is also a PowerShell-specific note about curl aliasing, but no equivalent Linux/macOS shell notes.
Recommendations
- List installation links for all platforms in parallel order (e.g., Windows, Linux, macOS) or rotate the order to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl' for Ubuntu) rather than just 'install curl package'.
- Add shell-specific notes for Linux/macOS where relevant, similar to the PowerShell note for curl.
- Ensure examples and notes reference all major platforms equally, not just Windows-specific behaviors.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows-specific certutil tool is mentioned after the Linux base64 command. The Windows example includes additional steps for removing headers, which are not discussed for Linux. All other instructions and examples use cross-platform tools (OpenSSL, Azure CLI, kubectl) and are not Windows-specific.
Recommendations
- Explicitly mention macOS compatibility for base64 and OpenSSL commands.
- Provide equivalent Linux/macOS commands for removing certificate headers (e.g., using grep or sed), as done for Windows with findstr.
- Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider showing Linux/macOS and Windows commands side-by-side for encoding and header removal, rather than listing Windows separately.
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
Summary
The documentation is largely cross-platform, focusing on Azure CLI and kubectl commands, which are available on Windows, Linux, and macOS. However, there is a minor bias in the ordering of installation instructions for Azure kubelogin, where Windows and Mac are mentioned first, and Linux instructions are provided separately. There are no PowerShell-specific examples, but Azure CLI is used throughout, which is cross-platform. No Windows-only tools or patterns are mentioned, and Linux/macOS users can complete all tasks described.
Recommendations
- Present installation instructions for Azure kubelogin for Linux, macOS, and Windows in parallel or in a single section, rather than listing Windows/Mac first.
- Explicitly state that all Azure CLI and kubectl commands are cross-platform and provide links to installation instructions for Linux/macOS where relevant.
- Where possible, add notes or links for Linux/macOS users about any OS-specific nuances (e.g., file paths, SSH access).
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical steps, but PowerShell examples are consistently presented alongside CLI, sometimes with more detail. Azure PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since Linux-native tools (like Bash scripts or shell commands) are not referenced. However, Azure CLI is cross-platform and the examples use standard environment variables for proxy configuration, which are compatible with Linux/macOS. There are no Windows-only tools or instructions, and the documentation does not prioritize Windows tools over Linux equivalents, but PowerShell is always present.
Recommendations
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows.
- Add clarifying statements that Azure PowerShell is primarily for Windows, while Azure CLI is cross-platform.
- Consider including Bash script examples or referencing Linux/macOS shell environments where relevant.
- Ensure that environment variable examples use syntax for both Windows (PowerShell) and Linux/macOS (Bash).
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 32-bit and 64-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-only commands or tools, nor does it exclude Linux/macOS users from completing the tasks. The CLI commands shown are cross-platform, but the management machine requirements and CLI installation links could be clearer about Linux/macOS compatibility.
Recommendations
- Add explicit mention that Azure CLI is supported on Linux and macOS, and provide installation links for those platforms.
- Clarify whether 32-bit/64-bit requirements apply to Linux/macOS or are Windows-specific.
- Include a note that the az arcappliance extension and commands are cross-platform unless there are known limitations.
- If possible, provide example CLI installation commands for Linux/macOS alongside Windows.
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 parity between Windows and Linux for most Azure Arc gateway operations, including CLI and PowerShell examples, and explicitly mentions Linux-specific endpoints. However, Windows/PowerShell examples are sometimes presented before Linux equivalents, and there are minor references to Windows tools (e.g., PowerShell, Windows Admin Center) before Linux tools. The documentation does not omit Linux instructions, but the ordering and emphasis slightly favor Windows.
Recommendations
- Ensure that CLI examples are presented before PowerShell examples, or provide both simultaneously, to avoid Windows-first ordering.
- Where possible, clarify that CLI commands work on both Windows and Linux, and explicitly state OS-agnostic instructions.
- When referencing tools like Windows Admin Center, also mention comparable Linux management tools or clarify if none exist.
- Review ordering in tabbed sections to ensure Linux/CLI is not always secondary to Windows/PowerShell.
- Continue to highlight Linux-specific endpoints and installation requirements, as done with 'packages.microsoft.com'.
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, but there is a notable Windows bias: Windows NTP server (time.windows.com) is mentioned specifically, and several endpoints (e.g., login.windows.net, sts.windows.net, servicebus.windows.net) use 'windows' in their domain names. The Windows NTP server is described as the default for Hyper-V, but no Linux NTP server example is provided. Additionally, Windows-related endpoints are listed before Linux-specific ones (e.g., Microsoft open source packages manager for Linux appears later in the table). There are no PowerShell-only examples or instructions, but the ordering and endpoint naming favor Windows.
Recommendations
- Add Linux NTP server examples (e.g., ntp.ubuntu.com or pool.ntp.org) alongside time.windows.com, clarifying when each is used.
- Explicitly mention that appliance VMs and management machines can be Linux-based, and provide guidance for Linux environments where relevant.
- Reorder the endpoint tables to avoid listing Windows-specific endpoints first unless required by the deployment sequence.
- Where endpoints are Windows-branded but required for all platforms, clarify their cross-platform relevance.
- Add notes for Linux users about any differences in network configuration or required tools.
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 covers both Linux and Windows platforms for the Azure Connected Machine agent, but there is a mild Windows bias. Windows tools and terminology (e.g., Windows Admin Center, Windows installation package) are mentioned before Linux equivalents in several places. Windows-specific resources and features (such as Windows Admin Center and Windows Server benefits) are referenced more frequently and often appear first in lists and tables. However, Linux is also addressed, and Linux-specific URLs and OpenSSL are mentioned, so Linux users can complete the task without significant friction.
Recommendations
- Present Linux and Windows examples/resources in parallel or alternate their order to avoid Windows-first bias.
- Add explicit Linux configuration guidance or troubleshooting links where Windows-specific troubleshooting is provided (e.g., for TLS issues).
- Clarify when features/tools are Windows-only to avoid confusion for Linux users.
- Where Windows Admin Center is referenced, provide Linux alternatives or note that it is Windows-specific.
- Ensure parity in documentation for proxy configuration, firewall rules, and cryptographic protocol guidance 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 most sections. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. In some sections, Windows is mentioned first (e.g., 'Windows and Linux'), and PowerShell is presented alongside CLI, but not with Linux-native tools. The CLI examples are cross-platform, but Linux-specific shell examples (bash, zsh) are not shown explicitly.
Recommendations
- Explicitly state that Azure CLI commands work in Linux shells (bash, zsh) and provide sample commands in those contexts.
- Consider providing sample scripts or command sequences for common Linux shell environments (e.g., bash) to demonstrate parity.
- Where PowerShell is referenced, clarify its availability on Linux (PowerShell Core), or provide links to Linux installation instructions.
- When listing supported tools, avoid always mentioning Windows first; alternate or use 'Linux and Windows' where appropriate.
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, including separate tables for each OS and links to relevant resources. However, Windows extensions are listed first, which may subtly signal Windows as the primary platform. All deployment methods (CLI, PowerShell, portal, templates) are mentioned equally, and partner extensions are shown for both OSes. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or explicitly state that both are equally supported.
- Add a brief introductory statement clarifying that all extension management methods and most extensions are available for both Windows and Linux, to reinforce parity.
- Ensure that CLI and PowerShell guides referenced in the 'Related content' section provide Linux-specific examples where appropriate.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed and visually emphasized (with a screenshot). The Linux/Bash example is present and functional, but is shown after the Windows example. References to Azure CLI are only in the 'Related content' section, and the main workflow focuses on PowerShell for Windows.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
- Ensure equal detail and visual emphasis (screenshots, explanations) for both Windows and Linux examples.
- Mention Azure CLI as a cross-platform tool for relevant tasks in the main workflow, not just in 'Related content'.
- Clarify that both Windows and Linux are fully supported throughout the article, especially in introductory sections.
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 provides troubleshooting guidance for both Windows and Linux, including error codes, exit codes, and log locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. There is a minor bias in presenting Windows tools and paths (e.g., `%ProgramData%`, PowerShell commands) before Linux equivalents, but Linux parity is maintained throughout with equivalent examples and instructions.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Explicitly mention Linux log file locations and commands before or alongside Windows equivalents.
- Where possible, provide cross-platform command syntax in a unified table or section.
- Ensure troubleshooting steps reference both Windows and Linux paths/tools equally.
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, indicating a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a brief note clarifying that az CLI and Helm commands are fully supported on Linux/macOS and Windows.
- Ensure that any future examples or troubleshooting steps include both Bash and PowerShell variants.
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 before Linux equivalents in several sections. The retry command for Windows is shown first, and the Windows-specific PowerShell execution policy step is detailed, while Linux instructions are more concise. However, Linux parity is generally maintained, with clear Bash instructions and references.
Recommendations
- Present Windows and Linux instructions in parallel or in a tabbed format to avoid implicit prioritization.
- Ensure that Linux-specific troubleshooting or preparatory steps (e.g., script permissions, required packages) are as detailed as Windows steps.
- Consider listing Linux instructions before Windows in some sections, or alternating order to demonstrate equal support.
- Add explicit confirmation that both PowerShell and Bash scripts are functionally equivalent and supported.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there are minor instances of Windows bias: PowerShell is listed before other automation tools in the SDKs/tools section, and some links (such as Azure Automation and AVS onboarding) default to Windows examples or tabs. Windows-specific features are referenced, but these are appropriate given Azure's hybrid focus and the nature of VMware environments.
Recommendations
- Ensure Linux CLI and Bash examples are provided alongside PowerShell in automation sections.
- Where links default to Windows tabs, add explicit references or links to Linux/macOS instructions.
- When listing tools (CLI, PowerShell, SDKs), alternate order or clarify cross-platform support.
- Highlight Linux support in onboarding and management scenarios, especially in quick start guides.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but consistently presents Bash examples first. However, the PowerShell examples are equally comprehensive and not prioritized over Bash. There is no evidence of Windows-only tools or patterns, and the Azure CLI commands are cross-platform. The documentation does not mention Linux-specific tools or workflows, but Linux users can follow all instructions without friction.
Recommendations
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, and Windows.
- Consider adding a brief note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows or PowerShell Core on other platforms.
- If possible, provide a short section on running Azure CLI commands in Linux/macOS environments (e.g., installation, shell 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, in each section, Bash examples are consistently shown before PowerShell, which is a minor bias in favor of Linux/macOS users ('windows_first' bias reversed). No evidence of Windows-only tools, missing Linux examples, or exclusive Windows patterns is found.
Recommendations
- No action needed for Linux parity. If desired, alternate the order of Bash and PowerShell tabs in different sections to balance visibility.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
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, and the PowerShell cmdlets are shown immediately after the CLI section. There are no explicit Linux/macOS-specific instructions or notes, and the PowerShell section does not clarify that PowerShell Core is cross-platform. The CLI examples are cross-platform, but the presence of a dedicated PowerShell section may give the impression of a Windows bias, especially since PowerShell is often associated with Windows environments.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and recommended for Linux/macOS users.
- Add a brief note that Azure PowerShell is available on all platforms via PowerShell Core, or clarify if any examples require Windows PowerShell.
- Consider listing Azure CLI as the primary or default method for automation, with PowerShell as an alternative.
- If possible, add a short section or note confirming that all steps are supported on Linux/macOS, and that no Windows-specific tools are required.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are always shown after Bash. There is no evidence of Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. No Windows-specific tools or terminology are used, and Linux/macOS users can follow the Bash instructions without issue. However, the presence of PowerShell examples throughout may suggest a slight Windows bias, as PowerShell is primarily used on Windows, though it is available cross-platform.
Recommendations
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, or for users who prefer PowerShell.
- If possible, add a note at the top explaining that both Bash and PowerShell are supported on all platforms, but Bash is the default for Linux/macOS.
- Ensure that Bash instructions are complete and do not reference Windows-only concepts.
- If usage statistics show most users are on Linux/macOS, consider showing Bash examples first and PowerShell examples as optional.
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, but PowerShell examples are consistently shown after Bash. There are no Windows-only tools or patterns used, and all commands are based on cross-platform Azure CLI and Helm. No Windows-specific tools or behaviors are mentioned. Linux parity is strong, but Bash examples are always shown first, which is a minor bias.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid always showing Bash first.
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a note clarifying that PowerShell examples are for Windows or PowerShell Core users, while Bash is for Linux/macOS or Windows users with WSL.
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 presents Azure CLI (Linux/macOS-friendly) examples first. However, the PowerShell example is given equal prominence, and there are no Linux-specific shell examples (e.g., Bash scripts) or explicit references to Linux tools. The documentation does not mention Windows-specific tools or patterns outside of PowerShell, nor does it prioritize Windows tools over cross-platform ones. Overall, the bias is minimal and mostly limited to the inclusion of PowerShell as a primary example, without Linux shell equivalents.
Recommendations
- Add Bash shell script examples for common tasks, such as importing images, to improve parity for Linux/macOS users.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Consider including a table or section summarizing tool availability and platform compatibility.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for those platforms.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is consistently presented as a primary or equal method, and is referenced throughout tables and sections. CLI examples are cross-platform, but PowerShell is not, and its prominence may confuse or frustrate Linux/macOS users. Additionally, the documentation refers to 'Connect-AzContainerRegistry' and other PowerShell cmdlets without clarifying their Windows-centric nature. However, Linux/macOS users can complete all tasks using Azure CLI and Docker, and there are some mentions of alternative tools like podman.
Recommendations
- Clearly indicate that Azure PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Present Azure CLI examples before PowerShell in tables and sections, or group them under OS-specific tabs.
- Reduce the prominence of PowerShell in general explanations unless the feature is Windows-only.
- Explicitly state that all tasks can be completed with Azure CLI and Docker (or podman), and provide links to cross-platform installation guides.
- Consider adding a short section or callout for Linux/macOS users, summarizing the recommended tools and commands.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently lists PowerShell examples immediately after CLI, and references PowerShell as a primary tool alongside CLI. There are no explicit Windows-only tools or commands, and Azure CLI is cross-platform. However, PowerShell is traditionally associated with Windows, and its inclusion may signal a slight Windows bias, especially since no Bash or Linux-specific shell examples are provided. The documentation does not mention Linux/macOS tools or patterns, nor does it provide Bash or shell script equivalents.
Recommendations
- Add Bash or shell script examples for common import scenarios, especially since Azure CLI is cross-platform and widely used on Linux/macOS.
- Clarify that Azure CLI commands can be run on Linux/macOS, and provide guidance for those environments (e.g., installation links, shell usage).
- Consider referencing Linux/macOS environments explicitly in prerequisites and examples to reinforce parity.
- If PowerShell is included for completeness, note that it is available cross-platform, but also provide Bash alternatives.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for both Azure CLI and PowerShell, but PowerShell is mentioned alongside CLI in the initial deployment section and is given its own example. The instructions for opening a terminal reference Visual Studio Code (cross-platform), but the key combination (ctrl + `) is Windows-centric. PowerShell is included as a primary option, which is more common on Windows, while Bash or Linux-specific instructions are not explicitly highlighted. There are no Linux/macOS-specific examples or explicit mention of Bash terminals, and PowerShell is presented as a first-class option.
Recommendations
- Add explicit Bash/Linux/macOS terminal instructions alongside PowerShell and Azure CLI.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide Bash-specific guidance where relevant.
- Mention common Linux/macOS terminal key combinations for opening the integrated terminal in Visual Studio Code.
- Consider showing Azure CLI (Bash) examples first, or at least equally with PowerShell.
- Add a note that PowerShell is available cross-platform, but Bash is the default shell on Linux/macOS.
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 authentication/removal examples, with PowerShell examples given equal prominence. However, PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create a perception of Windows bias. Additionally, keyboard shortcuts for stopping containers ('Ctrl+C') are described generically but may be more familiar to Windows users. The order of listing installation links (macOS, Windows, Linux) and the use of PowerShell tabs may also subtly favor Windows users.
Recommendations
- Ensure that Linux/macOS users are equally represented by providing Bash or shell script examples where appropriate, especially for automation scenarios.
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for non-Windows environments.
- Consider adding explicit Bash examples for authentication and image removal, or note that Azure CLI commands are suitable for Linux/macOS.
- If PowerShell is included, mention that it is available cross-platform (via PowerShell Core), but clarify its typical usage scenarios.
- Review the order of installation links and examples to avoid subtle Windows-first ordering.