226
Pages Scanned
54
Pages Flagged
226
Changed Pages
23.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06
Scan Information
Started At: 2026-02-15 00:00:06
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 226
Files Completed: 226
Problematic Pages
54 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 toward Windows/PowerShell usage. All onboarding scripts and command examples are provided only for PowerShell, and prerequisites reference Windows-specific tools like 'winget'. There are no Bash, Linux, or macOS equivalents or instructions, making it difficult for non-Windows users to follow the onboarding process.
Recommendations
- Provide equivalent Bash shell script examples for Linux/macOS users, or clearly state if only PowerShell scripts are supported.
- Replace 'winget' installation instructions with cross-platform alternatives (e.g., 'apt', 'yum', 'brew', or direct download links) for Azure CLI and kubectl.
- Explicitly mention platform support for the onboarding scripts (e.g., if only Windows/PowerShell is supported, state this at the top).
- If possible, provide or link to onboarding scripts compatible with Bash or cross-platform scripting environments.
- Add notes or sections for Linux/macOS users, including any prerequisites or environment setup steps specific to those platforms.
Create Pull Request
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command examples for connecting to the SQL Server instance using PowerShell syntax, specifically for running sqlcmd via kubectl exec. No equivalent Linux/macOS shell examples (e.g., Bash) are provided, and PowerShell is used as the default/only shell for these steps. This may create friction for Linux/macOS users unfamiliar with PowerShell syntax.
Recommendations
- Add Bash shell examples alongside PowerShell for kubectl exec and sqlcmd commands.
- Clarify that the commands can be run from any OS with kubectl and sqlcmd installed, and provide OS-agnostic instructions.
- Ensure that all steps involving shell commands are demonstrated in both Windows (PowerShell) and Linux/macOS (Bash) contexts.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. There are no examples or guidance for running the script on Linux/macOS systems, nor is there mention of Bash, shell, or cross-platform alternatives. The script appears to require PowerShell, which is available on Linux/macOS, but this is not clarified or demonstrated.
Recommendations
- Clarify that PowerShell Core (pwsh) can be used on Linux/macOS and provide example commands for those platforms.
- Add instructions for installing PowerShell on Linux/macOS if not already present.
- Show example usage with 'pwsh' rather than only Windows-style '.\RGCleanScript.ps1', e.g., 'pwsh RGCleanScript.ps1 ...' or './RGCleanScript.ps1 ...' for Unix shells.
- Mention any platform-specific requirements or limitations of the script, if any.
- If the script is truly cross-platform, explicitly state this in the documentation.
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 examples or guidance for Linux/macOS users, such as Bash or cross-platform alternatives, nor mention of how to execute the migration on non-Windows platforms.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core on Linux/macOS.
- Explicitly state platform requirements and, if possible, offer cross-platform migration instructions.
- Include notes or troubleshooting for Linux/macOS users who may need to install PowerShell Core.
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
missing_linux_example
Summary
The documentation page provides CLI examples using PowerShell syntax (with backticks for line continuation and $variable notation), which is specific to Windows environments. There are no equivalent Bash or Linux/macOS shell examples, and the CLI installation/update instructions are shown in Bash only in some sections, but configuration examples are exclusively PowerShell. There is no mention of Linux-specific tools or patterns, nor any explicit guidance for Linux/macOS users. This creates friction for non-Windows users who may not be familiar with PowerShell syntax or variable usage.
Recommendations
- Provide equivalent Bash examples for all CLI commands, especially where PowerShell syntax is used.
- Include notes clarifying that CLI commands work on Linux/macOS and provide sample variable usage for those platforms.
- Avoid using PowerShell-specific line continuation (backticks) and variable notation in generic CLI documentation, or show both styles side-by-side.
- Add a section or callout for Linux/macOS users to ensure parity and clarity.
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 demonstrates a notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, and references to file paths in JSON templates use Windows-style paths (e.g., C:\, E:\). There are no Bash or Linux shell equivalents for any of the automation steps, and the onboarding scripts are referenced as PowerShell (.ps1) files. The documentation assumes a Windows environment for scripting and file management, which creates friction for Linux/macOS users who may need to adapt commands and paths.
Recommendations
- Provide Bash/zsh shell equivalents for all PowerShell script examples, especially for az CLI commands.
- Use cross-platform file path examples (e.g., /home/user/config.yaml) or clarify how to adapt paths for Linux/macOS.
- Mention that onboarding scripts are available in PowerShell and provide guidance or alternative scripts for Linux/macOS users (e.g., Python, Bash).
- Add notes or sections explicitly addressing Linux/macOS environments, including any prerequisites or limitations.
- Ensure JSON templates reference generic or platform-neutral file paths.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is focused on configuring AKS Edge Essentials for Linux, but uses Windows-specific PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to perform Linux node configuration tasks. There are no native Linux shell examples for checking or setting sysctl values, and the text editor recommendation (Notepad) is Windows-centric. This creates friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
- Provide native Linux shell commands for checking and setting sysctl values (e.g., 'cat /proc/sys/fs/inotify/max_user_instances' and 'echo ... | sudo tee ...').
- Recommend Linux text editors (e.g., nano, vim) alongside Notepad for editing configuration files.
- Clarify whether PowerShell is required on Linux, or provide alternative instructions for Linux environments.
- Ensure all steps can be completed using standard Linux tools without reliance on Windows/PowerShell.
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 PowerShell, SQL Server Profiler) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure PowerShell is marked as unsupported, SQL Server PowerShell is listed as supported. There are no Linux-specific tools or examples, and Linux-native management approaches (such as sqlcmd, mssql-cli, or Azure Data Studio) are not mentioned. However, the core features are platform-agnostic, and the page does not provide step-by-step examples favoring Windows.
Recommendations
- Add Linux-native tools such as Azure Data Studio, sqlcmd, and mssql-cli to the Tools section.
- Clarify that SQL Server PowerShell is available cross-platform via PowerShell Core, or provide Linux/macOS alternatives.
- Include references or links to documentation for managing SQL Managed Instance enabled by Azure Arc from Linux/macOS environments.
- Balance tool recommendations to highlight cross-platform options alongside Windows tools.
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 default to Windows tools, paths, and workflows (e.g., using C:\ paths, referencing Notepad/OneNote, and SQL Server Management Studio), with little or no mention of Linux/macOS equivalents. Linux users are left to infer how to adapt the instructions, especially for backup file creation and local file path usage.
Recommendations
- Include Linux/macOS equivalents for file paths (e.g., /home/user/backup/test.bak) alongside Windows examples.
- Mention cross-platform editors (e.g., VS Code, nano, vim) instead of or in addition to Notepad/OneNote for copying SAS tokens.
- Explicitly state that SQL Server Management Studio (SSMS) is Windows-only and suggest Azure Data Studio or sqlcmd as cross-platform alternatives.
- Provide example backup commands for Linux-based SQL Server installations (e.g., using /var/opt/mssql/backup/ as the backup path).
- When referencing tools like Azure Storage Explorer or Visual Studio Code, clarify their cross-platform availability.
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 is a mild Windows bias: Windows examples and instructions are often presented first, Windows-specific tools (PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail, and a cleanup script for stale resources is only provided in PowerShell. Linux instructions are present and clear, but advanced automation examples (like scripting for stale resource cleanup) are Windows/PowerShell-only.
Recommendations
- Present Linux and Windows instructions in parallel or alternate order to avoid 'windows_first' bias.
- Provide equivalent Linux automation scripts (e.g., Bash or Python) for tasks like stale resource cleanup.
- Expand Linux-specific guidance for update automation (e.g., using cron, unattended-upgrades, or package manager hooks).
- Where Windows tools are mentioned (e.g., Group Policy, WSUS), briefly note Linux equivalents or alternatives (e.g., configuration management tools like Ansible, Puppet, or native package managers).
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 signs of Windows bias: PowerShell is referenced for troubleshooting HTTP/2 errors, Windows paths are shown in error messages, and Windows-specific tools (RDP, remote PowerShell) are discussed. Linux-specific troubleshooting commands and examples are largely missing or appear after Windows ones. The GLIBC error is the only explicit Linux issue covered, but Linux CLI troubleshooting is not as prominent as Windows/PowerShell.
Recommendations
- Add Linux/macOS equivalents for PowerShell troubleshooting steps, such as using curl with HTTP/2 or OpenSSL for certificate validation.
- Provide Linux/macOS-specific examples for CLI commands, including file paths and permission troubleshooting (e.g., SSH folder access).
- Mention Linux/macOS methods for network diagnostics (e.g., using 'ping', 'nslookup', 'dig', 'curl', 'traceroute') alongside Windows tools.
- Ensure error messages and troubleshooting steps reference both Windows and Linux environments equally.
- Clarify when a step is Windows-only and provide alternative instructions for Linux/macOS users.
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 provides only a Windows/PowerShell-based recovery script and workflow, with no mention of Linux/macOS equivalents or alternative methods. All instructions and downloadable scripts are Windows/PowerShell-centric, and there is no guidance for users operating from Linux or macOS environments.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools such as Azure CLI.
- Explicitly state if recovery is only supported from Windows, and if so, clarify the technical limitations.
- If possible, offer a cross-platform script (e.g., in Python or Bash) or containerized solution.
- Add a note in the prerequisites section about supported operating systems for the recovery process.
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 instructions are exclusively shown using Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The file path examples use Windows-style paths (e.g., D:\Azure\Templates), further reinforcing Windows-first patterns.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
- Provide Bash script samples for Linux/macOS users where appropriate.
- Include Linux-style file path examples (e.g., /home/user/Azure/Templates) in sample commands.
- Clarify that both PowerShell and CLI can be used on any platform, and link to cross-platform deployment documentation.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page exhibits notable Windows bias, especially in the 'Auto Arc-enablement script' section, which exclusively provides PowerShell-based automation and references Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux equivalents, and Linux-specific automation (e.g., Bash, systemd timers, cron) is missing. While Linux is acknowledged in prerequisites and out-of-band methods, the primary scripted automation and scheduling guidance is Windows-centric.
Recommendations
- Provide Bash or shell script equivalents for the automation script, or clarify if the helper script is cross-platform.
- Include instructions for running the automation at scale on Linux/macOS, such as using cron or systemd timers instead of Windows Task Scheduler.
- Add examples for Linux users, including how to set execution permissions (chmod +x), and how to run the script from a Bash terminal.
- Clarify whether the helper script is PowerShell-only or if a cross-platform version exists.
- Ensure parity in automation and scheduling guidance for both Windows and Linux environments.
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
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Windows and Linux instructions for uninstalling the Arc agent, but the deboarding script section is Windows/PowerShell-only. The script is only shown as a PowerShell script, and there are no instructions or mention of running the script from Linux/macOS, nor is there a Bash or cross-platform alternative. Additionally, Windows/PowerShell instructions are presented first and in more detail.
Recommendations
- If the deboarding script is PowerShell-only and cannot be run on Linux/macOS, explicitly state this limitation and provide manual removal steps for Linux/macOS users.
- If possible, provide a Bash or cross-platform version of the deboarding script, or document how to run the PowerShell script using PowerShell Core (pwsh) on Linux/macOS.
- Present Windows and Linux/macOS instructions in parallel sections or clarify platform requirements at the start of each section.
- Add a note about script compatibility (e.g., whether it works with PowerShell Core on non-Windows platforms).
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page for disaster recovery operations of the Azure Arc resource bridge VM provides only PowerShell examples and references, with no mention of Bash, Linux shell, or cross-platform alternatives. The onboarding script and its usage are shown exclusively in PowerShell syntax, and there is no guidance for Linux/macOS users on how to perform equivalent operations. The script editing and execution steps assume a Windows environment, creating friction for non-Windows users.
Recommendations
- Provide Bash or shell script examples alongside PowerShell for onboarding and recovery operations.
- Clarify whether the onboarding script is cross-platform or Windows-only; if cross-platform, show Linux/macOS usage.
- Mention prerequisites for Linux/macOS users, such as PowerShell Core installation or alternative tools.
- Add explicit instructions for editing and running the onboarding script on Linux/macOS, including command syntax and environment requirements.
- Consider referencing Azure CLI commands where possible, as Azure CLI is cross-platform.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell examples. There are no Linux/macOS-specific instructions or script alternatives, and PowerShell is presented as the default for CLI usage, 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 in Bash and PowerShell.
- Offer Bash or shell script equivalents for bulk_deployment.ps1 and workflow-delete.ps1, or note if the scripts are cross-platform.
- Explicitly state platform requirements for scripts and commands, and link to guidance for Linux/macOS users if PowerShell is required.
- Add a note clarifying that Azure CLI commands can be run in any shell environment, not just PowerShell.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses Windows-specific tooling (winget), with no Linux/macOS alternative. The file extraction example in the Bash tab uses Expand-Archive, which is a PowerShell/Windows command, not a native Bash/Linux tool. There are no Linux/macOS-specific instructions for these steps, and Windows paths are used throughout. Bash and PowerShell tabs are provided, but Bash examples often use Windows commands, creating confusion for Linux/macOS users.
Recommendations
- Provide Linux/macOS-specific instructions for installing kubectl (e.g., using curl or package managers like apt, yum, or brew).
- Replace Expand-Archive in Bash examples with native Linux/macOS commands (e.g., unzip or tar).
- Use cross-platform file path examples (e.g., /home/user/path or ~/workspace) in Bash sections.
- Ensure Bash examples use commands available on Linux/macOS, not Windows-only tools.
- Add explicit notes or tabs for macOS if there are platform-specific differences.
- Review all Bash examples to confirm they are valid for Linux/macOS environments.
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 use PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). There are no explicit Linux/bash equivalents for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, which provides both Bash and PowerShell tabs. This creates friction for Linux/macOS users, especially in sections where only PowerShell is shown and Windows-specific scripting patterns (e.g., ConvertTo-Json, Out-File, [Convert]::ToBase64String) are used.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell examples, especially for Azure CLI, Docker, and kubectl commands.
- Avoid using Windows-specific scripting constructs (e.g., ConvertTo-Json, Out-File) without showing cross-platform alternatives (e.g., jq, echo, cat, base64).
- Where possible, use platform-neutral Azure CLI syntax and highlight cross-platform compatibility.
- Clearly indicate when a command is Windows-only, and provide guidance for Linux/macOS users.
- Review and update sections to ensure Linux/macOS users can follow troubleshooting steps without friction.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and PowerShell is referenced in the 'Related content' section before Azure CLI. There is a slight preference for Windows tools and ordering, but Linux parity is maintained throughout with equivalent Bash examples and links.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- In the 'Related content' section, list Azure CLI and Bash examples before or alongside PowerShell to balance tool visibility.
- Explicitly state that both Windows and Linux are fully supported at the start of the article to reassure cross-platform users.
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 helper script, but Windows/PowerShell instructions are consistently presented first and with more detailed notes (e.g., warnings about PowerShell ISE). The retry command section also shows Windows before Linux. There is a slight emphasis on Windows tools and patterns, but Linux parity is maintained throughout.
Recommendations
- Alternate the order of Windows and Linux instructions to avoid always showing Windows first.
- Provide equally detailed notes for Linux users (e.g., potential issues with Bash shells or permissions).
- Explicitly mention macOS support if applicable, or clarify if only Windows and Linux are supported.
- Ensure screenshots and UI references are OS-neutral or include Linux/macOS equivalents if relevant.
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 command and workflow step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. There are no Windows-only tools, patterns, or commands used, and all instructions are cross-platform via Azure CLI and kubectl.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in sections, or explicitly state that both are equally supported.
- Add a short note at the top clarifying that Bash is for Linux/macOS and PowerShell is for Windows, to help users quickly identify their relevant section.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS-specific guidance where relevant.
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
powershell_heavy
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere. While it covers both Windows and Linux enhancements, Windows-specific features (such as customizing Windows VM guest settings and Windows Server Management) are mentioned before Linux equivalents. Windows tools like Azure PowerShell and System Center Configuration Manager are highlighted, and PowerShell is listed alongside Azure CLI and REST API, but Linux-focused tooling (e.g., Bash, shell scripts) is not explicitly referenced. However, Linux support is mentioned (Arc agent installation via SSH), and cross-platform SDKs and tools are covered.
Recommendations
- Ensure Linux examples and tooling (e.g., Bash scripts, Linux-native automation tools) are mentioned alongside Windows tools.
- When listing management tools, alternate the order or explicitly state cross-platform compatibility.
- Add links or references to Linux-specific guides or examples where possible.
- Clarify when features are Windows-only to avoid confusion for Linux users.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently lists Bash examples before PowerShell. There are no Windows-only tools or patterns used, and Linux parity is maintained throughout. No Linux/macOS examples are missing, and all commands are cross-platform via the Azure CLI and Helm.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs or explicitly stating that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows users, to help new users identify their platform.
- Ensure that any future examples using platform-specific tools (e.g., Windows CMD or Linux utilities) are accompanied by their cross-platform equivalents.
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 (a Windows-centric tool) alongside CLI, but does not provide explicit Linux/bash examples or clarify parity. PowerShell is mentioned before Linux shell equivalents, which may subtly prioritize Windows users.
Recommendations
- Clarify that Azure Copilot can generate both PowerShell and Bash/CLI scripts, and provide examples for each.
- Explicitly mention Linux/macOS compatibility where relevant, especially for script generation.
- Consider listing Bash/CLI examples before or alongside PowerShell to avoid Windows-first ordering.
- Add a note about script types supported and any limitations for Linux/macOS users.
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 it does mention sqlcmd (which is cross-platform), SSMS is listed first and no Linux-native graphical tools (such as Azure Data Studio or DBeaver) are mentioned. The examples for connecting via sqlcmd are generic and do include Linux, but the overall pattern is Windows-first in tool recommendations and examples.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit examples for connecting from Linux/macOS using graphical tools, not just sqlcmd.
- Reorder tool recommendations so that cross-platform options are listed before or alongside Windows-only tools.
- Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation instructions for client tools across platforms, but there are subtle Windows biases. Windows links are often listed first, and specific instructions for Windows (e.g., using cmd.exe instead of PowerShell for curl) are highlighted, while Linux installation instructions are less explicit or only briefly mentioned (e.g., 'Linux: install curl package'). There is a PowerShell-specific note about curl, but no equivalent Linux/macOS shell guidance. The Linux installation process for curl is not linked, and Linux/macOS users may need to search for details.
Recommendations
- List Linux/macOS installation instructions and links before or alongside Windows, not after.
- Provide explicit installation links for Linux/macOS tools (e.g., link to curl installation instructions for Linux/macOS).
- Add shell-specific notes for Linux/macOS users, similar to the PowerShell note for Windows.
- Ensure all tool installation instructions are equally detailed for all platforms.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding, but the Windows section is more detailed, mentioning certutil and findstr, while the Linux example is brief. The Linux example is presented first, but the Windows section includes additional manual steps and commands. No PowerShell-specific examples are given, and the rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl). However, the Windows encoding example lacks parity with Linux: Linux users are not told how to remove headers, and Windows users are given more guidance.
Recommendations
- Add instructions for Linux users to remove certificate headers (e.g., using grep or sed) to match the Windows guidance.
- Clarify that base64 encoding and header removal steps are needed on both platforms.
- Consider providing macOS-specific notes if there are differences.
- Ensure all steps are equally detailed for both Windows and Linux users.
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
Summary
The documentation page provides Azure CLI and kubectl examples throughout, which are cross-platform. However, there are subtle signs of Windows bias: Windows and Mac installation instructions for Azure kubelogin are mentioned first, with Linux instructions following. The page also references the Azure portal for role assignment and Conditional Access configuration, which is equally accessible on all platforms but often associated with Windows environments. There are no PowerShell-specific commands, but the ordering of instructions and references to Windows/Mac before Linux indicate a minor Windows-first bias.
Recommendations
- Reorder installation instructions for Azure kubelogin to mention Linux first or equally alongside Windows/Mac.
- Explicitly state that all Azure CLI and kubectl commands are cross-platform and provide any necessary Linux/macOS-specific notes where relevant.
- Where possible, provide parity in screenshots or UI references for Linux/macOS users (for example, browser access or Azure portal usage).
- Ensure that any references to local file paths or SSH instructions clarify platform differences (e.g., path separators, default shell environments).
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 consistently refers to Azure CLI installation, but in the 'Management machine requirements' section, the Azure CLI installation link defaults to the Windows tab. There are no explicit Linux/macOS examples or links, and no mention of Linux-specific installation or requirements for the management machine, despite Azure CLI being cross-platform. However, the overall guidance is generic and does not reference Windows-only tools or patterns.
Recommendations
- Add explicit instructions or links for installing Azure CLI on Linux and macOS, not just Windows.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide parity in example commands and links.
- Where referencing Azure CLI installation, use a neutral link or include tabs for all supported OSes.
- If there are OS-specific requirements (e.g., 32-bit/64-bit), clarify whether these apply to Linux/macOS as well.
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 generally presents Windows download links and version numbers before Linux equivalents and occasionally references Windows-specific tools (e.g., PowerShell, msiexec) and installer behaviors. However, Linux support is consistently present, and Linux-specific improvements and bug fixes are also documented. There are no critical sections that are Windows-only, and Linux users can access all relevant information.
Recommendations
- Present Windows and Linux download links and version numbers in parallel or randomize order to avoid implicit prioritization.
- When referencing Windows-specific installation methods (e.g., msiexec, PowerShell), provide equivalent Linux installation instructions or cross-link to Linux install documentation.
- Where possible, clarify when a fix or feature is platform-specific to avoid confusion.
- Consider adding a short section or table at the top summarizing parity and platform-specific 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 page lists both Windows and Linux-related endpoints and requirements, but there is a mild Windows bias. Windows-specific services (e.g., Windows NTP, sts.windows.net, login.windows.net, servicebus.windows.net) are mentioned, and Windows terminology appears in some notes. However, Linux endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io) are also included. No platform-specific command examples are given, and the requirements are generally platform-agnostic. The order of some Windows-related endpoints precedes Linux equivalents, and Windows NTP is called out explicitly, but Linux NTP is not.
Recommendations
- Explicitly mention Linux NTP server options (e.g., pool.ntp.org) alongside Windows NTP.
- Clarify that the management machine and appliance VM can be either Windows or Linux, and provide any platform-specific notes if needed.
- Ensure parity in endpoint explanations (e.g., for log collection, clarify if Windows and Linux logs are handled differently).
- Where Windows-specific endpoints are listed, note Linux alternatives if applicable.
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 connecting servers to Azure Arc using the azcmagent CLI. While the core command syntax and most examples are platform-neutral, the authentication section presents 'Interactive browser login (Windows only)' as the first option and describes Windows certificate store usage in detail, including specific certificate store locations and thumbprint-based authentication. Additionally, the access token example references the Windows PowerShell cmdlet Get-AzAccessToken without mentioning Linux/macOS alternatives. These patterns indicate a mild Windows bias, though Linux authentication methods are described and supported.
Recommendations
- Reorder authentication options so platform-neutral or Linux-default methods (e.g., device code login) are presented first.
- When referencing access token acquisition, include cross-platform alternatives (e.g., Azure CLI az account get-access-token) alongside PowerShell.
- Clarify certificate authentication for Linux/macOS, noting file-based certificate usage and omitting Windows certificate store details unless relevant.
- Add explicit Linux/macOS command examples where possible, especially for authentication and certificate handling.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Windows and Linux information for Azure Arc-enabled servers, but there are minor signs of Windows bias. Windows installation package URLs are listed first in tables, and Windows Admin Center is mentioned as a management tool without Linux alternatives. Windows-specific configuration issues are referenced before Linux equivalents. However, Linux is explicitly supported and referenced throughout, and critical information for Linux users is present.
Recommendations
- In tables listing installation package URLs, alternate the order or list Linux and Windows together to avoid Windows-first bias.
- When mentioning Windows Admin Center, clarify its Windows-specific nature and, if possible, reference Linux management alternatives (such as Azure CLI, SSH, or other tools).
- Ensure troubleshooting and configuration sections provide Linux-specific guidance and links alongside Windows references.
- Where Windows-specific tools or settings are discussed (e.g., TLS registry settings), provide equivalent Linux/OpenSSL guidance or links.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, with separate tables for each OS and clear links to Linux-specific resources. However, Windows extensions are listed first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and Linux examples are present throughout. No critical Linux omissions or Windows-only tools are evident.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to reinforce equal importance.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) support both Windows and Linux extensions where applicable.
- Add a brief introductory note confirming Linux parity and support, to reassure non-Windows users.
- Ensure that linked deployment guides (e.g., CLI, PowerShell) include both Windows and Linux examples.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations, but there is evidence of Windows bias. Windows examples and log file paths are presented first, and PowerShell-specific commands and references (such as using '&' and environment variables) are prominent. Windows log file locations and troubleshooting steps are often mentioned before Linux equivalents. There are also references to Windows-specific tools (e.g., PowerShell, '%TEMP%', '%ProgramData%') without always providing the Linux equivalent in the same context.
Recommendations
- Present Windows and Linux examples side-by-side, or alternate which platform is shown first in each section.
- Ensure all troubleshooting steps referencing Windows-specific tools or paths (e.g., '%TEMP%', '%ProgramData%') are immediately followed by Linux equivalents (e.g., '/tmp', '/var/opt/azcmagent').
- Where PowerShell syntax is used, provide equivalent Bash commands for Linux users.
- Clarify when a solution or log location is platform-specific, and provide parity for Linux wherever possible.
- Consider using generic command syntax (e.g., 'azcmagent ...') before showing platform-specific examples.
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 Azure CLI, PowerShell, and REST API as supported experiences, but lists PowerShell examples and references before Linux/CLI equivalents. The 'Next steps' section places PowerShell before REST API, and the custom metadata includes 'devx-track-azurepowershell' but not a Linux-specific tag. However, the page explicitly states support for both Windows and Linux, and provides links to Azure CLI documentation, which is cross-platform.
Recommendations
- Ensure that Linux and Windows examples are given equal prominence in all sections.
- List Azure CLI (Linux-friendly) examples before or alongside PowerShell examples in 'Next steps' and throughout the documentation.
- Add explicit Linux-specific tags or metadata if possible.
- Clarify that Azure CLI is fully supported and provide sample Linux shell commands where appropriate.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there is a mild Windows bias: Windows examples and links are sometimes presented first (e.g., in Azure Automation and Update Manager sections), and PowerShell is highlighted as a primary automation tool, with less emphasis on Bash or Linux-native scripting. Some links and examples reference Windows-specific tabs or features before Linux equivalents.
Recommendations
- Ensure Linux examples and links are presented alongside Windows ones, not just as secondary options.
- Highlight Bash and Linux-native scripting tools (e.g., Azure CLI usage on Linux/macOS) equally with PowerShell.
- Where automation is discussed, mention both PowerShell and Bash/Python as first-class options.
- Review linked pages to ensure Linux instructions are easily discoverable and not hidden behind Windows-first tabs.
- Add explicit statements or examples showing Linux VM onboarding and management parity.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and in more detail, including download links. Linux requirements are mentioned briefly and lack equivalent detail or links. The Windows download links are provided, but Linux equivalents (such as wget or systemd documentation) are not. No Linux-specific example scripts or troubleshooting guidance are given, and Windows tools are mentioned before Linux tools.
Recommendations
- Provide download links or documentation references for Linux tools (e.g., wget, systemd).
- List Linux requirements before or alongside Windows requirements, rather than after.
- Add example installation scripts for both Windows (PowerShell) and Linux (bash), or clarify that both are supported with parity.
- Include troubleshooting guidance for Linux environments, similar to any provided for Windows.
- Ensure parity in detail and clarity for both Windows and Linux prerequisites.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, which is a minor form of 'windows_first' bias. No Windows-specific tools or patterns are used, and Linux examples are present throughout.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
- Explicitly state that Bash examples are suitable for Linux/macOS terminals and PowerShell for Windows, to clarify cross-platform applicability.
- Add a brief note confirming that all commands are supported equally on Linux, macOS, and Windows when using Azure CLI.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first, followed by PowerShell. No Windows-specific tools or patterns are mentioned exclusively, and all commands use the Azure CLI, which is cross-platform. There are no missing Linux examples, and no Windows tools are referenced. The PowerShell examples are provided for parity, but Bash is prioritized in tab order.
Recommendations
- Consider clarifying that both Bash and PowerShell examples are fully supported on Windows, Linux, and macOS, as Azure CLI works across platforms.
- Explicitly mention that Bash examples can be used on Linux/macOS, and PowerShell on Windows, but both shells are available on all platforms.
- If possible, provide a brief note about how to install Azure CLI on Linux/macOS for completeness.
- Ensure that tab order does not imply platform preference, or rotate tab order periodically.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented immediately after Bash, which could be interpreted as a minor 'windows_first' bias. No Windows-specific tools, patterns, or exclusive instructions are present, and all steps are equally applicable to Linux/macOS environments via Bash and Azure CLI.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that all Azure CLI commands are cross-platform and Bash examples are intended for Linux/macOS users.
- Ensure screenshots and portal instructions do not reference Windows-specific UI elements unless necessary.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
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 shown after Bash, and some PowerShell-specific commands (such as base64 encoding) are included. There are minor instances where Windows-specific file encoding (UTF-8 with BOM) is mentioned, but Linux/Mac equivalents are also addressed. No critical steps are Windows-only, and Linux users can complete all tasks using the Bash instructions.
Recommendations
- Continue providing both Bash and PowerShell examples for all commands.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows at the start of the page.
- Where file encoding is discussed, clarify how to check/change encoding on Linux/macOS (e.g., using 'file' or 'iconv').
- Ensure that any command or tool referenced (such as 'armclient' in PowerShell) has a Linux/macOS equivalent or a note if it is Windows-only.
- If possible, provide a combined table or toggle for Bash/PowerShell examples to make parity clearer.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, ensuring parity between Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias. There are no Windows-exclusive tools, patterns, or terminology, and Linux examples are not missing.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell examples in future documentation, or explicitly state that Bash is shown first for consistency, not preference.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance alongside Windows instructions.
Azure Arc
Create a Basic Solution with Common Configurations with Workload Orchestration
...ation/quickstart-solution-with-common-configuration.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. There is a slight bias in the sense that PowerShell is given equal prominence, even though Bash is the more universal shell for Linux/macOS users. No Windows-only tools or patterns are used, and all commands are based on the Azure CLI, which is cross-platform. There are no missing Linux examples, and no Windows-specific tools are mentioned.
Recommendations
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right tab.
- Optionally, add a short note in the prerequisites section indicating that all CLI commands work on Linux, macOS, and Windows, and that users should select the appropriate shell tab.
- Ensure that any environment setup instructions in linked prerequisite docs also provide Linux/macOS parity.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and receives slightly more prominence. There are no Windows-only tools or patterns, and both Windows and Linux users can use the Azure portal and Azure CLI. However, the ordering and phrasing may subtly favor Windows users by listing PowerShell before CLI and referring to 'text document' (which may imply Notepad/Windows).
Recommendations
- Alternate the order of PowerShell and CLI mentions, or list CLI first to better reflect cross-platform parity.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
- Use neutral language such as 'text editor' instead of 'text document' to avoid implying Windows tools.
- Consider adding a brief note that both PowerShell and CLI are available on all major platforms, or link to installation guides for each.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry. However, the PowerShell example is presented immediately after the CLI example, and PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash, shell scripting) or explicit mention of Linux/macOS workflows outside Azure CLI. The CLI example is cross-platform, but the inclusion of PowerShell as a primary alternative may subtly reinforce Windows-centric patterns.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding a Bash shell example for importing images using Docker CLI (if relevant), or explicitly state that Azure CLI commands work on Linux/macOS.
- Mention that Azure PowerShell is available on Linux/macOS, but is most commonly used on Windows.
- Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm). No critical sections are Windows-only.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is good.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- If possible, add a note at the top indicating that all commands are cross-platform unless otherwise specified.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are present throughout, and in some sections (such as variable naming and file paths), Windows conventions (e.g., backslashes in file paths) are used. Bash examples are always shown first, but the PowerShell tab is equally detailed. There is no evidence of Windows-only tools or missing Linux examples; all commands use the Azure CLI, which is cross-platform.
Recommendations
- Ensure that file path examples in PowerShell use forward slashes or note that backslashes are Windows-specific.
- Clarify that PowerShell examples are for Windows users and Bash for Linux/macOS, if not already stated.
- Consider adding a note that all Azure CLI commands are cross-platform and can be run in Bash or PowerShell on any OS.
- If possible, provide additional context for macOS users regarding any potential differences in shell behavior.
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, but the PowerShell section is given equal prominence to the CLI section, and there is no explicit mention of Linux/macOS compatibility for PowerShell commands. The Azure CLI is cross-platform and shown first, but the PowerShell section could be interpreted as Windows-centric, especially since no Bash or shell-specific guidance is given. All tools referenced (Azure CLI, Azure PowerShell, REST API, Portal) are cross-platform, but the inclusion of PowerShell without clarifying its cross-platform availability may create a mild Windows bias.
Recommendations
- Clarify that Azure PowerShell is available on Linux and macOS, not just Windows.
- Explicitly state that Azure CLI commands work on all platforms (Windows, Linux, macOS).
- Consider adding a short Bash shell script example for deploying the dashboard template using Azure CLI, to reinforce Linux parity.
- If possible, mention that all deployment methods (Portal, CLI, PowerShell, REST) are supported on all major OSes.
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 both Azure CLI and Azure PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is featured equally alongside CLI. In several sections, PowerShell examples are given immediately after CLI, and references to PowerShell cmdlets are present throughout. While the CLI is cross-platform, PowerShell is primarily used on Windows, though it is available on Linux/macOS. There is minor bias in the 'Next steps' section, which lists PowerShell after CLI, and in the frequent mention of PowerShell as a primary authentication method. However, Docker and Azure CLI are featured and are cross-platform. The documentation does mention alternative container tools (like podman) and provides guidance for non-Docker environments, which helps Linux parity.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Add explicit Linux/macOS notes or examples where PowerShell is mentioned, indicating that Azure CLI is the recommended tool for Linux/macOS users.
- Consider providing bash shell script examples alongside PowerShell, especially for automation scenarios.
- In sections listing authentication methods, consider listing Azure CLI first, as it is the most universally supported tool.
- Where Docker is referenced, note that podman and other container tools are supported, and provide explicit Linux/macOS command examples where appropriate.
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 examples for Helm and Azure CLI, which are cross-platform tools. However, in the 'Set the following environment variables' section, the command uses 'set' (a Windows CMD syntax) without providing the equivalent Linux/macOS example ('export'). Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, then PowerShell, then Portal, which is a minor 'windows_first' bias. All other commands use cross-platform syntax or Bash-style variables, but the initial environment variable example may confuse Linux/macOS users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') syntax for environment variable examples.
- Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
- When listing options for cluster creation, consider mentioning Azure CLI and Portal before PowerShell, or note PowerShell is Windows-specific.
- Review all command snippets to ensure they use Bash-style syntax or provide alternatives for Windows CMD/PowerShell where relevant.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently lists Azure PowerShell examples after Azure CLI. Azure PowerShell is a Windows-centric tool, but Azure CLI is cross-platform. No Windows-only tools or patterns are prioritized, and all examples are available for both platforms. There are no missing Linux/macOS examples, and no exclusive mention of Windows tools. The only minor bias is the ordering of examples, with Azure CLI (cross-platform) shown first, followed by Azure PowerShell (Windows-centric).
Recommendations
- Maintain the current ordering, as Azure CLI is cross-platform and shown first.
- Consider explicitly stating that Azure CLI commands work on Linux/macOS/Windows, while Azure PowerShell is primarily for Windows users.
- Add a brief note at the top clarifying that all Azure CLI examples are suitable for Linux/macOS/Windows, and PowerShell examples are for Windows or PowerShell Core users.
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 consistently lists Azure PowerShell after Azure CLI and includes explicit PowerShell code blocks. There are no Linux/macOS-specific examples or mentions of Bash or shell scripting, and the PowerShell example is given equal prominence to the CLI example. However, Azure CLI is cross-platform and is listed first, mitigating most bias. No Windows-only tools or patterns are mentioned, and the documentation does not exclude Linux/macOS users from completing any tasks.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit Bash/shell script examples where appropriate, especially for common operations.
- Mention that Azure PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users to use Azure CLI.
- Consider reordering examples so that CLI (cross-platform) is always shown first, and PowerShell is clearly marked as Windows-specific.