234
Pages Scanned
50
Pages Flagged
234
Changed Pages
21.4%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:32
Scan Information
Started At: 2026-02-23 00:00:32
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 demonstrates a strong Windows/PowerShell bias: all onboarding scripts and usage examples are provided exclusively for PowerShell, with no mention of Bash, Linux, or macOS equivalents. Prerequisites reference Windows-specific tools (winget), and all command-line instructions assume a Windows environment. There are no instructions or examples for running the scripts on Linux or macOS, nor is there guidance on adapting the process for non-Windows users.
Recommendations
- Provide Bash or shell script equivalents for onboarding tasks, or clarify if the scripts are Windows-only.
- Include Linux/macOS installation instructions for prerequisites (e.g., using apt, yum, or Homebrew instead of winget).
- Document whether the .ps1 scripts can be run with PowerShell Core on Linux/macOS, and provide guidance for those platforms.
- If the onboarding process is truly Windows-only, state this explicitly at the top of the documentation.
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 page exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. All examples are PowerShell-based, and there is no mention of Bash, shell, or cross-platform alternatives. The script is only referenced as a .ps1 file, implying Windows/PowerShell usage. There are no Linux/macOS instructions or examples, and the documentation does not clarify whether the script can be run with PowerShell Core on Linux/macOS or if there is an equivalent Bash script.
Recommendations
- Clarify whether the RGCleanScript.ps1 script can be run using PowerShell Core on Linux/macOS, and provide explicit instructions for those platforms if supported.
- If the script is Windows-only, provide a Bash or shell script alternative for Linux/macOS users, or explain how Linux/macOS users can achieve the same cleanup.
- Add example commands for Linux/macOS environments, including any prerequisites (such as installing PowerShell Core if needed).
- Mention cross-platform compatibility in the prerequisites section, or clearly state if the script is Windows-only.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for migration, with instructions to run it in PowerShell. There are no Linux/macOS shell or cross-platform alternatives, nor is there guidance for users on non-Windows platforms. The script and instructions assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
- Provide a Bash or cross-platform script for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Add explicit instructions for running the migration on Linux/macOS, including any prerequisites (e.g., PowerShell installation, script compatibility).
- Mention any limitations or workarounds for non-Windows users, or offer a manual migration process if a script is not available.
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 Linux configuration steps. No native Linux shell or SSH examples are provided for these steps, creating friction for Linux/macOS users who may not have access to PowerShell or Windows tools.
Recommendations
- Provide equivalent Linux-native commands (e.g., using SSH or direct shell access) for checking and setting sysctl parameters.
- Clarify if 'Invoke-AksEdgeNodeCommand' is available cross-platform, or offer alternatives for Linux/macOS environments.
- Add explicit instructions for Linux users to run sysctl commands directly on the node, rather than via PowerShell.
- Ensure all critical steps have Linux-native examples, not just PowerShell/Windows-centric ones.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command examples for connecting to the SQL Server pod using PowerShell syntax and references the use of sqlcmd, which is commonly associated with Windows environments. The PowerShell examples are shown exclusively, with no equivalent Linux/macOS shell (bash) examples provided. This may create friction for Linux/macOS users, as Azure Arc-enabled data services are often deployed on Kubernetes clusters running on Linux nodes.
Recommendations
- Add equivalent bash shell examples for connecting to the SQL Server pod using sqlcmd, e.g., using standard shell syntax instead of PowerShell.
- Clarify that sqlcmd is cross-platform and provide installation instructions for Linux/macOS if needed.
- Ensure all kubectl and T-SQL commands are shown in a platform-neutral way, and avoid using Windows-specific shell syntax unless the feature is Windows-only.
- Consider including notes or sections explicitly for Linux/macOS users, especially for credential decoding and connecting to pods.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides examples and file paths primarily for Windows users (e.g., C:\Backupfiles\test.bak) and does not offer equivalent Linux/macOS examples for key steps such as backing up the database or copying files with kubectl. Tools like Visual Studio Code and Azure Storage Explorer are cross-platform, but the backup/restore examples and file path conventions are Windows-centric, which may confuse or hinder Linux/macOS users.
Recommendations
- For every example using a Windows file path (e.g., C:\Backupfiles\test.bak), provide a Linux/macOS equivalent (e.g., /home/user/backup/test.bak).
- Explicitly mention that Visual Studio Code and Azure Storage Explorer are available on Linux/macOS, and provide installation links or notes where appropriate.
- When demonstrating the use of kubectl cp, show both Windows and Linux/macOS source file path examples.
- Clarify any OS-specific prerequisites or steps, and ensure that Linux/macOS users are not left to infer the correct commands or paths.
- Consider adding a short section or callout box addressing cross-platform usage, especially for common database administration tasks.
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
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps for removing headers. The Linux example is brief and lacks equivalent guidance for decoding or header removal. Windows tools (certutil, findstr) are mentioned explicitly, while Linux alternatives are not. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and is generally platform-neutral.
Recommendations
- Expand Linux example to include decoding and header removal steps, possibly using 'base64 -d' and 'grep -v' or 'sed' for header removal.
- Mention Linux equivalents for Windows tools (e.g., 'grep -v CERTIFICATE b64-encoded.txt > updated-b64.txt' instead of 'findstr').
- Ensure both Linux and Windows examples are equally detailed and placed side-by-side for parity.
- Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, or Windows.
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 issues and is intended for cross-platform environments. However, there are several instances where Windows/PowerShell tools and patterns are mentioned first or exclusively, and Linux equivalents are missing or less emphasized. For example, PowerShell is referenced for troubleshooting HTTP2 errors, and Windows-centric terminology (e.g., 'Remote PowerShell', 'RDP', 'time.windows.com') appears without Linux alternatives. Some CLI commands and troubleshooting steps are described generically, but when OS-specific instructions are given, Windows is prioritized or Linux is omitted.
Recommendations
- Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP2 troubleshooting).
- When referencing folder permissions or SSH access, include Linux/macOS file path and permission examples alongside Windows.
- Mention Linux/macOS tools (e.g., terminal, SSH, nslookup, dig) wherever Windows tools (PowerShell, RDP) are discussed.
- Clarify that Azure CLI commands work equally on Linux/macOS and Windows, and provide OS-specific install/downgrade instructions.
- Replace or supplement references to 'time.windows.com' with cross-platform NTP sources.
- Ensure troubleshooting steps for network, DNS, and proxy issues include Linux/macOS command examples and guidance.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell deployment commands are presented first and solely, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does not mention or show Linux-native tools or deployment patterns, and file path examples use Windows-style paths (e.g., 'D:\Azure\Templates\...') in command samples.
Recommendations
- Add Azure CLI deployment command examples alongside PowerShell, especially for template deployments.
- Show Bash or shell scripting alternatives for Linux/macOS users.
- Include Linux-style file path examples (e.g., '/home/user/Azure/Templates/...') in command samples.
- Explicitly state that both PowerShell and CLI are supported, and link to relevant CLI documentation.
- Consider presenting CLI and PowerShell examples side-by-side or alternating their order.
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, uninstall, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and tools (such as PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are presented in greater detail and often appear before Linux equivalents. The cleanup script for removing stale resources is only provided in PowerShell, with no Linux/bash alternative. Windows-specific tools and patterns (e.g., Control Panel, Registry Editor, Msiexec) are described extensively, while Linux instructions are more concise and lack advanced scripting or automation examples.
Recommendations
- Provide equivalent bash or shell scripts for Linux users, especially for tasks like cleanup of stale Arc resources.
- Ensure Linux examples are given equal prominence and detail as Windows examples, including automation and advanced usage.
- Where possible, mention Linux tools (e.g., cron, systemd, package managers) alongside Windows tools (e.g., Group Policy, WSUS).
- Consider adding troubleshooting and automation guidance for Linux environments, similar to the PowerShell scripts provided for Windows.
- When listing upgrade methods or tools, alternate the order or provide a neutral listing (e.g., alphabetical, or 'Windows and Linux' together).
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides recovery instructions and a script for Windows users, using PowerShell and referencing a Windows-specific script. There are no examples, scripts, or guidance for Linux or macOS users, nor any mention of equivalent tools or workflows for non-Windows platforms.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or Python.
- Clarify whether the recovery process is supported only on Windows, or if cross-platform options exist.
- If the script is Windows-only, explicitly state this limitation and offer alternative manual steps for Linux/macOS users.
- Include examples for Linux (e.g., using curl, ssh, or Azure CLI) 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 instructions and examples for Windows users, especially for running the deboarding script via PowerShell. Linux users are not given equivalent script execution guidance, and Windows instructions are presented first and in greater detail. The script appears to be PowerShell-based, with no mention of a Linux-compatible version or how to run it on Linux/macOS. Manual removal steps are platform-neutral, but the automation is Windows-centric.
Recommendations
- Provide instructions for running the deboarding script on Linux/macOS, or clarify if the script is Windows-only.
- If the script is PowerShell-only, consider offering a Bash or cross-platform version, or document how to use PowerShell Core on Linux/macOS.
- Present Linux and Windows instructions in parallel, rather than Windows-first.
- Explicitly state platform limitations for the script, so Linux/macOS users know their options.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page exhibits moderate Windows bias. The primary automation script for Arc agent installation is a PowerShell script, with instructions focused on Windows environments (e.g., PowerShell terminal, Set-ExecutionPolicy, Windows Task Scheduler). Linux-specific guidance is limited to a brief sudo configuration note, and Linux/macOS equivalents for scripting and scheduling are missing. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux alternatives.
Recommendations
- Provide a Bash or Python version of the automation script for Linux/macOS users, or document how to run the PowerShell script cross-platform (e.g., with PowerShell Core).
- Include example instructions for running the script on Linux/macOS, such as using cron for scheduling instead of Windows Task Scheduler.
- Add Linux/macOS terminal usage examples alongside PowerShell examples.
- Clarify any OS-specific requirements for the script and agent installation.
- Ensure parity in out-of-band automation methods (e.g., show Ansible, Bash, or Python examples before or alongside Windows tools).
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 for disaster recovery operations of the Azure Arc resource bridge VM is heavily focused on PowerShell scripting, with all code examples and onboarding instructions provided exclusively in PowerShell. There is no mention of Bash, Linux shell, or cross-platform alternatives, nor are Linux/macOS usage patterns or tools referenced. The onboarding script is referenced as a .ps1 file, implying Windows/PowerShell usage, and no Linux-specific guidance or parity is provided.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
- Explicitly state platform requirements for the onboarding script (e.g., if it must be run on Windows/PowerShell, mention this up front).
- If possible, offer Azure CLI or cross-platform alternatives for steps currently requiring PowerShell.
- Add guidance for Linux/macOS users, including how to install/run PowerShell Core if required, or how to adapt the script for their environment.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for all CLI commands and references PowerShell scripts (.ps1) for automation, without providing Bash or shell equivalents. There are no explicit Linux/macOS examples or guidance, and PowerShell is presented as the default scripting environment, which may create friction for Linux/macOS users.
Recommendations
- Provide CLI command examples using Bash syntax (e.g., az ... in Bash, not PowerShell).
- Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or clarify if the .ps1 scripts are cross-platform (e.g., PowerShell Core).
- Explicitly mention if the Azure CLI commands are platform-agnostic and can be run in Bash or other shells.
- Add notes or examples for Linux/macOS users, including any required adaptations for file paths or script execution.
- Clarify if PowerShell Core is required for non-Windows platforms, and link to installation instructions if so.
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
windows_tools
missing_linux_example
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for orchestration diagnostics, onboarding, and log collection. Paths in JSON templates use Windows-style backslashes and drive letters. There are no Bash or Linux/macOS shell equivalents, and no mention of Linux-specific tools or patterns. The use of PowerShell and Windows file paths is pervasive, even though the topic (Azure Arc-enabled Kubernetes clusters and workload orchestration) is cross-platform and commonly used on Linux.
Recommendations
- Add Bash/CLI examples alongside PowerShell scripts for all az commands and onboarding steps.
- Provide Linux/macOS file path examples in JSON templates (e.g., /home/user/config.yaml) and clarify path conventions.
- Explicitly state that scripts can be run from Linux/macOS with az CLI and provide guidance for non-Windows users.
- Where PowerShell is used for scripting, offer Bash equivalents or note any limitations.
- Review screenshots and instructions to ensure parity for Linux/macOS users accessing Azure portal and Log Analytics.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere, with some bias toward Windows. Windows-specific features (e.g., guest OS customization for Windows VMs, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) are mentioned before Linux equivalents or without Linux parity. Azure PowerShell is listed alongside Azure CLI and REST APIs, but no Linux-specific CLI tools are highlighted. Windows tools (System Center Configuration Manager, Group Policy) are mentioned for agent installation, with only one Linux tool (Ansible) referenced. Some features are Windows-only by nature, but overall, Linux examples and tools are less prominent.
Recommendations
- Ensure Linux-specific features (e.g., guest OS customization for Linux VMs) are mentioned with equal prominence and detail.
- Provide Linux-first or cross-platform examples where possible, especially for agent installation and VM management.
- Include references to Linux-native tools (e.g., shell scripts, cloud-init, Puppet, Chef) alongside Windows tools for at-scale operations.
- When listing SDKs or CLI tools, clarify their cross-platform compatibility and provide Linux usage examples.
- Balance the order of Windows and Linux features to avoid 'windows_first' impression.
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 PowerShell and Windows command-line patterns. Most examples use PowerShell syntax, even for cross-platform tools like Azure CLI, and some commands (e.g., Base64 encoding, file manipulation) are given only in PowerShell. Linux/macOS equivalents (bash or shell) are missing for critical steps, except in the 'service groups' section, which provides both Bash and PowerShell tabs. This creates friction for Linux/macOS users, especially in sections involving scripting, file encoding, and registry management.
Recommendations
- Provide Bash/shell equivalents for all PowerShell examples, especially for Azure CLI commands, file manipulation, and Base64 encoding.
- Clearly indicate which commands are cross-platform and which are Windows-specific.
- Add notes or tabs for Linux/macOS users where PowerShell syntax is used, explaining how to achieve the same result in Bash.
- Review file encoding and manipulation steps to ensure Linux/macOS compatibility (e.g., use 'iconv', 'cat', or 'sed' instead of PowerShell-specific commands).
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 shows evidence of Windows bias in several areas. The 'winget' command is used as the only example for installing kubectl, which is a Windows-specific tool, with no Linux/macOS installation guidance provided. In the section on extracting ZIP files, the Bash tab uses the Windows-native 'Expand-Archive' command (not available on Linux/macOS), and all example paths are Windows-style (e.g., 'C:\path\to\archive.zip'). There are no Linux/macOS-specific commands or examples for these steps. The rest of the documentation uses Azure CLI and kubectl, which are cross-platform, but the initial setup steps may create friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt/yum/brew').
- For extracting ZIP files, offer Linux/macOS Bash examples using 'unzip' or 'tar' alongside Windows 'Expand-Archive'.
- Use generic file paths or show both Windows and Linux/macOS path formats.
- Ensure all critical setup steps have Linux/macOS equivalents and are presented equally.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The release notes for Workload Orchestration in Azure Arc generally provide cross-platform guidance, with most CLI examples using the Azure CLI (az), which is available on Windows, Linux, and macOS. However, in the May 2025 release section, CLI examples are given in PowerShell syntax (using backticks for line continuation and variables with $), which is Windows-centric and may confuse Linux/macOS users. Additionally, PowerShell examples are shown before Bash equivalents, and Bash is not provided for those commands.
Recommendations
- Provide Bash syntax examples alongside PowerShell for CLI commands, especially for configuration set/download.
- Clarify that Azure CLI commands are cross-platform and provide OS-specific guidance where relevant.
- Use generic CLI syntax (without OS-specific line continuation or variable conventions) in documentation unless the feature is Windows-only.
- Consider showing Bash examples first or equally with PowerShell to avoid implicit Windows prioritization.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page for Azure Arc resource bridge system requirements presents Azure CLI installation links and references with Windows as the default or first option. However, it does not provide explicit Windows-only examples, nor does it reference Windows-specific tools or patterns. The CLI commands shown are cross-platform, and there are no PowerShell-specific instructions or Windows-only tooling. Linux/macOS users may experience minor friction due to Windows-centric links and ordering.
Recommendations
- Provide Azure CLI installation links for Linux and macOS alongside Windows, or use a generic cross-platform link.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide explicit statements or examples for Linux/macOS users.
- Ensure that CLI commands and file paths are shown in a cross-platform manner (e.g., avoid Windows-style paths unless necessary).
- Add a note or section about supported operating systems for the management machine, including Linux and macOS.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, listing both in separate, equally detailed tables. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, templates) are mentioned without bias, and partner extensions are shown for both OSes. No critical Linux features are missing, and Linux examples are present where relevant.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or combining them into a single table with OS columns to reinforce parity.
- Explicitly state that all deployment methods (Azure CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Ensure that linked usage/deployment guides for Linux extensions are as comprehensive as their Windows counterparts.
- Add a brief note at the start clarifying that both Windows and Linux are fully supported and covered in this documentation.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias (since PowerShell is the Windows shell, but Bash is shown first). No exclusive Windows tools or patterns are used, and all commands rely on cross-platform Azure CLI and Helm tools. There are no missing Linux examples, and no Windows-specific tools or terminology are prioritized.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs or clarifying that both are equally supported.
- Explicitly mention that all examples are cross-platform and can be used on Linux, macOS, and Windows (with PowerShell or Bash).
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 equivalents (Azure CLI). No explicit Linux/macOS examples or tools are provided, but the page does not provide any code examples at all.
Recommendations
- Clarify that Azure Copilot can generate scripts for both Azure CLI (cross-platform) and PowerShell (Windows-centric), and consider listing Azure CLI first to emphasize cross-platform support.
- Add explicit mention that generated scripts can target Bash (Linux/macOS) as well as PowerShell, and provide examples for both where appropriate.
- Ensure future documentation includes sample outputs for both Azure CLI and PowerShell to demonstrate parity.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux-compatible example is provided, SSMS is listed first and there are no examples for popular Linux/macOS SQL clients (e.g., DBeaver, Azure Data Studio). The documentation also lacks explicit parity for Linux/macOS users in terms of graphical client options.
Recommendations
- List cross-platform tools (e.g., Azure Data Studio, DBeaver) alongside SSMS for connecting to SQL Managed Instance.
- Provide explicit Linux/macOS client examples and instructions, including graphical tools.
- Ensure that Linux/macOS users are not implicitly directed to Windows-only solutions by listing cross-platform options first or equally.
- Clarify that sqlcmd is available on both Windows and Linux, and provide installation instructions or links for Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There are explicit notes about Windows PowerShell and cmd.exe, but Linux-specific instructions are less detailed (e.g., 'Linux: install curl package' without a link). The note about 'curl' in PowerShell is prominent, but no equivalent Linux/macOS shell guidance is given. Overall, Linux/macOS users can complete the task, but the documentation favors Windows in ordering and detail.
Recommendations
- List installation links for all platforms in parallel order (Windows, Linux, macOS) or alphabetically to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions or links for tools like 'curl', matching the detail given for Windows.
- Add shell-specific notes for Linux/macOS (e.g., bash/zsh usage of curl) similar to the PowerShell note.
- Balance platform-specific guidance: if mentioning Windows cmd.exe or PowerShell, also mention Linux/macOS equivalents where relevant.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are included, there are no explicit Linux/macOS alternatives or examples, and Windows tools are presented as primary options. However, the page does not provide actual command examples, and the Azure Arc SQL Managed Instance is a cross-platform service.
Recommendations
- Add explicit mention of cross-platform management tools such as Azure Data Studio, which runs natively on Linux/macOS.
- Clarify which tools are available on Linux/macOS and which are Windows-only.
- Provide links or guidance for Linux/macOS users on managing SQL Managed Instance enabled by Azure Arc (e.g., using Azure CLI, Azure Data Studio, or VS Code).
- If PowerShell scripting is mentioned, also highlight Bash scripting or other cross-platform automation options.
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 consistently presents Azure PowerShell examples immediately after Azure CLI, and sometimes with more detailed explanation. While Azure PowerShell is not strictly Windows-only, it is most commonly used on Windows, and the documentation does not mention Bash or Linux-specific shell examples. However, Azure CLI commands are cross-platform and the environment variable instructions use both export (Linux/macOS) and PowerShell syntax, showing some parity.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux/macOS.
- Add Bash shell example blocks for environment variable setup (e.g., using export for Linux/macOS, as already shown, but clarify OS context).
- Mention that Azure PowerShell can be used on Linux/macOS, or provide Bash alternatives where appropriate.
- Consider adding a short section or callout about running these tasks on Linux/macOS, including any prerequisites or differences.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation includes references to Windows-specific services (e.g., time.windows.com, sts.windows.net, login.windows.net, servicebus.windows.net) and Windows NTP as the default, suggesting a Windows-centric perspective. Windows-related endpoints are mentioned alongside general endpoints, and Windows terminology appears before Linux equivalents (e.g., Windows NTP before mentioning alternatives). However, Linux-specific endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io) and SSH are also included, indicating some Linux parity. No explicit Linux/PowerShell command examples are present, but the listing order and notes favor Windows tools and patterns.
Recommendations
- Clarify when Windows-specific endpoints (e.g., time.windows.com) are only required for Windows deployments, and provide Linux alternatives (e.g., ntp.ubuntu.com or pool.ntp.org) where appropriate.
- Add explicit notes or examples for Linux management machines, including references to Linux tools and patterns.
- Ensure endpoint descriptions and notes are platform-neutral unless a service is truly Windows-only.
- Where Windows terminology is used (e.g., 'Windows NTP'), mention Linux equivalents in the same section and with equal prominence.
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. However, Windows download links are consistently listed first, and Windows-specific installer instructions (such as using msiexec or PowerShell) are highlighted in the 'Known Issues' section. Windows tools and patterns (e.g., PowerShell, MSI installer) are mentioned, while Linux equivalents (such as shell commands or package managers) are not described in similar detail. The Linux download link is present, and Linux-specific changes are documented, but Windows-centric instructions and ordering create minor friction for Linux users.
Recommendations
- Alternate the order of Windows and Linux download links or list them together to avoid Windows-first bias.
- Provide Linux-specific installer troubleshooting tips in the 'Known Issues' section, similar to the Windows guidance.
- When mentioning Windows tools (e.g., PowerShell, msiexec), also reference Linux equivalents (e.g., shell scripts, package managers) where relevant.
- Ensure parity in the level of detail for both Windows and Linux installation and upgrade instructions.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides examples for Azure portal, Azure CLI, and PowerShell throughout, with PowerShell commands shown alongside CLI commands. In some sections, Windows/PowerShell-specific notes are included (e.g., log file paths, PowerShell command syntax). However, Linux equivalents are generally present (e.g., CLI commands, Linux log paths), and the documentation does not exclusively focus on Windows tools or patterns. Windows examples (PowerShell) are sometimes shown before or alongside Linux/CLI examples, and there are minor references to Windows-specific tools (e.g., download.microsoft.com for Windows installation package).
Recommendations
- Ensure that CLI examples are presented before PowerShell examples to avoid Windows-first impression.
- Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Where file paths or log locations are referenced, always provide both Windows and Linux/macOS equivalents side-by-side.
- Clarify in onboarding instructions that scripts and agents are available for both Windows and Linux servers.
- Add explicit Linux/macOS onboarding steps or troubleshooting notes where relevant.
- Where Windows-specific endpoints or tools are mentioned (e.g., download.microsoft.com), also highlight Linux equivalents (e.g., packages.microsoft.com) and clarify their purpose.
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
minor_windows_example
Summary
The documentation provides parity for both Linux and Windows agents, including URLs for downloading installation packages and notes on cryptographic protocol support. However, Windows-specific tools and services (e.g., Windows Admin Center, Windows installation package, Windows Server TLS configuration) are mentioned first or exclusively in several sections. Windows-related endpoints and service tags are often listed before Linux equivalents, and troubleshooting links are Windows-focused. Linux information is present but sometimes secondary.
Recommendations
- Where possible, list Linux and Windows endpoints/examples together or alternate their order to avoid Windows-first bias.
- Add troubleshooting links or references for Linux TLS/OpenSSL configuration, similar to the Windows-specific troubleshooting link.
- Clarify when Windows tools (e.g., Windows Admin Center) are optional or Windows-only, and provide equivalent Linux management options if available.
- Ensure that Linux-specific guidance (e.g., OpenSSL configuration, package management) is as prominent and detailed as Windows guidance.
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: Windows interactive browser login is described first and labeled as 'Windows only', and Windows certificate store usage is detailed before Linux certificate file usage. The access token section references a Windows PowerShell cmdlet ('Get-AzAccessToken') as the primary method for obtaining a token, without mentioning Linux/macOS equivalents or Azure CLI alternatives. However, Linux authentication methods (device code, Azure CLI) are well covered and examples are generally cross-platform.
Recommendations
- When referencing access token acquisition, include Azure CLI commands (e.g., 'az account get-access-token') alongside PowerShell examples to ensure Linux/macOS parity.
- Present authentication options in a neutral order or clarify which are cross-platform, rather than starting with Windows-only methods.
- For certificate-based authentication, explicitly mention Linux/macOS file-based certificate usage before or alongside Windows certificate store options.
- Where possible, provide Linux/macOS-specific notes or examples (e.g., shell commands for hostname retrieval, certificate file paths).
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
windows_first
Summary
The documentation mentions both Windows and Linux support for the Run command on Azure Arc-enabled servers. However, there is a subtle bias: PowerShell is listed before Linux/CLI in several places, and the 'devx-track-azurepowershell' custom tag is present. The 'Next steps' section also lists PowerShell before REST API, and Azure CLI is listed first but is not clearly prioritized for Linux. There are no explicit Linux examples or Linux-specific guidance, and minor notes about Linux (e.g., name length restriction) are brief.
Recommendations
- Ensure Linux examples and guidance are equally represented alongside Windows/PowerShell examples.
- In 'Next steps', clarify which tools are best suited for Linux users (e.g., Azure CLI) and provide links to Linux-specific usage where relevant.
- Add explicit Linux command/script examples or reference Linux shell usage in the main documentation.
- Balance the order of tool mentions (e.g., alternate between CLI and PowerShell, or group by OS).
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 is a mild Windows bias. Windows examples and log file paths are presented first in several sections, and Windows-specific tools (such as PowerShell and Windows environment variables) are referenced 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 in sections to avoid always presenting Windows first.
- Where possible, present Windows and Linux examples side-by-side, or use tabs to allow users to select their OS.
- Explicitly mention Linux equivalents for Windows-specific tools or paths, such as referencing sudo for elevated permissions alongside 'administrator'.
- Ensure troubleshooting steps and remediation advice are equally detailed for both platforms.
- Consider using neutral language (e.g., 'elevated user context (administrator/root)') consistently throughout.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux requirements for the Azure Arc agent, but Windows tools (.NET Framework, PowerShell) are listed first and with download links, while Linux requirements are listed second and more briefly. Windows PowerShell is mentioned explicitly, but there is no equivalent mention of Bash or shell scripting for Linux. There are no Linux-specific examples or links to Linux installation guides, and Windows URLs (e.g., download.microsoft.com) are referenced before Linux ones.
Recommendations
- Present Linux and Windows requirements in parallel, rather than listing Windows first.
- Include links to Linux installation guides or scripts, similar to the Windows download links.
- Mention Linux shell scripting or command-line tools (e.g., Bash) where Windows PowerShell is referenced.
- Provide Linux-specific examples or walkthroughs for installing the Azure Arc agent.
- Clarify that both Windows and Linux are equally supported, and avoid subtle prioritization of Windows tools.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is generally cross-platform and highlights both Windows and Linux support for Azure Arc-enabled VMware vSphere. However, there is a mild Windows bias: Windows tools (PowerShell, Windows Server management, Windows registry, etc.) are often mentioned before Linux equivalents, and some links and examples default to Windows tabs or scenarios. PowerShell and Windows-centric automation are emphasized, while Linux-specific tools and examples are less prominent or referenced secondarily.
Recommendations
- Where automation tools are discussed (e.g., Azure Automation runbooks), explicitly mention Bash or Linux shell scripting alongside PowerShell, and provide links or tabs for Linux-focused instructions.
- When referencing configuration and monitoring features (e.g., change tracking, VM extensions), ensure Linux capabilities are described with equal detail and not just as an afterthought.
- In lists of supported tools and SDKs, avoid listing PowerShell or Windows tools first by default; alternate or group by platform.
- Where links default to Windows tabs (e.g., Windows Server management), add parallel links or clear guidance for Linux users.
- Add Linux/macOS-specific examples or callouts where appropriate, especially in sections about automation, configuration, and monitoring.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for each command, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, which could be interpreted as a minor 'windows_first' bias, but no critical Windows-only tools or patterns are used.
Recommendations
- Consider alternating the order of Bash and PowerShell examples or explicitly state that both are equally supported.
- Add a brief note clarifying that Bash examples are suitable for Linux/macOS terminals and PowerShell for Windows, to help new users.
- Ensure that any referenced scripts (e.g., 'Clean-up script') are available in both Bash and PowerShell versions, or clarify their platform compatibility.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, and sometimes the Bash tab is listed first. There are no Windows-specific tools or patterns used, and all instructions are based on the Azure CLI, which is cross-platform. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, to reassure users.
- If possible, alternate the order of Bash and PowerShell tabs or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to avoid perceived bias.
- Add a brief note in the prerequisites section indicating that all CLI examples are cross-platform unless otherwise noted.
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 for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash, which could be considered 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
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
- Explicitly state in the introduction that both Linux/macOS and Windows are fully supported, and that all commands are available in both Bash and PowerShell.
- Ensure that any OS-specific nuances (such as file encoding or carriage return handling) are clearly explained for both platforms, as is done in the connection string step.
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 and variable definitions. Bash examples are consistently shown before PowerShell, but there are no Windows-specific tools or patterns, and Linux parity is maintained throughout. No critical steps are Windows-only, and all instructions are equally applicable to Linux/macOS users.
Recommendations
- Consider alternating the order of Bash and PowerShell sections, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying cross-platform support for the Azure CLI and that Bash examples are suitable for Linux/macOS terminals.
- Ensure that any future examples or troubleshooting steps include Linux/macOS-specific guidance if needed.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users rather than Windows. No Windows-specific tools or patterns are mentioned exclusively, and all commands use the cross-platform Azure CLI and Helm tools.
Recommendations
- No changes needed for Linux parity. The documentation is already inclusive.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to avoid perceived bias.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
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, PowerShell examples are consistently presented after Bash examples, which is a minor 'windows_first' bias. No evidence of Windows-only tools, missing Linux examples, or exclusive Windows patterns is found. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
- Explicitly mention that both Bash and PowerShell examples are equivalent and suitable for Linux/macOS and Windows environments.
- Add a note clarifying that Azure CLI and Helm are cross-platform tools, and that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash).
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying dashboard templates. However, the PowerShell section is given equal prominence to the CLI section, and PowerShell is referenced in the overview alongside CLI and REST API. The PowerShell examples use Windows-centric syntax, but Azure CLI is cross-platform and is shown first. There are no missing Linux examples, and no Windows-only tools are referenced. The JSON templates and portal instructions are platform-neutral.
Recommendations
- Clarify that Azure PowerShell is available on Linux and macOS, not just Windows.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Consider mentioning Bash or shell scripting as alternatives for automation, especially for Linux/macOS users.
- If possible, add a brief note about installing Azure PowerShell on Linux/macOS, or link to cross-platform installation instructions.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash, and the PowerShell sections use Windows-style path separators and syntax. There is no evidence of Windows-only tools or patterns, and all commands use cross-platform Azure CLI and Helm. However, the PowerShell examples are present throughout, which may suggest a slight Windows bias, but Linux parity is maintained.
Recommendations
- Consider explicitly stating that all commands are cross-platform and that Bash examples can be used on Linux/macOS, while PowerShell is for Windows users.
- Add a note clarifying that Azure CLI and Helm are available on all platforms.
- If possible, provide a brief section on running PowerShell Core on Linux/macOS, or clarify that Bash is the default for Linux/macOS.
- Ensure that file paths and command syntax in PowerShell examples do not assume Windows-only conventions (e.g., use '/' instead of '\' for paths where possible).
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and linked more prominently. There are no explicit Windows-only tools or patterns, but the order and emphasis could suggest a Windows bias. All portal instructions are platform-neutral, but the tips and next steps favor PowerShell before CLI, which may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI and PowerShell options in parallel, or alternate their order to avoid implying preference.
- Clarify that Azure CLI works cross-platform and is often preferred for Linux/macOS users.
- Add brief notes or links about using Azure CLI on Linux/macOS, especially in tips and next steps.
- Ensure that examples and links for CLI and PowerShell are equally visible and accessible.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
minor_windows_tools
Summary
The documentation provides authentication examples for both Azure CLI and Azure PowerShell throughout, but PowerShell (a Windows-centric tool) is consistently given equal prominence to Azure CLI. In several sections, PowerShell examples are presented immediately after CLI examples, and the table of authentication methods lists PowerShell alongside CLI and Docker. There is no explicit Linux/macOS bias, but the prominence of PowerShell may create friction for Linux users. The documentation does mention alternative container tools like podman, but only briefly and as an afterthought. There are no Linux-specific examples or explicit mention of Linux/macOS workflows.
Recommendations
- Add explicit Linux/macOS workflow examples, such as using Bash scripts or shell commands.
- Clarify that Azure CLI is cross-platform and PowerShell is optional, not required for Linux/macOS users.
- Expand the section on alternative container tools (podman, nerdctl, etc.) with concrete examples for Linux/macOS environments.
- Consider adding a table or section highlighting authentication from Linux/macOS terminals, including environment variable usage and token management.
- Ensure that Docker and Azure CLI examples are shown first, with PowerShell as an optional alternative.
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 generally uses cross-platform tools (Helm CLI, Azure CLI), but there are subtle Windows biases. The environment variable example uses Windows-style 'set' instead of cross-platform 'export', and the order of Kubernetes cluster creation options lists Azure PowerShell before Azure CLI and portal, which may imply Windows-first. No explicit Linux/macOS examples are given for environment variable setting or shell commands, and no mention is made of shell differences (e.g., PowerShell vs Bash).
Recommendations
- Replace 'set' with 'export' for environment variable examples, or provide both Windows (set) and Linux/macOS (export) commands.
- Clarify that Azure CLI and Helm CLI commands are cross-platform and work on Linux/macOS as well as Windows.
- When listing options for Kubernetes cluster creation, consider listing Azure CLI first (as it is cross-platform) or note parity.
- Add a note or section on shell differences for authentication and scripting, especially for environment variables.
- Ensure all command examples are tested and work on Linux/macOS terminals.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is presented as equally prominent to Azure CLI. There are no explicit Linux/macOS examples or mentions of Linux-specific tools or shell environments. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, and its inclusion as a first-class option may create friction for Linux/macOS users. Additionally, PowerShell examples are sometimes shown immediately after CLI examples, rather than CLI-only or Linux-first.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Explicitly mention that PowerShell examples are primarily for Windows users, and that Azure CLI works natively on Linux/macOS.
- Consider adding brief notes or examples for using Azure CLI in Bash or other Linux shells, especially for steps involving authentication or scripting.
- If possible, reorder sections so Azure CLI examples appear before PowerShell, or add a note about platform suitability.
- Add a short section or FAQ addressing Linux/macOS users and their preferred tooling.
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 viewing usage), but consistently lists PowerShell examples after CLI and references Windows-specific tools (PowerShell) alongside cross-platform tools. There are no Linux/macOS-specific examples or explicit mentions of Linux tools, but the CLI examples are cross-platform. The ordering and inclusion of PowerShell examples may create a slight Windows-first impression, but Linux users can complete all tasks using the CLI.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and preferred for Linux/macOS users.
- Consider adding a brief note indicating that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
- If relevant, include examples for Bash scripting or highlight CLI usage in Linux/macOS terminals.
- Ensure that CLI examples are shown first and clearly labeled as cross-platform.