226
Pages Scanned
54
Pages Flagged
226
Changed Pages
23.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-06 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
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for migration and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. There is no guidance for Linux/macOS users on how to perform the migration, and the script appears to be Windows-centric.
Recommendations
- Provide a Bash or cross-platform script equivalent for Linux/macOS users.
- Clarify whether the PowerShell script can be run with PowerShell Core on Linux/macOS, and provide instructions if so.
- Explicitly state platform requirements and offer guidance for non-Windows environments.
- Include Linux/macOS example commands and troubleshooting tips.
Create Pull Request
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting HTTP2 issues, Windows paths are shown in error messages, and Windows-specific tools (like Remote PowerShell and RDP) are discussed. Linux-specific troubleshooting commands are rarely given, and Linux CLI examples (such as for checking DNS or network connectivity) are missing or less prominent. The GLIBC error is the only explicit Linux troubleshooting section. Azure CLI is used throughout, which is cross-platform, but some instructions (e.g., downgrading Azure CLI via pip) are not clearly separated for Linux/macOS users. Windows tools and patterns are mentioned first or exclusively in several sections.
Recommendations
- Provide Linux/macOS equivalents for PowerShell troubleshooting commands (e.g., using curl or wget for HTTP2 tests).
- Add Linux/macOS examples for common troubleshooting steps, such as checking DNS resolution (e.g., dig, nslookup, ping), file permissions, and network connectivity.
- Clarify when instructions differ for Windows vs. Linux/macOS, especially for Azure CLI installation/downgrade and SSH folder permissions.
- Avoid referencing Windows tools (PowerShell, RDP) exclusively; mention SSH and Linux-native tools where applicable.
- Ensure error messages and troubleshooting steps are not Windows-path-centric (e.g., C:\ paths), and provide Linux/macOS equivalents.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides only PowerShell examples and scripts for disaster recovery operations, with no mention of Bash, Linux shell, or cross-platform alternatives. All script editing and execution instructions assume a Windows environment, creating friction for Linux/macOS users. The onboarding script is referenced as a .ps1 file and only PowerShell commands are shown.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
- Explicitly state platform requirements for the onboarding script (e.g., 'Windows/PowerShell required' or 'works on Linux with PowerShell Core').
- If possible, offer guidance for running the onboarding script on Linux/macOS (e.g., using PowerShell Core, prerequisites, or alternative workflows).
- Add a note at the start of the article about supported platforms for the disaster recovery process.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax and Windows-style command lines (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd), without offering equivalent Linux/macOS shell examples. PowerShell is used for SQL queries, and Windows command patterns are shown first and exclusively, even though the underlying operations are cross-platform. There are no explicit Linux/macOS shell examples for connecting to SQL Server or decoding secrets.
Recommendations
- Provide Linux/macOS shell examples (e.g., using bash) alongside PowerShell examples for connecting to SQL Server in the pod.
- Show how to decode base64 secrets using Linux/macOS tools (e.g., echo ... | base64 -d) in addition to any Windows/PowerShell methods.
- Clarify that the sqlcmd tool and kubectl commands work on any OS, and offer sample commands for both environments.
- Avoid using PowerShell syntax exclusively; use generic shell syntax or provide both variants.
- Ensure that examples are OS-neutral or explicitly show parity between Windows and Linux/macOS.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as backup file paths using Windows-style (C:\Backupfiles\...), and references to tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives. There are no explicit Linux/macOS examples for file paths or tools, and Windows paths are shown first and exclusively in backup/restore steps. The use of Visual Studio Code is cross-platform, but the instructions do not clarify this or provide Linux/macOS-specific guidance.
Recommendations
- Add Linux/macOS examples for backup file paths (e.g., /home/user/Backupfiles/test.bak) alongside Windows examples.
- Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and clarify which tools are available on Linux/macOS.
- Explicitly state that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links for Linux/macOS.
- Provide guidance for Linux/macOS users on connecting to SQL Server and running backup/restore commands.
- Show kubectl cp examples using Linux/macOS source file paths.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is generally Linux-focused, but it uses Windows-centric Azure PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. This creates friction for Linux users who may not have PowerShell installed or prefer standard Linux tools.
Recommendations
- Provide equivalent Linux shell commands for sysctl configuration, such as 'sysctl fs.inotify.max_user_instances' and 'echo ... | sudo tee -a /etc/sysctl.conf && sudo sysctl -p', directly in Bash.
- Clarify whether PowerShell is required on Linux, and if so, provide installation instructions or alternatives.
- Where possible, use native Linux commands and tools for Linux node management, or offer both PowerShell and Bash examples.
- Review all steps to ensure Linux users can complete them without relying on Windows-centric tools.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation instructions for client tools across platforms, but Windows-specific guidance is often presented first or more prominently. For example, kubectl installation links list Windows before Linux/macOS, and curl installation notes focus on Windows and PowerShell, with Linux instructions being less explicit. There is also a note about using cmd.exe on Windows 10, but no comparable Linux shell guidance. Linux installation instructions are sometimes missing or less detailed.
Recommendations
- Present installation instructions for all platforms (Windows, Linux, macOS) in parallel, or rotate the order to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions for tools like curl, not just 'install curl package'.
- Add Linux shell guidance where Windows-specific shell guidance is given (e.g., if mentioning cmd.exe for Windows, mention bash/zsh for Linux/macOS).
- Clarify PowerShell-specific notes and provide equivalent Linux/macOS command examples where relevant.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_authentication
Summary
The documentation references Windows-centric tools such as SQL Server Management Studio (SSMS), SQL Server PowerShell, and Windows Authentication as supported features. PowerShell scripting support is explicitly listed, and Windows Authentication is included in the security features. However, Linux equivalents (such as sqlcmd, mssql-tools, or Linux authentication mechanisms) are not mentioned. The order of tools and features does not strongly prioritize Windows, but the lack of Linux-specific examples or tools creates friction for Linux/macOS users.
Recommendations
- Add examples or references for Linux/macOS management tools such as sqlcmd, mssql-tools, Azure Data Studio, and relevant CLI usage.
- Clarify authentication options for Linux deployments, such as Microsoft Entra ID or SQL authentication, and note limitations of Windows Authentication on non-Windows platforms.
- Include PowerShell alternatives (e.g., Bash, Python scripts) for manageability tasks.
- Explicitly state cross-platform compatibility for features and tools where applicable.
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
missing_linux_example
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with most features and fixes clearly marked for each OS. However, there is a consistent pattern of Windows download links and examples being listed before Linux, and troubleshooting steps (e.g., file permission changes) are only given for Windows, with no Linux equivalents. Command-line examples and known issue resolutions are exclusively shown for Windows (Command Prompt/PowerShell), and Windows-specific tools and patterns (e.g., .msi installers, PowerShell scripts) are referenced without Linux alternatives or parity in guidance.
Recommendations
- When providing troubleshooting steps (such as editing permissions on agentconfig.json), include equivalent Linux commands (e.g., using chmod or chown) if the issue can occur on Linux, or explicitly state if it is Windows-only.
- Alternate the order of download links and examples, or present both Windows and Linux instructions side-by-side to avoid a 'Windows-first' impression.
- Where PowerShell or Windows command-line examples are given, provide equivalent Bash or shell commands for Linux users.
- Ensure that improvements or features that are Linux-specific are highlighted with the same prominence as Windows-specific ones.
- If a known issue or fix is Windows-only, clearly label it as such and confirm that Linux users are not affected.
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
missing_linux_example
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no examples for Azure CLI or Bash. This creates friction for Linux/macOS users, as PowerShell is not their default shell and Azure CLI is more commonly used on those platforms. The documentation also omits explicit Linux/macOS instructions for editing parameter files and running deployments.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands, especially for deploying ARM templates.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide equivalent CLI syntax for each deployment step.
- Include instructions or tips for editing parameter files on Linux/macOS (e.g., using nano, vim, or VS Code).
- Consider showing Azure CLI examples first or side-by-side with PowerShell to avoid implicit Windows-first bias.
- Clarify that PowerShell is cross-platform, but Azure CLI is often preferred on Linux/macOS.
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
Summary
The documentation provides deployment options for both Linux and Windows, but PowerShell is prominently featured as a cross-platform onboarding method, despite its primary association with Windows. Windows-specific tools and methods (Windows Admin Center, Configuration Manager, Group Policy) are listed separately and in detail, while Linux-specific automation tools (such as Ansible) are mentioned but not given equal prominence or example depth. PowerShell is presented as a universal solution, which may create friction for Linux users who prefer native shell scripting or other Linux-centric tools.
Recommendations
- Provide explicit Bash or shell script examples for Linux onboarding, alongside PowerShell.
- Highlight Linux-native automation tools (e.g., shell scripts, cron, systemd) as alternatives to PowerShell for Linux users.
- Ensure that Linux-specific onboarding methods are described with equal detail and clarity as Windows methods.
- Clarify that PowerShell is cross-platform but may not be the preferred tool for all Linux users.
- Consider listing Linux and Windows methods separately or in parallel to avoid implicit Windows-first ordering.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a mild Windows bias: Windows examples and instructions are often presented first, and Windows-specific tools (PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail. The cleanup script for removing stale resources is only provided in PowerShell, with no equivalent Bash or Azure CLI example for Linux users. Some Windows-specific automation and update infrastructure are discussed without Linux analogs.
Recommendations
- Present Linux and Windows instructions in parallel or alternate order to avoid 'windows_first' bias.
- Provide equivalent Bash or Azure CLI scripts for resource cleanup tasks, not just PowerShell.
- Where Windows-specific tools (e.g., Group Policy, WSUS) are discussed, mention Linux equivalents (e.g., cron jobs, package managers, systemd timers) or clarify if no direct equivalent exists.
- Ensure Linux sections are as detailed as Windows sections, especially for automation and update management.
- Consider adding troubleshooting and automation examples for Linux environments (e.g., using shell scripts).
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 both Windows and Linux context, but Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly for Azure Arc deployment, while Linux equivalents are not. PowerShell is referenced as a primary scripting method, and Windows deployment options are described before Linux options. There are no explicit Linux example commands or references to Linux-native tools (e.g., SSH, Linux package managers), and Bash is only mentioned generically. This creates friction for Linux users seeking parity in deployment guidance.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, SSH, or Linux package managers.
- Mention Linux-native tools and workflows (e.g., Ansible, systemd, cron) alongside Windows tools.
- Provide Linux-specific guidance for agent installation, configuration, and troubleshooting.
- Ensure that Linux deployment options are described with equal prominence and detail as Windows options.
- Include example commands for Linux environments (e.g., Bash, Azure CLI on Linux).
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides extensive PowerShell examples and references Windows-specific tools (such as New-AzStorageBlobSASToken and New-NetFirewallRule) throughout. Windows examples and terminology are often presented first or exclusively, especially in the REST API section, which only shows Windows firewall configuration. There is a lack of Linux-specific script examples (e.g., bash or shell scripts for Linux firewall management), and Linux usage is only briefly mentioned in notes or as an afterthought. This creates friction for Linux users, who must infer how to adapt the instructions for their systems.
Recommendations
- Add Linux-specific script examples throughout, such as using bash or shell scripts for common administrative tasks (e.g., configuring firewall rules with iptables or ufw).
- Provide parity in REST API examples, showing both Windows (PowerShell) and Linux (bash) scenarios.
- When referencing tools like New-AzStorageBlobSASToken, include CLI alternatives or note how Linux users can generate SAS tokens.
- Ensure that both Windows and Linux are equally represented in introductory and example sections, rather than presenting Windows first.
- Clarify OS-specific requirements and limitations in each example, not just in notes.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation provides recovery instructions and a downloadable script only for Windows environments, specifically using PowerShell. There are no equivalent instructions, scripts, or guidance for performing the recovery from a Linux or macOS machine, nor is it stated whether such recovery is possible or not. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternative is given.
Recommendations
- Clarify whether recovery is supported from non-Windows (Linux/macOS) environments. If not, state this explicitly to set user expectations.
- If possible, provide equivalent recovery scripts and instructions for Linux/macOS environments (e.g., Bash, Python).
- If the PowerShell script can be run cross-platform (e.g., with PowerShell Core), document how to do so on Linux/macOS.
- Add a note at the top of the recovery section indicating platform support and any limitations.
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_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a notable Windows bias. The primary automation script for at-scale enablement is a PowerShell script, with instructions and scheduling examples exclusively using Windows tools (PowerShell, Task Scheduler). There are no equivalent Bash or Linux-native examples for running the script or scheduling jobs. Out-of-band methods mention Ansible but provide more detailed steps and links for Windows-centric tools (Configuration Manager, Group Policy, PowerShell). Linux users are left to infer or adapt steps, creating friction.
Recommendations
- Provide a Bash or shell script equivalent for the auto Arc-enablement script, or clarify if the script is cross-platform.
- Include explicit instructions and examples for running the automation script on Linux/macOS (e.g., using Bash, cron).
- Show how to schedule the script as a cron job on Linux, not just with Windows Task Scheduler.
- Ensure parity in out-of-band methods by providing detailed Linux automation examples (e.g., systemd timers, Bash scripts), not just referencing Ansible.
- Clearly indicate OS compatibility for all scripts and tools.
- Where possible, present Linux/macOS examples alongside or before Windows examples, or in parallel tabs.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy changes and script invocation, but does not offer equivalent Linux/macOS guidance. The script appears to be a PowerShell script, and no Bash or cross-platform alternatives are mentioned. Windows instructions are given first and in more detail, while Linux users are left without clear steps for running the script or workarounds.
Recommendations
- Explicitly state whether the deboarding script can be run on Linux/macOS (e.g., via PowerShell Core), and provide instructions for those platforms if supported.
- If the script is Windows-only, mention this limitation clearly and offer alternative manual steps or a Bash version for Linux/macOS users.
- Provide parity in example commands and troubleshooting notes for Linux/macOS users, including how to install and use PowerShell Core if needed.
- Consider offering a cross-platform script or Azure CLI-based approach for deboarding.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to perform clean-up tasks. There are no examples or guidance for Linux/macOS users, such as using Bash or cross-platform scripting tools. The script itself is a Windows/PowerShell artifact, and the page does not mention alternatives or compatibility for non-Windows environments.
Recommendations
- Provide information about whether RGCleanScript.ps1 can be run using PowerShell Core (pwsh) on Linux/macOS, or clarify if it is Windows-only.
- If possible, offer a Bash or cross-platform script alternative, or document how Linux/macOS users can perform equivalent clean-up tasks.
- Add explicit notes about script compatibility and prerequisites for non-Windows users.
- Include example commands for Linux/macOS environments, or reference Azure CLI commands for resource deletion.
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 presents Azure CLI commands in PowerShell syntax (e.g., `$rg`, `$subId`, and `.ps1` scripts), and all example scripts are PowerShell (.ps1) files. There are no Bash or Linux/macOS shell examples, and the use of PowerShell variables and scripts may create friction for Linux/macOS users. The documentation does not mention Linux equivalents or provide guidance for running these commands in Bash or on non-Windows platforms.
Recommendations
- Provide Azure CLI command examples in Bash syntax alongside PowerShell, using Bash-style variables (e.g., `$rg` vs. `RG=mygroup`).
- Offer equivalent Bash scripts for bulk deployment and workflow deletion, or clarify that the PowerShell scripts can be run cross-platform with PowerShell Core.
- Explicitly state that Azure CLI commands are cross-platform and provide guidance for Linux/macOS users.
- Add notes or tabs for Linux/macOS users, showing how to adapt the commands and scripts.
- Avoid using only PowerShell-specific syntax in documentation unless the feature is Windows-only.
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 Windows-specific tooling (winget), with no Linux/macOS alternative. In the file extraction step, the Bash tab uses the Windows-native Expand-Archive command, which is not available on Linux/macOS, and no Linux-native alternative (like unzip) is provided. Throughout, Windows paths (e.g., C:\path\to\archive.zip) are used in examples, and Windows tools are mentioned first or exclusively. While Azure CLI and kubectl are cross-platform, the instructions and examples are skewed toward Windows environments, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS alternatives for installing kubectl (e.g., curl, apt, brew).
- In Bash examples, use cross-platform commands (e.g., unzip) instead of Windows-native Expand-Archive.
- Include Linux/macOS file path examples alongside Windows paths.
- Ensure that all steps are clearly cross-platform, or explicitly note any Windows-only steps.
- Consider adding a dedicated section or tab for Linux/macOS users where relevant.
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 focused on Windows/PowerShell usage. All onboarding scripts are provided as PowerShell (.ps1) scripts, and all command-line examples use PowerShell syntax. The prerequisites reference Windows-specific tools like 'winget'. There are no examples or instructions for running the scripts on Linux or macOS, nor are there any Bash or shell script equivalents provided. This creates friction for non-Windows users, who may not be able to follow the instructions directly.
Recommendations
- Provide Bash or shell script equivalents for the onboarding scripts, or clarify if the scripts are cross-platform (e.g., compatible with PowerShell Core on Linux/macOS).
- Include Linux/macOS installation instructions for prerequisites (e.g., using 'apt', 'brew', or direct download for Azure CLI and kubectl) instead of only 'winget'.
- Add explicit guidance for Linux/macOS users on how to run the scripts (e.g., using pwsh if scripts are compatible, or provide alternative scripts).
- If the scripts are Windows-only, clearly state this limitation at the top of the documentation.
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, and Docker, are presented in PowerShell syntax, with no equivalent Bash or Linux shell examples for critical troubleshooting steps. Only the 'service group' section provides both Bash and PowerShell tabs, while all other sections default to PowerShell. There are also PowerShell-specific patterns (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding) that are not translated for Linux/macOS users.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell examples, especially for Azure CLI, Docker, and Kubernetes commands.
- Avoid using PowerShell-specific syntax (e.g., variable assignment with $var, ConvertTo-Json, Out-File) in generic Azure CLI or Docker commands; use cross-platform syntax where possible.
- Where file encoding or manipulation is required, offer Linux/macOS alternatives (e.g., using 'cat', 'jq', 'iconv', or 'base64').
- Ensure troubleshooting steps are platform-neutral unless Windows-specific functionality is required.
- Add a note clarifying that all commands are cross-platform unless otherwise stated, and provide guidance for Linux/macOS users.
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 PowerShell examples for authentication, but PowerShell is given equal or greater prominence than is typical for cross-platform docs. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI in every example may create friction for Linux/macOS users. Additionally, the documentation refers to Docker as the default container tool, with only a brief mention of alternatives like podman, and the table of authentication methods lists PowerShell commands before or alongside CLI commands, sometimes with PowerShell-specific terminology. There are no explicit Linux/macOS-specific examples or notes, and the CLI examples are not always shown first.
Recommendations
- Prioritize Azure CLI examples before PowerShell in all sections, as Azure CLI is fully cross-platform.
- Clearly indicate that PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Add explicit Linux/macOS usage notes or examples, especially for authentication flows and environment variable usage.
- Expand the section on alternative container tools (podman, nerdctl, etc.) with concrete examples and troubleshooting tips for non-Docker environments.
- In tables and lists, list Azure CLI commands before PowerShell, and avoid implying PowerShell is required for Linux/macOS users.
Container Registry
Quickstart - Create Geo-Replicated Registry - ARM Template
...ontainer-registry-get-started-geo-replication-template.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation primarily demonstrates deploying the ARM template via the Azure portal, with only brief mention of alternative deployment methods (Azure PowerShell, Azure CLI, REST API) in a single sentence and a link. There are no explicit Linux/macOS examples or CLI walkthroughs, and the portal-based workflow is shown first and in detail, which is more familiar to Windows users. The cleanup instructions also rely solely on the portal. This creates friction for Linux/macOS users who may prefer or require CLI-based workflows.
Recommendations
- Add step-by-step examples for deploying the ARM template using Azure CLI and Azure PowerShell, including command-line snippets.
- Provide cleanup instructions using Azure CLI commands (e.g., az group delete).
- Consider showing CLI-based deployment as an alternative alongside the portal workflow, not just as a link.
- Explicitly mention that all steps can be performed on Linux/macOS using the Azure CLI.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before the cross-platform sqlcmd tool. However, it does provide a sqlcmd example that works on both Linux and Windows. There are no Linux-specific tools (such as Azure Data Studio or DBeaver) mentioned, and the instructions for connecting focus on SSMS and sqlcmd. The Azure CLI commands are cross-platform, but the overall tone and examples prioritize Windows tools and patterns.
Recommendations
- Mention cross-platform GUI tools such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit Linux/macOS connection instructions, including any OS-specific considerations.
- Show examples for both Windows and Linux/macOS environments, especially for sqlcmd usage.
- Clarify that SSMS is Windows-only and recommend alternatives for non-Windows users.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Linux and Windows information for Azure Arc-enabled servers, but Windows-specific tools and terminology (e.g., Windows Admin Center, Windows installation package) are mentioned first or more prominently. Windows endpoints and tools are often listed before their Linux equivalents, and Windows-specific notes are included in several sections. However, Linux is also covered, and critical information for Linux users is present.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, alternating order where possible.
- Where Windows-specific tools (e.g., Windows Admin Center) are mentioned, provide equivalent Linux management options or clarify if none exist.
- In tables and lists, avoid always listing Windows resources first; consider grouping by platform or alternating order.
- Add explicit Linux troubleshooting links or references, similar to the Windows TLS configuration issues link.
- Clarify any Windows-only requirements to avoid confusion for Linux users.
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, but is slightly less prominent. The prerequisites and instructions mention both OSes, and links to both Windows and Linux guides are provided. Overall, the bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
- Ensure screenshots and visual aids are provided for both Windows and Linux examples.
- Explicitly mention that the instructions apply equally to both Windows and Linux, and highlight any OS-specific differences.
- Consider adding a brief summary table comparing Windows and Linux steps for quick reference.
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 parity between Azure CLI and Azure PowerShell throughout, with examples for both. However, the PowerShell examples are not inherently Windows-specific, as Azure PowerShell is cross-platform. There are no Windows-only tools or patterns, and Linux/macOS users can use Azure CLI or Azure PowerShell. The only minor bias is that PowerShell examples are sometimes shown immediately after CLI examples, but neither is prioritized or presented as Windows-only.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, not just Windows.
- Consider explicitly mentioning that both Azure CLI and Azure PowerShell are available on all major platforms.
- If possible, add brief notes or links about running Azure CLI and PowerShell on Linux/macOS for new users.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for all major steps, ensuring parity for cross-platform users. However, in most sections, PowerShell examples are presented after Bash, which is a minor 'windows_first' bias. There are no Windows-only tools or patterns, and Linux/macOS users are not missing any critical information or examples.
Recommendations
- Continue to provide Bash and PowerShell examples side-by-side for all steps.
- Consider alternating the order of Bash and PowerShell tabs in some sections, or explicitly state that both platforms are equally supported.
- Ensure that any platform-specific notes (e.g., handling UTF-8 BOM, base64 encoding) are clear for both Bash and PowerShell 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
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding, but the Linux example is presented first and is more concise. The Windows method relies on certutil and findstr, which are Windows-specific tools, and requires manual header removal. No PowerShell-specific examples are given, and all other steps (openssl, Azure CLI, kubectl) are cross-platform. The bias is minor, as Windows users are given explicit instructions, but Linux is treated as the default.
Recommendations
- Provide a PowerShell example for base64 encoding and header removal for Windows users, as PowerShell is more commonly used than certutil/findstr.
- Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider mentioning macOS explicitly alongside Linux where relevant.
- Add a note about using openssl on Windows, including installation guidance if needed.
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 operations. However, Azure PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and in some sections, PowerShell examples are presented before or alongside CLI examples. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and no Bash/shell script examples beyond Azure CLI. The use of PowerShell as a primary example may create friction for Linux/macOS users who may not have PowerShell installed or prefer native shell scripting.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and recommend it as the default for Linux/macOS users.
- Present Azure CLI examples before PowerShell examples in all sections.
- Add explicit notes or callouts for Linux/macOS users, e.g., confirming that all steps are supported on those platforms.
- Where environment variables are set, show both Bash (export) and PowerShell ($Env:) syntax side-by-side.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, proxy settings).
Azure Arc
Quickstart: Connect an existing Kubernetes cluster to Azure Arc
...les/azure-arc/kubernetes/quickstart-connect-cluster.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but the PowerShell examples are given equal prominence to Azure CLI, and PowerShell-specific instructions (including environment variable setup) are included. There is minor Windows bias in the use of PowerShell as a primary scripting option alongside Azure CLI, and in the explicit mention of Windows as a Docker installation target before Linux/Mac in some lists. However, Linux-specific instructions and requirements are present, and the documentation is generally cross-platform.
Recommendations
- Consider clarifying that Azure PowerShell is available on Linux/macOS, or add Bash scripting equivalents where PowerShell is used for environment variable setup.
- When listing Docker installation options, consider mentioning Linux first, or listing all platforms equally (Linux, Mac, Windows) to avoid subtle Windows-first ordering.
- Explicitly note that Azure CLI and PowerShell are both cross-platform, and provide links to installation instructions for Linux/macOS where relevant.
- Where possible, provide Bash shell examples alongside PowerShell for tasks like setting environment variables, especially in proxy configuration sections.
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
missing_linux_example
Summary
The documentation page for Azure Arc resource bridge system requirements exhibits minor Windows bias. While the Azure CLI is referenced as the primary management tool, links and instructions for installing Azure CLI are Windows-focused (e.g., linking to the Windows install page and specifying x64/32-bit requirements without mentioning Linux/macOS equivalents). There are no explicit Linux/macOS instructions or examples for management machine setup, CLI installation, or file paths, which may create friction for non-Windows users.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS management machines.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide parity in examples and requirements.
- Mention file path conventions for Linux/macOS when discussing configuration file storage.
- Ensure CLI commands and prerequisites are platform-agnostic or provide platform-specific guidance where necessary.
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 (PowerShell) and Linux (CLI) examples for all major operations, but Windows/PowerShell examples are often presented before Linux/CLI. Some minor notes reference Windows-specific behaviors (e.g., setting --gateway-resource-id to null in PowerShell). The monitoring section gives both Windows and Linux log locations. There is a slight preference for Windows-first ordering and PowerShell usage, but Linux parity is generally maintained.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux users see their platform represented first in some sections.
- Explicitly state that all CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
- Where possible, clarify any Windows-specific notes (such as setting --gateway-resource-id to null) and provide equivalent Linux guidance if needed.
- Consider adding a short section at the start confirming that all features and instructions apply equally to Linux and Windows servers unless otherwise noted.
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 Windows bias. The 'Interactive browser login' is described as Windows-only and appears first in the authentication options section, while Linux is only mentioned as the default for device code login. Windows certificate store usage is described in detail, but Linux equivalents (such as PEM/PFX file usage) are not explained with equal depth. The access token example references a PowerShell cmdlet ('Get-AzAccessToken') without mentioning Linux alternatives. However, overall, the documentation is usable for Linux users, and most examples are cross-platform.
Recommendations
- Reorder authentication options so that cross-platform methods (device code, service principal, Azure CLI) appear before Windows-only options.
- Provide equivalent Linux tooling or commands for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token').
- Expand certificate authentication guidance for Linux, including file permissions and typical storage locations.
- Clarify that most examples are cross-platform and explicitly state which options are Windows-only.
- Where Windows certificate store is discussed, briefly mention Linux certificate handling for parity.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation covers troubleshooting for both Windows and Linux, but there is a mild bias toward Windows. Windows examples and log file paths are presented first, and PowerShell syntax is used for Windows commands. Windows-specific tools and concepts (elevated command prompt, PowerShell version requirements, Windows environment variables) are mentioned before their Linux equivalents. However, Linux examples and paths are included and parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Provide both PowerShell and Bash syntax for commands where applicable.
- Explicitly mention Linux equivalents for Windows-specific instructions (e.g., 'elevated command prompt' vs. 'sudo').
- Ensure troubleshooting steps reference both Windows and Linux log file locations equally.
- Consider grouping Windows and Linux sections together or clarifying parity in introductory text.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first in the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout with equivalent instructions and tooling.
Recommendations
- Alternate the order of Windows and Linux instructions in sections, or present them side-by-side to avoid implicit prioritization.
- Explicitly mention macOS compatibility if the Bash script works on macOS, or clarify if it does not.
- Ensure screenshots and UI references are OS-neutral or provide Linux/macOS-specific guidance if needed.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides a generally cross-platform overview of Azure Arc-enabled VMware vSphere, but exhibits minor Windows bias. Windows/PowerShell are mentioned first or exclusively in several places (e.g., Azure Automation runbooks, Windows Server management, and AVS deployment tabs). Linux equivalents are referenced but not always with equal prominence or example depth. No critical sections are Windows-only, but Linux/macOS users may encounter friction due to Windows-first ordering and lack of explicit Linux-focused examples.
Recommendations
- Ensure that Linux examples and references are given equal prominence alongside Windows/PowerShell, especially in sections about automation and VM extensions.
- Where tabs or links are Windows-only (e.g., 'tabs=windows'), add Linux/macOS tabs or clarify parity.
- Expand references to Linux tools and workflows (e.g., Bash, Ansible, shell scripts) in automation and onboarding scenarios.
- Provide explicit Linux/macOS CLI examples where PowerShell is mentioned.
- Review quick start and deployment guides to ensure Linux onboarding is equally documented.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for each command, but consistently presents Bash examples before PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider clarifying that Azure CLI commands work identically on Linux, macOS, and Windows.
- Optionally, add a note at the top stating that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows (or cross-platform PowerShell).
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 some sections, PowerShell examples are presented immediately after Bash, and in a few places, minor copy-paste errors favor Windows variable syntax. There are no Windows-only tools or patterns, and all instructions are cross-platform via Azure CLI. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Ensure Bash and PowerShell examples are equally prominent, possibly by alternating their order or using tabs to avoid implicit Windows-first bias.
- Correct minor copy-paste errors in PowerShell examples (e.g., variable assignment syntax) to improve clarity for Windows users.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
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 is no evidence of Windows-only tools, Windows-specific patterns, or missing Linux examples. All commands use the Azure CLI, which is cross-platform, and variable definitions are shown for both Bash and PowerShell. No Windows tools or PowerShell-heavy bias is present.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider alternating the order of Bash and PowerShell tabs or explicitly stating that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Ensure that any referenced scripts or files (such as onboarding scripts) are compatible with both Bash and PowerShell environments.
- If possible, clarify in the prerequisites that both Linux/macOS and Windows environments are supported.
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
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown immediately after Bash, and the PowerShell syntax is given equal prominence. There is no evidence of Windows-only tools or patterns being prioritized, nor are Linux examples missing. However, the PowerShell examples are sometimes slightly more detailed (e.g., variable assignment), and the structure may subtly imply parity between Windows and Linux, but Bash is always shown first. No Windows-specific tools or patterns are mentioned, and all commands are cross-platform (Azure CLI, kubectl).
Recommendations
- Ensure Bash examples are always shown first, as currently done.
- Consider adding a note clarifying that Azure CLI and kubectl commands are fully cross-platform and can be run on Linux, macOS, and Windows.
- If possible, highlight that PowerShell examples are for Windows users, but Bash is the default for Linux/macOS.
- Review variable assignment sections to ensure Bash and PowerShell examples are equally detailed.
- If the audience is primarily Linux/macOS, consider making Bash the default and PowerShell optional.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
Summary
The documentation is generally cross-platform, focusing on Azure CLI and portal usage, which are available on both Windows and Linux/macOS. However, in the May 2025 release section, the CLI examples are shown using PowerShell syntax (with backticks for line continuation and variables with $), which is Windows-centric and may confuse Linux/macOS users who use Bash or other shells.
Recommendations
- Provide CLI examples in both PowerShell and Bash syntax, or use Bash syntax as the default since it is more universally compatible.
- Add a note clarifying that CLI commands work in any shell, and provide guidance on adapting line continuations and variable syntax for different platforms.
- Where possible, avoid using shell-specific syntax (like backticks or $-prefixed variables) in CLI documentation unless the documentation is specifically for that shell.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell, indicating a 'windows_first' bias is not present. There are no Windows-specific tools, patterns, or terminology used exclusively or preferentially. All commands use the Azure CLI, which is cross-platform. No critical steps are Windows-only, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is achieved.
- Consider clarifying that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- If desired, alternate the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
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 consistently presents Bash examples first. There is no evidence of Windows-only tools or patterns, and all commands use cross-platform Azure CLI and Helm. However, the presence of PowerShell examples throughout may suggest a slight Windows bias, especially since PowerShell is primarily used on Windows, though it is available cross-platform.
Recommendations
- Clarify that PowerShell examples are also valid for PowerShell Core on Linux/macOS.
- Consider adding a note that Bash and PowerShell examples are functionally equivalent and both supported on all platforms.
- Ensure that any platform-specific nuances (such as file path syntax or environment variable usage) are documented for both Bash and PowerShell.
- If possible, provide a brief summary at the top indicating that all steps are cross-platform and do not require Windows.
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 all CLI commands, ensuring parity between Linux/macOS and Windows users. However, in each section, Bash examples are consistently shown before PowerShell, which is a minor 'windows_first' bias (the opposite: 'linux_first'). No evidence of PowerShell-heavy content, exclusive Windows tools, or missing Linux examples is found. All instructions are cross-platform and use the Azure CLI, which is available on Linux, macOS, and Windows.
Recommendations
- Maintain the current structure, as both Bash and PowerShell examples are provided.
- Consider alternating the order of Bash and PowerShell examples or explicitly stating that both are equally supported.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance if Windows-specific instructions are added.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There are no Windows-exclusive tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Linux/macOS examples are missing, and no Windows-specific tools are mentioned. The only minor bias is that Bash (Linux/macOS) examples are always shown first, followed by PowerShell (Windows).
Recommendations
- Maintain the current parity between Bash and PowerShell examples.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, especially for new users.
- Optionally, alternate the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is a minor bias, as PowerShell is traditionally associated with Windows, there is no explicit prioritization or omission of Linux/bash examples. The rest of the documentation is platform-neutral, focusing on the Azure mobile app, which is available for both iOS and Android.
Recommendations
- Clarify that generated scripts can include Bash/CLI examples for Linux/macOS users, not just PowerShell.
- Explicitly mention Bash or shell script generation alongside PowerShell and CLI to reinforce cross-platform support.
- If examples are provided in future updates, ensure parity by including both PowerShell and Bash/CLI examples.
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
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first. This ordering may subtly prioritize Windows/PowerShell users, even though Azure CLI is fully cross-platform. No examples or instructions are exclusive to Windows, and all steps are portal-based and platform-agnostic.
Recommendations
- Alternate the order in which Azure CLI and PowerShell are mentioned, or mention Azure CLI first to reflect its cross-platform nature.
- Explicitly note that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
- Where possible, provide direct example commands for both Azure CLI and PowerShell, ensuring parity and clarity for all users.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for both Azure CLI and PowerShell, but PowerShell is mentioned alongside CLI in the opening sentence and is given its own example tab. The instructions for opening the terminal reference Visual Studio Code, which is cross-platform, but the key combination (ctrl + `) is Windows-centric. There are no Linux-specific examples or explicit mention of Bash or Linux/macOS terminal environments. The cleanup instructions only reference the Azure portal, which is platform-neutral.
Recommendations
- Explicitly mention that Azure CLI commands can be run in Bash on Linux/macOS, not just in PowerShell.
- Add a Bash example tab for deploying the Bicep file, or clarify that the CLI example works identically on Bash, Zsh, and other shells.
- Adjust terminal instructions to reference macOS/Linux key combinations (e.g., 'Ctrl+`' on Windows, 'Cmd+`' on macOS) or simply say 'open your terminal'.
- Consider mentioning that Visual Studio Code is available on Linux/macOS, or suggest other editors commonly used on those platforms.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. However, the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool. The documentation does not explicitly mention Linux-native tools (such as Bash or shell scripting) or provide Linux/macOS-specific guidance. Azure CLI is cross-platform, but PowerShell is presented as an alternative without clarifying its platform limitations. The order of examples (CLI first, then PowerShell) is appropriate, but the lack of explicit Linux/macOS parity or mention of native shell usage is a minor bias.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users to use Azure CLI.
- Consider adding a brief Bash shell example for Docker image manipulation, if relevant.
- Add a note about Azure Cloud Shell availability for both CLI and PowerShell, and its platform independence.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for registry authentication and image removal, but PowerShell examples are given equal prominence and detail as CLI examples. There is a slight 'windows_first' bias: PowerShell is mentioned alongside CLI in prerequisites and throughout, even though PowerShell is primarily used on Windows. However, all Docker commands are cross-platform and the Azure CLI is available on Linux/macOS. No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider listing Azure CLI examples before PowerShell in each section, or marking PowerShell as 'Windows only'.
- Add explicit notes or tabs for Linux/macOS users where authentication or registry management is discussed, highlighting Azure CLI usage.
- Ensure parity in example detail for Azure CLI and Docker commands, and avoid implying PowerShell is equally relevant for Linux/macOS.
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 example uses the Windows 'set' command instead of the cross-platform 'export', and the order of Kubernetes cluster creation options lists Azure PowerShell before Linux-friendly alternatives. No PowerShell-specific commands are given, but there is a lack of explicit Linux/macOS examples for environment variables.
Recommendations
- Replace 'set ACR_NAME=<container-registry-name>' with 'export ACR_NAME=<container-registry-name>' or provide both commands for Windows and Linux/macOS.
- When listing options for creating AKS clusters, mention Azure CLI (Linux/macOS-friendly) before Azure PowerShell.
- Add notes clarifying that all Azure CLI and Helm commands are cross-platform, and provide explicit examples for Linux/macOS where relevant.
- Ensure all environment variable instructions are shown for both Windows (set) and Linux/macOS (export).
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations such as viewing usage and changing SKUs. However, in several sections, Azure PowerShell is mentioned before REST API or alongside CLI, and PowerShell examples are given equal prominence to CLI. There are no Linux-specific tools or shell examples (e.g., Bash scripting), but the CLI examples are cross-platform. No critical features are Windows-only, and Linux/macOS users can complete all tasks using the CLI or REST API.
Recommendations
- When listing programmatic options, consistently mention Azure CLI before PowerShell, as CLI is cross-platform and PowerShell is Windows-first.
- Consider adding Bash or shell script examples where appropriate, especially for automation scenarios.
- Clarify that Azure CLI commands work on all platforms, while PowerShell is primarily for Windows (though available cross-platform).
- Where possible, provide REST API examples or links for users who may not use CLI or PowerShell.
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 options for signing in to the registry, but the PowerShell section is presented equally alongside CLI, and PowerShell is a Windows-centric tool. However, Docker instructions and links are provided for Linux, Mac, and Windows, and all portal steps are platform-neutral. No critical steps are Windows-only, but PowerShell is mentioned as an option for registry login, which may create minor friction for Linux/macOS users who typically use Azure CLI.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider presenting Azure CLI instructions first, as it is the most universally supported tool.
- Add a brief note clarifying that Azure PowerShell is available on Linux/macOS but is less commonly used outside Windows.
- Ensure that all command-line examples and links are equally accessible and relevant for Linux/macOS users.