233
Pages Scanned
54
Pages Flagged
233
Changed Pages
23.2%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06
Scan Information
Started At: 2026-02-18 00:00:06
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 233
Files Completed: 233
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 environments. All onboarding scripts and examples are provided only as PowerShell (.ps1) scripts, and users are instructed to use PowerShell terminals. Prerequisites reference Windows-specific tools like 'winget' for installing dependencies. There are no Bash/shell script equivalents, nor are there instructions or examples for Linux/macOS users. This creates significant friction for non-Windows users attempting to follow the onboarding process.
Recommendations
- Provide equivalent Bash or shell scripts for Linux/macOS users, or document manual steps for these platforms.
- Include Linux/macOS installation instructions for dependencies (e.g., using apt, yum, or Homebrew instead of winget).
- Explicitly state platform requirements and, if only Windows is supported, clarify this early in the documentation.
- If possible, refactor onboarding scripts to be cross-platform (e.g., using Python or Azure CLI scripts instead of PowerShell-only).
- Add notes or troubleshooting sections for common issues faced by Linux/macOS users.
Create Pull Request
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 recovery instructions exclusively for Windows machines, using a PowerShell script and Windows-specific tooling. No Linux/macOS examples, scripts, or guidance are provided, and the recovery workflow is described only in the context of Windows.
Recommendations
- Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts.
- Clarify whether the recovery process can be performed from non-Windows platforms, and if not, explain the limitation.
- If the PowerShell script is cross-platform (PowerShell Core), indicate compatibility and provide usage examples for Linux/macOS.
- Offer guidance on prerequisites and connectivity checks for Linux/macOS environments.
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 and instructs users to run it in PowerShell, with no mention of Bash, Linux, or cross-platform alternatives. This creates friction for Linux/macOS users, as PowerShell is not natively available and the script may not run without additional setup.
Recommendations
- Provide a Bash or cross-platform script for migration, or clarify if PowerShell Core (pwsh) is supported on Linux/macOS.
- Explicitly mention how Linux/macOS users can run the migration (e.g., using PowerShell Core, prerequisites, or alternative steps).
- Add examples or instructions for Linux/macOS environments, including any required dependencies.
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 introduces Windows-centric tools and patterns (Invoke-AksEdgeNodeCommand) for Linux configuration steps. It lacks direct Linux-native command examples (e.g., using SSH or running sysctl locally), and relies on PowerShell/Windows tooling to manage Linux nodes, which may not be available or familiar to Linux/macOS users.
Recommendations
- Provide native Linux command-line examples for sysctl configuration, such as SSH-ing into the node and running 'sysctl' and editing '/etc/sysctl.conf' directly.
- Clarify whether Invoke-AksEdgeNodeCommand is required or if standard Linux administration methods can be used.
- Add guidance for Linux/macOS users who may not have access to Windows tools or PowerShell.
- Ensure all steps can be completed using Linux-native tools and document those options explicitly.
Medium 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 and some instructions (e.g., for curl and kubectl) reference Windows-specific behaviors and PowerShell. Linux installation instructions are less explicit, sometimes only mentioning 'install curl package' without a link or example. There is also a note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance.
Recommendations
- List Linux and macOS installation links before or alongside Windows links to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions or links for all tools, not just 'install curl package'.
- Add Linux/macOS-specific notes where Windows-specific behaviors are mentioned (e.g., clarify curl usage differences on Linux/macOS).
- Ensure parity in guidance for verifying tool versions and installation steps across all platforms.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are included, Windows tools are more prominent and listed first in several places. There are no Linux-specific examples or tools mentioned, and PowerShell is referenced as a scripting option without mention of Bash or cross-platform alternatives.
Recommendations
- Add examples or mention of Linux-compatible tools such as Azure Data Studio, Bash scripting, or cross-platform SQL utilities.
- Clarify that PowerShell scripting support is available on Linux via PowerShell Core, or provide Bash/CLI alternatives for scripting tasks.
- Balance tool lists by including cross-platform or Linux-native tools alongside Windows tools, and avoid listing Windows tools first unless they are the only option.
- Where possible, provide links or guidance for Linux/macOS users to achieve similar manageability and scripting tasks.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as using Windows file paths (e.g., C:\Backupfiles\test.bak) and referencing Windows tools like SQL Server Management Studio (SSMS) and Azure Storage Explorer. Linux/macOS equivalents or alternative commands are not provided, and Windows paths are shown first or exclusively in backup/restore examples. This creates friction for Linux/macOS users who may need to adapt instructions for their environment.
Recommendations
- Include Linux/macOS file path examples (e.g., /home/user/Backupfiles/test.bak) alongside Windows paths in backup/restore commands.
- Mention and provide instructions for Linux-compatible tools (e.g., Azure CLI, azcopy, or cross-platform alternatives to Azure Storage Explorer and SSMS).
- Add notes or sections clarifying how to perform each step on Linux/macOS, especially for connecting to SQL Server and handling backup files.
- When showing commands (e.g., kubectl cp), provide both Windows and Linux/macOS source file path examples.
- Explicitly state that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links for Linux/macOS.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page for Azure Arc resource bridge system requirements references Azure CLI as the primary management tool and provides links to Windows-specific Azure CLI installation instructions. It does not mention Linux or macOS management machine requirements, nor does it provide parity for CLI installation or usage examples on those platforms. The examples and instructions are Windows-centric, with no explicit guidance for Linux/macOS users.
Recommendations
- Add explicit guidance for Linux and macOS users, including links to Azure CLI installation instructions for those platforms.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide minimum requirements for each.
- Provide example CLI commands and file paths for Linux/macOS environments alongside Windows examples.
- Ensure that references to Azure CLI are not limited to Windows-specific tabs or links.
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 guidance for both Windows and Linux users, with clear sections and examples for each platform. However, there is a mild Windows bias: Windows instructions and tools (such as PowerShell, Group Policy, WSUS, and Microsoft Update) are often presented first, and some advanced automation examples (like the cleanup script) are only provided in PowerShell. Windows-specific tools and patterns are described in greater detail, while Linux instructions are generally limited to package manager commands and lack comparable scripting or automation examples.
Recommendations
- Provide equivalent automation scripts for Linux users (e.g., Bash scripts for stale resource cleanup using Azure CLI).
- Ensure Linux examples are presented alongside Windows examples, not always after them.
- Expand Linux sections to include advanced management scenarios, such as using cron jobs or systemd for agent maintenance.
- Where possible, reference cross-platform tools (e.g., Azure CLI) before platform-specific tools (e.g., PowerShell).
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting and DNS resolution examples, Windows-specific tools (like Remote PowerShell and RDP) are referenced, and Windows terminology (e.g., 'management machine', 'workstation', 'console session') is used. Linux equivalents (such as Bash or Linux CLI commands) are not provided alongside PowerShell examples, and Windows tools are mentioned first or exclusively in some sections. While there is some Linux-specific troubleshooting (GLIBC errors), overall, Linux/macOS users may experience friction due to missing parity in examples and tool references.
Recommendations
- Provide Linux/macOS equivalents for PowerShell commands (e.g., use dig, nslookup, curl, etc.) wherever PowerShell is used.
- Include Bash or Linux CLI examples alongside Windows/PowerShell examples for network and DNS troubleshooting.
- Mention Linux remote access tools (e.g., SSH, console access) alongside Windows tools like RDP.
- Clarify terminology to be platform-neutral (e.g., 'management machine' instead of 'workstation').
- Ensure all CLI commands (az arcappliance, etc.) are shown to work on both Windows and Linux, and note any OS-specific requirements.
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 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 template examples themselves are balanced, but the operational guidance is Windows-centric.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
- Explicitly mention that both Azure PowerShell and Azure CLI can be used for deploying ARM templates, and link to relevant CLI documentation.
- Consider showing CLI/Bash examples before or alongside PowerShell, or clarify that PowerShell is cross-platform.
- Add a note about PowerShell Core being available on Linux/macOS, if PowerShell is preferred.
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_tools
Summary
The documentation page provides disaster recovery instructions for Azure Arc resource bridge in VMware vSphere environments, but all script examples and operational guidance are exclusively in PowerShell (.ps1) format. There are no Bash, shell, or Linux/macOS-compatible script examples or instructions, and the onboarding script is referenced only as a PowerShell script. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native shell environments.
Recommendations
- Provide equivalent Bash or shell script examples for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
- Explicitly state platform requirements for the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS, mention this and provide installation guidance).
- Include instructions for running the onboarding script on Linux/macOS, or offer a downloadable cross-platform version.
- If the onboarding script is Windows-only, consider developing and publishing a Linux/macOS-compatible version.
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 provides multiple methods for installing Arc agents at scale for VMware VMs, but there is notable Windows bias. The auto-enablement script is PowerShell-based, with instructions and examples exclusively for Windows (e.g., Set-ExecutionPolicy, Windows Task Scheduler). There are no equivalent Linux shell or cron job examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux alternatives, and Linux-specific guidance is limited to a brief sudo configuration note. Out-of-band methods mention Ansible, but most scripted automation is Windows-centric.
Recommendations
- Provide a Bash or shell script version of the auto-enablement script for Linux/macOS users, with usage instructions.
- Include examples for scheduling the script as a cron job on Linux, not just Windows Task Scheduler.
- Offer guidance for running the PowerShell script on Linux (using PowerShell Core), or clarify limitations.
- Ensure parity in examples for both Windows and Linux, especially in automation and at-scale deployment scenarios.
- Highlight any differences or prerequisites for Linux/macOS environments (e.g., script execution, authentication).
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, step-by-step instructions for running the deboarding script on Windows using PowerShell, but does not mention or provide equivalent instructions for running the script on Linux or macOS. The script section is labeled 'Windows' and all example commands are PowerShell-specific, with no Bash or cross-platform alternatives. This creates friction for Linux/macOS users who may also need to remove vCenter environments from Azure Arc.
Recommendations
- Explicitly state whether the deboarding script can be run on Linux/macOS, and if so, provide equivalent Bash or shell instructions.
- If the script is PowerShell-only, clarify this limitation early in the section and provide guidance for Linux/macOS users (e.g., using PowerShell Core, or running the script from a Windows machine).
- If a cross-platform version of the script exists or can be made available, include download and usage instructions for Linux/macOS.
- Present both Windows and Linux/macOS instructions in parallel where applicable, or at least acknowledge the experience for non-Windows users.
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 (.ps1) for bulk deployment and workflow deletion. There are no Bash or Linux/macOS shell examples, and the only provided automation scripts are Windows PowerShell (.ps1) files. This creates friction for Linux/macOS users, who may need to adapt commands and cannot use the provided scripts directly.
Recommendations
- Provide Azure CLI command examples in Bash syntax alongside PowerShell, especially since Azure CLI is cross-platform.
- Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or clarify how Linux/macOS users can perform these tasks.
- Explicitly note any OS requirements for scripts and provide guidance for Linux/macOS users where PowerShell scripts are referenced.
- Add a section or callout explaining how Linux/macOS users can adapt the workflow, including script alternatives or manual steps.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively provides a PowerShell script (RGCleanScript.ps1) and only demonstrates usage in PowerShell, with no mention of Bash, shell scripts, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the script appears to be designed primarily for Windows environments.
Recommendations
- Provide a Bash or shell script equivalent (e.g., RGCleanScript.sh) for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Include explicit instructions and command-line examples for running the script on Linux/macOS, using PowerShell Core (pwsh) if applicable.
- Mention any prerequisites or dependencies for running the script on non-Windows platforms (e.g., installation of PowerShell Core, az CLI).
- If the script is Windows-only, clearly state this limitation at the beginning of the documentation and suggest manual clean-up steps or alternative approaches for Linux/macOS users.
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 extensive PowerShell-based examples and scripts for enabling and managing diagnostics, log collection, and orchestration on Azure Arc-enabled Kubernetes clusters. All CLI and scripting instructions are given in PowerShell syntax, with no Bash or Linux shell equivalents. File paths in JSON templates and scripts use Windows-style paths (e.g., C:\Users\...), and references to running scripts are exclusively in PowerShell (.ps1). There are no Linux/macOS-specific instructions or examples, and the documentation assumes a Windows environment for orchestration and onboarding.
Recommendations
- Add Bash or Linux shell equivalents for all PowerShell commands and scripts, especially for az CLI usage.
- Provide examples using Linux/macOS file paths and conventions in JSON templates and onboarding instructions.
- Clarify whether the onboarding scripts and tooling are cross-platform or Windows-only; if cross-platform, provide guidance for Linux/macOS users.
- Include notes or sections for Linux/macOS users, highlighting any differences or prerequisites.
- Where possible, use platform-neutral az CLI commands instead of PowerShell-specific syntax (e.g., avoid backticks for line continuation).
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses 'winget', a Windows-only package manager, with no Linux/macOS alternative. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a Bash/Linux-native tool. There are no Linux/macOS-specific instructions for these steps, and Windows paths are used throughout. While Azure CLI and kubectl are cross-platform, the documentation prioritizes Windows tools and patterns, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew').
- Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' for Linux/macOS users.
- Include Linux/macOS file path examples alongside Windows paths.
- Ensure Bash tab examples use Bash-native commands, not PowerShell/Windows commands.
- Add explicit notes or sections for Linux/macOS users where steps differ.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section. Bash examples are shown elsewhere, but PowerShell is used for configuration commands without equivalent Bash/Linux syntax. The Azure CLI is cross-platform, but the use of PowerShell-specific syntax (backticks, variables like $rg) may confuse Linux/macOS users. There is a minor tendency to show Windows-style CLI examples first or exclusively in some sections.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell CLI examples, especially for configuration commands.
- Use generic CLI syntax (without OS-specific shell features) when possible, or show both PowerShell and Bash versions side-by-side.
- Clarify that Azure CLI commands work on all platforms and highlight any OS-specific differences.
- Avoid using PowerShell-specific syntax (backticks, $variables) in generic documentation unless the section is Windows-specific.
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-style command usage. Most examples, including those for Azure CLI, Docker, and Kubernetes, are provided only in PowerShell syntax, with no equivalent Bash or Linux shell examples for critical steps. Windows-specific scripting patterns (e.g., variable assignment, Base64 encoding, file encoding checks) are used throughout, and Linux/macOS users are not given parity guidance. Bash examples are only provided in the 'service groups' section, and even there, PowerShell is shown first or equally, but the rest of the document is Windows-centric.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and Kubernetes steps.
- Use cross-platform variable syntax and avoid Windows-specific scripting patterns (e.g., PowerShell variable assignment, Base64 encoding).
- Explicitly mention file encoding checks for Linux/macOS users (e.g., how to check/save UTF-8 files in Linux editors).
- Ensure that troubleshooting steps can be followed on Linux/macOS, including Docker and kubectl commands.
- Where PowerShell is used for scripting, offer Bash alternatives or clarify which steps are Windows-only.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides authentication options for Azure Container Registry, with examples for both Azure CLI and Azure PowerShell. However, PowerShell examples are prominent throughout, and the CLI examples are not explicitly shown for Linux/macOS environments (e.g., bash shell usage, environment variable syntax). Windows/PowerShell tools are mentioned alongside Azure CLI, but Linux-specific guidance (such as shell syntax or troubleshooting for Linux users) is missing. The 'Next steps' section also lists PowerShell and CLI separately, but does not clarify cross-platform usage.
Recommendations
- Add explicit Linux/macOS shell examples for Azure CLI commands, including bash/zsh syntax for environment variables and piping.
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and provide troubleshooting tips for common Linux issues (e.g., Docker daemon permissions).
- Include a note or section on using Azure CLI in bash/zsh, and highlight cross-platform compatibility.
- Balance PowerShell and CLI examples by showing Linux/macOS usage patterns where relevant.
- In the 'Next steps' section, link to cross-platform guides or clarify that Azure CLI is available on all major OSes.
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 presents Windows/PowerShell examples first and in greater detail, with Linux/Bash examples following. Windows tools (PowerShell) are mentioned before Linux equivalents, and screenshots for both platforms are provided. However, Linux parity is maintained throughout, with equivalent Bash examples and links to Linux-specific guidance.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid Windows-first bias.
- Ensure that Linux/Bash examples are as detailed as Windows/PowerShell examples.
- Explicitly mention that both Windows and Linux are fully supported, and highlight any differences in prerequisites or permissions.
- Add links to Linux-specific troubleshooting or best practices where relevant.
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, but consistently lists Bash examples first. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There is a minor bias in the ordering of examples, but no substantive impact on Linux/macOS users.
Recommendations
- Continue to provide both Bash and PowerShell examples for all commands.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS environments and PowerShell for Windows, to clarify usage for new users.
- Maintain parity in future updates by ensuring all features and instructions are available for both platforms.
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 shown after Bash examples, which is a minor 'windows_first' bias. No exclusive Windows tools, patterns, or missing Linux examples are present. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs in future documentation, or clarify that Bash is for Linux/macOS and PowerShell is for Windows.
- Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant instructions.
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 mentions SQL Server Management Studio (SSMS) as the primary GUI tool for connecting, which is Windows-only, and lists it before sqlcmd. However, it does provide a sqlcmd example for both Linux and Windows. There are no Linux-specific GUI tools mentioned, and SSMS is referenced as the main graphical option. The command-line examples are cross-platform, but the documentation subtly prioritizes Windows tools and patterns.
Recommendations
- Mention cross-platform GUI tools such as Azure Data Studio alongside SSMS, and provide examples for connecting with them.
- Clarify that sqlcmd is available on both Linux and Windows, and provide explicit Linux/macOS instructions (e.g., installation steps or package names).
- Avoid listing Windows-only tools (SSMS) first; instead, present cross-platform options equally.
- Add a note about using other SQL clients on Linux/macOS, such as DBeaver or Squirrel SQL.
Azure Arc
Quickstart - Deploy Azure Arc-enabled data services - directly connected mode - Azure portal
...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page provides a quickstart for deploying Azure Arc-enabled data services in directly connected mode via the Azure portal. While the instructions are generally cross-platform, there is a minor Windows bias in the output example for the Azure CLI command 'az aks get-credentials', which references a Windows file path (C:<current path>\.kube\config) as the default location for the kubeconfig file. No PowerShell-specific commands, Windows-only tools, or missing Linux/macOS examples are present. All CLI commands (az, kubectl) are cross-platform, and Visual Studio Code is also available on Linux/macOS.
Recommendations
- Update the output example for 'az aks get-credentials' to mention both Windows and Linux/macOS default kubeconfig locations, e.g., 'C:\<current path>\.kube\config' for Windows and '~/.kube/config' for Linux/macOS.
- Add a note clarifying that all CLI commands work on Windows, Linux, and macOS, and that Visual Studio Code is cross-platform.
- If possible, include screenshots or output examples from Linux/macOS environments alongside Windows examples.
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 connectivity requirements for Azure Arc resource bridge, with some evidence of Windows bias. Windows-specific services (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are mentioned, and Windows NTP is referenced before any Linux alternatives. However, Linux endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io) are also included, and SSH is listed as a primary inbound protocol. There are no explicit PowerShell-only examples or missing Linux equivalents, but Windows tools and endpoints appear more frequently and are sometimes mentioned first.
Recommendations
- Clarify when Windows-specific endpoints (e.g., time.windows.com) are only required for Windows deployments, and provide Linux alternatives (e.g., pool.ntp.org) where applicable.
- Ensure that Linux-specific requirements (such as NTP, package sources, and management tools) are equally highlighted and described.
- Where Windows endpoints are listed, add notes for Linux users about equivalent services or clarify if the endpoint is required regardless of OS.
- Review the order of endpoint listing to avoid always mentioning Windows endpoints first unless there is a technical reason.
- Add explicit examples or notes for Linux management machines if any steps differ.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_example
missing_linux_example
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows-specific instructions (using certutil and findstr) are more detailed and include extra steps. The Linux example is brief and lacks troubleshooting or alternative approaches. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl), but the Windows encoding section stands out as biased.
Recommendations
- Expand Linux instructions for base64 encoding to include troubleshooting tips or alternative commands (e.g., using openssl for encoding).
- Provide parity in detail for Linux users, such as how to remove headers from base64 output if needed.
- Consider mentioning macOS explicitly, as its base64 utility is similar to Linux.
- Clarify that most steps are cross-platform and highlight any OS-specific differences equally.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but PowerShell examples are consistently presented alongside CLI and sometimes before Linux-native alternatives. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no Linux-specific shell examples (e.g., Bash scripts), and the environment variable instructions for proxy setup are shown for both Bash (export) and PowerShell ($Env), but PowerShell is given equal prominence. No Windows-only tools are referenced, but the documentation does not explicitly highlight Linux/macOS compatibility or provide Linux-first examples.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS environments.
- Consider presenting Azure CLI examples before PowerShell, or labeling PowerShell as Windows-specific.
- Add explicit notes about Linux/macOS compatibility where relevant.
- Provide Bash script examples for common tasks, especially for onboarding and proxy configuration.
- Include troubleshooting tips for Linux/macOS environments if applicable.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page provides Azure CLI and kubectl examples throughout, which are cross-platform tools. However, there are subtle signs of Windows bias: Windows/Mac installation instructions for Azure kubelogin are mentioned first, with Linux instructions following; some commands reference 'console' generically but do not clarify shell differences; and there is no explicit mention of PowerShell, but Azure CLI is often associated with Windows environments. Linux-specific nuances (such as SSH, file paths, and package management) are addressed, but not always with equal prominence or clarity compared to Windows/Mac. Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Ensure Linux installation instructions are given equal prominence and clarity as Windows/Mac.
- Explicitly state that Azure CLI and kubectl commands are cross-platform and provide shell-specific notes where relevant.
- Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path differences).
- Where possible, provide explicit examples for both bash and PowerShell if command syntax differs.
- Clarify that 'console' refers to any terminal (bash, zsh, PowerShell, etc.) and note any OS-specific prerequisites.
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 for `azcmagent connect` shows mild Windows bias. Windows authentication options (interactive browser login and certificate store usage) are described first and in greater detail, while Linux authentication flows are mentioned later. The access token example references a Windows PowerShell cmdlet (`Get-AzAccessToken`) without mentioning Linux equivalents. However, Linux authentication methods (device code, Azure CLI) are documented and supported, and most examples are cross-platform.
Recommendations
- Reorder authentication options so that cross-platform methods (device code, Azure CLI) are described before Windows-only flows.
- When referencing access token acquisition, mention Linux/macOS methods (e.g., Azure CLI `az account get-access-token`) alongside PowerShell.
- Clarify which authentication options are cross-platform and which are Windows-only in a summary table.
- Add explicit Linux/macOS examples where relevant, such as shell commands for obtaining access tokens.
- Ensure parity in detail for Linux authentication flows (e.g., certificate usage outside Windows certificate stores).
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. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and partner extensions are shown for both OSes. No critical Linux features are missing, and Linux users can complete all tasks described.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side if feasible.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Ensure that any linked deployment guides (e.g., manage-vm-extensions-cli.md, manage-vm-extensions-powershell.md) provide Linux-specific examples where applicable.
- Add a brief note at the start clarifying that Azure Arc-enabled servers support both Windows and Linux equally.
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 tools (such as PowerShell, msiexec, and GUI installer instructions) are mentioned in troubleshooting and known issues, with no equivalent Linux command-line examples or troubleshooting guidance. Some improvements and bug fixes reference Windows tools/scripts (e.g., ExtensionCleanup.ps1, MSI signature verification) without Linux parity. Linux-specific issues and improvements are included, but Windows patterns are more prominent in guidance and examples.
Recommendations
- Alternate the order of Windows and Linux download links or present them together to avoid implicit prioritization.
- When mentioning Windows-specific troubleshooting steps (e.g., using msiexec or PowerShell), provide equivalent Linux instructions (such as using sudo, rpm, or systemctl) where applicable.
- For script-based improvements (e.g., ExtensionCleanup.ps1), clarify if there are Linux equivalents or note their absence.
- Expand known issues and troubleshooting sections to include Linux-specific guidance, not just Windows installer problems.
- Ensure parity in highlighting improvements and bug fixes for both platforms, and avoid referencing Windows tools/scripts without mentioning Linux alternatives.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Windows (PowerShell) and Linux (CLI) examples for all major operations, but Windows/PowerShell examples are often presented before Linux/CLI equivalents. Some minor notes reference Windows-specific behaviors (e.g., PowerShell-specific CLI syntax, Windows Admin Center scenario), and the log file location is described for both OSes. Overall, Linux parity is maintained, but Windows is subtly prioritized in ordering and some tool mentions.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux users see their preferred tools first in some sections.
- Explicitly state that all CLI examples work on Linux/macOS and Windows, and clarify any OS-specific syntax differences.
- Where Windows tools (e.g., Windows Admin Center) are mentioned, add equivalent Linux management tools or clarify if none exist.
- Ensure that Linux log file paths and instructions are equally prominent and detailed as Windows instructions.
- Review scenario lists to ensure Linux scenarios are not omitted or presented after Windows scenarios.
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 before REST API and does not provide explicit Linux-specific examples or tools in the overview. However, it does state that both Windows and Linux are supported, and notes a Linux-specific limitation. The bias is minor and mostly in ordering, not in content or capability.
Recommendations
- Ensure that Linux examples and tools (such as Bash or shell scripting) are mentioned alongside PowerShell in introductory sections.
- When listing supported experiences, alternate the order or explicitly state parity between Windows and Linux.
- Add explicit examples or links for Linux users, such as Bash scripts or Linux command-line usage, in the overview or next steps.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation generally maintains parity between Windows and Linux, explicitly referencing both platforms for the Azure Connected Machine agent. However, there are minor signs of Windows bias: Windows-related tools and services (e.g., Windows Admin Center, Windows installation package, Windows Server versions) are mentioned first or exclusively in some sections, and Windows-specific configuration issues are referenced before Linux equivalents. Linux examples and troubleshooting are less detailed, and Windows terminology appears more frequently.
Recommendations
- Ensure Linux and Windows examples are presented together or alternate their order to avoid 'windows_first' bias.
- Expand Linux-specific troubleshooting guidance, especially for TLS/OpenSSL configuration and agent installation.
- Where Windows tools (e.g., Windows Admin Center) are mentioned, clarify Linux alternatives or note their platform specificity.
- Provide links to Linux documentation for configuring secure connectivity, proxies, and TLS settings.
- Add explicit Linux agent update instructions or references where Windows update paths are described.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, including error codes, exit codes, and log locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples are shown after. Windows-specific tools and paths (e.g., PowerShell, %ProgramData%) are mentioned alongside Linux equivalents, but Windows is often prioritized in ordering and detail.
Recommendations
- Present Windows and Linux examples in parallel or alternate order, rather than always showing Windows first.
- Where possible, provide cross-platform command syntax (e.g., azcmagent usage) before platform-specific invocation details.
- Ensure Linux log file paths and troubleshooting steps are as detailed as Windows.
- Avoid referencing Windows tools (e.g., PowerShell) without also mentioning Linux equivalents (e.g., Bash, sudo).
- Consider using tabs or collapsible sections for platform-specific instructions to improve parity and clarity.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and PowerShell notes are presented first and in greater detail. Windows-specific caveats (e.g., avoiding PowerShell ISE) are highlighted, while Linux instructions are more concise. The retry command section also lists Windows before Linux. There is no evidence of missing Linux examples or exclusive mention of Windows tools; parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them side-by-side to avoid implicit prioritization.
- Expand Linux instructions to include any relevant caveats or troubleshooting tips, similar to the PowerShell ISE note for Windows.
- Ensure screenshots and UI references are OS-neutral or clarify if they apply equally to Linux users.
- Consider adding a summary table or section that highlights cross-platform compatibility and any OS-specific requirements.
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 are subtle signs of Windows bias: PowerShell is listed before other automation tools, and Windows-specific links/examples (such as Windows Server management and Windows tabs in links) are often shown first or exclusively. Linux support is mentioned, but Windows terminology and tooling appear more prominently.
Recommendations
- Ensure Linux examples and links are provided alongside Windows ones, especially in 'Next steps' and automation sections.
- When listing tools (CLI, PowerShell, SDKs), alternate the order or explicitly note Linux/macOS compatibility.
- Add links and references to Linux-specific documentation (e.g., Linux onboarding, Linux VM extensions, Linux runbooks).
- Where runbooks or automation are discussed, provide Bash or Python examples in addition to PowerShell.
- Review linked pages (e.g., 'Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud') to ensure Linux parity.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned, but these are appropriate given the context. However, in the June 2024 section, Azure PowerShell is listed after Azure CLI and REST APIs, and Windows-specific tools like System Center Configuration Manager and Group Policy are mentioned before Linux equivalents (Ansible) in the October 2024 section. There is some minor bias in the ordering and emphasis of Windows tools, but Linux features (such as SSH-based agent installation and Ansible) are also included.
Recommendations
- Ensure Linux tools and methods (such as Ansible) are mentioned alongside or before Windows tools when listing options for agent installation.
- Provide explicit examples or links for Linux-based workflows where possible, especially for agent installation and VM management.
- Consider alternating the order of Windows and Linux tools in lists to avoid implicit prioritization.
- Add clarifying notes when a feature is Windows-only to avoid confusion for Linux users.
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 receives slightly more emphasis. There are no Windows-only tools or patterns, but the ordering and phrasing may subtly favor Windows users. All examples are cross-platform, but PowerShell is highlighted before CLI, which is more native to Linux/macOS.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions to avoid implicit prioritization.
- Explicitly note that Azure CLI is cross-platform and works natively on Linux/macOS.
- Add brief instructions or links for installing Azure CLI and PowerShell on Linux/macOS.
- Consider including a short example command for both PowerShell and Azure CLI in the main content, not just in tips.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and with download links, while Linux requirements are listed more briefly. Windows download links are more prominent, and Windows PowerShell is mentioned specifically, but Linux equivalents (such as Bash or shell scripting) are not referenced. No Linux-specific onboarding or management examples are given, and Windows terminology (e.g., 'Windows Admin Center') appears in networking requirements without Linux alternatives.
Recommendations
- List Linux and Windows requirements in parallel, alternating order or grouping by OS.
- Provide download links or references for Linux tools (e.g., systemd documentation, wget installation guides).
- Mention Linux shell scripting or command-line alternatives where Windows PowerShell is referenced.
- Clarify if Windows Admin Center is required only for Windows scenarios, and provide Linux alternatives if available.
- Add explicit Linux onboarding or management examples/scripts if possible.
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 step, ensuring parity for Linux/macOS and Windows users. However, in nearly all sections, PowerShell examples are presented after Bash examples, indicating a minor 'windows_first' bias in ordering. No exclusive Windows tools or patterns are used, and Linux examples are not missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to clarify intent.
- Add a short note at the top explaining that Bash is recommended for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- Ensure that any future updates continue to provide both Bash and PowerShell examples for all CLI steps.
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 shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add a brief note at the top clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and that Bash and PowerShell examples are provided for user convenience.
- If possible, provide a generic CLI example (without shell-specific syntax) for users of other shells.
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 cross-platform parity. However, PowerShell examples are sometimes shown first or in equal prominence, and some minor details (like base64 encoding) are explained separately for Windows and Linux. There is no evidence of Windows-only tools or missing Linux examples, but the structure occasionally gives Windows/PowerShell equal or slightly more prominence than Bash/Linux.
Recommendations
- Ensure Bash (Linux/macOS) examples are consistently shown first, as Linux is the primary platform for container orchestration and Kubernetes.
- Clarify that Bash examples are suitable for Linux/macOS, and PowerShell for Windows, to help users quickly identify their relevant section.
- Where possible, highlight any OS-specific differences (e.g., file encoding, base64 commands) in a neutral, cross-platform way.
- Consider adding a summary table at the top indicating which sections are relevant for each OS, to improve navigation.
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 nearly every section, Bash examples are shown first, followed by PowerShell. There are no Windows-specific tools or patterns used, and all commands are cross-platform via the Azure CLI. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections, or explicitly state that Bash is shown first for consistency, not preference.
- Add a brief note at the start clarifying that both Bash and PowerShell are supported and that the Azure CLI works on all platforms.
- 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, PowerShell examples are always shown after Bash, which is a minor 'windows_first' bias in ordering. There are no Windows-specific tools, commands, or patterns used exclusively, and all instructions are cross-platform via Azure CLI and Helm.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add a brief note clarifying that all Azure CLI commands work on both platforms, and that PowerShell is primarily for Windows users.
- If possible, provide a generic shell example (where applicable) to further emphasize cross-platform compatibility.
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 for 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, PowerShell pipeline usage) are used. Bash examples are always shown first, but PowerShell is given equal prominence, which may be unnecessary for Linux/macOS-focused users. There are no Windows-only tools or patterns, and the Azure CLI and Helm commands are cross-platform.
Recommendations
- Consider clarifying that PowerShell examples are primarily for Windows users, while Bash is for Linux/macOS.
- Explicitly note that Bash examples are suitable for macOS and Linux terminals.
- Where possible, avoid Windows-specific file path conventions (e.g., backslashes) in PowerShell examples, or provide guidance for Linux PowerShell users.
- If the audience is primarily Linux/macOS, consider making Bash the default and PowerShell optional.
- Ensure that all scripts and commands are tested on both platforms.
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for deploying Azure dashboards using Azure CLI and Azure PowerShell. Azure CLI is cross-platform, but Azure PowerShell is primarily associated with Windows, though it is available on Linux/macOS. The PowerShell section is presented after the CLI section, and all command-line examples use Azure CLI (which is Linux-friendly) or PowerShell (which is Windows-centric). No Windows-only tools or patterns are prioritized, and Linux/macOS users are not excluded from any workflow. However, the inclusion of PowerShell may subtly reinforce Windows-centric patterns, though Azure CLI is shown first.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (Linux/macOS) and provide installation links for non-Windows users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding a short note or example showing how to run Azure CLI commands on Linux/macOS (e.g., bash shell).
- If possible, provide links to Azure CLI and PowerShell installation guides for all platforms.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry. However, the PowerShell example is given equal prominence and is presented immediately after the CLI example, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux-specific tools or workflows. The CLI example is cross-platform, but the PowerShell example is Windows-centric. The page does not exclusively mention Windows tools, but the parity for Linux/macOS users could be improved by clarifying CLI cross-platform support and adding Bash/Linux shell context.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Add a Bash shell example or clarify that the Azure CLI example works natively in Bash and other Linux/macOS shells.
- Consider mentioning Linux-native tools (such as Docker CLI) where relevant, or provide links to Linux/macOS setup guides for Azure CLI.
- If PowerShell is shown, clarify its availability on Linux/macOS, or note that it is primarily a Windows tool.
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. While Azure CLI is cross-platform, PowerShell is often associated with Windows, and its mention may subtly prioritize Windows users. However, there are no exclusive Windows examples, tools, or patterns, and the overall guidance is platform-neutral.
Recommendations
- Clarify that both Azure CLI and PowerShell are cross-platform tools, and provide examples or links for using them on Linux/macOS.
- Consider mentioning Bash or shell scripting as alternatives for Linux/macOS users, or explicitly state that generated scripts can target multiple platforms.
- Ensure future examples or screenshots include parity for Linux/macOS environments where applicable.
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, the environment variable setting example uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'). Additionally, the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal, and no explicit Linux/macOS guidance. Most commands are generic and applicable to all platforms, but minor Windows-first bias is present.
Recommendations
- Add Linux/macOS equivalents for environment variable setting (e.g., 'export ACR_NAME=<container-registry-name>') alongside the Windows 'set' command.
- Clarify that Azure CLI commands are cross-platform and provide any necessary shell-specific instructions (e.g., bash vs. cmd).
- When listing options for creating AKS clusters, consider mentioning Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
- Review all command examples to ensure they work as written on Linux/macOS, and add notes or alternatives where needed.
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
powershell_heavy
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, with no exclusive focus on Windows tools or patterns. However, Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is fully cross-platform) may be seen as a mild Windows bias. In some sections, Azure CLI examples are listed before PowerShell, but both are always present. There are no missing Linux/macOS examples, and no use of Windows-only tools or patterns outside of PowerShell.
Recommendations
- Clearly state that both Azure CLI and Azure PowerShell are supported, but Azure CLI is recommended for cross-platform (Linux/macOS/Windows) usage.
- Consider adding a short note at the top explaining that Azure CLI commands work on all platforms, while PowerShell is most common on Windows (though available cross-platform).
- If possible, add Bash or shell script examples for common workflows, or clarify that Azure CLI commands can be run in Bash, Zsh, or other shells.
- Ensure that any references to installing tools include Linux/macOS instructions (the current links do this via the Azure CLI install page).
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 PowerShell examples and references alongside or immediately after CLI examples. There are no Linux/macOS-specific examples or explicit mention of Linux tools, and PowerShell is referenced as a primary alternative to Azure CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Ensure Azure CLI examples are presented first, as CLI is cross-platform and preferred for Linux/macOS users.
- Clearly indicate that Azure PowerShell is Windows-centric, and suggest Azure CLI for Linux/macOS users.
- Where possible, provide Bash shell examples (using Azure CLI) and clarify that PowerShell examples are optional for Windows users.
- Add explicit notes or sections for Linux/macOS users, highlighting cross-platform tools and workflows.
- Avoid implying parity between Azure CLI and PowerShell unless both are equally supported on all platforms.