226
Pages Scanned
53
Pages Flagged
226
Changed Pages
23.5%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-08 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
55 issues found
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides recovery instructions and a downloadable script exclusively for Windows/PowerShell environments, with no mention of Linux or cross-platform alternatives. All examples and tooling are Windows-centric, and there are no steps or scripts for Linux/macOS users.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
- Clearly indicate if recovery is only supported from Windows, and explain why (e.g., dependencies on SCVMM or PowerShell modules unavailable on Linux).
- If feasible, offer a platform-agnostic recovery method (such as an Azure CLI or REST API workflow) to ensure Linux/macOS users can perform the same recovery operations.
Create Pull Request
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 references Windows tools (e.g., Notepad, SSMS) without offering equivalent Linux/macOS commands, file paths, or tool suggestions. Linux/macOS users are left to adapt the instructions themselves, which may cause confusion or friction.
Recommendations
- Add parallel examples for Linux/macOS users, including file paths (e.g., /home/user/backup/test.bak) and commands.
- Mention cross-platform alternatives to Notepad (e.g., gedit, nano, TextEdit) when suggesting where to paste credentials.
- Clarify that Visual Studio Code, Azure Storage Explorer, and kubectl are cross-platform, and provide installation links for Linux/macOS.
- When referencing SSMS (Windows-only), suggest Azure Data Studio as a cross-platform alternative for backup/restore operations.
- Show both Windows and Linux/macOS file path examples in backup/restore commands and kubectl cp usage.
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
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances where Windows-specific tools (PowerShell, RDP) are referenced, and Windows-centric patterns (e.g., PowerShell commands, Windows paths) are presented before Linux equivalents. For example, PowerShell is used for HTTP/2 troubleshooting, and Windows file paths are shown in error messages. Linux troubleshooting commands are mentioned only in passing (e.g., ldd --version for GLIBC), and some CLI instructions reference Windows environments (e.g., C:\Program Files).
Recommendations
- Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP/2 troubleshooting).
- Ensure CLI troubleshooting steps include both Windows and Linux paths and error messages.
- When referencing file system locations or permissions, include both Windows and Linux/macOS examples.
- When suggesting remote access, mention SSH for Linux/macOS alongside RDP for Windows.
- Review all troubleshooting steps to ensure Linux/macOS users are equally supported and not required to use Windows tools.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell migration script (WOGAMigration.ps1) and instructs users to run it in PowerShell, with no mention of Bash, Linux shell equivalents, or cross-platform alternatives. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell environments.
Recommendations
- Provide a Bash or shell script equivalent for Linux/macOS users.
- Document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core, pwsh).
- Add explicit instructions or troubleshooting for Linux/macOS environments.
- Clarify if the script is cross-platform or Windows-only, and offer alternatives if not.
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
While the documentation is focused on configuring AKS Edge Essentials on Linux, it relies on the PowerShell-based Invoke-AksEdgeNodeCommand for system configuration steps (e.g., checking and setting sysctl values). There are no direct Linux shell (bash) equivalents provided for these commands, which may create friction for users working directly on Linux hosts without Windows tools.
Recommendations
- Provide native Linux shell (bash) command examples for checking and setting sysctl values (e.g., 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p').
- Clarify when and why Invoke-AksEdgeNodeCommand is required, and offer alternatives for users managing Linux hosts directly.
- Ensure all critical configuration steps can be completed using standard Linux tools, not just via PowerShell modules.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd) and labels these blocks as 'powershell'. There are no explicit Linux/macOS shell examples, and the PowerShell blocks are presented first and exclusively. This may create friction for Linux/macOS users unfamiliar with PowerShell or expecting bash/zsh syntax.
Recommendations
- Add equivalent Linux/macOS shell examples (e.g., bash/zsh) for connecting to the SQL Server pod using sqlcmd.
- Label code blocks appropriately (e.g., 'console' or 'bash') instead of 'powershell' when the command is not PowerShell-specific.
- Ensure that instructions and examples are platform-neutral where possible, or provide parallel examples for each major OS.
- Clarify that the commands can be run from any OS with kubectl and sqlcmd installed, not just Windows/PowerShell environments.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly lists PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools like Azure CLI and Visual Studio Code. No Linux/macOS-specific examples, tools, or patterns are provided, and Windows tools are listed without Linux alternatives or parity discussion.
Recommendations
- Add examples or mention of Linux/macOS-compatible management tools (e.g., sqlcmd, Azure Data Studio, mssql-cli).
- Clarify which features and tools are available or supported on Linux/macOS environments.
- Provide parity tables or notes for manageability features and scripting support on non-Windows platforms.
- Include links or references to cross-platform documentation and usage guides.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation references Azure CLI installation links that default to Windows, and mentions Azure CLI x64 and x86 requirements without clarifying Linux/macOS equivalents. The management machine requirements and CLI instructions do not specify Linux/macOS support or provide parity guidance, which may create friction for non-Windows users.
Recommendations
- Explicitly state that Azure CLI is supported on Linux and macOS, and provide installation links for those platforms alongside Windows.
- Clarify whether 'x64' and 'x86' requirements apply to Linux/macOS, or if they are Windows-specific.
- Add examples or guidance for Linux/macOS management machines, including directory paths and CLI usage.
- Ensure CLI commands and file locations are described in a cross-platform manner.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally provides parity between Windows and Linux for feature lists and bug fixes, but there is a consistent pattern of presenting Windows download links and version numbers before Linux. Known issue troubleshooting steps are provided only for Windows, with detailed PowerShell and Command Prompt commands, while Linux equivalents are absent. Some improvements and bug fixes reference Windows-specific tools (e.g., PowerShell scripts, MSI installer) without mentioning Linux alternatives.
Recommendations
- When presenting download links or version tables, alternate the order or present Windows and Linux together to avoid implicit prioritization.
- For troubleshooting steps (e.g., editing agent configuration files), provide equivalent Linux commands (such as chmod/chown or nano/vi usage) alongside Windows instructions.
- Where improvements or bug fixes reference Windows-specific tools (e.g., PowerShell scripts, MSI installer), clarify if there are Linux equivalents or note if the issue is not applicable to Linux.
- Consider adding a section or callout for Linux-specific known issues and troubleshooting steps, even if there are currently none, to demonstrate parity.
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 a comprehensive overview of deployment options for both Linux and Windows, but there is a noticeable emphasis on Windows-specific tools and workflows. PowerShell is highlighted as a primary method for both platforms, and several Windows-only methods (such as Windows Admin Center, Group Policy, and Configuration Manager) are listed separately and in detail. Linux-specific automation tools (other than Ansible) are not mentioned, and PowerShell is presented as a cross-platform solution, which may not align with typical Linux admin workflows.
Recommendations
- Add explicit Bash or shell script examples for Linux where PowerShell is currently suggested, or clarify that PowerShell Core is required on Linux for those methods.
- Include Linux-native automation tools (e.g., cloud-init, shell scripts, or configuration management tools like Chef/Puppet) if supported.
- When listing onboarding methods, alternate the order or group by OS to avoid a Windows-first impression.
- Clarify in the PowerShell method description that it is cross-platform, and provide direct Linux command-line examples where possible.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there are signs of Windows bias: Windows examples and instructions are often presented first, especially in sections with tabbed content; PowerShell is heavily used for scripting and automation examples (e.g., stale resource cleanup); and Windows-specific tools and infrastructure (e.g., Group Policy, WSUS, Configuration Manager) are described in detail, while Linux equivalents (such as package management automation or scripting) are not covered as thoroughly.
Recommendations
- Alternate the order of Windows and Linux examples in tabbed sections, or present Linux instructions first in some cases.
- Provide equivalent Linux shell scripts for automation tasks, such as stale resource cleanup, using Azure CLI or Bash.
- Expand documentation for Linux update automation (e.g., using cron, unattended-upgrades, or systemd timers) to match the detail given for Windows update infrastructure.
- Include references to Linux configuration management tools (e.g., Ansible, Puppet, Chef) where Windows tools like Group Policy or Configuration Manager are mentioned.
- Where PowerShell scripts are provided for Azure resource management, offer Azure CLI or Bash alternatives for Linux users.
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 each VM extension, ensuring parity in template usage. However, all deployment commands and walkthroughs use Azure PowerShell exclusively, with no Azure CLI or Bash examples. PowerShell commands are shown first and are the only method described for deploying templates, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Additionally, file path examples use Windows-style paths (e.g., 'D:\Azure\Templates'), which may be confusing for non-Windows users.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell, especially for template deployments (e.g., az deployment group create).
- Include Bash or shell script snippets for Linux/macOS users where appropriate.
- Show file path examples using both Windows and Linux conventions (e.g., 'D:\Azure\Templates' and '/home/user/Azure/Templates').
- Explicitly mention that Azure PowerShell commands can be run cross-platform, but Azure CLI is often preferred on Linux/macOS.
- Consider listing Azure CLI deployment commands before or alongside PowerShell to avoid 'windows_first' bias.
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
missing_linux_example
Summary
The documentation provides a generally cross-platform overview but exhibits some Windows bias. Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly, while Linux equivalents (such as Cockpit, cloud-init, or Linux package managers) are not. PowerShell is referenced as a deployment method, but Bash is only mentioned generically, with no concrete Linux command-line examples. There are no Linux-specific deployment walkthroughs or examples, and Windows deployment options are listed before Linux ones.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, cloud-init, or Ansible for onboarding Linux servers.
- Mention Linux-native tools (e.g., Cockpit, systemd, package managers) where appropriate, especially in the 'Deploying Azure Arc' section.
- Provide concrete Bash or shell command examples alongside PowerShell, not just generic references.
- Balance the order of presentation so that Linux and Windows deployment options are given equal prominence.
- Clarify that all major features and workflows are supported on both Windows and Linux, or call out any exceptions.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples (especially in PowerShell and REST API sections) are Windows-centric. PowerShell examples use Windows-style scripts and paths, and REST API examples exclusively show Windows-specific commands (e.g., New-NetFirewallRule). There is a lack of Linux-specific script examples (e.g., using bash or Linux firewall commands), and Windows tools (like New-AzStorageBlobSASToken) are referenced without Linux equivalents. The Azure CLI section also defaults to PowerShell syntax in its script example. Linux is only mentioned in passing, and Linux users are left to infer how to adapt the examples.
Recommendations
- Provide parallel Linux-focused examples for each scenario, using bash scripts, Linux shell commands, and Linux file paths.
- In PowerShell sections, clarify cross-platform usage or provide bash alternatives where possible.
- In REST API examples, include at least one Linux scenario (e.g., using iptables or ufw for firewall configuration).
- When referencing tools like New-AzStorageBlobSASToken, mention cross-platform alternatives or CLI equivalents.
- In all sections, alternate or balance the order of Windows and Linux examples, or clearly label which OS each example targets.
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 moderate Windows bias. The primary automation script is PowerShell-based, with instructions to use Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents. Linux-specific guidance is limited to a brief sudo configuration note, and there are no Linux shell or cron examples for running the automation script. Out-of-band methods mention Ansible, but most scripted examples and automation focus on Windows environments.
Recommendations
- Provide equivalent Bash/shell script examples for Linux/macOS users, including instructions for running the automation script in a Linux environment.
- Add guidance for scheduling the automation script using Linux cron jobs, not just Windows Task Scheduler.
- Ensure that all PowerShell scripts are accompanied by Linux-compatible alternatives or clarify if the script is Windows-only.
- Mention Linux tools and patterns (e.g., systemd timers, cron) alongside Windows tools.
- Expand Linux-specific prerequisites and troubleshooting sections.
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 shell, or cross-platform alternatives. All command-line instructions and code snippets are PowerShell-based, and there is no guidance for Linux or macOS users on how to perform equivalent operations or run the script. This creates friction for non-Windows users attempting disaster recovery operations.
Recommendations
- Provide explicit instructions for running the onboarding script on Linux/macOS, including prerequisites (such as PowerShell Core installation) and any differences in usage.
- Offer Bash or shell script alternatives if available, or clarify if the onboarding script is cross-platform and how to execute it on non-Windows systems.
- Add notes about required tools for Linux/macOS users (e.g., PowerShell Core, Azure CLI) and any potential limitations.
- Include Linux/macOS-specific examples or highlight any OS-specific steps.
- Clarify if the onboarding script is Windows-only; if so, suggest workarounds or alternatives for Linux/macOS users.
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, with PowerShell-specific guidance and notes. Linux users are not given equivalent instructions or examples for running the script, and Windows steps are presented first and in greater detail. However, Linux uninstall instructions for the agent are included, and the overall process is not Windows-exclusive.
Recommendations
- Add explicit instructions and examples for running the deboarding script on Linux/macOS, including shell commands and prerequisites.
- Clarify whether the deboarding script can be run cross-platform (e.g., with PowerShell Core or Azure CLI), and provide guidance for Linux users.
- Present Windows and Linux instructions in parallel or clearly labeled sections to improve parity.
- Include troubleshooting notes for Linux/macOS environments similar to the PowerShell ISE note for Windows.
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 a PowerShell script (bulk_deployment.ps1) for bulk deployment automation. There are no explicit Linux/macOS shell examples (e.g., Bash), and the script provided is Windows-specific, creating friction for non-Windows users. Azure CLI is cross-platform, but the documentation's examples and automation focus on Windows tools and syntax.
Recommendations
- Provide Azure CLI command examples in Bash syntax, or clarify that the CLI commands work identically on all platforms.
- Offer a Bash shell script equivalent to bulk_deployment.ps1, or provide guidance for Linux/macOS users on how to perform bulk deployment automation.
- Explicitly state platform compatibility for the Azure CLI commands and scripts.
- Mention any prerequisites or limitations for Linux/macOS users, such as the lack of a PowerShell script equivalent.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. All usage examples are PowerShell-based, with no mention of Linux/macOS-compatible alternatives (such as Bash scripts or cross-platform instructions). The script is referenced as a .ps1 file, which is traditionally associated with Windows environments, and there is no guidance for Linux users on how to run the script (e.g., using PowerShell Core on Linux/macOS or alternative approaches).
Recommendations
- Add instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux and macOS, including any prerequisites or installation steps.
- Provide explicit examples for Linux/macOS users, such as running './RGCleanScript.ps1' in pwsh, and clarify any differences in syntax or behavior.
- Mention whether the script is compatible with cross-platform PowerShell (PowerShell Core), or provide a Bash equivalent if possible.
- Include troubleshooting tips for Linux/macOS users (e.g., file permissions, execution policy).
- Clearly state if the script is Windows-only, or highlight cross-platform support if available.
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 provides all CLI and scripting examples using PowerShell syntax and Windows-style file paths. There are no Bash, Linux, or macOS shell examples, and file path references (e.g., C:\, E:\) are Windows-specific. The onboarding scripts are referenced as PowerShell (.ps1) only, with no mention of Bash or cross-platform alternatives. This creates friction for Linux/macOS users, who must translate commands and paths themselves.
Recommendations
- Provide Bash/zsh equivalents for all PowerShell CLI examples, using Linux/macOS file path conventions.
- Clarify whether the onboarding scripts (.ps1) are cross-platform (e.g., can be run with PowerShell Core on Linux/macOS) or provide Bash alternatives.
- Use generic file path placeholders or show both Windows and Linux/macOS path formats in JSON templates.
- Explicitly mention any OS requirements for scripts and tools, and link to cross-platform installation instructions for Azure CLI and PowerShell Core.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The extraction instructions for the ZIP file use Windows-specific paths and tools (e.g., Expand-Archive with Windows-style paths, winget for kubectl installation), and do not provide Linux/macOS equivalents. Bash examples are shown, but often with Windows paths or commands that are not cross-platform. There is no guidance for Linux/macOS users on extracting ZIP files or installing kubectl. The documentation assumes a Windows environment in several places, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS equivalents for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/workspace').
- Use cross-platform paths in Bash examples (e.g., '/home/user/cm/workspace' instead of 'C:\path\to\cm\workspace').
- Add instructions for installing kubectl on Linux/macOS (e.g., 'curl -LO ...', 'sudo apt install kubectl', or 'brew install kubectl').
- Clarify which commands are Windows-only and offer alternatives for other platforms.
- Ensure Bash examples are truly cross-platform and not just Windows paths in Bash syntax.
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/PowerShell environments. All onboarding scripts and usage examples are provided only for PowerShell, with no mention of Bash, Linux, or macOS equivalents. Windows-specific tools like 'winget' are used for prerequisites, and there are no instructions for installing dependencies on Linux/macOS. This creates friction for non-Windows users and may prevent them from following the onboarding process without significant adaptation.
Recommendations
- Provide Bash (or generic shell) equivalents for all PowerShell script invocations, or clarify if the scripts are truly Windows-only.
- List Linux/macOS installation commands for prerequisites (e.g., using apt, yum, brew for Azure CLI and kubectl) alongside or before Windows/winget commands.
- Indicate script compatibility (e.g., if .ps1 scripts are cross-platform via PowerShell Core, state this explicitly; if not, provide alternative scripts or guidance for Linux/macOS users).
- Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
- Reorder examples or provide tabs for Windows, Linux, and macOS to ensure parity.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI examples primarily in Bash, but the May 2025 release section includes only PowerShell syntax for configuration commands, which may create friction for Linux/macOS users. Otherwise, the documentation is largely cross-platform, focusing on Azure CLI and portal usage, with no exclusive mention of Windows tools or patterns.
Recommendations
- Add equivalent Bash examples for CLI commands shown in PowerShell syntax, especially in the May 2025 release section.
- Clarify that Azure CLI commands can be run on any OS and provide OS-neutral syntax where possible.
- Ensure future examples consistently include both Bash and PowerShell variants, or use OS-neutral command formatting.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most command examples, including those for Azure CLI, Kubernetes, Docker, and file manipulation, are provided in PowerShell syntax only, with no equivalent Bash or Linux shell examples. Windows-specific scripting patterns (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding via .NET) are used throughout. Bash/Linux examples are only provided in the 'Troubleshoot service groups' section, and even there, PowerShell is shown first or equally. This creates friction for Linux/macOS users, who must translate Windows-centric instructions to their environments.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and Kubernetes operations.
- Use cross-platform variable assignment and scripting patterns (e.g., environment variables, jq for JSON manipulation, base64 for encoding) instead of PowerShell-specific constructs.
- Where file encoding or manipulation is required, offer Linux/macOS-compatible instructions (e.g., using iconv, cat, jq, etc.).
- Ensure Bash examples are presented before or alongside PowerShell, not after.
- Review all troubleshooting steps for Windows-centric language and tools, and add Linux/macOS guidance as needed.
Container Registry
Quickstart - Create Geo-Replicated Registry - ARM Template
...ontainer-registry-get-started-geo-replication-template.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation primarily describes deploying an ARM template via the Azure portal, with brief mention of Azure PowerShell, Azure CLI, and REST API as alternative methods. However, the portal workflow is detailed step-by-step, while CLI/PowerShell methods are only referenced via a link, with no direct examples or instructions. There are no explicit Windows-only tools, but the lack of Linux/macOS-specific guidance or parity in example coverage creates a subtle bias toward Windows/portal users.
Recommendations
- Add explicit step-by-step instructions and examples for deploying the ARM template using Azure CLI, including commands compatible with Linux/macOS.
- Provide PowerShell examples as a secondary option, ensuring CLI instructions are not overshadowed.
- Include guidance for reviewing and cleaning up resources using Azure CLI, not just the portal.
- Clarify that all deployment and management steps can be performed cross-platform, and highlight CLI as a first-class option.
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 throughout, with PowerShell examples often shown alongside CLI and portal instructions. Windows-specific paths and tools (e.g., PowerShell, Windows log file locations) are mentioned, but Linux equivalents are also provided. In some sections, Windows log file locations are listed first. There is minor bias in the order and prominence of Windows examples, but Linux parity is generally maintained.
Recommendations
- Ensure Linux and macOS examples are given equal prominence and ordering alongside Windows/PowerShell examples.
- Where file paths or log locations are mentioned, alternate between Windows and Linux order, or list Linux first in some cases.
- Explicitly mention that Azure CLI commands work cross-platform, and clarify any OS-specific prerequisites.
- Add notes for macOS users where relevant (e.g., file paths, script execution).
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used exclusively, and all commands are cross-platform (using Azure CLI and Helm).
Recommendations
- Maintain the current parity of examples for both Bash and PowerShell.
- 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, to reassure users.
- If possible, add a note clarifying that Azure CLI and Helm are available on all major platforms.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There is a specific note about using cmd.exe on Windows 10 instead of PowerShell for curl, and a mention that curl in PowerShell is an alias for Invoke-WebRequest, but no equivalent Linux/macOS shell guidance. The Linux installation for curl is referenced generically ('install curl package') without a link or command, and there are no explicit Linux/macOS shell examples or troubleshooting tips.
Recommendations
- List installation links for Linux/macOS before or alongside Windows, rather than Windows first.
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl', 'brew install curl').
- Add shell-specific guidance for Linux/macOS users, similar to the PowerShell/cmd.exe notes for Windows.
- Include troubleshooting tips or version checks for Linux/macOS environments as well as Windows.
- Ensure parity in detail and clarity for Linux/macOS instructions compared to Windows.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before sqlcmd (which is cross-platform). However, the command-line example for connecting uses sqlcmd and explicitly notes Linux compatibility. No Linux-specific tools (like Azure Data Studio or other SQL clients) are mentioned, and SSMS is referenced first throughout. There are no PowerShell-specific commands, but the focus on SSMS as the main GUI tool creates a mild Windows bias.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for connecting to SQL Managed Instance.
- Provide example connection instructions for Azure Data Studio or other popular Linux/macOS SQL clients.
- List sqlcmd as the first example, or clarify that it works on both Linux and Windows.
- Add a note that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
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 approaches for base64 encoding files, but the Windows method (certutil) is described in detail and includes additional steps and commands, while the Linux method is presented as a single command without further explanation. The Windows example is given immediately after the Linux command, and the Windows-specific tool (certutil) is mentioned with a link to Microsoft documentation. There are no PowerShell-heavy examples, and the rest of the guide uses cross-platform tools (openssl, Azure CLI, kubectl). However, the Windows encoding workflow is more verbose and prominent, while Linux users are given minimal guidance.
Recommendations
- Expand the Linux base64 encoding section to include decoding instructions and handling output, similar to the Windows example.
- Provide parity in guidance for Linux users, such as how to remove headers from base64 output if needed.
- Consider mentioning macOS explicitly where Linux is referenced, as the commands are likely compatible.
- Clarify that the base64 command is available on most Unix-like systems and provide troubleshooting tips for installation if missing.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical steps, but consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI. In some sections, PowerShell examples are given equal prominence to CLI, and environment variable examples for proxy configuration are shown in both Bash (Linux/macOS) and PowerShell syntax. However, there are no Linux-specific command-line examples (e.g., Bash scripts), and PowerShell is not natively available on most Linux systems. The documentation does not mention Linux tools or patterns (such as systemd, iptables, or Linux-specific networking commands), nor does it reference macOS. Azure CLI is cross-platform, but PowerShell is presented as an alternative throughout, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clearly indicate that Azure CLI is the recommended and cross-platform method for Linux/macOS users, and that PowerShell is optional for Windows users.
- Present Azure CLI examples first in each section, followed by PowerShell as an alternative for Windows users.
- Add explicit notes clarifying that Azure PowerShell commands require PowerShell Core on Linux/macOS, and provide installation links if relevant.
- Include Bash script examples or references for common tasks, especially for onboarding and proxy configuration.
- Mention Linux/macOS compatibility in prerequisites and tool installation steps.
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` shows minor Windows bias. Windows authentication options are described first, and Windows certificate store usage is detailed before Linux equivalents. The access token example references a PowerShell cmdlet (`Get-AzAccessToken`) without mentioning Linux alternatives. However, Linux authentication methods (device code, Azure CLI) are well covered, and most examples are cross-platform.
Recommendations
- Reorder authentication options so Linux-default methods (device code, Azure CLI) are described before Windows-only methods.
- When referencing access token acquisition, include Linux/macOS methods (e.g., Azure CLI: `az account get-access-token`) alongside PowerShell.
- Clarify certificate handling for Linux (e.g., typical file locations, permissions) in the certificate authentication section.
- Add explicit Linux/macOS example commands where appropriate, especially for authentication and certificate usage.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation includes references to Windows-specific services (e.g., 'time.windows.com' as the NTP server, 'servicebus.windows.net', 'sts.windows.net', 'login.windows.net') and Windows terminology, but also covers Linux-related endpoints (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com'). Windows NTP is mentioned explicitly, and Windows endpoints appear before Linux ones in some lists. However, the documentation does not provide OS-specific command examples or configuration steps, and both Linux and Windows endpoints/tools are referenced.
Recommendations
- Clarify that NTP can be configured with Linux NTP servers as well, not just 'time.windows.com'.
- Where Windows-specific endpoints are mentioned (e.g., 'servicebus.windows.net', 'sts.windows.net'), note if Linux equivalents exist or if these are cross-platform.
- Ensure that Linux-related endpoints and tools are given equal prominence and explanation.
- Add explicit notes or examples for Linux users where relevant (e.g., how to configure outbound connectivity for Linux management machines).
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation covers both Linux and Windows platforms for the Azure Connected Machine agent, with clear mention of Linux-specific installation sources and TLS requirements. However, there is a mild Windows bias: Windows installation/package URLs are consistently listed before Linux equivalents, and Windows Admin Center is referenced as a management tool without mention of Linux alternatives. Additionally, troubleshooting and cipher suite configuration links are Windows-specific, while Linux guidance is more generic (referencing OpenSSL).
Recommendations
- List Linux and Windows installation package URLs in parallel or alternate order to avoid Windows-first bias.
- Include references to Linux management tools or clarify that Windows Admin Center is Windows-only.
- Provide Linux-specific troubleshooting links or guidance for TLS configuration (e.g., OpenSSL settings, common Linux issues).
- Expand Linux guidance beyond generic OpenSSL references, such as mentioning how to verify TLS settings or cipher suites on common distributions.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Windows and Linux Azure Arc-enabled servers, and provides parity in most sections. However, there is a minor bias in the order of examples: Azure PowerShell is presented after Azure CLI, but PowerShell is referenced heavily and installation instructions are only given for PowerShell (not for Bash or Linux shells). In the 'Manage automatic extension upgrade' section, Azure CLI is described as cross-platform, but PowerShell is presented as a separate tab, which may subtly prioritize Windows users. No critical Linux functionality is missing, and all CLI commands are cross-platform.
Recommendations
- Add explicit instructions for installing Azure CLI on Linux/macOS, similar to the PowerShell module installation tip.
- Clarify that Azure PowerShell can be used on Linux/macOS as well, or link to installation instructions for those platforms.
- Consider mentioning Bash/zsh usage in the PowerShell section, or provide parity tips for Linux users.
- Ensure screenshots and portal navigation are not Windows-centric (current screenshots are neutral).
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 dedicated tables for each OS. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, templates) are mentioned equally, and partner extensions are shown for both OSes. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to reinforce parity.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Add a brief introductory note emphasizing equal support for Windows and Linux Arc-enabled servers.
- Ensure linked deployment guides for CLI and PowerShell include both Windows and Linux examples.
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, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed and visually emphasized (with a screenshot). The Linux/Bash example follows and is also accompanied by a screenshot. The prerequisites and guidance are generally balanced, mentioning both Windows and Linux requirements and linking to platform-specific tutorials. The 'Related content' section lists PowerShell before Azure CLI, which may subtly reinforce Windows-first patterns.
Recommendations
- Present Windows and Linux examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
- Ensure equal detail and visual emphasis for both Windows and Linux examples (e.g., screenshots, code comments).
- In 'Related content', list Azure CLI and PowerShell together or alternate their order to avoid Windows-first bias.
- Consider adding a brief note at the start clarifying that both Windows and Linux are fully supported and that examples for both are provided.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, with clear parity in error/exit code tables and log file locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. Windows-specific log paths and tools (e.g., PowerShell, Windows environment variables) are mentioned before Linux equivalents. There is minor bias in ordering and tool emphasis, but Linux users are not blocked from completing any task.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid implicit prioritization.
- Where possible, provide cross-platform command syntax side-by-side for clarity.
- Ensure Linux log paths and troubleshooting steps are equally prominent and detailed.
- Add explicit notes that all troubleshooting steps apply to both Windows and Linux unless otherwise stated.
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is focused on Azure Arc-enabled System Center Virtual Machine Manager (SCVMM), which is a Windows-centric technology. Most requirements, examples, and supported operating systems are Windows Server versions. Windows tools and concepts (WinRM, Windows Management Framework, VMM IP Pool, SCVMM admin accounts) are mentioned first and in detail. Linux support is referenced, but only as an alternative for installing Arc agents, and Linux requirements are listed after Windows. The deployment script is noted to work on Linux, but with performance caveats.
Recommendations
- Clarify early in the document that SCVMM is a Windows-only management platform and that Linux support is limited to guest OS agent installation.
- Provide more explicit Linux examples for agent installation, including command-line steps and troubleshooting tips.
- Where Linux is supported (e.g., agent installation), ensure Linux requirements and steps are given equal prominence to Windows.
- Add a comparison table or section summarizing Windows vs. Linux support for each major feature.
- If possible, improve the deployment script performance for Linux workstations, or document workarounds.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there are subtle signs of Windows bias: Windows-related features (such as Windows Server management and Extended Security Updates) are highlighted first in benefit lists, and PowerShell is mentioned before other automation tools in the context of Azure Automation. Some links and examples reference Windows-specific tabs or features before Linux equivalents, even though Linux is supported.
Recommendations
- Ensure Linux examples and references are presented alongside Windows examples, not after or as an afterthought.
- When listing automation tools, mention Bash or Linux shell scripting equally with PowerShell.
- Where links point to Windows-specific documentation (e.g., tabs=windows), also provide links or tabs for Linux guidance.
- In benefit lists, clarify which features are Windows-only and which apply to Linux, to avoid confusion.
- Consider adding explicit Linux-focused scenarios or examples to highlight parity.
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
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and PowerShell notes are presented first and in greater detail. Windows-specific issues (e.g., PowerShell ISE limitations, Set-ExecutionPolicy) are discussed, while Linux instructions are more concise. The retry command section also presents Windows first. However, Linux parity is generally maintained, and both platforms are supported.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid Windows-first bias.
- Add troubleshooting notes for Linux (e.g., common Bash issues, permission requirements) similar to the PowerShell ISE note for Windows.
- Ensure that screenshots and UI references are platform-neutral or clarify if any steps differ for Linux users.
- Consider a table or tabbed layout for OS-specific instructions to improve clarity and parity.
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 CLI commands, but consistently presents Bash examples first. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. No critical sections are Windows-only, and all tasks can be completed on Linux/macOS using the Azure CLI.
Recommendations
- Continue to provide both Bash and PowerShell examples for cross-platform parity.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- If possible, add a brief note at the top indicating that all commands are cross-platform via Azure CLI.
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 are based on the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows-only tools are referenced.
Recommendations
- Consider alternating the order of Bash and PowerShell examples to avoid implicit prioritization.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
- If possible, provide a brief note about using Azure CLI in different environments (e.g., Bash on Linux/macOS, PowerShell on Windows) for clarity.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, but the Bash tab is presented first. There are no Windows-specific tools, patterns, or exclusive examples; all instructions use the Azure CLI, which is cross-platform. No Linux examples are missing, and Linux users can follow the Bash instructions without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider alternating the order of Bash and PowerShell tabs or clarifying that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state that Azure CLI commands work on all platforms to reassure users.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, and in some cases, variable syntax in PowerShell is shown with Windows-style conventions. There are no Windows-only tools or patterns, and all commands are cross-platform (Azure CLI, kubectl). No Linux example is missing, and no Windows-specific tools are mentioned.
Recommendations
- Maintain Bash examples as the default or first tab, as currently done.
- Consider clarifying that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a brief note at the top indicating that both Bash and PowerShell are supported, and users should select the tab matching their environment.
- Ensure that all variable names and file paths are generic and not Windows-specific (e.g., avoid backslashes or Windows drive letters).
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying dashboards, but the PowerShell section is given equal prominence to the CLI section and is not clearly marked as Windows-specific. PowerShell is cross-platform, but many Linux/macOS users prefer the CLI. The CLI examples are shown before PowerShell, which is good, but the PowerShell section could be more clearly marked as optional for non-Windows users. There are no Linux/macOS-specific shell examples (e.g., bash scripting), but the CLI commands are cross-platform. No Windows-only tools or patterns are used, and the documentation does not omit Linux support.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but most Linux/macOS users will prefer the Azure CLI.
- Optionally, add a brief note at the start of the PowerShell section indicating that PowerShell is available on all platforms, but CLI is the default on Linux/macOS.
- Consider adding a short bash script example for deploying a dashboard template using the Azure CLI to further improve Linux parity.
- Ensure that all CLI examples use syntax compatible with bash/zsh (e.g., avoid Windows-style line continuations).
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented before PowerShell, which could be considered a minor 'windows_first' bias if the reverse were true. No Windows-specific tools or patterns are mentioned exclusively, and all commands use the cross-platform Azure CLI and Helm tools. There are no missing Linux examples or Windows-only tools.
Recommendations
- Maintain the current structure, as Bash examples are shown first, which is preferable for Linux/macOS parity.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
- If possible, clarify that Azure CLI and Helm are cross-platform tools to reassure users of compatibility.
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 for Linux/macOS and Windows users. However, PowerShell examples are present throughout and sometimes shown immediately after Bash, which may be interpreted as a mild Windows bias. There are no Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. Bash examples are consistently provided first, and there are no missing Linux examples or exclusive Windows tools.
Recommendations
- Maintain Bash examples as the primary tab and ensure Bash is shown first for all code blocks.
- Clarify in the introduction that all steps are cross-platform and that PowerShell is provided for Windows users.
- Consider adding a note that Azure CLI and Helm commands are identical across platforms, except for shell syntax.
- Ensure that any future additions do not introduce Windows-only tools or patterns unless the feature is Windows-specific.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions generating CLI and PowerShell scripts as a key capability of Azure Copilot in the mobile app. PowerShell is listed alongside CLI, but is traditionally associated with Windows, and its mention before Bash or Linux shell scripting may subtly prioritize Windows users. No explicit Linux/Bash examples or tools are referenced, and PowerShell is the only scripting language named besides 'CLI'.
Recommendations
- Explicitly mention Bash or Linux shell scripting as a supported output for code generation.
- Provide examples or clarify that Azure Copilot can generate scripts for both Windows (PowerShell) and Linux/macOS (Bash, Azure CLI).
- Ensure parity in documentation by listing Bash/Linux shell scripting alongside PowerShell, not after or omitted.
- Add a note that Azure Copilot supports cross-platform script generation, including for Linux and macOS users.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. However, the Azure CLI example (which is cross-platform and Linux-friendly) is presented first, followed by the Azure PowerShell example. No Windows-specific tools or patterns are mentioned exclusively, and there are no missing Linux/macOS examples. The overall workflow and recommendations are platform-neutral, focusing on Azure services and Docker, which are cross-platform.
Recommendations
- Maintain the Azure CLI example as the primary example, since it is cross-platform.
- Consider explicitly mentioning that Azure CLI works on Linux, macOS, and Windows, while Azure PowerShell is most commonly used on Windows.
- If possible, add a brief note clarifying that all shown workflows are supported on Linux/macOS unless otherwise stated.
- Ensure parity in future updates by providing Bash or shell script examples if automation is discussed.
- No changes are strictly required, but clarifying platform support can further improve Linux/macOS user experience.
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 instructions and is given its own tab. There is a minor Windows bias in that PowerShell is referenced and the Visual Studio Code terminal shortcut (Ctrl+`) is Windows-centric, but Linux users are not blocked from completing the task. The CLI example is cross-platform and appears first.
Recommendations
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS.
- Mention Bash or other Linux/macOS terminals as alternatives to PowerShell and Visual Studio Code terminal.
- Provide explicit instructions or shortcuts for opening terminals on Linux/macOS.
- Consider listing Azure CLI instructions before PowerShell in all sections.
- Add a note that PowerShell Core is available cross-platform, but Bash is the default shell on Linux/macOS.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, with PowerShell examples and references present throughout. In several places, PowerShell is mentioned alongside CLI, and in the main authentication options table, PowerShell commands are often listed after CLI but before mentioning Linux-specific alternatives. However, the CLI examples are cross-platform and the documentation does mention using alternative container tools (like podman) and provides bash-style variable assignment, which is Linux-friendly. There are no sections that are Windows-only, and Linux users can complete all tasks described.
Recommendations
- Continue to present Azure CLI examples first, as these are cross-platform, but consider explicitly stating that Azure CLI commands work on Linux, macOS, and Windows.
- Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, or provide bash/zsh equivalents where relevant.
- In the authentication options table, consider listing CLI-only or bash-native options before PowerShell, or clearly marking PowerShell as optional for Windows users.
- Expand the section on alternative container tools to include a brief example for Linux/macOS users using bash/zsh, if any differences exist.
- Where environment variables are set (e.g., DOCKER_COMMAND), clarify that the syntax shown is bash/zsh and works on Linux/macOS.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell authentication and image removal examples, but PowerShell examples are given equal prominence and are not clearly marked as Windows-only. The PowerShell sections may create friction for Linux/macOS users, as PowerShell is not the default shell on those platforms. Additionally, in the prerequisites, Windows is mentioned before Linux/macOS in the Docker installation links, and PowerShell is listed as a way to create a registry before the Azure CLI.
Recommendations
- Clearly indicate that Azure PowerShell examples are primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more widely used outside Windows.
- Add explicit notes or tabs clarifying which commands are platform-specific, and provide parity for Linux/macOS users.
- In prerequisites, list Linux/macOS before Windows or alphabetically to avoid subtle Windows-first bias.
- Where possible, avoid suggesting PowerShell as a primary method for tasks that can be accomplished with Azure CLI.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is generally cross-platform, as Helm and Azure CLI are available on Windows, Linux, and macOS. However, there are subtle Windows biases: the environment variable setup uses the Windows 'set' command without a Linux/macOS equivalent, and the order of Kubernetes cluster creation options lists Azure PowerShell before the Azure portal and Azure CLI. No explicit Linux/macOS examples are provided for environment variable setup, and the 'set' command may confuse non-Windows users.
Recommendations
- Provide both Windows and Linux/macOS commands for setting environment variables (e.g., 'set' for Windows, 'export' for Linux/macOS).
- When listing options for creating AKS clusters, mention cross-platform tools (Azure CLI) first, or clarify which options are platform-specific.
- Add notes or callouts indicating that all CLI commands (Helm, Azure CLI) are cross-platform, and provide links to installation guides for Linux/macOS.
- Review all example commands to ensure they are either platform-neutral or include both Windows and Linux/macOS variants.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally and sometimes first, which may create friction for Linux/macOS users. There are no explicit Linux/macOS-specific examples or notes, and PowerShell is not a native shell on Linux/macOS, though it is available. No Windows-only tools or patterns are used, and the CLI examples are cross-platform. However, the documentation does not mention Bash or other Linux-native shells, nor does it clarify that Azure CLI is preferred for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is optional.
- Add a note clarifying that PowerShell examples are also usable on Linux/macOS if PowerShell Core is installed, but Azure CLI is more common.
- Consider showing Azure CLI examples first, as it is the default shell in Azure Cloud Shell and is more widely used on Linux/macOS.
- Add a brief section or FAQ addressing usage from Linux/macOS environments, confirming parity and any caveats.