226
Pages Scanned
51
Pages Flagged
226
Changed Pages
22.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-10 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
54 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 (WOGAMigration.ps1) for the migration process and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. There is no guidance for Linux/macOS users, nor is there an equivalent script or instructions for non-Windows environments.
Recommendations
- Provide a Bash or shell script equivalent for Linux/macOS users.
- Document how to run the migration on Linux/macOS, including prerequisites and any required tools.
- If the PowerShell script is cross-platform (PowerShell Core), clarify this and provide instructions for installing/running PowerShell on Linux/macOS.
- Explicitly state platform requirements and offer alternatives or workarounds for non-Windows users.
Create Pull Request
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 deployment tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly, while Linux equivalents (such as Cockpit, Linux graphical installers, or Linux-native management tools) are not. PowerShell is referenced as a deployment scripting option before Bash, and Windows deployment methods are described in more detail. Linux-specific examples, tools, or workflows are missing or less prominent.
Recommendations
- Add explicit Linux deployment examples and tools, such as using Ansible, shell scripts, or Linux-native graphical installers.
- Provide Bash/Linux command-line examples alongside PowerShell, ensuring parity in scripting guidance.
- Mention Linux management tools (e.g., Cockpit, systemd, cron) where relevant, not just Windows Admin Center.
- Ensure that Linux deployment options are described with equal detail and prominence as Windows options.
- Include links to Linux-specific documentation and prerequisites for Azure Arc and Azure Monitor Agent.
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 both Linux and Windows ARM template examples for all VM extensions, ensuring parity in template content. However, all deployment instructions and sample commands exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. Windows file paths are used in sample commands, further reinforcing Windows-first patterns.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployments (e.g., az deployment group create).
- Include Bash shell usage notes or examples for Linux/macOS users.
- Use generic file paths (e.g., ./Templates/filename.json) in examples instead of Windows-specific paths.
- Explicitly mention that both PowerShell and CLI are supported, and link to CLI documentation where relevant.
- Consider presenting CLI and PowerShell examples side-by-side or alternating which is shown first.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is focused on preparing Linux with AKS Edge Essentials, but uses Windows-centric tools and patterns (Invoke-AksEdgeNodeCommand) for Linux system configuration. There are no native Linux shell examples for critical sysctl configuration steps, and Notepad is mentioned as a text editor, which is Windows-specific.
Recommendations
- Provide native Linux shell command examples for sysctl configuration (e.g., using sudo sysctl and echo/tee directly in Bash).
- Replace or supplement Notepad references with Linux text editors (e.g., nano, vim, or gedit).
- Clarify when Windows tools are required, and offer Linux-native alternatives for all steps where possible.
- Ensure all critical configuration steps can be completed using standard Linux commands, not only via Windows/PowerShell tools.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page primarily references Windows-centric tools and patterns, such as SQL Server Management Studio (SSMS) and Azure CLI commands for VM networking, without providing parity for Linux/macOS users. While sqlcmd is mentioned as cross-platform, SSMS is Windows-only and is listed first. There are no examples for Linux-native GUI clients (e.g., Azure Data Studio), nor are there explicit instructions for Linux/macOS users regarding firewall/network configuration or alternative tools.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio or DBeaver alongside SSMS, and provide examples for their use.
- Provide explicit instructions or examples for connecting from Linux/macOS, including any differences in authentication or networking.
- Clarify that sqlcmd is available on Linux and macOS, and provide installation guidance or links for those platforms.
- If network/firewall configuration is required, note any Linux/macOS-specific steps or tools (e.g., using SSH tunneling if NSG rules are not feasible).
- Avoid listing Windows-only tools (SSMS) first; instead, present cross-platform options equally.
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, but does not offer equivalent Linux/macOS shell examples. The PowerShell examples are shown first and exclusively, which may create friction for Linux/macOS users, especially since Azure Arc-enabled data services are cross-platform and often deployed on Kubernetes clusters running Linux.
Recommendations
- Add Linux/macOS shell (bash) examples alongside PowerShell for commands such as kubectl exec and sqlcmd.
- Explicitly mention that sqlcmd and kubectl commands can be run from any OS, and provide syntax for both Windows (PowerShell) and Linux/macOS (bash).
- Avoid using PowerShell-specific syntax (e.g., backticks, variable interpolation) unless the example is clearly labeled as Windows-only.
- Where possible, show bash examples first or equally alongside PowerShell to reinforce cross-platform parity.
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 file paths primarily for Windows environments (e.g., C:\Backupfiles\test.bak), and does not offer equivalent Linux/macOS examples for backing up databases or copying files. Tools like Visual Studio Code and Azure Storage Explorer are cross-platform, but the backup and file copy steps are shown only with Windows-style paths and commands, which may confuse or hinder Linux/macOS users.
Recommendations
- Include Linux/macOS equivalents for file paths in backup examples (e.g., /home/user/backup/test.bak).
- Show both Windows and Linux/macOS examples for the BACKUP DATABASE command and kubectl cp usage.
- Explicitly state that the steps apply to all platforms, and clarify any platform-specific differences.
- Add notes or callouts where tool usage or file system conventions differ between Windows and Linux/macOS.
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 examples and notes are often presented first or in more detail. For 'kubectl', Windows installation is listed first, and there is a specific note about using cmd.exe instead of PowerShell for curl. For 'curl', Windows is explicitly linked, while Linux is mentioned only as 'install curl package' without a link or command. There is also a PowerShell-specific note about curl aliasing, but no equivalent Linux/macOS shell guidance.
Recommendations
- Present Linux/macOS installation instructions and links before or alongside Windows, not after.
- For 'curl', provide explicit Linux/macOS installation commands (e.g., 'sudo apt install curl', 'brew install curl') and relevant links.
- Add shell-specific notes for Linux/macOS users (e.g., bash/zsh) similar to the PowerShell note.
- Ensure parity in detail and clarity for Linux/macOS instructions, not just Windows.
- Consider a platform-neutral table or section, or clearly separate instructions by OS.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_authentication
windows_first
Summary
The documentation page lists several Windows-centric tools and features, such as PowerShell scripting support, SQL Server Management Studio (SSMS), SQL Server Data Tools (SSDT), and Windows Authentication. While Azure CLI and Visual Studio Code are mentioned, Windows tools are referenced more frequently and prominently. PowerShell scripting is highlighted as a manageability feature, and Windows Authentication is listed as a supported security feature, with no mention of Linux/macOS alternatives or parity. The tools table includes multiple Windows-only tools, and PowerShell is referenced in both manageability and unsupported features sections.
Recommendations
- Add explicit examples or guidance for Linux/macOS users, such as using Bash scripting or cross-platform tools.
- Clarify which tools are cross-platform and which are Windows-only, and provide alternatives for Linux/macOS where possible.
- Mention authentication options available for Linux/macOS users, such as Microsoft Entra ID or SQL Authentication, and note any limitations.
- Include links to documentation for using Azure Arc SQL Managed Instance from Linux/macOS environments.
- Reorder tool lists to avoid Windows-first bias and highlight cross-platform tools equally.
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
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation includes references to Windows-specific services (e.g., time.windows.com for NTP, sts.windows.net, login.windows.net, servicebus.windows.net) and Windows terminology (e.g., 'Management machine' and 'Hyper-V default is Windows NTP') without always providing Linux equivalents or clarifying cross-platform applicability. Windows NTP is mentioned, but Linux NTP alternatives are not. Windows-related endpoints appear before Linux-specific ones (e.g., Microsoft open source packages manager for Linux is listed after Windows NTP). However, SSH and Kubernetes API server ports are documented, which are cross-platform.
Recommendations
- Clarify that NTP can use Linux NTP servers (e.g., pool.ntp.org) and provide Linux-specific guidance alongside Windows NTP.
- Where Windows-specific endpoints are mentioned (e.g., sts.windows.net, login.windows.net), explain their relevance for Linux deployments or provide Linux alternatives if applicable.
- Ensure Linux tools and endpoints (such as packages.microsoft.com) are given equal prominence and not listed after Windows-specific items.
- Explicitly state that the management machine and appliance VM can be Linux or Windows, and provide any OS-specific requirements or examples.
- Add notes or examples for Linux-based management machines and appliance VMs where relevant.
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 indications of Windows bias: PowerShell is used for network troubleshooting (e.g., Invoke-WebRequest, Resolve-DnsName) without equivalent Linux/macOS commands; Windows paths and error messages are shown first or exclusively; and some CLI instructions reference Windows-specific patterns (e.g., uninstalling Azure CLI via installer, referencing C:\Program Files). Linux-specific troubleshooting (such as using curl, nslookup, or ldd) is mentioned only in a few places and often as an afterthought. There are missing Linux/macOS equivalents for several diagnostic steps, especially for proxy, DNS, and network validation.
Recommendations
- Provide Linux/macOS command equivalents for all PowerShell examples (e.g., use curl or wget for HTTP troubleshooting, dig or nslookup for DNS).
- When referencing file paths or error messages, include both Windows and Linux/macOS formats.
- Ensure CLI installation/downgrade instructions cover both Windows and Linux (e.g., apt, yum, brew, pip).
- Add troubleshooting steps for Linux/macOS environments, especially for proxy and network configuration.
- Where PowerShell is used, offer Bash or shell script alternatives.
- Review all troubleshooting steps for platform neutrality and parity.
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 provides both Windows and Linux parity for most features and bug fixes, but exhibits Windows bias in several areas. Windows download links and version numbers are consistently listed first. Windows-specific troubleshooting steps (e.g., using Command Prompt and PowerShell commands) are provided, while Linux equivalents are missing for similar issues. Windows tools (attrib, PowerShell, msiexec) are referenced without Linux alternatives. Some known issues and installation guidance are Windows-only, with no Linux troubleshooting guidance.
Recommendations
- When listing download links, alternate the order or present both Windows and Linux equally.
- For troubleshooting steps, provide Linux equivalents (e.g., chmod/chown for file permissions, shell commands for agent configuration).
- Include Linux-specific known issues and solutions where relevant.
- Reference Linux tools and commands alongside Windows tools when discussing installation, configuration, or troubleshooting.
- Ensure that bug fix explanations and feature descriptions are equally detailed for both platforms.
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 provides deployment options for the Azure Connected Machine agent, covering both Linux and Windows. However, several onboarding methods are Windows-specific (e.g., Windows Admin Center, Group Policy, Configuration Manager), and PowerShell is highlighted as a cross-platform tool but is more commonly associated with Windows. Windows-specific tools and methods are listed separately and in greater detail, and PowerShell-based onboarding is mentioned before Linux-native alternatives (e.g., Bash, Ansible). There are no Linux-only onboarding methods or examples provided, and Linux-native automation tools (other than Ansible) are missing.
Recommendations
- Add Linux-specific onboarding examples, such as Bash scripts or instructions using native Linux tools.
- Clarify which PowerShell methods are cross-platform and provide equivalent Bash or shell script examples for Linux users.
- Include Linux-native automation options (e.g., using shell scripts, cron jobs, or other configuration management tools like Puppet or Chef).
- Ensure that Linux onboarding methods are described with equal detail and prominence as Windows methods.
- Consider listing Linux and Windows methods in parallel, rather than grouping Windows-specific options at the end.
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, uninstall, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and instructions are often presented first, PowerShell scripts are used for automation and cleanup tasks without equivalent Bash or shell scripts for Linux, and Windows-specific tools (such as Group Policy, WSUS, Configuration Manager, Control Panel, and Msiexec) are described in detail while Linux equivalents are not discussed or are presented more briefly. The cleanup script for stale resources is only provided in PowerShell, leaving Linux users without a native example.
Recommendations
- Provide Linux shell script equivalents for automation tasks, such as cleanup of stale Arc-enabled server resources.
- Present Linux and Windows instructions in parallel or alternate their order to avoid always showing Windows first.
- Expand Linux sections to include more detail about package management, update automation, and system tools (e.g., using cron for scheduled upgrades, or systemd for service management).
- Where Windows-specific tools are discussed (e.g., Group Policy, WSUS), mention Linux alternatives or clarify their absence.
- Include Bash or shell script examples for tasks currently only shown in 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 provides extensive PowerShell examples and references to Windows tools (such as New-NetFirewallRule and New-AzStorageBlobSASToken), with Windows-centric scripting and REST API scenarios. While the Azure CLI section is present, its examples use Windows PowerShell syntax (Write-Host) and do not demonstrate Linux shell scripting. The REST API section is exclusively Windows-focused, showing only Windows Server scenarios and Windows firewall configuration. There are no Linux-specific script examples, and Windows tools are referenced before Linux equivalents.
Recommendations
- Add Linux-specific script examples in Azure CLI and PowerShell sections (e.g., bash or sh scripts, Linux command usage).
- In REST API examples, include a Linux scenario (such as configuring iptables or ufw for firewall rules) alongside the Windows example.
- When referencing tools for generating SAS tokens or managing blobs, mention cross-platform alternatives or clarify if the tool is Windows-only.
- Ensure CLI examples use cross-platform syntax (e.g., echo instead of Write-Host) and provide both Windows and Linux script samples.
- Balance the order of examples so that Linux and Windows are treated equally, or explicitly state when an example is Windows-only.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exclusively provides PowerShell examples and references a .ps1 onboarding script, with no mention of Bash, Linux shell, or cross-platform alternatives. All scripting and command-line instructions assume a Windows environment, creating friction for Linux/macOS users who may need to perform disaster recovery operations for Azure Arc-enabled VMware vSphere environments.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements for the onboarding script (e.g., if it requires Windows/PowerShell, mention this up front).
- If possible, offer a platform-agnostic onboarding script or instructions for running the script on Linux/macOS (e.g., via PowerShell Core or Azure CLI).
- Add notes or links to Linux/macOS guidance for Azure Arc resource bridge disaster recovery.
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 exhibits notable Windows bias, particularly in the 'Auto Arc-enablement script' section, where only PowerShell examples and Windows Task Scheduler are provided for automation. Windows-centric tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively, with no Linux/macOS equivalents or examples. While Linux is referenced in prerequisites and out-of-band methods, the primary scripted automation path is Windows-only, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, especially for the automation script.
- Include instructions for running the automation script as a cron job on Linux (using crontab), not just Windows Task Scheduler.
- Clarify whether the helper script (.ps1) can be run cross-platform (e.g., with PowerShell Core), or provide a platform-neutral version.
- Add examples for Linux/macOS terminals where PowerShell is referenced.
- Ensure parity in automation and scheduling guidance for both Windows and Linux environments.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed instructions and examples for Windows users, especially when running the deboarding script, including PowerShell-specific guidance and troubleshooting. Linux users are not given equivalent instructions for running the script, nor is there mention of how to execute the script on Linux/macOS. Windows instructions and examples are presented first and in greater detail.
Recommendations
- Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites and command examples (e.g., using Bash, Azure CLI, or PowerShell Core).
- Clarify whether the deboarding script is cross-platform or Windows-only; if it is cross-platform, provide Linux/macOS usage guidance.
- Present Windows and Linux instructions in parallel sections or tables for parity.
- Mention any requirements or limitations for Linux/macOS users (e.g., PowerShell Core compatibility, Azure CLI usage).
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) as the only provided automation example. There are no Bash or Linux/macOS shell examples, and the script is only available in PowerShell. This creates friction for Linux/macOS users, who may not have PowerShell installed or prefer Bash scripting.
Recommendations
- Provide Azure CLI command examples in Bash syntax as well as PowerShell, or use generic CLI syntax that works cross-platform.
- Offer a Bash shell script equivalent to bulk_deployment.ps1, or provide guidance for running the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
- Clarify that Azure CLI commands are cross-platform and can be run in Bash, PowerShell, or other shells.
- Add notes or tabs for Linux/macOS users, indicating any differences or prerequisites (such as installing PowerShell Core if using .ps1 scripts).
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides a PowerShell script (RGCleanScript.ps1) and only shows PowerShell usage examples. There are no instructions or examples for running the clean-up process on Linux or macOS, nor is there mention of a Bash/sh or cross-platform alternative. This may prevent Linux/macOS users from easily performing the clean-up task.
Recommendations
- Provide a Bash or cross-platform (e.g., Python) version of the clean-up script, or document how Linux/macOS users can perform equivalent clean-up steps.
- If the PowerShell script is compatible with PowerShell Core (pwsh) on Linux/macOS, explicitly state this and provide usage examples for those platforms.
- Add a note clarifying platform compatibility and any prerequisites for running the script on non-Windows systems.
- If only Windows is supported, explicitly state this limitation at the top of the page.
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 shows evidence of Windows bias, particularly in the installation instructions for kubectl, where only the Windows-specific 'winget' command is provided. Additionally, the Bash example for extracting ZIP files incorrectly uses the Windows PowerShell 'Expand-Archive' command, which is not available on Linux/macOS. Throughout the page, file paths and examples often use Windows-style paths (e.g., 'C:\path\to\archive.zip') as the default, and Linux/macOS equivalents are not provided or mentioned. While Azure CLI and kubectl are cross-platform tools, the documentation does not offer Linux/macOS-specific instructions for common tasks such as extracting ZIP files or installing kubectl, creating friction for non-Windows users.
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew').
- Add 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 Bash examples use commands available on Linux/macOS (avoid PowerShell-specific commands in Bash tabs).
- Review all examples to ensure parity for Linux/macOS users, especially in setup and installation sections.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, with no Bash or Linux/macOS shell equivalents. File paths in JSON templates and script instructions use Windows-style (backslash) paths, and the onboarding scripts are referenced as PowerShell (.ps1) files only. There is no mention of Linux/macOS alternatives or guidance for non-Windows users, despite the topic being cross-platform (Azure Arc-enabled Kubernetes clusters, container logs, OpenTelemetry, etc.).
Recommendations
- Provide Bash/zsh shell equivalents for all PowerShell script examples, especially for az CLI commands, which are cross-platform.
- Use platform-neutral file paths in JSON templates, or provide separate examples for Windows and Linux/macOS.
- Clarify whether onboarding scripts are available in Bash or Python for Linux/macOS users, or provide guidance on running PowerShell scripts on those platforms (e.g., via PowerShell Core).
- Add explicit notes or sections for Linux/macOS users, including troubleshooting tips and environment setup instructions.
- Ensure all az CLI commands are shown in both Windows (PowerShell) and Linux/macOS (Bash) syntax where applicable.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page is heavily biased toward Windows environments. All onboarding scripts and examples are provided exclusively for PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. The prerequisite commands use 'winget', a Windows-only package manager, and there are no instructions for installing Azure CLI or kubectl on Linux/macOS. The instructions repeatedly direct users to open a PowerShell terminal, and all script examples are in PowerShell syntax. No Linux or macOS equivalents are provided, creating friction for non-Windows users.
Recommendations
- Provide Bash or shell script equivalents for onboarding tasks, or clarify if the scripts are cross-platform.
- Add instructions for installing Azure CLI and kubectl using Linux/macOS package managers (e.g., apt, yum, brew).
- Explicitly state platform requirements for the onboarding scripts (e.g., if .ps1 scripts require Windows/PowerShell Core).
- Offer guidance for running PowerShell scripts on Linux/macOS (using PowerShell Core), or provide alternative scripts.
- Reorder examples so that Linux/macOS instructions are given equal prominence, or at least referenced alongside Windows steps.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily skewed toward PowerShell and Windows-style command syntax. Most examples and solutions use PowerShell, even for tasks that are cross-platform (e.g., Azure CLI, Docker, Kubernetes). There are few, if any, Bash or Linux-native command examples in the main troubleshooting sections. Bash examples only appear in the 'service groups' section, and even there, PowerShell is shown alongside Bash, but Bash is not presented first. Several commands use Windows-specific syntax (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding), and there is no guidance for Linux/macOS equivalents, creating friction for non-Windows users.
Recommendations
- Provide Bash/Linux/macOS equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
- Show Bash examples first or alongside PowerShell, especially in cross-platform contexts.
- Avoid using Windows-specific command patterns (e.g., PowerShell variable assignment, ConvertTo-Json, Out-File) without Linux alternatives.
- Add notes or tabs indicating which commands are for Windows/PowerShell and which are for Bash/Linux.
- Review all troubleshooting steps to ensure Linux/macOS users can follow them without needing to translate PowerShell syntax.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal prominence to CLI, and no explicit Linux/macOS shell examples are provided. In several sections, PowerShell is presented as a primary method alongside CLI, which may not be relevant for Linux/macOS users. There are no bash/zsh or native Linux/macOS terminal examples, and some instructions (such as environment variable usage) are not tailored for non-Windows shells.
Recommendations
- Add explicit bash/zsh (Linux/macOS) shell examples for all authentication flows, especially for scripting scenarios.
- Clarify that PowerShell examples are primarily for Windows users, and provide equivalent bash commands for Linux/macOS users.
- In sections discussing environment variables (e.g., DOCKER_COMMAND), provide both Windows (set) and Linux/macOS (export) syntax.
- Consider reordering examples to show cross-platform CLI (az, docker) first, and PowerShell second or in a Windows-specific tab.
- Explicitly mention that Azure CLI and Docker commands work on Linux/macOS, and provide any OS-specific caveats if needed.
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 are no missing Linux examples or exclusive Windows tools; parity is maintained, but Windows is prioritized in ordering.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order in sections to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are fully supported at the start of relevant sections.
- Consider using tabs or collapsible sections for OS-specific instructions to improve clarity and parity.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatically retrieving subscription and tenant IDs. However, PowerShell is mentioned first in all cases, and the CLI is presented as an alternative. There are no Windows-only tools or commands, but the ordering and phrasing subtly favor Windows/PowerShell users. No Linux/macOS-specific examples or considerations are provided.
Recommendations
- Present Azure CLI and PowerShell options in parallel, or alternate which is listed first.
- Explicitly note that Azure CLI works cross-platform (Windows, Linux, macOS), while PowerShell is most common on Windows.
- Consider including example CLI commands for Linux/macOS users, such as showing CLI output in a Bash terminal.
- Add a brief note that both tools are available on all platforms, but CLI is often preferred on Linux/macOS.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for setting up workload orchestration, but the Bash tab is presented first. There are no Windows-specific tools or patterns, and all commands use the cross-platform Azure CLI. No Linux/macOS examples are missing, and the PowerShell tab is provided for Windows users. The only minor bias is the order of example tabs, with Bash (Linux/macOS) shown before PowerShell (Windows).
Recommendations
- Ensure that Bash and PowerShell examples are equally prominent and accessible.
- Consider clarifying that Azure CLI commands work on both Windows and Linux/macOS, and that PowerShell can be used cross-platform.
- If possible, provide a brief note about using Azure CLI in different environments (Windows, Linux, macOS) for further clarity.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias towards Linux/macOS users rather than Windows. There are no Windows-only tools, patterns, or missing Linux examples. Both platforms are equally supported throughout.
Recommendations
- No significant changes needed. Both Bash and PowerShell examples are present and comprehensive.
- If desired, alternate the order of Bash and PowerShell tabs in some sections to avoid perceived bias.
- Ensure that any platform-specific nuances (e.g., file encoding, base64 commands) are clearly explained for both environments, which is already done.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows instructions (using certutil and findstr) are more detailed and appear after the Linux example. However, the Linux example is brief and lacks guidance for decoding or removing headers, while the Windows example covers these steps. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and is generally platform-neutral.
Recommendations
- Expand the Linux base64 example to include decoding and header removal, matching the detail provided for Windows.
- Mention cross-platform alternatives for header removal (e.g., using grep or sed on Linux/macOS).
- Clarify that Azure CLI and kubectl commands work on all platforms.
- Consider presenting Linux/macOS and Windows instructions side-by-side for parity.
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 throughout, but PowerShell examples are consistently presented alongside CLI, sometimes immediately after, and environment variable examples for PowerShell use Windows syntax (e.g., $Env:VAR), while CLI uses Linux/macOS syntax (export VAR). There are no explicit Linux/macOS-specific instructions or troubleshooting tips, and PowerShell is referenced as a primary tool, which may create friction for Linux users unfamiliar with PowerShell.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, clarifying that PowerShell is optional and not required on those platforms.
- Provide troubleshooting tips for Linux/macOS environments, especially around proxy configuration and environment variables.
- Consider showing Azure CLI examples first, or marking PowerShell as 'Windows/optional'.
- Mention that Azure PowerShell can be installed on Linux/macOS, but Azure CLI is more common for those platforms.
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 (e.g., /cli/azure/install-azure-cli-windows?tabs=azure-cli) and mentions Azure CLI x64/32-bit requirements without clarifying Linux/macOS compatibility. However, there are no explicit Windows-only tools or PowerShell examples, and the CLI commands provided are cross-platform. The management machine requirements and CLI extension instructions are generic, but the Windows-centric installation link and lack of Linux/macOS parity in examples or guidance create minor friction.
Recommendations
- Add explicit guidance for installing Azure CLI on Linux and macOS, including relevant links.
- Clarify that the management machine can be Linux, Windows, or macOS, and provide OS-specific instructions or notes where appropriate.
- Ensure examples and instructions reference cross-platform compatibility, and avoid defaulting to Windows installation links.
- If there are any OS-specific limitations (e.g., Azure CLI extension support), document them clearly.
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 examples are consistently presented alongside CLI and portal instructions. Windows-specific details (such as PowerShell command syntax, Windows log file locations, and references to Windows installation packages) are present, but Linux equivalents are also mentioned (e.g., Linux log file paths, Linux onboarding instructions, and references to Linux installation packages). However, minor Windows bias is evident in some sections, such as mentioning Windows PowerShell nuances and listing Windows Admin Center as a scenario without Linux alternatives.
Recommendations
- Ensure Linux and macOS command-line instructions (e.g., Bash syntax) are as prominent as PowerShell examples, possibly by explicitly labeling CLI examples as cross-platform.
- When referencing log file locations, clarify both Windows and Linux paths equally and avoid listing Windows first unless contextually appropriate.
- For onboarding and monitoring instructions, highlight any Linux/macOS-specific steps or caveats, if applicable.
- Consider including explicit Bash shell examples for CLI commands to reinforce cross-platform support.
- When listing scenarios, mention Linux alternatives or clarify if a scenario is Windows-only.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Windows and Linux information for Azure Arc-enabled server connectivity, but Windows examples and tools (such as Windows Admin Center and Windows installation package) are often mentioned first or more prominently. Windows-specific tools and scenarios are referenced in service tags and URL tables, sometimes without equivalent Linux-focused examples or tools. However, Linux installation and connectivity requirements are also clearly documented.
Recommendations
- Ensure Linux-related examples and tools are presented with equal prominence and ordering as Windows equivalents (e.g., list Linux installation package before or alongside Windows).
- Where Windows Admin Center is mentioned, consider referencing popular Linux management tools or clarify that Linux management is performed differently.
- Add explicit Linux configuration troubleshooting links or examples, similar to the Windows TLS configuration troubleshooting link.
- Review ordering in tables and lists to avoid consistently placing Windows first.
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. The authentication options section mentions Windows interactive browser login first and describes it as the default, while Linux is only referenced in the context of device code login. Windows certificate store usage is described in detail, but no Linux equivalent is provided. The access token example references the Windows PowerShell cmdlet `Get-AzAccessToken` without mentioning Linux alternatives. However, most examples and instructions are generic and applicable to both platforms.
Recommendations
- Present Linux authentication flows and examples alongside Windows, not after.
- Add explicit Linux certificate usage instructions (e.g., storing PEM/PFX files in typical Linux locations, permissions).
- For access token acquisition, mention Linux/macOS alternatives (such as using Azure CLI: `az account get-access-token`).
- Clarify platform-specific defaults (e.g., device code login is default on Linux) earlier in the document.
- Where Windows tools (like certificate stores or PowerShell cmdlets) are referenced, provide Linux/macOS equivalents or links.
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 describing features and management options. However, there is a mild Windows bias: PowerShell examples and references are given their own section, and PowerShell is mentioned alongside Azure CLI and portal, even though PowerShell is primarily a Windows-centric tool. In the 'Manage automatic extension upgrade' section, the order of examples is Azure portal, Azure CLI, then Azure PowerShell, which is a common but subtle 'windows_first' pattern. All CLI examples are cross-platform, but PowerShell is presented as a parallel option, which may imply greater importance for Windows users.
Recommendations
- Explicitly note that Azure PowerShell is available on Linux and macOS (via PowerShell Core), not just Windows.
- Consider mentioning Bash or other Linux-native scripting options in the CLI section, or providing sample shell scripts for Linux users.
- Ensure that references to PowerShell do not imply it is the default or preferred method unless justified.
- Where possible, clarify that all management options (portal, CLI, PowerShell) are equally applicable to both Windows and Linux Arc-enabled servers.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, with separate, equally detailed tables for each OS. However, the Windows extensions section is presented first, followed by Linux, which is a minor ordering bias. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are listed together, and partner extensions are shown for both OSes. No critical Linux omissions or Windows-only examples are present.
Recommendations
- Consider alternating the order of Windows and Linux sections, or explicitly stating that both OSes are equally supported.
- Add a brief introductory note clarifying that all deployment methods and most extensions are available for both Windows and Linux, except where noted.
- Ensure that future updates maintain parity in detail and links for both OSes.
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 using managed identity on Azure Arc-enabled servers. However, Windows/PowerShell instructions and output are presented first, and PowerShell is referenced more prominently in related content. The Linux example is present and complete, but Windows tools and terminology appear before their Linux equivalents throughout the article.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Ensure related content links reference Azure CLI and Bash examples equally with PowerShell.
- Where possible, use neutral language (e.g., 'use your preferred shell') and avoid Windows-first phrasing.
- Add explicit statements that both Windows and Linux are fully supported, and clarify any OS-specific requirements.
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 both Windows and Linux troubleshooting for the Azure Connected Machine agent. However, there are minor signs of Windows bias: Windows log file paths and PowerShell/Windows-specific commands are sometimes mentioned first, and Windows tools (e.g., PowerShell version requirements, Windows environment variables) are referenced. Linux examples and paths are provided, but Windows is often presented before Linux, and some remediation steps reference Windows tools more directly.
Recommendations
- Alternate the order of Windows and Linux examples to avoid always presenting Windows first.
- Where possible, provide Linux equivalents alongside Windows-specific tools (e.g., for log file locations, environment variables, and command syntax).
- Clarify when remediation steps are OS-specific, and ensure Linux steps are equally detailed.
- Add explicit notes or sections for macOS if supported.
- Ensure troubleshooting tables reference both Windows and Linux paths/tools where applicable.
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 generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there is a subtle Windows bias: Windows-specific tools (PowerShell, Windows registry, Windows Server management) are mentioned before or more prominently than Linux equivalents, and some links default to Windows tabs. PowerShell is referenced as a primary automation tool, and Windows-centric management features are highlighted, even though Linux is also supported. Linux examples, tools, and scenarios are less emphasized or are mentioned after Windows.
Recommendations
- When referencing automation tools (e.g., PowerShell, runbooks), explicitly mention Bash or shell scripting for Linux where applicable.
- Ensure that links to Azure Automation and other hybrid tools include Linux tabs/examples by default or in parallel with Windows.
- Highlight Linux management scenarios and tools (e.g., systemd, Linux daemons, Linux VM extensions) equally alongside Windows features.
- In lists or feature descriptions, alternate the order of Windows and Linux mentions, or group them together to avoid 'Windows first' ordering.
- Provide explicit Linux-focused examples or callouts where possible, especially for onboarding, monitoring, and automation tasks.
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 are listed more briefly. Windows-specific tools and patterns (PowerShell, .NET Framework) are mentioned before Linux equivalents, and Windows download links are provided, but Linux instructions are minimal. No Linux command examples or detailed installation steps are given, and Windows terminology (e.g., 'Windows Admin Center') appears in networking requirements.
Recommendations
- Present Windows and Linux requirements in parallel, rather than listing Windows first.
- Provide download links and installation instructions for Linux dependencies (e.g., systemd, wget) similar to Windows.
- Include Linux command-line examples for installing the Azure Connected Machine agent, not just Windows/PowerShell.
- Clarify Linux-specific networking scenarios (e.g., SSH) and tools where relevant.
- Ensure Linux terminology and tools are mentioned with equal prominence to Windows tools.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, but consistently presents Bash examples before PowerShell. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There is a minor bias in example ordering, with Bash (Linux/macOS) shown first, which actually favors Linux/macOS users.
Recommendations
- No changes needed. Bash examples are shown first, which is preferable for Linux/macOS parity.
- Continue to provide both Bash and PowerShell examples for cross-platform accessibility.
- If possible, clarify that Bash examples are suitable for Linux/macOS terminals and PowerShell for Windows, to help users select the right syntax.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned, but Linux features (such as SSH-based agent installation) are also present. However, in sections listing tools (June 2024), Azure PowerShell is mentioned alongside Azure CLI and REST APIs, and Windows-related management tools (System Center Configuration Manager, Group Policy) are listed before Linux equivalents (Ansible). Windows examples and tools tend to be mentioned first or more prominently, but Linux parity is generally maintained.
Recommendations
- Ensure Linux tools and examples (such as Ansible) are listed alongside or before Windows tools when describing at-scale agent installation methods.
- Where possible, provide explicit Linux/macOS examples for management tasks, not just Windows/PowerShell.
- Consider balancing the order of tool mentions (e.g., Azure CLI before PowerShell) to avoid subtle Windows-first bias.
- Add links or references to Linux-specific documentation or guides 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 operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, rather than alternating or giving equal prominence. There are no Windows-specific tools or patterns, and all instructions use the cross-platform Azure CLI. No Linux/macOS examples are missing, and no Windows-only tools are referenced.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
- Explicitly state that all CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a brief note clarifying that PowerShell examples are for Windows users, while Bash is for Linux/macOS, to further assist readers.
- Ensure screenshots and portal instructions are not Windows-centric (e.g., avoid referencing Windows-specific browser behaviors).
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown first and exclusively in some cases. There are no explicit Linux/macOS-specific instructions or parity for downloading or setting configuration files, and no mention of Linux shell equivalents for those commands.
Recommendations
- Provide both Bash and PowerShell examples for CLI commands, especially for configuration file operations.
- Ensure that CLI instructions use cross-platform syntax (e.g., avoid PowerShell-specific line continuation unless also showing Bash equivalents).
- Add notes clarifying that Azure CLI commands work on Linux/macOS and Windows, and highlight any OS-specific considerations.
- Where possible, show Bash examples first or alongside PowerShell to avoid implicit Windows prioritization.
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, which could be considered a minor 'windows_first' bias, but no critical Windows-only tools or patterns are used. All commands rely on cross-platform Azure CLI and Helm tools.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
- Explicitly mention that all commands are cross-platform and can be run on Linux, macOS, or Windows.
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
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-only tools or patterns are used, and all commands are cross-platform (az CLI, Helm). There are no missing Linux examples, and no exclusive mention of Windows tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state that Bash commands can be run on Linux/macOS terminals and PowerShell commands on Windows, for user clarity.
- Ensure that any future additions (e.g., troubleshooting, environment setup) also provide cross-platform instructions.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in nearly all sections, Bash examples are presented before PowerShell, which is a positive sign for Linux parity. There are no Windows-only tools, patterns, or references; all commands use the Azure CLI and Helm, which are cross-platform. No evidence of Windows bias is found in the examples, ordering, or tool selection.
Recommendations
- Maintain the current approach of providing both Bash and PowerShell examples for all steps.
- Continue to present Bash examples first to reinforce Linux/macOS parity.
- Ensure that any future additions (e.g., troubleshooting or advanced scenarios) also include Bash and PowerShell examples.
- If possible, clarify in the prerequisites that all tools used (Azure CLI, Helm) are cross-platform and provide links to installation instructions for Linux/macOS and Windows.
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 examples for deploying Azure dashboards using the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform and featured before PowerShell, the PowerShell section is prominent and included as a distinct method. The documentation does not show any Linux/macOS-specific tools or shell examples (e.g., Bash), nor does it clarify that Azure PowerShell is available on Linux/macOS. The ordering of examples (CLI before PowerShell) is positive, but the PowerShell section could be perceived as Windows-centric due to its historical association with Windows.
Recommendations
- Explicitly state that Azure CLI and Azure PowerShell are both cross-platform and supported on Windows, Linux, and macOS.
- Add Bash shell examples for Azure CLI usage, demonstrating deployment from a Linux/macOS terminal.
- Clarify that Azure PowerShell can be used on Linux/macOS, and provide installation links or notes.
- Consider including REST API examples using curl or similar cross-platform tools.
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 (which typically refers to Azure CLI, a cross-platform tool). PowerShell is traditionally associated with Windows, and its mention before Bash or Linux shell scripting may subtly prioritize Windows users. However, the documentation does not provide actual script examples or instructions that are Windows-specific, nor does it omit Linux/macOS equivalents.
Recommendations
- Clarify that Azure Copilot can generate scripts for both Azure CLI (cross-platform) and PowerShell, and consider mentioning Bash or Linux shell scripting if supported.
- If examples are added in the future, ensure parity by providing both PowerShell and Azure CLI/Bash examples.
- Explicitly state that Azure Copilot supports script generation for users on all platforms (Windows, Linux, macOS).
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There is no explicit Linux/macOS bias, but the inclusion of PowerShell as a primary example may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. The page does not provide shell (bash) or Linux-native command examples, nor does it mention Linux tools or patterns for registry management.
Recommendations
- Add bash shell examples for image import, using Azure CLI, to demonstrate Linux-native workflows.
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Consider including a note or section for Linux/macOS users, highlighting Azure CLI usage in bash/zsh shells.
- If PowerShell is included, indicate its cross-platform availability, but prioritize CLI/bash examples for Linux/macOS parity.
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, with PowerShell examples given equal prominence. However, there is a slight Windows-first bias in listing Azure PowerShell as an option alongside Azure CLI, rather than, for example, Bash scripts or Linux-native tools. All Docker CLI commands are cross-platform, and installation links are provided for macOS, Windows, and Linux. No critical Linux/macOS gaps are present.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows/PowerShell users, and Azure CLI is cross-platform.
- Consider listing Azure CLI examples before PowerShell, or explicitly noting that CLI is recommended for Linux/macOS.
- Optionally, provide Bash script examples for common tasks, or mention that all Docker CLI commands work identically on Linux/macOS.
- Ensure that any PowerShell-specific instructions are clearly marked as such.
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 both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is mentioned alongside CLI in the introductory deployment instructions and has its own example section. The instructions for opening a terminal reference Visual Studio Code (cross-platform), but the PowerShell example may be more familiar to Windows users. No Linux-specific shell (e.g., Bash) or macOS-specific guidance is given, and PowerShell is not as commonly used on Linux/macOS. However, Azure CLI is cross-platform and is shown first.
Recommendations
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform users.
- Add a Bash example or clarify that the CLI example is suitable for Bash/zsh terminals on Linux/macOS.
- Consider removing or de-emphasizing PowerShell unless there is a specific need for Windows users.
- Add a note for Linux/macOS users about using their preferred terminal and shell.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command examples for Helm and Azure CLI, which are cross-platform, but in the 'Set the following environment variables' section, it uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'). Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, but includes Azure PowerShell and Portal options, which is acceptable. Overall, the bias is minor and mostly limited to the environment variable example.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') commands for setting environment variables.
- Add a note clarifying that Azure CLI and Helm commands are cross-platform and can be run on Windows, Linux, and macOS.
- Where shell commands are shown, indicate the shell type or provide alternatives for Bash and PowerShell if syntax differs.