230
Pages Scanned
57
Pages Flagged
230
Changed Pages
24.8%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:40
Scan Information
Started At: 2026-02-28 00:00:40
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 230
Files Completed: 230
Problematic Pages
58 issues found
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux context, but there is a notable Windows bias: Windows tools (Admin Center, Graphical Installer) are mentioned explicitly, and PowerShell is referenced before Bash. Linux equivalents (such as SSH, Linux package managers, or Linux-specific deployment tools) are not mentioned or are less prominent. Windows deployment options are described in more detail, and Windows examples/tools appear first in several sections.
Recommendations
- Add explicit Linux deployment examples and tools (e.g., SSH, Linux package managers, or Linux-specific scripts) alongside Windows options.
- Mention Bash and PowerShell equally, and provide sample Bash commands/scripts for Linux users.
- Include references to Linux graphical installers or management tools if available.
- Ensure Linux deployment at scale (e.g., Ansible) is described with parity to Windows tools like Group Policy.
- Where Windows tools are mentioned (Admin Center, Graphical Installer), add a note about Linux alternatives or clarify if none exist.
Create Pull Request
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. There are no examples or guidance for Linux/macOS users, such as Bash or cross-platform alternatives. The script and all usage instructions assume a Windows/PowerShell environment, which may exclude or confuse users on other platforms.
Recommendations
- Provide a Bash or cross-platform shell script alternative (e.g., `RGCleanScript.sh`) for Linux/macOS users, or clarify if the script is compatible with PowerShell Core (pwsh) on all platforms.
- Add explicit instructions for running the script on Linux/macOS, including any prerequisites (such as installing PowerShell Core or required modules).
- If only PowerShell is supported, clearly state that the script requires PowerShell and provide guidance for installing PowerShell Core on non-Windows systems.
- Consider including az CLI command examples for common clean-up tasks as an alternative for users who prefer not to use PowerShell scripts.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using PowerShell syntax and references the use of sqlcmd, but does not offer equivalent Linux/macOS shell examples. The PowerShell examples are shown first and exclusively, which may create friction for Linux/macOS users, even though the underlying tools (kubectl, sqlcmd) are cross-platform.
Recommendations
- Provide Linux/macOS shell (bash) examples alongside PowerShell, especially for commands using kubectl exec and sqlcmd.
- Clarify that sqlcmd and kubectl are cross-platform and can be used from any OS, and specify any OS-specific requirements.
- Show both PowerShell and bash syntax for connecting to the pod and running SQL commands.
- Avoid using PowerShell-specific formatting (e.g., backticks, command continuation) unless necessary; use generic shell syntax where possible.
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 mostly Linux-focused, but it introduces Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell equivalents. The use of PowerShell-like commands for Linux tasks may confuse Linux/macOS users and limits their ability to follow instructions directly.
Recommendations
- Provide native Linux shell (bash) command equivalents for sysctl configuration steps, e.g., 'sysctl fs.inotify.max_user_instances' and 'echo ... | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
- Clarify whether Invoke-AksEdgeNodeCommand is required or if standard Linux commands can be used directly on the node.
- Add explicit instructions for Linux users to SSH into the node and run commands natively, rather than using Windows/PowerShell tools.
- Ensure all steps can be completed using standard Linux tooling, and present Linux-native commands before any Windows/PowerShell alternatives.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and highlights PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are mentioned, Windows tools are listed first and more prominently. There are no Linux-specific tools or examples provided, and PowerShell is referenced without mention of Bash or Linux scripting alternatives.
Recommendations
- Add examples or references for Linux/macOS users, such as Bash scripting or cross-platform tools.
- Mention and provide guidance for using Azure Data Studio, which is cross-platform.
- Clarify which tools are available on Linux/macOS and which are Windows-only.
- Include parity tables or notes for tool support across operating systems.
- Highlight Azure CLI usage with Linux/macOS examples where possible.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation frequently presents Windows-centric examples and tools first (e.g., file paths like C:\Backupfiles\test.bak, use of SSMS, and screenshots/steps for Azure Storage Explorer on Windows), with no explicit Linux/macOS equivalents or guidance. Linux users are left to infer how to adapt the instructions, especially for backup file creation and local file path usage.
Recommendations
- Provide parallel examples for Linux/macOS users, such as using /home/username/Backupfiles/test.bak as the backup path.
- Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and clarify that Visual Studio Code is available on all platforms.
- For Azure Storage Explorer, clarify that it is cross-platform and provide links or notes for Linux/macOS installation and usage.
- When showing commands with file paths, show both Windows and Linux/macOS formats side by side.
- Explicitly state that all steps can be performed from Linux/macOS unless a step is Windows-only, and provide any required adaptations.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in most feature tables. However, Windows-specific tools (Command Prompt, PowerShell, MSI installer) are referenced exclusively in troubleshooting and known issues, and Windows command examples are provided without Linux equivalents. Windows download links and version numbers are consistently listed before Linux. This creates friction for Linux users, especially in troubleshooting scenarios.
Recommendations
- For troubleshooting and known issues, provide equivalent Linux commands and instructions (e.g., how to modify agentconfig.json permissions on Linux, using chmod/chown).
- Where Windows tools (PowerShell, Command Prompt, MSI installer) are mentioned, add Linux alternatives (bash, shell scripts, RPM/DEB installers) and examples.
- Alternate the order of Windows and Linux download links and version numbers, or present them side-by-side.
- Explicitly state when an issue or fix is Windows-only or Linux-only to avoid confusion.
- Ensure that all critical operational instructions are available for both platforms.
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides deployment options for the Azure Connected Machine agent across Linux and Windows. However, several onboarding methods are Windows-specific (e.g., Windows Admin Center, Group Policy, Configuration Manager), and PowerShell is highlighted as a cross-platform tool but is more commonly associated with Windows. Windows-specific tools and methods are listed separately and in greater detail, while Linux-specific automation tools (other than Ansible) are not mentioned. The order of examples and methods tends to prioritize Windows tools and workflows.
Recommendations
- Add Linux/macOS-specific onboarding examples, such as using Bash scripts or native Linux automation tools (e.g., shell scripts, cron jobs, Puppet, Chef).
- Clarify PowerShell's cross-platform support and provide equivalent Bash or shell script examples for Linux users.
- Consider balancing the order of methods so Linux and Windows approaches are presented equally.
- Include links or references to Linux-specific documentation where available.
- Explicitly state when a method is Windows-only and suggest Linux alternatives where possible.
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. PowerShell is a Windows-centric tool, though it is available cross-platform. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. The template examples themselves are balanced, but the operational guidance is Windows-first.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell, e.g., az deployment group create.
- Explicitly mention that PowerShell is available cross-platform, but provide Bash/CLI alternatives for Linux/macOS users.
- Consider showing Azure CLI examples first or in parallel with PowerShell to avoid Windows-first impression.
- Clarify that the templates can be deployed from any OS, not just Windows.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples (especially in PowerShell and REST API sections) are Windows-centric. PowerShell examples use Windows-style paths and scripts, and REST API examples exclusively show Windows firewall configuration (New-NetFirewallRule, .ps1 scripts). There are no Linux-specific script examples (e.g., bash, shell scripts, or Linux firewall commands like iptables or ufw). Azure CLI examples use PowerShell-style commands (Write-Host), and there are no Linux shell script examples. The documentation also references Windows tools (e.g., New-AzStorageBlobSASToken) without mentioning Linux alternatives. Linux is only mentioned in passing, and Linux-specific scripting patterns are not demonstrated.
Recommendations
- Add Linux-specific script examples in all sections (PowerShell, Azure CLI, REST API), such as running bash scripts, using Linux shell commands (e.g., echo, id, iptables, ufw), and referencing .sh files.
- In the REST API section, provide a Linux scenario (e.g., configuring a firewall rule with iptables or ufw) alongside the Windows example.
- When showing how to upload or reference scripts, include Linux file paths and script types (.sh) as well as Windows (.ps1).
- For Azure CLI examples, use Linux-native commands (e.g., echo, id) and show both Windows and Linux script invocations.
- Reference cross-platform tools or clarify that New-AzStorageBlobSASToken is available on all platforms, or provide az CLI equivalents.
- Explicitly call out any differences in script parameter handling between Windows and Linux, and provide examples for both.
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 downloadable script exclusively for Windows, using PowerShell. There are no examples or guidance for Linux/macOS users, nor is it clarified whether recovery is possible from non-Windows systems. The section is titled 'Recover Arc resource bridge from a Windows machine', and no alternative is offered.
Recommendations
- Clarify whether recovery is possible from Linux/macOS, and if not, explicitly state that the process is Windows-only.
- If feasible, provide equivalent recovery instructions and scripts for Linux/macOS users (e.g., Bash or Python scripts).
- Add a note about platform requirements and limitations to set user expectations.
- If the script is Windows-only due to dependencies, explain the technical reasons for this.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page for disaster recovery operations of the Azure Arc resource bridge VM provides only PowerShell script examples and references, with no mention of Linux/macOS shell equivalents or cross-platform onboarding script usage. The onboarding and recovery steps are described exclusively using PowerShell syntax, and there is no guidance for users on Linux or macOS systems. This creates friction for non-Windows users attempting to perform the same operations.
Recommendations
- Provide onboarding script usage examples for Bash or other Linux/macOS shells if the script supports cross-platform execution.
- Clarify whether the onboarding script is Windows-only or cross-platform; if Windows-only, state this explicitly to set expectations.
- If possible, offer instructions or alternatives for Linux/macOS users, such as using Azure CLI or a platform-neutral method.
- Include notes about required environments and dependencies for running the onboarding script.
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
missing_linux_example
windows_tools
Summary
The documentation consistently uses PowerShell syntax for all CLI examples and references only PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) for automation, without providing equivalent Bash or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the use of .ps1 scripts assumes a Windows or PowerShell Core environment.
Recommendations
- Provide CLI command examples in both PowerShell and Bash syntax, or use a neutral shell format.
- Offer equivalent Bash scripts (e.g., bulk_deployment.sh) for Linux/macOS users, or document how to run the .ps1 scripts with PowerShell Core on those platforms.
- Explicitly state that the .ps1 scripts can be run with PowerShell Core on Linux/macOS, and provide installation guidance if needed.
- Where possible, avoid using shell-specific features in CLI examples, or clarify any platform dependencies.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page exhibits notable Windows bias in its automation section. The primary script for batch Arc agent installation is a PowerShell script, with instructions focused on Windows environments (e.g., PowerShell terminal, Set-ExecutionPolicy, Windows Task Scheduler for cron jobs). Windows tools and patterns are mentioned first and exclusively in several sections, while Linux equivalents (such as bash scripting or cron) are missing. Although Linux is referenced in prerequisites and out-of-band methods, the main scalable automation example is Windows-centric.
Recommendations
- Provide a bash or shell script equivalent for batch Arc agent installation, with instructions for Linux/macOS users.
- Include examples for scheduling the script using Linux cron jobs, not just Windows Task Scheduler.
- Offer guidance for running the script in cross-platform environments (e.g., Azure Cloud Shell, WSL, or native Linux/macOS terminals).
- Ensure out-of-band methods include Linux-focused automation examples (e.g., Ansible, shell scripts) with equal prominence.
- Where possible, show both Windows and Linux command examples side-by-side.
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 both Windows and Linux instructions for uninstalling the Azure Connected Machine agent, but the deboarding script section is heavily PowerShell-centric and only provides Windows/PowerShell instructions for running the script. Windows instructions and notes are presented first and in greater detail, while Linux/macOS users are not given equivalent guidance for running the deboarding script or troubleshooting.
Recommendations
- Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), command syntax, and troubleshooting notes.
- Mention PowerShell Core as a cross-platform option and clarify if the script can be run on Linux/macOS, or provide an alternative Bash script if not.
- Present Windows and Linux instructions in parallel sections, or clarify platform limitations up front.
- Add troubleshooting tips for Linux/macOS users, similar to the PowerShell ISE note for Windows.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a notable Windows bias. All CLI/script examples are provided in PowerShell syntax, with no Bash or Linux/macOS shell equivalents. Paths in JSON templates use Windows-style (C:\, E:\) exclusively. The onboarding and diagnostic scripts are referenced as PowerShell (.ps1) files, with no mention of Bash or cross-platform alternatives. This creates friction for Linux/macOS users, who may not be able to follow the steps directly.
Recommendations
- Provide Bash/zsh shell equivalents for all PowerShell CLI examples, especially for az CLI commands, which are cross-platform.
- Include Linux/macOS file path examples in JSON templates alongside Windows paths.
- Document how to run onboarding and diagnostic scripts on Linux/macOS (e.g., provide Bash scripts or instructions for using PowerShell Core on non-Windows platforms).
- Clarify if the infra_onboarding.ps1 script is supported on Linux/macOS, and if not, offer a cross-platform alternative.
- Where possible, use platform-neutral language and tools (e.g., az CLI, kubectl) and avoid assuming Windows as the default environment.
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 oriented toward Windows environments: all examples use PowerShell scripts (.ps1), instructions explicitly reference opening a PowerShell terminal, and prerequisites use Windows-specific tooling (winget). There are no Bash/shell script equivalents, nor are there instructions for running these onboarding scripts on Linux or macOS. This creates friction for non-Windows users and may prevent them from completing onboarding without significant adaptation.
Recommendations
- Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the existing scripts with PowerShell Core on those platforms.
- Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
- Explicitly state whether the onboarding scripts are supported on Linux/macOS, and if not, provide guidance or alternatives.
- Include example commands and terminal instructions for both Windows (PowerShell) and Linux/macOS (Bash or 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 example for installing kubectl uses 'winget', a Windows-only tool, without providing a Linux/macOS alternative. In the 'Extract ZIP' section, the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a native Bash/Linux command. There are no Linux/macOS-specific instructions for these steps, and Windows paths are used in examples. The structure of the page consistently presents Windows-centric tools and patterns first or exclusively, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS alternatives for installing kubectl (e.g., using 'curl' or package managers like 'apt', 'brew', or 'yum').
- In the 'Extract ZIP' section, use native Bash/Linux commands such as 'unzip' or 'tar' instead of 'Expand-Archive'.
- Include Linux/macOS file path examples alongside Windows paths.
- Review all Bash sections to ensure they use cross-platform commands and do not rely on Windows-specific tools.
- Clearly indicate which instructions are Windows-only and provide parity for Linux/macOS users wherever possible.
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, with instructions to run it in PowerShell. There are no examples or guidance for Linux/macOS users, such as Bash or cross-platform alternatives. The script filename and usage imply Windows-centric tooling, creating friction for non-Windows users.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Add explicit instructions for running the migration script on Linux/macOS, including any prerequisites (e.g., installing PowerShell Core).
- Mention cross-platform compatibility if the script works on all OSes, or offer a platform-neutral migration method.
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 PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash/Linux CLI examples. The Azure CLI is cross-platform, but the use of PowerShell-style command formatting and variables may create friction for Linux/macOS users. Most other CLI examples use Bash syntax, but the PowerShell examples are shown first and exclusively in some sections.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell CLI examples, especially for configuration set/download commands.
- When showing CLI examples, use cross-platform syntax (e.g., Bash) or explicitly note both Windows (PowerShell) and Linux/macOS (Bash) versions.
- Avoid using PowerShell-specific variable syntax (e.g., $rg, $solutionName) in CLI examples unless also showing Bash equivalents.
- Review all CLI documentation for consistent cross-platform parity.
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 documentation for workload orchestration in Azure Arc shows notable Windows bias. Most command-line examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., az CLI, kubectl, docker). There are no explicit Linux/bash equivalents for critical troubleshooting steps, except in the 'service groups' section, where both Bash and PowerShell tabs are provided. Windows/PowerShell syntax is used by default throughout, and some commands (e.g., Base64 encoding, file manipulation) use PowerShell-specific patterns without Linux alternatives.
Recommendations
- Provide Bash/Linux equivalents for all az CLI, kubectl, and docker commands, especially for steps involving file manipulation, Base64 encoding, and JSON creation.
- Use cross-platform syntax for az CLI commands (e.g., avoid PowerShell variable syntax and backticks in examples).
- Add explicit notes or tabs for Linux/macOS users, clarifying any OS-specific steps.
- Ensure file encoding instructions are relevant for Linux/macOS editors (e.g., mention how to check/save UTF-8 encoding in Vim/Nano).
- For Base64 encoding, provide Linux command (e.g., echo -n '<token>' | base64) alongside PowerShell.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal or greater prominence than is typical for cross-platform parity. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in all sections may confuse Linux/macOS users. In several places, PowerShell commands are presented before or at the same level as CLI, and there are no explicit Bash or shell script examples for Linux/macOS users. The documentation also references the Azure portal and Windows-style tools without clarifying cross-platform alternatives.
Recommendations
- Clearly indicate that Azure PowerShell is optional and primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- In code tabs, show Azure CLI (Bash/shell) as the default or first example, with PowerShell as an alternative.
- Add explicit Bash/shell script examples for common authentication flows, especially for automation scenarios.
- Clarify that Azure CLI and Docker commands work natively on Linux/macOS, and provide troubleshooting tips for those platforms.
- Where the Azure portal is referenced, note that it is web-based and platform-agnostic.
- Consider adding a short section or note about cross-platform support and tool recommendations for Linux/macOS users.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions using both Azure CLI and PowerShell, but PowerShell is featured prominently and mentioned alongside Azure CLI as a primary option. The instructions for opening a terminal reference Visual Studio Code and a Windows-specific key combination (ctrl + `), which may not be the same on Linux/macOS. There are no explicit Linux/macOS examples or references to Bash or shell environments. The cleanup instructions focus on the Azure portal, which is cross-platform, but do not mention CLI-based cleanup commands.
Recommendations
- Add explicit Bash/Linux/macOS terminal instructions, including how to open a terminal and navigate directories.
- Provide Azure CLI examples first, as it is cross-platform, and clarify that PowerShell is optional for Windows users.
- Include cleanup commands using Azure CLI for resource deletion, not just portal instructions.
- Mention that Visual Studio Code and the Azure CLI are available on Linux/macOS, and provide relevant links or notes.
- Clarify any key combinations or terminal instructions that differ on Linux/macOS.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell authentication/removal examples, but PowerShell is given equal prominence to Azure CLI, and Windows-specific PowerShell tools are mentioned alongside cross-platform CLI tools. The instructions for stopping containers use 'Ctrl+C', which is universal, and Docker commands are cross-platform. However, PowerShell is not available on all Linux/macOS systems by default, and its inclusion may create friction for non-Windows users. The order of listing Azure CLI and PowerShell examples is neutral, but the presence of PowerShell throughout may be perceived as Windows-centric.
Recommendations
- Clearly indicate that Azure PowerShell examples are primarily for Windows users, and suggest Azure CLI as the preferred cross-platform option.
- Add explicit notes that Azure CLI works on Linux/macOS and is recommended for those platforms.
- Consider providing Bash shell examples for common tasks, or clarify that all Docker commands shown are cross-platform.
- If possible, add a Linux/macOS-specific section or tab for authentication/removal using Azure CLI and Docker.
- Review links and references to ensure Linux/macOS users are guided to relevant installation and usage docs.
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 provides authentication options and examples for both Windows and Linux, but there is a mild bias in favor of Windows: the interactive browser login is described as 'Windows only' and is presented first, and Windows certificate store options are discussed in detail. The access token section references a Windows-specific PowerShell cmdlet (Get-AzAccessToken) without mentioning Linux alternatives. However, Linux authentication methods (device code, service principal, Azure CLI) are well-covered, and examples are generally OS-neutral.
Recommendations
- Present authentication options in a more OS-neutral order, or explicitly state Linux defaults first when relevant.
- For access token acquisition, mention cross-platform methods (e.g., Azure CLI az account get-access-token) alongside Windows PowerShell cmdlets.
- Clarify that most examples and flags are applicable to both Windows and Linux unless otherwise noted.
- Add a brief note or table summarizing which authentication methods are available on each OS.
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 most sections, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users rather than Windows. There are no Windows-only tools, patterns, or missing Linux examples. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
- No significant changes needed. The documentation already provides both Bash and PowerShell examples for all steps.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to ensure equal prominence.
- Explicitly mention that all commands are cross-platform and can be run on Linux, macOS, or Windows (with Bash or PowerShell).
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 first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use the cross-platform Azure CLI and Helm. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Maintain the current structure, as Bash and PowerShell examples are both provided.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, if not already stated.
- Optionally, add a note indicating that Azure CLI and Helm are cross-platform tools.
- Continue to provide parity in future updates.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access to subscription and tenant IDs. However, PowerShell is mentioned first in tips and next steps, and the language subtly prioritizes PowerShell (a Windows-centric tool) over Azure CLI (cross-platform). No Linux-specific examples, screenshots, or guidance are provided, but CLI parity is maintained.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions to avoid implicit prioritization.
- Explicitly note that Azure CLI works on Linux/macOS and provide a brief example or screenshot for CLI usage.
- Add a short section or tip for Linux/macOS users, clarifying that all portal steps are platform-agnostic and CLI is fully supported.
- Where possible, provide CLI commands before PowerShell, or at least equally.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides installation instructions for client tools across platforms, but Windows installation links are often listed first. There are several Windows-specific notes, such as recommending cmd.exe over PowerShell for curl, and mentioning PowerShell's curl alias. Linux installation instructions are present but sometimes less detailed or secondary. The overall bias is minor, as Linux/macOS users can still follow the instructions, but Windows is subtly prioritized.
Recommendations
- Present installation links for all platforms in parallel, rather than listing Windows first.
- Provide equally detailed instructions for Linux/macOS, including explicit package installation commands (e.g., 'sudo apt install curl').
- Clarify PowerShell-specific notes as optional, and ensure Linux/macOS equivalents are mentioned where relevant.
- Where possible, avoid platform-specific recommendations unless necessary, or provide alternatives for other OSes.
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 demonstrates mild Windows bias by mentioning SQL Server Management Studio (SSMS) as the primary graphical client tool and referencing Windows-centric patterns first. However, it does provide a Linux-compatible example using sqlcmd and acknowledges Linux environments (AKS, kubeadm, OpenShift). There are no exclusive Windows-only tools or commands, but SSMS is presented as the default GUI option, which is Windows-only.
Recommendations
- Explicitly mention cross-platform GUI tools such as Azure Data Studio alongside SSMS.
- Provide example connection instructions for Azure Data Studio or other Linux/macOS-compatible SQL clients.
- Clarify that sqlcmd is available on Linux, macOS, and Windows, and provide installation guidance or links for non-Windows platforms.
- Consider listing Linux/macOS options first or equally with Windows tools to avoid 'windows_first' bias.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation references Azure CLI installation with links that default to Windows installation instructions and mentions Azure CLI x64/32-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-specific commands or tools, and the overall guidance is platform-neutral. There are no PowerShell examples or Windows-only tools mentioned, but the management machine requirements link to Windows installation first and do not explicitly mention Linux/macOS compatibility.
Recommendations
- Add explicit guidance for Linux and macOS users regarding Azure CLI installation and compatibility.
- Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link.
- Clarify that the management machine can be Linux, macOS, or Windows, and specify any OS-specific requirements if applicable.
- Ensure examples and instructions are platform-neutral or include platform-specific variations where necessary.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is generally cross-platform and focused on Azure Arc resource bridge, which is not Windows-specific. However, there are minor signs of Windows bias: PowerShell is used for some troubleshooting steps (e.g., testing HTTP/2 connectivity and DNS resolution), and Windows paths are referenced in error messages. Windows tools and patterns (PowerShell, RDP) are mentioned before Linux equivalents, and Linux commands are less prominent or sometimes missing. Most CLI examples use Azure CLI, which is cross-platform, but PowerShell is referenced for troubleshooting network issues.
Recommendations
- Provide Linux/macOS equivalents for PowerShell troubleshooting steps, such as using curl or wget for HTTP/2 tests and dig/nslookup for DNS resolution.
- When referencing file paths or error messages, clarify if they are OS-specific and provide Linux/macOS alternatives where relevant.
- Ensure troubleshooting steps and CLI commands are equally documented for Linux/macOS environments, including permissions and SSH folder access.
- Mention Linux/macOS remote access patterns (e.g., SSH, terminal) alongside Windows (RDP, PowerShell) when discussing remote operations.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Windows and Linux guidance, but Windows/PowerShell examples are often presented first or with more detail. PowerShell commands are included throughout, and there are occasional references to Windows-specific tools or paths. However, Linux parity is generally maintained, and CLI examples are cross-platform. The bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux users see relevant instructions first in some sections.
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux/macOS.
- Where file paths or log locations are mentioned, always provide both Windows and Linux equivalents side-by-side.
- Ensure that onboarding instructions and troubleshooting steps reference Linux/macOS as equally as Windows.
- Consider adding a note at the top clarifying that all Azure CLI instructions are supported on Linux/macOS.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_example
linux_first
Summary
The documentation provides both Linux and Windows approaches for base64 encoding files when preparing Kubernetes secrets. The Linux method (using 'base64') is presented first and is the default, while the Windows method (using 'certutil' and 'findstr') is included as an alternative. There is no PowerShell-heavy bias, and all core tasks can be completed on Linux/macOS. The Azure CLI and kubectl examples are platform-agnostic. The Windows-specific tools are mentioned only for encoding, and Linux parity is maintained throughout.
Recommendations
- Consider explicitly mentioning macOS compatibility alongside Linux for the 'base64' command.
- Provide a brief note for Windows users about using WSL or Git Bash as alternatives to certutil.
- Clarify that Azure CLI and kubectl commands work cross-platform.
- Optionally, add a PowerShell example for base64 encoding for Windows users who prefer PowerShell.
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 lists Azure PowerShell examples after Azure CLI. PowerShell is a Windows-centric tool, and its inclusion alongside CLI is reasonable, but there are no Linux/macOS-specific shell examples (e.g., Bash scripts) or explicit mention of Linux environments. However, the CLI examples are cross-platform, and environment variable instructions use both export (Linux/macOS) and PowerShell syntax, indicating some Linux parity. There are no Windows-only tools or patterns, but PowerShell is referenced throughout.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux/macOS.
- Add brief notes or examples for Bash scripting or Linux/macOS environments where relevant (e.g., setting environment variables).
- Consider mentioning that Azure PowerShell is available on Linux/macOS, or clarify its usage context.
- Ensure parity in troubleshooting or advanced scenarios for Linux users.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page displays minor Windows bias. Windows-specific services and endpoints (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are mentioned, and Windows NTP is referenced before any Linux alternatives. However, Linux endpoints and tools (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io, SSH) are also included, and most requirements are platform-neutral. No critical steps are Windows-only, but Windows terminology and endpoints appear more frequently and are sometimes listed first.
Recommendations
- Clarify that NTP can use Linux NTP servers (e.g., pool.ntp.org) and provide Linux NTP examples alongside Windows NTP.
- Where Windows-specific endpoints are mentioned (e.g., sts.windows.net, login.windows.net), note if Linux equivalents exist or if these are required regardless of OS.
- Ensure that Linux tools and endpoints are given equal prominence and are not listed after Windows examples by default.
- Add explicit statements confirming compatibility with Linux and macOS management machines, and reference Linux-specific configuration patterns where relevant.
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 referencing both platforms for the Azure Connected Machine agent. However, there are minor signs of Windows bias: Windows installation package URLs are listed first in tables, and Windows Admin Center (a Windows-only tool) is mentioned in service tags and endpoint descriptions before SSH (the cross-platform equivalent). Additionally, troubleshooting links and cipher suite configuration guidance are more detailed for Windows, with Linux relegated to a brief OpenSSL mention.
Recommendations
- List Linux and Windows installation package URLs in parallel or alternate order to avoid Windows-first bias.
- When mentioning Windows Admin Center, also highlight SSH as a cross-platform management option, and provide equal detail for both.
- Expand Linux-specific troubleshooting and TLS/cipher suite configuration guidance, including links to relevant Linux documentation (e.g., OpenSSL configuration, firewall/proxy setup).
- Ensure examples and notes reference both Linux and Windows equally, especially in sections about network configuration and security protocols.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Windows and Linux Azure Arc-enabled servers and provides parity in feature descriptions and CLI instructions. However, there is a mild Windows bias: PowerShell examples are given their own section and are presented after CLI examples, and PowerShell is referenced as a management tool alongside Azure CLI and portal. The order of examples (CLI first, then PowerShell) is good, but PowerShell is still emphasized as a primary management method, which may not be relevant for Linux users. All CLI examples are cross-platform, and Linux is explicitly mentioned as supported. No critical Linux-specific tools or shell examples (e.g., bash scripting) are provided, but this is not required for the described tasks.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and that Azure CLI is fully cross-platform.
- Consider adding explicit bash/zsh shell usage examples for Linux users, especially for scripting or automation.
- Mention that PowerShell Core is available on Linux, but most Linux users will prefer Azure CLI.
- Ensure that all screenshots and navigation instructions are not Windows-specific (e.g., avoid referencing Windows UI elements unless necessary).
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, with clear sections and examples for each. However, there is a mild Windows bias: Windows examples and tools (such as PowerShell, Group Policy, Microsoft Update, and Control Panel) are often presented first or in greater detail, and PowerShell scripts are used for cleanup tasks without equivalent Bash/Linux scripts. Windows-specific tools and patterns are described extensively, while Linux instructions are more concise and rely on standard package managers.
Recommendations
- Where PowerShell scripts are provided for automation (e.g., stale resource cleanup), offer equivalent Bash scripts or Azure CLI examples for Linux users.
- Ensure Linux examples are given equal prominence in tables and introductory sections, not always after Windows.
- Expand Linux instructions to include automation and scripting examples, not just manual package manager commands.
- Where Windows tools (e.g., Group Policy, Control Panel) are described, consider referencing Linux equivalents (e.g., systemd, cron, config files) for similar tasks if applicable.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows VM extensions before Linux VM extensions, with Windows-specific examples and tables appearing first. However, Linux extensions are comprehensively covered, and parity is maintained in extension lists and deployment methods. No critical functionality is Windows-only except where inherently required by the extension itself.
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 (Azure CLI, PowerShell, portal, ARM templates) support both Windows and Linux extensions.
- Add a brief introductory note clarifying that both Windows and Linux are equally supported, and that the ordering of tables is not indicative of priority.
- Ensure that links to Linux-specific documentation are as prominent as Windows links.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed, including error handling and output formatting. The Linux/Bash example is provided, but with less explanation and detail. References to Azure portal, PowerShell, and Azure CLI are given for related content, but no Linux-specific tools are mentioned.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Ensure both PowerShell and Bash examples have equivalent detail, including error handling and explanation.
- Add references to Linux-native tools (such as az CLI usage on Linux) where appropriate.
- Clarify that both Windows and Linux are equally supported for Azure Arc-enabled managed identity scenarios.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, including error codes, exit codes, and log file locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. There is a minor emphasis on Windows-specific paths and tools (e.g., PowerShell, Windows environment variables) before Linux equivalents, but Linux parity is maintained throughout with equivalent examples and instructions.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
- Explicitly mention Linux log file locations and permissions in the same detail as Windows.
- Where possible, use neutral language and avoid referencing Windows tools (e.g., PowerShell) before Linux tools unless contextually necessary.
- Ensure troubleshooting steps reference both Windows and Linux file paths and commands equally.
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. The troubleshooting and retry sections also show Windows commands before Linux equivalents. There is a minor bias toward Windows, but Linux users are not blocked from completing the task.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them side-by-side.
- Provide equally detailed notes for Linux users (e.g., warnings about Bash environments or common issues).
- Ensure screenshots and UI instructions are OS-neutral or clarify any OS-specific steps.
- Explicitly confirm parity of script functionality between Windows and Linux.
- Consider adding macOS instructions if the Bash script is compatible.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is generally cross-platform and highlights both Windows and Linux support for Azure Arc-enabled VMware vSphere. However, there are several subtle signs of Windows bias: PowerShell and Windows tools are mentioned before Linux equivalents, and some links and examples default to Windows tabs or scenarios. Automation and configuration examples reference PowerShell and Windows registry/files before Linux daemons, and some linked guides default to Windows-focused instructions. While Linux is supported and mentioned, the documentation tends to present Windows tools and workflows first, which may create minor friction for Linux/macOS users.
Recommendations
- Ensure that all automation and configuration examples mention Linux/bash and PowerShell equally, ideally presenting them side by side.
- Where links point to guides with OS-specific tabs, default to a neutral or Linux-first tab, or clarify that both Windows and Linux are supported.
- When referencing tools (e.g., Azure Automation, Update Manager), explicitly mention support for both Windows and Linux, and provide balanced examples.
- Review and adjust language to avoid always listing Windows before Linux (e.g., 'Windows and Linux servers' instead of 'Windows servers and Linux servers').
- Consider including explicit Linux/macOS CLI or scripting examples where possible, not just PowerShell.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and with download links, while Linux requirements are listed second and less prominently. Windows PowerShell is mentioned as a prerequisite for Windows, but no equivalent Linux scripting tool is referenced. The overall structure tends to mention Windows before Linux in several sections.
Recommendations
- Present Windows and Linux requirements in parallel or in a table to avoid Windows-first ordering.
- Provide download links or references for Linux prerequisites (e.g., systemd documentation, wget installation instructions) similar to Windows.
- Mention Linux scripting alternatives (e.g., bash, shell scripts) if PowerShell is referenced for Windows.
- Ensure examples and instructions are balanced for both Windows and Linux where applicable.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides a balanced overview of new features for Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux enhancements. However, in the June 2024 section, Azure PowerShell is listed after Azure CLI and REST APIs, but Windows-specific features (such as guest OS customization for Windows VMs and Windows Server Management) are highlighted. There is a slight tendency to mention Windows-related features and tools, but Linux support (e.g., SSH-based agent installation, Ansible playbook) is also referenced. No critical Linux parity gaps are detected.
Recommendations
- Ensure Linux-related enhancements are given equal prominence and detail as Windows features.
- Where possible, provide explicit Linux/macOS examples alongside Windows/PowerShell examples.
- Mention cross-platform tools (e.g., Ansible, Azure CLI) before Windows-specific tools (e.g., PowerShell, Group Policy) in lists.
- Clarify when features are Windows-only to avoid confusion for Linux users.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, ensuring parity for Linux and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, which may subtly prioritize Windows users. No Windows-specific tools or patterns are mentioned, and all instructions are cross-platform via Azure CLI.
Recommendations
- Ensure that Bash and PowerShell examples are presented equally, possibly alternating their order or explicitly stating that both are supported platforms.
- Add a brief note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples are suitable for Linux/macOS users.
- Consider including a generic shell example (without OS-specific syntax) for universal applicability.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring cross-platform parity. However, PowerShell examples are consistently presented after Bash examples, indicating a minor 'windows_first' bias. No Windows-specific tools or patterns are used exclusively, and Linux/macOS users are fully supported throughout.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
- Explicitly state at the beginning that both Linux/macOS and Windows are fully supported, and that users should select the tab matching their environment.
- Ensure that any editor or encoding instructions (e.g., UTF-8/BOM) clarify cross-platform differences, if relevant.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell tabs for all command-line examples, ensuring parity for Linux/macOS and Windows users. However, the PowerShell tab is presented after Bash, and the PowerShell examples are not strictly Windows-specific since all commands use the cross-platform Azure CLI. There is a slight bias in the inclusion of PowerShell examples, which are primarily relevant to Windows users, but no critical sections are Windows-only and all instructions are available in Bash.
Recommendations
- Clarify that both Bash and PowerShell examples are supported on all platforms where Azure CLI is available, including Windows, Linux, and macOS.
- Consider adding a note that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users, but both shells are available cross-platform.
- Ensure that any future examples that use Windows-only tools (e.g., cmd.exe, Windows-specific paths) are accompanied by Linux/macOS equivalents.
- If possible, provide a generic 'Azure CLI' tab that is shell-agnostic, or clarify that the commands are identical except for variable syntax.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented immediately after Bash, which may subtly reinforce a Windows-first mindset. No Windows-specific tools or patterns are mentioned, and all instructions are cross-platform via Azure CLI. No critical Linux/macOS gaps are present.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that Azure CLI commands are cross-platform and Bash examples are directly usable on Linux/macOS.
- Ensure screenshots and portal instructions are not Windows-centric (current screenshot is neutral).
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 presented before PowerShell, which is a minor bias ('windows_first') as Windows users may expect PowerShell examples first. There are no Windows-only tools, patterns, or missing Linux examples; all instructions are cross-platform and rely on the Azure CLI, which is available on both Windows and Linux/macOS.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is shown first for consistency.
- Add a short note at the top clarifying that all CLI commands work on both Linux/macOS (Bash) and Windows (PowerShell), and users should select the tab appropriate for their OS.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance if Windows-specific instructions are added.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are always shown after Bash and are equally detailed. There is no evidence of Windows-only tools or patterns, nor are Windows tools mentioned exclusively. The use of the Azure CLI and Helm is cross-platform, and the instructions are generic for both Linux and Windows environments. However, the presence of PowerShell examples throughout, and their explicit labeling, may indicate a slight Windows bias, especially since Bash is presented first in every case.
Recommendations
- Consider alternating the order of Bash and PowerShell examples to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell examples are supported on Windows, Linux, and macOS (where applicable).
- Add a note clarifying that Azure CLI and Helm commands work identically across platforms.
- If possible, provide guidance for macOS users (e.g., installation links for Azure CLI and Helm).
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 PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool. The CLI example is cross-platform, but the tab order presents Azure CLI first, followed by Azure PowerShell, which is a minor bias. No Linux-specific tools or shell examples (e.g., Bash scripting) are provided, but the Azure CLI example is sufficient for Linux/macOS users. There are no Windows-only tools or patterns mentioned, and no critical steps are Windows-exclusive.
Recommendations
- Explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider adding a Bash shell example for importing images using Azure CLI to reinforce Linux parity.
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is suitable for all platforms.
- If possible, provide links or references to Linux/macOS-specific guidance for Azure Container Registry operations.
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 Azure dashboards using three methods: Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform and presented before PowerShell, the PowerShell section is included as a distinct method, which may imply a Windows-centric bias. Additionally, PowerShell examples are provided, but there are no explicit Linux/macOS shell examples (e.g., Bash) or clarifications about cross-platform compatibility for PowerShell. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is typically associated with Windows, even though it is available on Linux/macOS. The ordering of sections (CLI before PowerShell) reduces the severity of bias, but the presence of PowerShell-specific instructions without explicit Linux/macOS shell alternatives is a minor bias.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Mention that PowerShell is available cross-platform, or provide Bash shell equivalents for Linux/macOS users.
- Consider adding a note about cross-platform compatibility for each tool.
- If PowerShell is included, ensure Linux/macOS users are aware of how to install and use PowerShell if desired.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for signing in to the registry, but Azure PowerShell (a Windows-centric tool) is given equal prominence alongside Azure CLI. However, Docker installation instructions are clearly provided for Mac, Windows, and Linux, and all Docker commands are cross-platform. No critical steps are Windows-only, but PowerShell is presented as a primary option, which may create minor friction for Linux/macOS users.
Recommendations
- Consider presenting Azure CLI as the default or primary method for cross-platform parity, with Azure PowerShell as an alternative for Windows users.
- Explicitly note that Azure CLI works on Linux/macOS/Windows, while Azure PowerShell is mainly for Windows (with limited support elsewhere).
- If possible, add a short note clarifying that PowerShell instructions are optional and not required for Linux/macOS users.
- Ensure that any future examples or screenshots do not default to Windows tools unless the feature is Windows-only.
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 minor signs of Windows bias: the environment variable setup uses the Windows-style 'set' command without showing the equivalent Linux/macOS 'export', and the order of Kubernetes cluster creation options lists Azure PowerShell before the Azure CLI and portal, which may subtly prioritize Windows tools. No explicit Linux/macOS examples are provided for environment variable setup, and the documentation does not clarify cross-platform command differences.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples for environment variable setup.
- Clarify that Azure CLI and Helm commands are cross-platform and work on Linux/macOS as well as Windows.
- When listing options for Kubernetes cluster creation, avoid prioritizing Windows-specific tools (Azure PowerShell) before cross-platform tools (Azure CLI).
- Add notes or callouts where commands may differ between platforms, especially for shell commands.
- Include sample shell prompts (e.g., '$' for bash, '>' for PowerShell) to indicate platform context.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently lists Azure PowerShell examples immediately after Azure CLI, and references PowerShell as a primary tool. However, Azure CLI is cross-platform and the examples are equally applicable to Linux/macOS. No Windows-specific tools, commands, or patterns are used, and no critical steps are Windows-only. There are no missing Linux/macOS examples, as Azure CLI is the recommended cross-platform method.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider explicitly stating that Azure PowerShell is available on Linux/macOS, or provide a brief note about its cross-platform support.
- If possible, add a short section or note for Linux/macOS users highlighting that all CLI examples work natively on their platforms.
- Ensure that any references to PowerShell do not imply Windows exclusivity.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as changing registry SKU and showing usage), but consistently lists PowerShell after CLI and does not provide explicit Linux/macOS shell examples. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and no Bash or Linux-specific instructions are given. The documentation also references the Azure portal, which is platform-agnostic, but does not mention Linux-native tools or workflows. This creates a mild Windows bias, especially for users unfamiliar with PowerShell.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Provide Bash shell examples or clarify that Azure CLI examples are suitable for Linux/macOS terminals.
- Consider including sample scripts or command sequences for Linux users (e.g., using Bash or zsh).
- Mention that PowerShell is available cross-platform, but highlight CLI as the primary tool for Linux/macOS.
- Add a note about installing Azure CLI on Linux/macOS, linking to relevant documentation.