230
Pages Scanned
52
Pages Flagged
230
Changed Pages
22.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06
Scan Information
Started At: 2026-02-27 00:00:06
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 230
Files Completed: 230
Problematic Pages
52 issues found
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_authentication
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and features (Windows Authentication, PowerShell scripting support) without providing Linux/macOS alternatives or parity. While Azure CLI and Visual Studio Code are cross-platform, the emphasis on Windows tools and authentication options creates friction for non-Windows users.
Recommendations
- Explicitly mention cross-platform alternatives for management and scripting, such as Azure Data Studio, sqlcmd, and Bash scripting.
- Clarify which tools/features are Windows-only and provide guidance for Linux/macOS users where possible.
- Add examples or links for using Azure CLI and VS Code on Linux/macOS for common management tasks.
- Note limitations for Windows Authentication and PowerShell scripting on non-Windows platforms, and suggest alternatives (e.g., Microsoft Entra authentication, Azure CLI).
Create Pull Request
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 generally Linux-focused, but it uses Windows/PowerShell-specific tooling (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. The text editor example (Notepad) is also Windows-centric, and there are no Linux-native command examples for sysctl configuration.
Recommendations
- Provide native Linux shell commands for sysctl configuration (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee ...').
- Replace or supplement Notepad with Linux text editors (e.g., nano, vim) when editing configuration files.
- Clarify whether Invoke-AksEdgeNodeCommand is required or if direct Linux shell access is possible, and provide Linux-native instructions if so.
- Ensure all steps can be completed using standard Linux tools, not only Azure/Windows-specific wrappers.
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-specific details and links are often presented first or more prominently. For example, installation links for 'kubectl' and 'curl' list Windows before Linux/macOS, and there is a note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance. The explanation about PowerShell's curl alias is Windows-specific, with no mention of similar issues on other platforms. Linux installation instructions for curl are vague ('install curl package') compared to the explicit Windows link.
Recommendations
- Present installation links for all platforms in parallel or alphabetical order (e.g., Linux, macOS, Windows) to avoid Windows-first bias.
- Provide equally detailed installation instructions for Linux and macOS (e.g., specify package manager commands for curl on Linux and Homebrew for macOS).
- Add notes about platform-specific issues for Linux/macOS where relevant, not just Windows (e.g., clarify curl usage differences on Linux shells).
- Avoid PowerShell-specific notes unless there are equivalent notes for Bash/zsh or other shells.
- Ensure that all examples and guidance are cross-platform unless the tool is Windows-only.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides several examples and instructions that assume a Windows environment, such as using Windows file paths (e.g., C:\Backupfiles\test.bak) and referencing tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives. There are no explicit Linux/macOS examples for creating backups or copying files, and the file path examples are Windows-centric. This may cause friction for Linux/macOS users attempting to follow the guide.
Recommendations
- Provide parallel examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) wherever Windows paths are shown.
- Mention and give examples using cross-platform tools (e.g., Azure Data Studio, sqlcmd) in addition to or instead of SSMS.
- Clarify that the backup and file copy steps can be performed from Linux/macOS, and show the equivalent commands.
- Where GUI tools are referenced (e.g., Azure Storage Explorer), note their cross-platform availability or suggest CLI alternatives (e.g., azcopy, Azure CLI).
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
powershell_heavy
Summary
The documentation provides authentication options and examples for connecting servers to Azure Arc using the azcmagent CLI. While the overall guidance is cross-platform, there is evidence of Windows bias: Windows authentication methods are described first, Windows certificate store options are detailed without Linux equivalents, and the access token section references PowerShell's Get-AzAccessToken as the primary method for obtaining tokens. Linux-specific guidance (such as using device code login and Azure CLI) is present but not as prominently featured or explained.
Recommendations
- Reorder authentication options so Linux-default methods (device code, Azure CLI) are described before Windows-only options.
- Add Linux-specific examples for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token') alongside PowerShell examples.
- Clarify certificate storage and usage for Linux (e.g., recommended file locations, permissions, and certificate formats) to match the detail given for Windows certificate stores.
- Explicitly state cross-platform support in examples and highlight any OS-specific caveats.
- Provide a table or section summarizing authentication methods by OS (Windows, Linux, macOS) for quick reference.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions for all major lifecycle tasks (install, upgrade, uninstall, proxy config), but Windows examples and tools (PowerShell, Group Policy, WSUS, MSI installer) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no Linux/bash equivalent. Windows-specific tools and patterns (Control Panel, Registry, Group Policy) are described in depth, while Linux instructions are more concise and rely on standard package managers.
Recommendations
- Provide bash or Azure CLI equivalents for PowerShell scripts, especially for resource cleanup.
- Ensure Linux instructions are as detailed as Windows, including troubleshooting and automation tips.
- Where possible, present Windows and Linux instructions side-by-side or in parallel tabs, rather than Windows-first.
- Add links or references to Linux-native automation tools (e.g., cron, systemd) for agent maintenance.
- For proxy configuration, clarify Linux service restart requirements and provide more detail on environment variable management.
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, sts.windows.net, login.windows.net, servicebus.windows.net) and mentions Windows NTP as a default for Hyper-V, but does not provide equivalent Linux examples or clarify Linux alternatives. Windows terminology and endpoints appear before Linux-specific ones (e.g., Microsoft open source packages manager for Linux is listed after Windows NTP). There are no explicit PowerShell or Windows-only command examples, but the service/endpoint bias and ordering favor Windows.
Recommendations
- Add Linux NTP server examples (e.g., ntp.ubuntu.com or pool.ntp.org) alongside time.windows.com, and clarify when to use each.
- Clarify that sts.windows.net, login.windows.net, and servicebus.windows.net are cross-platform endpoints, not Windows-only, or provide Linux-specific guidance if needed.
- Reorder the firewall/proxy table to group Linux and Windows endpoints/services equally, or add notes indicating Linux alternatives where relevant.
- Explicitly mention Linux management machines and appliance VMs, and ensure Linux-specific requirements (such as packages.microsoft.com) are highlighted equally.
- Add a short section or note confirming that both Windows and Linux management machines/appliance VMs are supported, and link to OS-specific configuration guidance if available.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page includes several examples and troubleshooting steps that reference Windows-specific tools and patterns, such as PowerShell cmdlets and Windows folder paths. Windows terminology (e.g., 'Remote PowerShell', 'RDP', 'time.windows.com') is mentioned before or instead of Linux equivalents. While Linux is referenced in some troubleshooting (e.g., glibc errors), Linux-specific commands and guidance are often missing or less prominent. Most CLI examples are generic, but where OS-specific troubleshooting is required, Windows is prioritized.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows-specific commands (e.g., use curl or wget for HTTP troubleshooting, and show how to test HTTP/2 with Linux tools).
- Add explicit Linux/macOS instructions for SSH folder permissions, DNS resolution (e.g., using dig or nslookup), and proxy configuration.
- Where Windows paths or tools are referenced (e.g., 'C:\Program Files'), add corresponding Linux/macOS paths and troubleshooting steps.
- Ensure that troubleshooting steps for network, proxy, and certificate issues include Linux/macOS guidance (e.g., how to check SSL proxy trust, how to configure environment variables for proxies).
- When referencing time synchronization (e.g., NTP), clarify how to check and configure NTP on Linux/macOS hosts.
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 across both Linux and Windows, but there is a notable emphasis on Windows-specific tools and methods. PowerShell is highlighted as a primary onboarding method for both OS types, and several Windows-only methods (Windows Admin Center, Configuration Manager, Group Policy) are listed separately. Windows tools and patterns (e.g., PowerShell, Configuration Manager, Group Policy) are mentioned more frequently and in greater detail than Linux equivalents. Linux-specific automation tools (such as Ansible) are included, but PowerShell is presented as a cross-platform solution, which may not be optimal for Linux users. The order of methods also places Windows-centric approaches before Linux-specific ones in several places.
Recommendations
- Provide explicit Linux shell (bash) examples and scripts alongside PowerShell examples for onboarding and automation.
- Highlight Linux-native automation tools (such as Ansible, shell scripts) earlier and more prominently, rather than positioning PowerShell as the default cross-platform solution.
- Add links or references to Linux package managers (e.g., apt, yum) for agent installation.
- Clarify which methods are best suited for Linux environments and provide guidance tailored to Linux administrators.
- Balance the order of presentation so that Linux and Windows methods are equally visible and accessible.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell 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 example commands, further reinforcing Windows-centric patterns.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
- Mention that Azure CLI and Bash can be used on Linux/macOS for template deployment, and provide sample commands.
- Use generic file paths (e.g., './AzureMonitorAgent.json') or note that file paths should be adapted for Linux/macOS environments.
- Consider presenting CLI and PowerShell examples side-by-side, or at least referencing CLI options in the 'Deployment commands' section.
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-specific tools (such as New-AzStorageBlobSASToken and New-NetFirewallRule), with Windows-focused scripting and REST API scenarios. Linux equivalents are mentioned but not demonstrated, and Linux-specific examples (such as shell scripting or firewall configuration) are missing. The REST API section exclusively uses Windows Server and PowerShell cmdlets, with no Linux scenario or shell script example.
Recommendations
- Add Linux-specific script examples in PowerShell, Azure CLI, and REST API sections (e.g., bash scripts, Linux firewall commands like ufw or iptables).
- Provide REST API examples targeting a Linux Arc-enabled server, including sample shell scripts.
- Balance PowerShell and Azure CLI examples by showing both Windows and Linux use cases.
- Mention and demonstrate Linux tools for generating SAS tokens (e.g., Azure CLI az storage blob generate-sas) instead of only PowerShell.
- Clarify when examples are Windows-specific and provide Linux alternatives where possible.
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 tends to mention Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, PowerShell) before Linux equivalents. PowerShell is highlighted as a deployment method, and Windows-specific graphical tools are referenced, while Linux tools (e.g., Bash, Ansible) are mentioned but not given equal prominence or example detail. There are no explicit Linux command examples or step-by-step Linux deployment instructions, and Windows deployment options are listed first.
Recommendations
- Provide explicit Linux deployment examples, such as Bash scripts or command-line instructions for onboarding Linux servers to Azure Arc.
- Mention Linux tools (e.g., Ansible, Bash) before or alongside Windows tools in deployment sections.
- Add references or links to Linux-specific documentation for Azure Monitor Agent and Azure Arc onboarding.
- Ensure parity in graphical and programmatic deployment guidance for Linux environments.
- Include sample commands or scripts for Linux environments where PowerShell or Windows tools are shown.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides recovery instructions and a script exclusively for Windows, using PowerShell. There are no examples or guidance for Linux/macOS users, nor is there mention of equivalent tools or scripts for those platforms. The section is titled 'Recover Arc resource bridge from a Windows machine', and no alternative is provided.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or Python.
- Clarify if the recovery process is supported only on Windows, and if so, explain the rationale.
- If possible, offer a cross-platform script or containerized tool to perform the recovery.
- Add a note about platform requirements for the disaster recovery script.
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 presents a notable Windows bias, especially in the 'Auto Arc-enablement script' section, where only PowerShell scripts and Windows Task Scheduler are used for automation. The script usage instructions and scheduling examples are Windows-centric, with no Linux/macOS equivalents provided. Windows tools (PowerShell, Task Scheduler) are mentioned exclusively, and Windows instructions are often presented before Linux ones. While Linux is acknowledged in prerequisites and out-of-band methods, Linux/macOS users lack parity in automation and scheduling guidance.
Recommendations
- Provide Bash or shell script equivalents for the auto-enablement script, or clarify if the script is cross-platform.
- Include instructions for running the script on Linux/macOS, such as using cron for scheduling instead of Windows Task Scheduler.
- Offer Linux/macOS-specific examples for script execution, including handling permissions and sudo usage.
- Clarify any OS limitations of the helper script and provide alternatives if it is Windows-only.
- Ensure parity in example ordering and tool recommendations (e.g., mention Ansible, cron, Bash alongside PowerShell and Task Scheduler).
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 the onboarding script as a PowerShell (.ps1) script, with no mention of Bash, Linux, or macOS equivalents. All command-line instructions and code snippets are Windows-centric, and there is no guidance for users on Linux or macOS platforms. This creates friction for non-Windows users attempting 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 platform requirements for the onboarding script (e.g., if it must be run on Windows/PowerShell, mention this up front).
- If possible, offer a cross-platform onboarding script or instructions for running PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
- Add notes or links for Linux/macOS users about prerequisites or alternative tooling.
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 page provides detailed instructions for both Windows and Linux VM agent removal, but when it comes to running the deboarding script for removing VMware vSphere resources from Azure Arc, only Windows/PowerShell instructions are given. The script is presented as a PowerShell script with no mention of a Linux or cross-platform equivalent, and Windows instructions are shown first and exclusively. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows environments for this critical step.
Recommendations
- Provide clear instructions or an alternative script for Linux/macOS users, such as a Bash or Python version, or document how to run the PowerShell script cross-platform (e.g., with PowerShell Core on Linux/macOS).
- Explicitly state any platform limitations for the deboarding script and offer guidance for Linux/macOS users (e.g., using PowerShell Core, or manual steps).
- Consider including manual removal steps in greater detail for users unable to run the PowerShell script.
- Present Windows and Linux instructions in parallel or clarify which steps are platform-specific.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell script examples. There are no Linux/macOS-specific instructions or examples, and the PowerShell syntax is used exclusively for CLI commands, which may confuse or hinder Linux/macOS users. The documentation does not mention how to run these scripts or commands on Linux/macOS, nor does it provide alternative shell script options.
Recommendations
- Provide Azure CLI command examples in Bash syntax, not just PowerShell.
- Add Linux/macOS-specific instructions for running bulk deployment and workflow deletion, including Bash shell script equivalents for bulk_deployment.ps1 and workflow-delete.ps1.
- Clarify that Azure CLI commands can be run in Bash or PowerShell, and show both syntaxes where appropriate.
- Mention any prerequisites or dependencies for Linux/macOS users (e.g., how to install Azure CLI, how to execute scripts).
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for migration and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. This creates friction for Linux/macOS users, as PowerShell is not natively available and no alternative script or instructions are provided.
Recommendations
- Provide a Bash or cross-platform script for migration, or document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core).
- Explicitly state if the script is compatible with PowerShell Core on Linux/macOS, and provide installation instructions if needed.
- Offer equivalent Linux/macOS command examples where possible.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section. Bash syntax is used elsewhere, but PowerShell is shown first and exclusively in some cases. There are no explicit Linux/macOS-specific examples or references to Linux tools, and the CLI commands are presented in a way that may be more familiar to Windows users. However, the Azure CLI is cross-platform, and most commands are generic, but the example formatting could create friction for Linux/macOS users.
Recommendations
- Provide both Bash and PowerShell examples for CLI commands, especially where PowerShell is used.
- Show Bash examples first or side-by-side with PowerShell to emphasize cross-platform support.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Avoid using PowerShell-specific syntax (e.g., backticks for line continuation) unless also providing Bash equivalents.
- Add notes or links for Linux/macOS users about CLI installation and usage.
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 PowerShell command examples for running the clean-up process. There are no Bash, shell, or cross-platform script alternatives, nor is there guidance for Linux/macOS users on how to perform the same task. The script and instructions are Windows-centric, creating friction for non-Windows users.
Recommendations
- Provide a Bash or shell script equivalent for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core (pwsh) on Linux/macOS.
- Include command examples for Linux/macOS environments, such as using pwsh or Bash.
- Clarify script compatibility (e.g., whether RGCleanScript.ps1 works with PowerShell Core on Linux/macOS, or if it is Windows-only).
- If the script is Windows-only, offer guidance or alternatives for Linux/macOS users to achieve the same clean-up tasks (e.g., using Azure CLI commands).
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The kubectl installation command uses 'winget', a Windows-only tool, with no Linux/macOS alternative provided. File extraction instructions use 'Expand-Archive', which is a PowerShell/Windows command, even in the Bash tab, and do not mention cross-platform alternatives like 'unzip'. Windows paths (e.g., 'C:\path\to\archive.zip') are used in examples, and Linux/macOS paths are not shown. These biases may cause friction for Linux/macOS users, especially during initial setup.
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or package managers like 'apt', 'brew').
- In Bash examples, use cross-platform tools like 'unzip' for extracting ZIP files, and show Linux/macOS file paths (e.g., '/home/user/archive.zip').
- Add explicit Linux/macOS alternatives wherever Windows-specific tools or patterns are mentioned.
- Ensure that Bash tabs do not use PowerShell/Windows-only commands.
- Consider including a section or table summarizing platform-specific steps for common tasks.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased toward Windows environments. All onboarding scripts and usage examples are provided exclusively for PowerShell, with no mention of Bash, Linux, or macOS equivalents. Windows-specific tools like 'winget' are referenced for installing dependencies, and there are no instructions or guidance for Linux/macOS users. This creates significant friction for non-Windows users attempting to follow the onboarding process.
Recommendations
- Provide Bash or shell script equivalents for the PowerShell onboarding scripts, or clarify if only PowerShell is supported.
- Include instructions for installing Azure CLI and kubectl on Linux/macOS (e.g., using apt, yum, brew, or official install scripts) alongside the 'winget' command.
- Explicitly state platform requirements and limitations at the top of the page if the scripts are only supported on Windows.
- If possible, offer cross-platform onboarding scripts or containerized solutions.
- Add notes or sections for Linux/macOS users, even if only to clarify current limitations and suggest alternatives.
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 guide for workload orchestration in Azure Arc demonstrates notable Windows bias. Most command-line examples are provided exclusively in PowerShell syntax, even for tasks that are cross-platform (e.g., az CLI, kubectl, docker). Linux/bash equivalents are missing for critical troubleshooting steps, and PowerShell is used for scripting and manipulating outputs (e.g., Base64 encoding, JSON file creation). Bash examples are only present in the 'Troubleshoot service groups' section, where both Bash and PowerShell are shown, but elsewhere PowerShell is used exclusively and shown first.
Recommendations
- Provide bash/Linux equivalents for all az CLI, kubectl, and docker commands, especially in sections where PowerShell is used for scripting (e.g., Base64 encoding, JSON file creation).
- Show bash/Linux examples before or alongside PowerShell examples for cross-platform tools.
- Avoid using PowerShell-specific syntax for az CLI, kubectl, and docker commands; use generic syntax where possible.
- Add notes clarifying when a command is Windows-specific, and offer Linux/macOS alternatives.
- For scripting tasks (e.g., manipulating connection strings, creating JSON files), provide bash/Linux shell alternatives (e.g., using jq, base64, echo, etc.).
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 presents Windows/PowerShell examples before Linux/Bash equivalents in the 'Acquire an access token using REST API' section. Windows-specific tools (PowerShell) are highlighted first, and screenshots show PowerShell output before Bash. However, Linux parity is maintained with Bash examples and links to Linux-specific tutorials.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which comes first to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are equally supported for Azure Arc-enabled servers.
- Include cross-platform CLI examples (e.g., Azure CLI) where possible.
- Ensure screenshots for both OSes are equally prominent.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows and Linux VM extensions in separate sections, with Windows extensions listed first. However, both platforms are covered equally, with comprehensive tables and links for each. Deployment methods (Azure CLI, PowerShell, portal, templates) are presented neutrally, and Linux-specific tools and extensions are included. No critical tasks are Windows-only, and Linux parity is maintained throughout.
Recommendations
- Consider alternating the order of Windows and Linux sections, or presenting them side-by-side where feasible, to avoid implicit prioritization.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Ensure that Linux examples and links are as prominent and detailed as Windows ones in any referenced sub-pages.
- Add a brief introductory note clarifying that Azure Arc-enabled servers support both Windows and Linux equally, to reinforce platform neutrality.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first in the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout with equivalent instructions and examples.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them side-by-side to avoid implicit prioritization.
- Explicitly mention macOS compatibility if the Bash script works on macOS, or clarify if it does not.
- Ensure screenshots and UI references are OS-neutral where possible.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are shown first, followed by PowerShell, which is a minor 'windows_first' bias. No evidence of PowerShell-heavy content, exclusive Windows tools, or missing Linux examples is found.
Recommendations
- Continue to provide both Bash and PowerShell examples for all CLI commands.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add clarifying notes where relevant to help users choose the correct shell for their OS.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are included throughout, and in some sections (such as variable naming and file path conventions), Windows/PowerShell patterns are visible. Bash examples are consistently shown first, but the presence of PowerShell throughout may signal a slight Windows bias. No Windows-only tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Maintain Bash as the first example for each step to reinforce Linux parity.
- Clarify in the introduction that all commands are cross-platform and that PowerShell is included for Windows users.
- Consider adding a note that Bash examples are suitable for macOS as well as Linux.
- Ensure file path conventions in PowerShell examples (e.g., .\file) are explained for Linux/macOS users if they copy/paste.
- If possible, provide a generic shell example or clarify that az CLI and Helm commands work identically on all platforms.
Low 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 sqlcmd, but these examples are shown exclusively in PowerShell syntax (with the PowerShell prompt and formatting). There is no explicit Linux/macOS shell example, even though the underlying commands (kubectl, sqlcmd) are cross-platform. The use of PowerShell formatting and prompt may confuse Linux/macOS users, and the documentation implicitly prioritizes Windows usage patterns.
Recommendations
- Provide equivalent Linux/macOS shell (bash) examples alongside PowerShell examples, especially for sqlcmd and kubectl commands.
- Use a generic shell prompt (e.g., $ or #) for cross-platform commands, or clarify that the commands work on all platforms.
- Explicitly mention that sqlcmd and kubectl are cross-platform tools and provide installation guidance for Linux/macOS if needed.
- Avoid using PowerShell-specific formatting unless the command is truly Windows-only.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_example
windows_first
Summary
The documentation provides both Linux and Windows approaches for base64 encoding files, but the Windows method (certutil) is presented as a special case, with additional manual steps required. The Linux command (base64) is shown first and described as usable on 'any Linux distribution.' The Windows example is included, but requires extra manual intervention (removing headers) and additional commands. There is no PowerShell-heavy bias, and all Azure CLI and kubectl examples are cross-platform. The overall bias is minor, with Windows tools mentioned but not prioritized.
Recommendations
- Clarify that both Linux and Windows users can use OpenSSL and Azure CLI/kubectl.
- Provide a PowerShell example for base64 encoding on Windows, which may be more familiar to Windows users than certutil.
- Explicitly state that the Azure CLI and kubectl commands work on both Windows and Linux.
- Consider mentioning cross-platform tools (e.g., Git Bash, WSL) for Windows users who prefer Linux-style commands.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux-compatible example is provided, SSMS is listed before sqlcmd and there are no examples for popular Linux/macOS GUI tools (such as Azure Data Studio or DBeaver). The documentation does not mention Linux-specific connection patterns or troubleshooting, and the focus on SSMS may create friction for Linux/macOS users.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit examples for connecting using Azure Data Studio or other Linux/macOS-compatible tools.
- Ensure that Linux/macOS users are aware that sqlcmd is available natively and provide installation instructions or links.
- Consider listing cross-platform tools before or alongside SSMS to avoid Windows-first bias.
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, and in some sections, PowerShell is shown before CLI. There is a slight bias toward Windows/PowerShell, as PowerShell is a Windows-centric tool, and its inclusion may imply Windows as a primary platform. However, Azure CLI examples are present and are cross-platform, and Linux-specific instructions (such as environment variable export syntax) are included. No Windows-only tools or patterns are used, and Linux users can complete all tasks.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and PowerShell is primarily for Windows users.
- Add a short note clarifying that both Azure CLI and PowerShell are supported, but CLI is recommended for Linux/macOS environments.
- Consider including bash shell script examples for common tasks, especially for onboarding and updating clusters.
- Where environment variables are set, show both Linux (export) and Windows (set) syntax for parity.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page for Azure Arc resource bridge system requirements shows minor Windows bias in the management machine requirements section, where the Azure CLI installation link defaults to the Windows version. However, the overall content is cross-platform, and does not reference Windows-only tools or patterns. No PowerShell examples or Windows-specific commands are present, and Linux/macOS users can complete all tasks described.
Recommendations
- Update the Azure CLI installation link in the management machine requirements section to reference the generic Azure CLI install page, or provide links for Windows, Linux, and macOS.
- Explicitly state that the management machine can be Windows, Linux, or macOS, as long as Azure CLI is installed.
- Add a note clarifying that all CLI commands are cross-platform unless otherwise stated.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with parity in most features and fixes. However, Windows download links and version numbers are consistently listed first, and Windows-specific installer tools (MSI, PowerShell, Command Prompt) are referenced in troubleshooting and known issues, with no equivalent Linux installer guidance or troubleshooting. Some improvements and bug fixes reference Windows tools/scripts (e.g., ExtensionCleanup.ps1, MSI signature verification), while Linux equivalents are not always described.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
- Add Linux-specific troubleshooting guidance for installer issues, including common commands (e.g., using rpm, dpkg, systemctl) and privilege escalation (e.g., sudo).
- When referencing Windows tools/scripts (e.g., PowerShell, MSI), provide Linux equivalents or clarify if the feature is Windows-only.
- Ensure that bug fixes and improvements for Linux are described with equal detail and visibility as Windows items.
- Consider a summary table or section highlighting Linux-specific changes and known issues, similar to 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 examples for Azure portal, Azure CLI, and Azure PowerShell in all major workflows. PowerShell examples are included alongside CLI, and in some cases, Windows-specific notes are given (e.g., PowerShell syntax, log file locations). However, Linux parity is generally maintained: CLI examples are cross-platform, Linux log file locations are specified, and Linux onboarding is referenced. Windows examples (PowerShell) are sometimes shown before CLI or Linux equivalents, and Windows-specific notes are occasionally highlighted.
Recommendations
- Ensure CLI examples are always shown before or alongside PowerShell, as CLI is cross-platform.
- Explicitly state that Azure CLI commands work on both Windows and Linux, and provide any necessary Linux-specific syntax or troubleshooting tips.
- Where PowerShell is used, clarify its applicability (Windows only) and provide Bash or shell alternatives if relevant.
- Review the order of examples to avoid Windows-first bias; consider alternating or grouping by platform.
- Expand Linux-specific guidance where possible (e.g., onboarding, log locations, troubleshooting).
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 generally maintains parity between Windows and Linux, explicitly mentioning both platforms and providing URLs for both installation packages. However, there are minor signs of Windows bias: Windows installation resources are listed first in tables, Windows Admin Center is referenced as a management tool (with no Linux equivalent mentioned), and Windows-specific TLS configuration issues are highlighted with a dedicated troubleshooting link. Linux is referenced, but Windows tools and patterns are sometimes prioritized or mentioned first.
Recommendations
- List Linux and Windows installation URLs side-by-side or alternate their order to avoid Windows-first bias.
- When referencing management tools like Windows Admin Center, clarify if there are Linux alternatives or explicitly state that it is Windows-only.
- Provide links to Linux-specific troubleshooting or configuration guidance (e.g., OpenSSL TLS configuration) alongside Windows guidance.
- Ensure examples and guidance for proxy, firewall, and TLS configuration are equally detailed 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 platforms for Azure Arc-enabled servers and provides parity in most sections. However, there is a mild Windows bias: PowerShell examples are provided alongside Azure CLI, and PowerShell is presented as a primary scripting option, which is more relevant to Windows users. In some sections, Windows-specific extensions are listed first, and PowerShell is mentioned before Linux shell alternatives. Azure CLI commands are shown as cross-platform, but PowerShell is still given equal prominence, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Explicitly state that Azure CLI commands work on both Linux and Windows, and consider showing Linux shell (bash/zsh) usage examples where relevant.
- Where PowerShell is mentioned, clarify its availability on Linux/macOS and provide links to installation instructions for those platforms.
- Consider adding sample scripts or command snippets for bash/zsh where appropriate, especially for Linux users.
- Ensure that Linux-specific extensions or scenarios are given equal prominence in lists and examples.
- Review the order of examples and tools to avoid always listing Windows/PowerShell first.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but there is a mild bias toward Windows. Windows examples and log file paths are often mentioned first, and PowerShell syntax is used in Windows examples. Windows-specific tools and concepts (such as PowerShell, environment variables, and Windows log paths) are referenced before their Linux equivalents. However, Linux examples and paths are present and reasonably detailed.
Recommendations
- Alternate Windows and Linux examples so Linux is not always second.
- Provide Bash or shell script equivalents for any PowerShell-heavy examples.
- Where referencing log file locations or config paths, mention Linux paths first or equally.
- Ensure troubleshooting steps and remediation advice reference both Windows and Linux commands/tools where applicable.
- Clarify when a solution is Windows-specific and offer Linux alternatives if possible.
Azure Arc
Extensions security for Azure Arc-enabled servers
...main/articles/azure-arc/servers/security-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux examples for key configuration tasks, but Windows/PowerShell examples are consistently presented first. In some sections, Windows-specific command syntax (PowerShell) is highlighted before Linux (bash), and references to Windows tools (e.g., 'elevated command console') appear before their Linux equivalents. However, Linux parity is generally maintained, and most examples are given for both platforms.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Clarify that both Windows and Linux are equally supported for Azure Arc-enabled server extensions.
- Where possible, use generic CLI examples (e.g., Azure CLI) before platform-specific commands.
- Explicitly mention macOS support if applicable, or clarify its status.
- Use neutral language (e.g., 'run as administrator or root') instead of Windows-centric terms like 'elevated command console'.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are subtle signs of Windows bias. Windows/PowerShell examples and references are often mentioned first or exclusively, such as in links to Windows-specific tabs and PowerShell runbooks. Linux equivalents are referenced but not always with equal prominence or detail. Some links default to Windows tabs, and automation examples highlight PowerShell before Python. There are no explicit Linux command examples or Linux-centric workflow illustrations.
Recommendations
- Ensure that all linked guides and quickstarts include Linux/macOS examples and reference them equally alongside Windows.
- When listing supported automation tools (PowerShell, Python, etc.), avoid putting Windows tools first unless justified by usage statistics.
- Add explicit Linux/macOS command-line examples (e.g., Bash, CLI) where PowerShell is referenced.
- Review linked pages to ensure Linux parity in tabs and examples.
- Where possible, provide screenshots or walkthroughs for Linux environments in addition to Windows.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell CLI examples for updating external validation status, but consistently presents Bash examples first. There are no Windows-specific tools, patterns, or exclusive references; all API and CLI instructions are cross-platform. No PowerShell-only or Windows-only bias is present, and Linux parity is maintained throughout.
Recommendations
- Continue to provide both Bash and PowerShell examples for CLI commands.
- Consider explicitly stating that the Azure CLI commands work identically on Linux, macOS, and Windows.
- If possible, add a short note clarifying that the examples are cross-platform and that the Azure CLI is supported on all major OSes.
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 is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used exclusively or preferentially. All commands use the Azure CLI and Helm, both cross-platform tools. There are no missing Linux examples, nor is there any evidence of Windows-only tools or instructions.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell examples are supported on all platforms where Azure CLI and Helm are available.
- Add a brief note clarifying that Bash examples are suitable for Linux/macOS terminals and Windows users using WSL or Git Bash.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for each command, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, and the tab labels sometimes use 'PowerShell' instead of 'Windows', which may subtly imply Windows as a primary platform. There are no missing Linux examples or exclusive Windows tools/patterns.
Recommendations
- Ensure Bash and PowerShell examples are presented with equal prominence, possibly alternating their order or using neutral tab labels such as 'Linux/macOS' and 'Windows'.
- Clarify that both Bash and PowerShell examples are functionally equivalent and applicable depending on the user's OS.
- Consider adding a brief note at the top indicating that all commands are cross-platform via Azure CLI, and users can choose their preferred shell.
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 between Linux/macOS and Windows users. However, in each section, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No Linux/macOS examples are missing, and no Windows-only tools are referenced.
Recommendations
- Continue to provide both Bash and PowerShell examples for all CLI operations.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows, to reinforce parity.
- Add a short note clarifying that Azure CLI commands work on all platforms (Windows, Linux, macOS) and that Bash examples are suitable for Linux/macOS users.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are sometimes shown immediately after Bash, and certain minor details (such as base64 encoding) are explained in both environments. No Windows-specific tools or patterns are used, and Linux/macOS equivalents are present throughout. The documentation does not prioritize Windows tools or omit Linux examples, but PowerShell is given equal prominence, which may be unnecessary given the cross-platform nature of Azure CLI and Kubernetes.
Recommendations
- Consider listing Bash examples first in each section, as Bash is the default shell for Linux/macOS and is also available on Windows via WSL.
- Clarify that Bash examples are suitable for Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- Where possible, consolidate examples to highlight cross-platform commands (e.g., Azure CLI, Docker, kubectl) and minimize shell-specific syntax unless necessary.
- Ensure that any shell-specific instructions (such as file encoding or base64 commands) are clearly marked for their respective environments.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in nearly every section, Bash examples are shown first, followed by PowerShell. No Windows-specific tools or patterns are used exclusively, and all commands rely on cross-platform Azure CLI and Helm tools. There are no missing Linux examples, nor are Windows tools mentioned before their Linux equivalents.
Recommendations
- Maintain the current structure, as Linux/macOS parity is strong.
- Consider alternating the order of Bash and PowerShell tabs in some sections, or explicitly note that Bash is suitable for Linux/macOS and PowerShell for Windows, to reinforce parity.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While PowerShell is primarily associated with Windows, Azure CLI is cross-platform. However, the documentation does not provide explicit Linux/macOS examples or mention Bash scripts, and PowerShell is listed before CLI, which may subtly prioritize Windows users.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Mention Bash script generation as a possible capability if supported.
- When listing scripting options, alternate the order or explicitly state Linux/macOS support.
- Provide examples or links for Linux/macOS users where relevant.
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is presented after the CLI section. PowerShell is a Windows-centric tool (though cross-platform support exists), and its inclusion is appropriate, but there is no explicit mention that Azure CLI commands work on Linux/macOS equally well. The CLI examples are shown first, which is a positive for Linux parity. However, the PowerShell section could be interpreted as Windows-focused, especially since there is no Bash or shell scripting example, nor explicit reassurance for Linux/macOS users. No Linux-specific tools or shell scripting examples are provided.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding a short Bash shell script example for deploying a dashboard template using Azure CLI, to demonstrate Linux-native usage.
- In the PowerShell section, clarify that Azure PowerShell is available cross-platform, or link to installation instructions for Linux/macOS if appropriate.
- Ensure that any references to file paths or environment variables in examples use cross-platform conventions or provide both Windows and Linux/macOS variants if relevant.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is referenced throughout tables and sections. The main authentication table lists PowerShell commands alongside CLI commands, and PowerShell is given its own example blocks, even though Linux/macOS users rarely use PowerShell. There is a minor Windows-first bias in the order of examples and the persistent mention of PowerShell. However, Azure CLI (cross-platform) is always present, and Docker commands are shown in a platform-neutral way. There are no critical missing Linux/macOS instructions, but the prominence of PowerShell may confuse or distract non-Windows users.
Recommendations
- Clearly indicate that Azure PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- In the authentication options table, list Azure CLI before PowerShell, and consider footnoting PowerShell as 'Windows only' or 'optional'.
- Where PowerShell is shown, add a note that it is available cross-platform but is most commonly used on Windows, and link to installation instructions for Linux/macOS if relevant.
- Consider adding explicit bash/zsh shell examples where environment variables or scripting are involved, to further improve Linux parity.
- Review the overall balance of CLI vs PowerShell examples to ensure CLI is the default and PowerShell is supplementary.
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 several places (e.g., setting environment variables), Windows-style commands (e.g., 'set ACR_NAME=<container-registry-name>') are shown without Linux/macOS equivalents. Additionally, the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-specific) mentioned before Portal, and no explicit Linux/macOS guidance. The overall bias is minor, as most commands are cross-platform, but Linux/macOS users may encounter friction due to missing shell-specific instructions.
Recommendations
- Provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples for setting environment variables (e.g., use 'export ACR_NAME=<container-registry-name>' alongside 'set').
- Clarify that Azure CLI commands are cross-platform and can be used on Linux/macOS.
- When listing options for Kubernetes cluster creation, mention Linux/macOS-friendly methods (e.g., Azure CLI, Portal) before Windows-specific tools like PowerShell.
- Add notes or tabs for shell-specific instructions where relevant.
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 both Azure CLI and Azure PowerShell examples for all import scenarios, ensuring parity between command-line tools. However, PowerShell is a Windows-centric tool, and its examples are always presented alongside Azure CLI, sometimes with PowerShell mentioned first in metadata. There are no explicit Windows-only tools or patterns, and all instructions are cross-platform via Azure CLI. No Linux/macOS-specific examples or troubleshooting are provided, but the CLI is inherently cross-platform.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and preferred for Linux/macOS users.
- Consider adding a brief note or section for Linux/macOS users, confirming that Azure CLI works natively on their platforms and linking to installation instructions.
- Ensure that Azure CLI examples are presented first in each section, as it is the most cross-platform tool.
- Add troubleshooting tips for Linux/macOS environments if any issues are platform-specific.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations, such as viewing registry usage and changing SKUs. However, PowerShell examples are consistently shown alongside or immediately after CLI examples, and PowerShell is mentioned in API lists before REST API. There are no Linux-specific examples (e.g., Bash scripting), and the CLI examples are generic, but the presence and order of PowerShell references and examples indicate a mild Windows bias.
Recommendations
- Ensure that Azure CLI examples are presented first, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and Windows, and provide Bash shell usage examples where relevant.
- Consider adding notes or examples for common Linux container tooling (e.g., Podman, containerd) in performance sections.
- Clarify that PowerShell is primarily for Windows users, and link to cross-platform PowerShell documentation if relevant.