234
Pages Scanned
49
Pages Flagged
234
Changed Pages
20.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:11
Scan Information
Started At: 2026-02-21 00:00:11
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 234
Files Completed: 234
Problematic Pages
50 issues found
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows: all onboarding scripts and examples are provided only as PowerShell (.ps1) scripts, and users are instructed to use Windows-specific tools like 'winget'. There are no Bash or shell script equivalents, nor any Linux/macOS-specific instructions or examples. The documentation assumes a Windows environment by default.
Recommendations
- Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the onboarding process on those platforms.
- Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., 'apt', 'brew', or direct download links for Azure CLI and kubectl).
- Explicitly state platform requirements and, if Windows is required, clarify this early in the documentation.
- If PowerShell Core (pwsh) is supported on Linux/macOS, document this and provide instructions for installing and running the scripts cross-platform.
- Add Linux/macOS-specific examples and troubleshooting notes where relevant.
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 for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. All examples and guidance are Windows/PowerShell-centric, with no mention of Linux/macOS alternatives or cross-platform scripting options. The script appears to require PowerShell, and there are no Bash or shell script equivalents or instructions for running PowerShell Core on Linux/macOS.
Recommendations
- Provide instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux/macOS, including any prerequisites or compatibility notes.
- Offer a Bash or shell script equivalent for Linux users, or clarify if the PowerShell script is cross-platform.
- Explicitly state whether the script is Windows-only or can be used on other operating systems.
- Include example commands for Linux/macOS environments, such as using ./RGCleanScript.ps1 in pwsh, or provide guidance for installing PowerShell Core.
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 relies on the Windows-specific PowerShell cmdlet Invoke-AksEdgeNodeCommand for critical configuration steps on Linux nodes. No direct Linux shell (bash/SSH) alternatives are provided for checking or setting sysctl parameters, which may hinder Linux/macOS users who do not have access to PowerShell or the Azure AKS Edge Essentials PowerShell module.
Recommendations
- Provide equivalent Linux shell (bash/SSH) commands for checking and setting sysctl parameters, such as 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
- Clarify whether Invoke-AksEdgeNodeCommand is available cross-platform or only via Windows/PowerShell, and offer guidance for Linux-only environments.
- Ensure all critical steps can be completed using native Linux tools and commands, not just PowerShell cmdlets.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for interacting with the SQL Server instance inside a Kubernetes pod, but consistently uses PowerShell syntax for these examples (e.g., 'kubectl exec ...' blocks are labeled as 'powershell'). There are no Linux/macOS shell (bash) equivalents or explicit mention that the commands work cross-platform. The use of PowerShell syntax and labeling may create confusion or friction for Linux/macOS users, even though the underlying commands are compatible.
Recommendations
- Replace 'powershell' code block labels with 'console' or 'bash' where appropriate, since 'kubectl' and 'sqlcmd' commands are cross-platform.
- Add explicit bash examples or clarify that the commands work on Linux/macOS terminals as well.
- Include notes or sections addressing Linux/macOS users, especially for decoding base64 secrets (e.g., 'echo <base64> | base64 -d' for bash).
- Ensure that any references to tools or steps are not Windows-specific unless required by the scenario.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) in the 'Tools' section, and explicitly mentions PowerShell scripting support as a manageability feature. While Azure PowerShell is marked as 'No', SQL Server PowerShell is marked as 'Yes', and PowerShell scripting is highlighted as a supported feature. There are no Linux-specific tools (such as sqlcmd, mssql-cli, or Azure Data Studio) mentioned, nor are cross-platform scripting alternatives (like Bash or Python) referenced. However, the page does not provide step-by-step examples, so the bias is mostly in tool listing and feature emphasis.
Recommendations
- Add Linux/macOS-compatible tools such as Azure Data Studio, sqlcmd, and mssql-cli to the 'Tools' section.
- Mention Bash scripting or Python as alternative scripting options for manageability.
- Clarify that PowerShell scripting support refers to cross-platform PowerShell Core, if applicable.
- Provide guidance or links for Linux/macOS users to manage SQL Managed Instance enabled by Azure Arc.
- Ensure parity in tool recommendations by listing cross-platform options alongside Windows tools.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation links for client tools across platforms, but Windows links are often listed first and some instructions are Windows-centric. For example, the kubectl installation section references Windows first and includes a note about using cmd.exe instead of PowerShell for curl, but does not provide equivalent Linux/macOS command guidance. The curl section gives a Windows link and only mentions 'Linux: install curl package' without a link or explicit command. There is also a PowerShell-specific note about curl aliases, but no similar notes for Linux/macOS shells.
Recommendations
- List Linux/macOS installation links before or alongside Windows links, rather than Windows first.
- Provide explicit Linux/macOS installation commands for tools like curl (e.g., 'sudo apt install curl' or 'brew install curl').
- Add shell-specific notes for Linux/macOS users (e.g., bash/zsh differences) where relevant, not just PowerShell.
- Ensure all tool installation instructions are equally detailed for all platforms.
- Where possible, provide cross-platform command examples, not just Windows-specific guidance.
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 using Windows file paths (e.g., C:\Backupfiles\test.bak), referencing tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives, and showing Windows paths and examples before Linux equivalents. There are no explicit Linux/macOS examples for creating backups or copying files, and Linux file paths are only shown in restore commands, not in backup steps.
Recommendations
- Provide Linux/macOS examples for backing up SQL Server databases (e.g., using /home/user/Backupfiles/test.bak or /tmp/test.bak).
- Mention cross-platform tools such as Azure Data Studio or sqlcmd for database backup and restore, alongside SSMS.
- Show kubectl cp examples using Linux/macOS source file paths (e.g., /home/user/test.bak) in addition to Windows paths.
- Clarify that the steps and tools are applicable on both Windows and Linux, and highlight any OS-specific requirements.
- Add notes or sections for Linux/macOS users, including any differences in procedure or prerequisites.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation references Azure CLI installation with links that default to Windows instructions and does not specify Linux/macOS equivalents. There are no explicit Linux/macOS examples or guidance for management machine requirements, CLI installation, or file paths. Azure CLI is cross-platform, but the documentation does not acknowledge or provide parity for Linux/macOS users.
Recommendations
- Add explicit guidance and links for installing Azure CLI on Linux and macOS, not just Windows.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any OS-specific requirements or caveats.
- Include example file paths and CLI usage for Linux/macOS environments.
- Ensure all CLI commands are shown in a cross-platform manner (e.g., avoiding Windows-specific syntax or assumptions about directory structure).
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 errors, and Windows-specific tools (e.g., Remote PowerShell, RDP) are mentioned. In some cases, Windows command-line patterns (e.g., 'C:\Program Files...') are used in error messages. Linux-specific troubleshooting steps are limited, and Linux commands (such as nslookup, ldd) are referenced but not consistently provided as examples. Windows tools and patterns are often mentioned first or exclusively, with Linux equivalents missing or less detailed.
Recommendations
- Provide Linux/macOS equivalents for PowerShell troubleshooting steps (e.g., using curl or wget with HTTP2).
- Include Linux/macOS command examples alongside Windows commands for DNS resolution, file permissions, and proxy configuration.
- Avoid referencing Windows paths (e.g., 'C:\Program Files...') exclusively; include Linux paths where applicable.
- Clarify when steps are platform-specific and provide parity in guidance for both Windows and Linux management machines.
- Expand troubleshooting sections to explicitly address Linux/macOS scenarios, especially for CLI errors, SSH folder permissions, and proxy issues.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation for `azcmagent connect` shows evidence of Windows bias in several areas. The authentication options section lists 'Interactive browser login (Windows only)' first, and describes its default behavior on Windows before mentioning Linux defaults. Windows certificate store usage is detailed, while Linux equivalents are not. The access token section references the Windows PowerShell cmdlet `Get-AzAccessToken` as the primary example, without mentioning Linux/macOS alternatives. Overall, Linux is supported and mentioned, but Windows-specific tools and workflows are prioritized or exclusively described in some sections.
Recommendations
- Reorder authentication options so that cross-platform or Linux-default methods (e.g., device code, Azure CLI) are listed first or equally.
- When referencing access token acquisition, include Linux/macOS methods (e.g., Azure CLI: `az account get-access-token`) alongside PowerShell.
- For certificate-based authentication, clarify Linux/macOS certificate storage and usage, and provide examples for both platforms.
- Where Windows-specific tools (like certificate stores or PowerShell) are mentioned, add equivalent Linux/macOS guidance or explicitly state if not applicable.
- Ensure all examples and instructions are platform-neutral or provide both Windows and Linux/macOS variants.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions for all major agent lifecycle tasks (install, upgrade, uninstall, proxy configuration). However, Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Registry Editor, Msiexec) are often presented first or in greater detail. The cleanup script for stale resources is PowerShell-only, with no Linux/bash equivalent. Windows-specific tools and patterns are described extensively, while Linux instructions are concise and rely on standard package managers.
Recommendations
- Where possible, present Linux and Windows instructions in parallel or with equal prominence.
- Provide a bash or Azure CLI equivalent for the PowerShell cleanup script to enable Linux users to automate stale resource removal.
- Include more detailed Linux automation examples (e.g., using cron, systemd, or shell scripts) for tasks like upgrades and uninstalls.
- Consider adding troubleshooting tips for Linux environments, similar to the Windows-specific guidance.
- For proxy configuration, clarify any OS-specific nuances and provide examples for both Windows and Linux in each section.
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 instructions and sample commands are exclusively given in Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands and Windows-style file paths are shown first and throughout, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does mention that extensions can be deployed to Linux or Windows machines, but the actual deployment workflow is Windows/PowerShell-centric.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands for ARM template deployment.
- Include Bash shell examples for Linux/macOS users, especially for editing and deploying templates.
- Use platform-neutral file paths in examples (e.g., './AzureMonitorAgent.json') or provide both Windows and Linux path formats.
- Explicitly state that Azure CLI and Bash can be used for deployment, and link to relevant CLI documentation.
- Consider alternating the order of Linux and Windows examples to avoid Windows-first bias.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page presents a notable Windows bias, especially in the 'Auto Arc-enablement script' section, which exclusively provides PowerShell examples and references Windows Task Scheduler for automation. The script usage instructions are Windows-centric, with no Linux/macOS equivalents or guidance. Windows tools and automation patterns are mentioned first and in detail, while Linux approaches are only briefly referenced or omitted. Although the out-of-band methods mention Ansible playbooks, no Linux-specific example or parity is provided for the main scripted method.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, including instructions for running the helper script in those environments.
- Include guidance for automating the script via cron jobs on Linux, not just Windows Task Scheduler.
- Clarify whether the helper script can run on Linux/macOS, and if not, offer a Linux-compatible alternative.
- Ensure that both Windows and Linux automation patterns (e.g., PowerShell vs. Bash, Task Scheduler vs. cron) are covered equally.
- Add Linux/macOS-specific troubleshooting and prerequisites, such as handling sudo privileges and script execution permissions.
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 script examples and instructions, with no mention of Bash, Linux, or macOS equivalents. The onboarding and recovery steps are centered around editing and running a PowerShell (.ps1) script, and all code samples are PowerShell-based. There is no guidance for Linux/macOS users, nor are cross-platform alternatives discussed.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements for running the onboarding script (e.g., Windows-only, or if PowerShell Core is supported on Linux/macOS).
- If possible, offer instructions for running the onboarding script using PowerShell Core on Linux/macOS, or provide alternative methods for Linux users.
- Add a note about platform compatibility and any prerequisites for non-Windows environments.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page consistently uses PowerShell syntax for all CLI command examples and references PowerShell scripts (.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor is there guidance for running the Azure CLI commands on Linux/macOS. The use of PowerShell and Windows script files is presented as the default, which may create friction for Linux/macOS users.
Recommendations
- Provide Azure CLI command examples in Bash syntax, or clarify that the CLI commands work identically on Linux/macOS terminals.
- Offer equivalent Bash scripts for bulk deployment and workflow deletion, or explain how Linux/macOS users can run the PowerShell scripts (e.g., via PowerShell Core or alternative methods).
- Add notes or sections indicating cross-platform compatibility of the Azure CLI commands.
- Explicitly mention any platform-specific requirements or limitations for scripts, and provide alternatives where possible.
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 guidance and script invocation. There are no equivalent instructions or examples for running the script on Linux/macOS, nor is it clarified whether the script can be run cross-platform. Windows instructions are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
- Clarify whether the deboarding script can be run on Linux/macOS (e.g., with PowerShell Core or Azure CLI).
- If supported, provide explicit Linux/macOS instructions for downloading and running the script, including any prerequisites (such as PowerShell Core installation or using Bash/Azure CLI).
- If the script is Windows-only, state this clearly and provide alternative manual steps or scripts for Linux/macOS users.
- Present both Windows and Linux/macOS instructions in parallel, or at least mention Linux/macOS options before or alongside Windows guidance.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for all orchestration, onboarding, and log collection tasks. File paths in JSON templates and scripts use Windows conventions (e.g., C:\, E:\), and there are no Bash, Linux shell, or cross-platform CLI examples. The onboarding and diagnostic scripts are referenced as PowerShell (.ps1) files, with no mention of Linux/macOS equivalents or how to run these tasks on non-Windows systems. This creates friction for Linux/macOS users, who may not be able to follow the steps directly.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell (.ps1) scripts, or clarify if cross-platform support exists.
- Use generic or cross-platform file paths in JSON templates (e.g., /home/user/... instead of C:\Users\...).
- Add explicit instructions for Linux/macOS users, including how to run Azure CLI commands in Bash and how to handle onboarding if PowerShell scripts are not available.
- Mention any limitations or requirements for running orchestration scripts on Linux/macOS, and provide alternatives if possible.
- Where possible, show Azure CLI commands in Bash syntax (with line continuations using \) alongside PowerShell examples.
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 (WOGAMigration.ps1) for migration, with instructions to run it in PowerShell. There are no Bash, Linux shell, or cross-platform alternatives mentioned, and no guidance for Linux/macOS users on how to perform the migration.
Recommendations
- Provide a Bash or cross-platform script for Linux/macOS users.
- Document how to run the PowerShell script using PowerShell Core (pwsh) on Linux/macOS, if applicable.
- Explicitly state platform requirements and offer alternatives or workarounds for non-Windows environments.
- Add Linux/macOS-specific instructions or examples alongside Windows/PowerShell guidance.
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: Windows-specific tools (winget) are used for kubectl installation without Linux/macOS alternatives; file extraction instructions use Windows paths and PowerShell/Bash examples, but Bash is shown with Windows-centric commands; Windows paths and patterns are used throughout, and Linux/macOS users are not provided with equivalent instructions for key steps (e.g., kubectl install, file extraction).
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using curl or package managers like apt, yum, brew).
- For file extraction, include Linux/macOS Bash commands (e.g., unzip or tar) alongside Windows Expand-Archive.
- Show Bash examples with POSIX-style paths (e.g., /home/user/archive.zip) and clarify when Windows paths are used.
- Add explicit notes or tabs for Linux/macOS users where commands or tools differ.
- Ensure parity in all setup steps, including global variable definitions and file manipulations.
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-line examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). There are no Bash or Linux shell equivalents for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, which uses Bash/PowerShell tabs. This creates friction for Linux/macOS users, as they must translate PowerShell-specific commands and patterns to their environment.
Recommendations
- Provide Bash/Linux shell equivalents for all Azure CLI, Docker, and kubectl commands.
- Avoid using PowerShell-specific syntax (e.g., variables like $var, ConvertTo-Json, Out-File) in cross-platform scenarios; use generic CLI syntax or provide both PowerShell and Bash versions.
- Clearly indicate when a command is Windows-only, and offer alternative instructions for Linux/macOS users.
- Use tabs or sections to separate Windows/PowerShell and Linux/Bash examples throughout the troubleshooting steps, not just in the 'service groups' section.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides authentication examples for Azure Container Registry using both Azure CLI and Azure PowerShell, but PowerShell is featured prominently and often alongside CLI. Windows tools and patterns (PowerShell cmdlets) are mentioned throughout, sometimes before or equally with CLI. There is no explicit mention of Linux/macOS-specific shell environments (e.g., Bash), and no examples using Bash or Linux-native scripting. The use of 'docker' and 'podman' is cross-platform, but the documentation does not clarify or show Linux/macOS workflows or shell syntax, potentially creating friction for non-Windows users.
Recommendations
- Add explicit Bash/Linux/macOS shell examples for authentication workflows, especially for scripting scenarios.
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and provide sample shell syntax for environment variable usage (e.g., export TOKEN=...)
- Balance PowerShell and CLI coverage by showing CLI examples first, or side-by-side with Bash equivalents.
- Mention that PowerShell is available cross-platform, but provide Bash alternatives for Linux/macOS users.
- Include notes or tips for Linux/macOS users regarding installation and use of Docker, Azure CLI, and authentication flows.
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 critical operations, but Windows/PowerShell examples are often presented before Linux/CLI equivalents. Some minor notes reference Windows-specific behaviors (e.g., setting --gateway-resource-id to null in PowerShell), and Windows Admin Center is mentioned as a scenario, but Linux parity is generally maintained. The log file paths and instructions are clearly separated for Windows and Linux. There are no sections where Linux users are unable to complete tasks, but Windows examples are sometimes prioritized.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux users see their platform first in some sections.
- Explicitly state that all CLI commands work on Linux/macOS and Windows, and clarify any platform-specific nuances.
- Where possible, provide Bash shell script examples alongside PowerShell for automation.
- Review scenario lists to ensure Linux-relevant tools are mentioned equally (e.g., highlight SSH for Linux as well as Windows Admin Center).
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 files, but the Linux example is presented first and is more concise. The Windows section uses certutil and findstr, which are Windows-specific tools, and requires manual header removal. No PowerShell examples are given, and all other commands (openssl, kubectl, Azure CLI) are cross-platform. The Windows instructions are present but not prioritized or exclusive.
Recommendations
- Add explicit macOS instructions for base64 encoding (if any differences exist).
- Clarify that Azure CLI, kubectl, and openssl commands work on Windows, Linux, and macOS.
- Consider providing PowerShell alternatives for base64 encoding on Windows, as many users may prefer PowerShell over certutil.
- Mention that Linux commands also work on macOS, or provide macOS-specific notes if needed.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows and Linux VM extension tables separately, but Windows extensions are listed first and in greater detail. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, without prioritizing Windows-specific tools. No examples or walkthroughs are provided in this page, so there is no PowerShell-heavy or missing Linux example bias. Partner extensions are shown for both OSes. Overall, the bias is limited to Windows extensions being presented before Linux extensions.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them together in a unified table to emphasize parity.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, ARM templates) support both Windows and Linux extensions where applicable.
- Ensure future documentation sections or linked pages provide Linux examples and instructions alongside Windows ones.
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/PowerShell instructions are consistently presented first and in greater detail (e.g., notes about PowerShell ISE, execution policy). The retry command section also lists Windows before Linux. There is minor bias toward Windows in ordering and depth, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Provide equivalent troubleshooting notes for Linux (e.g., shell environment caveats, permissions) as are given for Windows/PowerShell.
- Ensure all screenshots and UI instructions are OS-neutral or clarify when differences exist.
- Explicitly state that both Windows and Linux are fully supported and highlight any OS-specific requirements or limitations.
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, which is a minor bias in favor of Linux/macOS users (not Windows). No evidence of Windows-only tools, Windows-first ordering, or missing Linux examples is found.
Recommendations
- No changes needed for Linux parity. If strict neutrality is desired, alternate the order of Bash and PowerShell tabs or clarify that both are equally supported.
- Continue to provide both Bash and PowerShell examples for all commands.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, ensuring parity for Linux/macOS and Windows users. However, in most sections, PowerShell examples are presented after Bash examples, which is a minor 'windows_first' bias. There are no Windows-only tools, commands, or patterns used, and all instructions are cross-platform (using Azure CLI and kubectl). No critical steps are Windows-only.
Recommendations
- Continue to provide both Bash and PowerShell examples for all CLI operations.
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that both are equally supported.
- Add a brief note at the top clarifying that all steps are cross-platform and that users should select the tab matching their environment.
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 the Azure CLI and Helm, which are cross-platform.
Recommendations
- No action needed for Linux parity. Both Bash and PowerShell examples are present and equivalent.
- If desired, alternate the order of Bash and PowerShell tabs in some sections to balance presentation.
- Ensure that any referenced scripts or files (e.g., .json, .yaml) are accessible and usable on both platforms.
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 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 PowerShell-specific commands, but SSMS is emphasized as a main tool, which may create friction for Linux/macOS users. No Linux-specific GUI clients (e.g., Azure Data Studio, DBeaver) are mentioned.
Recommendations
- Mention cross-platform GUI clients such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit examples for connecting from Linux/macOS using these clients.
- Clarify that sqlcmd is available on both Linux and Windows, and provide installation instructions for Linux/macOS.
- Consider showing Linux/macOS examples first or equally alongside Windows examples.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation primarily uses Azure CLI and kubectl commands, which are cross-platform. However, there are subtle signs of Windows bias: Windows/Mac installation instructions for Azure kubelogin are mentioned first, while Linux instructions are provided later. There are no explicit PowerShell examples, but Azure CLI is often associated with Windows users. Some instructions (such as editing files with 'vi') assume a Linux environment, but overall, the documentation does not provide Linux-specific troubleshooting or examples before Windows/Mac. The bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Present installation instructions for Azure kubelogin for Linux, Mac, and Windows in parallel or in a table, rather than listing Windows/Mac first.
- Explicitly state that Azure CLI and kubectl are cross-platform and provide links to installation instructions for all OSes.
- Add troubleshooting tips for Linux-specific issues (e.g., file permissions, SELinux, systemd) where relevant.
- Ensure that all commands and examples are clearly marked as cross-platform, and highlight any OS-specific steps.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in feature and bug fix tracking. However, there is a consistent pattern of listing Windows download links and version numbers before Linux, and Windows-specific tools and patterns (e.g., PowerShell, msiexec, .msi installers) are mentioned explicitly, sometimes without Linux equivalents in the same context. Some troubleshooting and known issues sections reference only Windows installer behaviors and solutions.
Recommendations
- Alternate the order of Windows and Linux download links and version listings, or present them together to avoid the impression of Windows primacy.
- Where Windows-specific tools (e.g., PowerShell, msiexec) are mentioned, ensure Linux equivalents (e.g., shell commands, package managers) are also referenced where applicable, or clarify when an issue is Windows-only.
- In known issues and troubleshooting sections, provide Linux-specific guidance if relevant, or explicitly state when an issue does not affect Linux.
- Consider including a summary table or section highlighting cross-platform parity and any OS-specific differences to make it clear when features or fixes apply to only one OS.
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 major tasks, but PowerShell examples are consistently presented alongside CLI, sometimes before Linux-specific guidance. There is no explicit Linux example (e.g., Bash scripts), but CLI commands are cross-platform. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. However, the CLI examples are sufficient for Linux parity, and environment variable instructions use both export (Linux/macOS) and $Env (Windows/PowerShell) syntax.
Recommendations
- Continue to provide Azure CLI examples as the primary cross-platform method.
- Consider explicitly stating that Azure CLI commands are supported on Linux/macOS and Windows.
- Optionally, clarify that PowerShell examples are for Windows users, and CLI is recommended for Linux/macOS.
- Add brief Bash script examples for common tasks, if relevant.
- Ensure that any environment variable instructions always show both export (Linux/macOS) and $Env (Windows/PowerShell) syntax.
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 lists both Windows and Linux-related endpoints, but there is evidence of Windows bias: Windows-specific services (e.g., time.windows.com, sts.windows.net, login.windows.net, servicebus.windows.net) are referenced, and Windows NTP is mentioned explicitly. Windows terminology (e.g., 'Management machine', 'Windows NTP') appears before Linux equivalents, and Windows endpoints are listed before Linux ones in some cases. However, Linux endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io) are also included, and SSH is referenced as a connectivity requirement, which is cross-platform.
Recommendations
- Clarify that NTP can use Linux NTP servers (e.g., pool.ntp.org) and provide guidance for Linux/macOS users.
- Mention Linux alternatives or equivalents for Windows-specific endpoints where applicable.
- Ensure examples and terminology are balanced, e.g., refer to 'management machine (Windows or Linux)' instead of just 'management machine'.
- List Linux-related endpoints and requirements alongside Windows ones, not after.
- Add explicit notes for Linux/macOS users where Windows-specific services are referenced.
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, with more detailed scripting and output illustration. PowerShell is emphasized in related content, and Windows prerequisites are listed before Linux. Overall, Linux parity is maintained, but Windows is subtly prioritized.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Ensure that Bash/Linux examples are as detailed and illustrated as PowerShell/Windows examples, including output screenshots.
- In related content, mention Azure CLI and Bash alternatives before or alongside PowerShell.
- Clarify that both Windows and Linux are equally supported for 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, but there are minor signs of Windows bias. Windows log file paths and PowerShell-style command syntax are mentioned first in some sections. Windows examples are presented before Linux examples in the verbose log section. References to Windows-specific tools (e.g., PowerShell, Windows environment variables) are present, but Linux equivalents are also included. Overall, Linux parity is maintained, but Windows is subtly prioritized in ordering and terminology.
Recommendations
- Present Linux and Windows examples in parallel or alternate order to avoid implicit prioritization.
- Where possible, use neutral language and paths (e.g., mention both `%ProgramData%` and `/var/opt/` together).
- Ensure troubleshooting steps reference both Windows and Linux tools equally (e.g., log locations, commands).
- Add explicit notes clarifying Linux requirements (e.g., root access, sudo usage) where relevant.
- Consider including a summary table of key differences between Windows and Linux troubleshooting steps.
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 parity for both Linux and Windows in most sections, including explicit mention of Linux and Windows installation URLs and agent support. However, there are minor indications of Windows bias: Windows installation URLs are listed before Linux in tables, and Windows-specific tools (Windows Admin Center) are referenced in service tags and endpoint descriptions, sometimes without Linux equivalents or alternatives. The cryptographic protocol section gives Windows-specific troubleshooting links and registry settings, while Linux is referenced generically via OpenSSL. Overall, Linux users can complete the task without significant friction.
Recommendations
- List Linux installation URLs before or alongside Windows URLs in tables to avoid 'windows_first' bias.
- When referencing Windows Admin Center, clarify Linux alternatives or state if no equivalent exists.
- Provide Linux-specific troubleshooting resources for TLS configuration (e.g., OpenSSL guides) alongside Windows links.
- Ensure that examples and descriptions are balanced between Linux and Windows, especially in sections about agent installation and network configuration.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page presents Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell is mentioned alongside Azure CLI in both metadata and main text, suggesting a Windows-centric approach. There is no explicit Linux shell example or mention of Bash, and PowerShell is listed before REST API and Linux-specific notes are minimal. The page does state Run command supports both Windows and Linux, but the focus on PowerShell and lack of Linux shell examples creates a mild Windows bias.
Recommendations
- Add explicit Bash or Linux shell examples alongside PowerShell examples in the main documentation.
- Mention Linux shell usage (e.g., Bash, sh) in the 'Experiences' section to clarify parity.
- Ensure that Linux-specific limitations (like the name length restriction) are highlighted equally with any Windows-specific notes.
- Consider listing Azure CLI and Bash examples before PowerShell to balance the order.
- Link to Linux-specific usage guides or troubleshooting if available.
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 in its descriptions and intent, but there are several instances where Windows-specific tools, examples, or references are mentioned before or more prominently than their Linux equivalents. PowerShell and Windows-centric tools are referenced in automation and configuration scenarios, and some links default to Windows tabs or examples. Linux support is mentioned, but often after Windows, and Linux-specific examples or guidance are less detailed or absent.
Recommendations
- Ensure that all automation and configuration examples (e.g., Azure Automation, onboarding, agent installation) provide both Windows and Linux command-line or script examples, not just PowerShell or Windows-centric instructions.
- When referencing tools or features (such as Azure Automation runbooks or Update Manager), explicitly mention and link to Linux documentation or provide Linux-specific tabs/examples alongside Windows ones.
- In lists or feature descriptions, avoid always listing Windows first; alternate or clarify that features apply equally to Linux and Windows where appropriate.
- Where links default to Windows tabs (e.g., Windows Server management), ensure Linux tabs are equally visible or provide direct links to Linux guidance.
- Add Linux-focused scenarios or callouts where relevant, especially in sections about configuration, monitoring, and agent deployment.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral or explicitly mention both Windows and Linux, there are a few instances where Windows-related features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are listed before Linux equivalents or Linux-specific enhancements. Additionally, Windows tools like System Center Configuration Manager and Group Policy are mentioned as methods for installing Arc agents at scale, with Linux tools (Ansible) appearing later in the list. However, Linux support is also referenced (e.g., SSH-based agent installation, Ansible playbook), and most features are not OS-specific.
Recommendations
- When listing tools or methods for agent installation, group Windows and Linux options together or alternate their order to avoid implicit prioritization.
- Explicitly mention Linux equivalents for Windows tools where possible (e.g., highlight Ansible, Puppet, Chef alongside SCCM and Group Policy).
- Ensure that Linux-related enhancements (such as guest OS customization) are given equal prominence and detail as Windows features.
- Consider adding links or references to Linux documentation/examples where Windows-specific features are discussed, if Linux alternatives exist.
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 each section, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or Windows-only tools mentioned.
Recommendations
- Continue to provide both Bash and PowerShell examples for all CLI operations.
- Consider clarifying that Azure CLI commands are fully cross-platform and can be run on Windows, Linux, and macOS.
- Optionally, rotate the order of Bash and PowerShell tabs or explicitly state that Bash is for Linux/macOS and PowerShell for Windows, to reinforce parity.
- Add a brief note at the start indicating that all CLI instructions are compatible with Linux, macOS, and Windows.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, but PowerShell examples are presented after Bash. There are no Windows-specific tools or patterns mentioned, and all commands use the cross-platform Azure CLI. No Linux/macOS examples are missing, and the content is not Windows-centric.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right tab.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance where relevant.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, indicating a minor 'windows_first' bias. There are no Windows-specific tools or patterns used exclusively, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly mention that Bash examples are intended for Linux/macOS users and PowerShell for Windows users, to avoid confusion.
- Ensure that any OS-specific nuances (such as file encoding or base64 commands) are clearly explained for both platforms.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, particularly in the May 2025 release section. While most CLI instructions use Bash syntax, the only explicit code samples for setting and downloading configurations are in PowerShell, and Bash equivalents are missing. The overall structure does not mention Windows tools or patterns exclusively, but the ordering and example choice suggest a mild Windows bias.
Recommendations
- Provide Bash equivalents for all PowerShell CLI examples, especially for configuration set and download commands.
- Ensure that CLI instructions are presented in a cross-platform manner, using generic syntax or offering both Windows (PowerShell) and Linux/macOS (Bash) versions.
- Add clarifying notes that Azure CLI commands work on all platforms and highlight any OS-specific differences if present.
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 shown before PowerShell, which is a minor 'windows_first' bias in ordering. No Windows-only tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to clarify intent.
- 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 the PowerShell examples are always shown after Bash. There are no Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, the PowerShell examples are present throughout, which may suggest a slight bias toward Windows users, but Linux/macOS users are fully supported. No critical Linux/macOS gaps are present.
Recommendations
- Consider adding a note clarifying that Bash examples are suitable for Linux/macOS and Windows (via WSL or Git Bash), while PowerShell is for Windows users.
- Ensure that Bash and PowerShell tabs are equally prominent and that Bash is not implicitly treated as secondary.
- If possible, provide guidance for running Bash scripts on Windows (e.g., using WSL or Git Bash) for parity.
- Explicitly state that all CLI commands are cross-platform and supported on Linux/macOS.
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 both are supported, PowerShell is a Windows-centric tool and is mentioned before Linux-native equivalents (such as Bash). No explicit Linux/macOS examples or tools (like Bash scripts) are referenced, but the page is generally platform-neutral and focused on the mobile app.
Recommendations
- Clarify that Azure Copilot can generate scripts for both PowerShell and Bash (or other Linux shells), not just PowerShell.
- Provide examples or mention Bash script generation alongside PowerShell to ensure Linux/macOS users feel equally supported.
- Consider rephrasing 'CLI and PowerShell scripts' to 'CLI scripts (including Bash and PowerShell)' or similar, to highlight cross-platform support.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, the PowerShell section is equally detailed and prominent, which may create friction for Linux/macOS users if PowerShell is perceived as a primary tool. No Windows-specific tools or patterns are mentioned exclusively, and all workflows are cross-platform. There are no missing Linux/macOS examples, and Docker CLI usage is referenced generically.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, not just Windows.
- Consider adding a brief note that Azure CLI is available on all major platforms, including Windows, Linux, and macOS.
- If possible, provide explicit Bash or shell script examples for common workflows, or link to Linux/macOS-specific guidance.
- Ensure that references to PowerShell do not imply Windows-only usage, and avoid language that suggests PowerShell is the default or preferred tool for all users.
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 the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is present and detailed, but there is no Linux/macOS shell-specific guidance or explicit mention that PowerShell Core is cross-platform. The examples and instructions do not show any Linux/macOS-specific shell commands or notes, and the PowerShell section could be interpreted as Windows-centric. However, the CLI examples are sufficient for Linux/macOS users, and no critical steps are Windows-only.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Mention that Azure PowerShell can be used cross-platform via PowerShell Core, or clarify if the examples require Windows PowerShell.
- Optionally, add Bash shell examples for deploying templates using Azure CLI to reinforce Linux parity.
- Ensure that any references to file paths or shell commands are neutral or provide both Windows and Linux/macOS variants if relevant.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command-line examples for Helm and Azure CLI, which are cross-platform, but there are subtle signs of Windows bias. The environment variable setup uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'). Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, then Azure PowerShell, then Azure Portal, which is a minor 'windows_first' pattern. However, most commands are generic and work on all platforms, and Helm/Azure CLI are cross-platform tools.
Recommendations
- For environment variable setup, include both Windows ('set') and Linux/macOS ('export') examples, e.g., - Windows: set ACR_NAME=<container-registry-name> - Linux/macOS: export ACR_NAME=<container-registry-name>
- When referencing Azure PowerShell, clarify that Azure CLI is recommended for cross-platform use, and provide parity in examples.
- Explicitly state that all shown commands work on Windows, Linux, and macOS unless otherwise noted.
- Where possible, show both Windows and Linux/macOS shell commands side-by-side for critical steps.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as changing registry SKU and showing usage), but PowerShell is consistently mentioned alongside or immediately after CLI, and REST API is referenced as well. However, there are no explicit Linux/macOS-specific examples or notes, and PowerShell is not a native tool on Linux/macOS. The CLI is cross-platform, but the order of presentation and inclusion of PowerShell may subtly favor Windows users.
Recommendations
- Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Present Azure CLI examples first, followed by PowerShell, to reduce Windows-first bias.
- Add a brief note clarifying that PowerShell examples are primarily for Windows users, and that PowerShell Core is available on Linux/macOS if desired.
- Consider including Bash shell scripting examples for common tasks, or referencing how Linux/macOS users can accomplish equivalent tasks.
- Where REST API is referenced, provide a simple curl example for Linux/macOS users.