225
Pages Scanned
56
Pages Flagged
225
Changed Pages
24.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-04 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 225
Files Completed: 225
Problematic Pages
57 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 page for onboarding scripts in workload orchestration is heavily biased towards Windows. All script examples use PowerShell (.ps1), and instructions explicitly require opening a PowerShell terminal. Prerequisites reference 'winget', a Windows-only package manager, with no mention of Linux/macOS equivalents. There are no Bash or shell script examples, and no guidance for Linux/macOS users on how to run the onboarding scripts or install dependencies.
Recommendations
- Provide Bash or shell script equivalents for onboarding tasks, or clarify if only PowerShell scripts are available.
- Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew, or manual download).
- Mention cross-platform alternatives to 'winget', such as 'apt', 'yum', or 'brew', for installing required tools.
- Clarify whether the PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide guidance for those environments.
- Add explicit notes or sections for Linux/macOS users, including any limitations or required adaptations.
Create Pull Request
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides a PowerShell script and PowerShell command examples for resource clean-up, without mentioning or providing equivalent Bash/shell scripts or instructions for Linux/macOS users. The script appears to require PowerShell, which is traditionally a Windows tool, and there is no guidance for running the script on Linux/macOS or using alternative tools.
Recommendations
- Provide instructions for running the PowerShell script on Linux/macOS using PowerShell Core (pwsh), including installation guidance if needed.
- Offer Bash or shell script alternatives for the clean-up process, or clarify if only PowerShell is supported.
- Explicitly state platform compatibility for the script (Windows, Linux, macOS) and note any limitations.
- If PowerShell is required, add a section for Linux/macOS users explaining how to install and use PowerShell Core.
- Include example commands for Linux/macOS users (using pwsh or Bash) alongside Windows/PowerShell examples.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page provides all CLI/script examples exclusively in PowerShell syntax, assumes Windows-style file paths (e.g., C:\, E:\), and references PowerShell scripts (.ps1) for orchestration. There are no Bash, shell, or Linux/macOS equivalents for commands or scripts, and Windows file path conventions are used throughout JSON templates. This creates friction for Linux/macOS users, who must adapt commands and scripts themselves.
Recommendations
- Provide Bash or shell equivalents for all PowerShell CLI examples, especially for az CLI commands.
- Use cross-platform file path examples in JSON templates (e.g., /home/user/schema.yaml) or note how to adapt for Linux/macOS.
- Offer .sh script alternatives or document how to run orchestration scripts on Linux/macOS.
- Clarify which steps are Windows-specific and which are cross-platform.
- Add notes or links for Linux/macOS users on adapting PowerShell scripts and file paths.
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 only PowerShell examples and references a PowerShell onboarding script for disaster recovery operations. There are no Bash or Linux/macOS shell equivalents, nor guidance for running the script on non-Windows platforms. The onboarding script and instructions are Windows-centric, creating friction for Linux/macOS users.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
- Explicitly mention whether the onboarding script can be run on Linux/macOS (e.g., via PowerShell Core or Azure CLI), and provide instructions for those environments if possible.
- Add notes or links for Linux/macOS users about prerequisites and alternative tooling.
- If the onboarding script is Windows-only, state this clearly and suggest workarounds or alternatives for non-Windows users.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is generally Linux-focused, but it uses the Windows-specific PowerShell cmdlet Invoke-AksEdgeNodeCommand for Linux node configuration, without providing native Linux shell alternatives. This creates friction for Linux users who may not have access to PowerShell or prefer standard Linux command-line tools.
Recommendations
- Provide native Linux shell commands (e.g., using ssh, sysctl, echo, and tee) for configuring fs.inotify.max_user_instances directly on Linux nodes.
- Clarify when PowerShell is required and offer equivalent Bash or Linux-native instructions.
- Ensure all steps can be completed on Linux without reliance on Windows tools or PowerShell.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides several command-line examples using PowerShell syntax (e.g., 'kubectl exec ...' and 'kubectl get secret ...') with the code block language explicitly set to 'powershell', even though the commands themselves are cross-platform. There are no Linux/macOS-specific shell examples or notes, and the use of PowerShell syntax highlighting may confuse non-Windows users. All examples are shown in a Windows-centric style, with no mention of Linux/macOS equivalents or shell environments.
Recommendations
- Change code block language from 'powershell' to 'console' or 'shell' for cross-platform commands like 'kubectl' and 'sqlcmd'.
- Add explicit notes clarifying that all commands work on Linux/macOS terminals as well as Windows (with appropriate tools installed).
- Where relevant, provide example commands using bash or sh syntax (especially for decoding base64, e.g., 'echo <string> | base64 -d').
- Avoid using Windows-specific terminology or highlighting unless the command is truly Windows-only.
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 and file paths (e.g., Visual Studio Code, SQL Server Management Studio, Azure Storage Explorer, and Windows-style paths like C:\Backupfiles\test.bak) without offering equivalent Linux/macOS alternatives or mentioning cross-platform options. Linux/macOS users may need to infer how to adapt steps, especially for backup file creation and tool usage.
Recommendations
- Include Linux/macOS file path examples (e.g., /home/user/Backupfiles/test.bak) alongside Windows paths.
- Mention and provide instructions for cross-platform tools such as Azure Storage Explorer (which is available for Linux/macOS) and alternatives to SQL Server Management Studio (e.g., Azure Data Studio, which is cross-platform).
- Clarify that Visual Studio Code and Azure Storage Explorer are available on Linux/macOS, and provide installation links for those platforms.
- For backup creation, show T-SQL examples using Linux/macOS file paths and explain how to run them from cross-platform clients.
- Explicitly state that all steps can be performed from Linux/macOS unless there are Windows-only requirements.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps (removing headers) not explained for Linux. The Linux example is brief and lacks parity in guidance. Windows tools (certutil, findstr) are mentioned explicitly, while Linux alternatives for header removal are not provided. The rest of the guide uses cross-platform tools (openssl, Azure CLI, kubectl), but the Windows encoding section is more prominent.
Recommendations
- Expand Linux guidance for base64 encoding to include instructions for removing headers (e.g., using grep or sed).
- Present Linux and Windows examples side-by-side for parity, rather than giving Windows-specific tools more detail.
- Mention macOS where appropriate, as its base64 utility and file handling are similar to Linux.
- Clarify that the base64 command works on macOS as well.
- Add a note about how to decode base64 files on Linux/macOS, matching the Windows certutil decode example if given.
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
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. While most examples and instructions are generic or CLI-based, there are several instances where Windows tools and patterns are referenced before Linux equivalents, and PowerShell is used for network troubleshooting (e.g., Invoke-WebRequest, Resolve-DnsName). Windows terminology (e.g., 'Remote PowerShell', 'RDP') is mentioned, and some commands are shown in Windows-centric contexts. Linux-specific troubleshooting is present (e.g., GLIBC errors), but Linux commands are less prominent and often appear after Windows examples.
Recommendations
- Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP troubleshooting, dig or nslookup for DNS resolution).
- When referencing CLI commands, clarify if they work equally on Linux/macOS and Windows, and note any OS-specific requirements.
- If troubleshooting steps involve Windows tools (like RDP or PowerShell), offer alternatives for Linux/macOS (e.g., SSH, terminal access).
- Ensure Linux-specific errors and solutions are as detailed and visible as Windows ones.
- Where possible, show Linux/macOS commands before or alongside Windows commands to improve parity.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Windows download links and examples before Linux equivalents and provides Windows-specific troubleshooting steps (e.g., using attrib and PowerShell commands) without Linux equivalents. Some installer and configuration issues are described only for Windows, and Windows tools (e.g., PowerShell, attrib, msiexec) are referenced without mentioning Linux alternatives. However, Linux support is present and release notes are generally parity-focused.
Recommendations
- When providing troubleshooting steps (such as editing permissions on config files), include equivalent Linux commands (e.g., chmod/chown) alongside Windows commands.
- Where possible, present Windows and Linux download links and instructions in parallel or grouped by OS, rather than always listing Windows first.
- If a known issue or workaround is Windows-only, clearly label it as such and consider adding a note if Linux is unaffected.
- When referencing Windows tools (PowerShell, attrib, msiexec), provide Linux equivalents (bash, chmod, rpm/dpkg, etc.) where applicable.
- Consider adding a section or callout for Linux-specific known issues or troubleshooting steps if any exist.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and tools (PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are often presented first or in greater detail, and a critical cleanup script is only provided in PowerShell with no Linux/bash equivalent. Windows-specific tools and patterns are described extensively, while Linux instructions are more generic and lack advanced automation examples.
Recommendations
- Provide equivalent bash or shell scripts for Linux users, especially for tasks like cleanup of stale resources.
- Ensure Linux examples are given equal prominence and detail, including automation and at-scale management scenarios.
- Where Windows tools (e.g., Group Policy, WSUS, Configuration Manager) are discussed, mention Linux equivalents or clarify their absence.
- Consider alternating the order of Windows and Linux sections, or presenting them side-by-side, to avoid 'windows_first' bias.
- Expand Linux sections to include troubleshooting, logging, and advanced management scenarios similar to Windows.
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux context, but there is a notable Windows bias. Windows tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly, with no equivalent Linux tools highlighted. PowerShell is referenced before Bash, and deployment examples/tools for Linux (such as Ansible) are mentioned only in passing. No explicit Linux-specific examples or workflows are provided, and Windows deployment options are described in more detail.
Recommendations
- Add explicit Linux deployment examples and workflows, such as using Ansible, shell scripts, or Linux-native package managers.
- Mention Linux tools (e.g., systemd, cron, SSH) for agent management alongside Windows tools.
- Provide Bash or shell script examples before or alongside PowerShell examples.
- Highlight Linux-specific considerations for agent installation, configuration, and troubleshooting.
- Balance the order and detail of Windows and Linux instructions to ensure parity.
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page provides deployment options for the Azure Connected Machine agent across both Linux and Windows platforms. However, there is a noticeable bias toward Windows, with PowerShell-based onboarding methods highlighted (including at scale), Windows-specific tools (Windows Admin Center, Configuration Manager, Group Policy) receiving dedicated sections, and Windows-only methods listed after the cross-platform options. Linux-specific automation tools (such as Ansible) are mentioned, but PowerShell is presented as a cross-platform method, despite its stronger association with Windows. No Linux-first or Linux-only onboarding methods (e.g., Bash scripts, cloud-init, or native Linux tools) are described in detail or given equal prominence.
Recommendations
- Add explicit Linux-specific onboarding examples and methods, such as Bash scripts, shell commands, or cloud-init for at-scale deployments.
- Clarify which PowerShell methods are truly cross-platform and provide equivalent Linux command-line examples where possible.
- Ensure Linux automation tools (e.g., Ansible, Puppet, Chef) are given equal prominence and detail as Windows tools.
- Consider listing Linux and Windows methods in parallel or alternating order to avoid 'windows_first' bias.
- Provide links to Linux-specific documentation or walkthroughs for onboarding.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment instructions and sample commands exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and are the only method shown for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does not mention or demonstrate Linux-native tools or deployment patterns, and file path examples use Windows-style paths.
Recommendations
- Add Azure CLI deployment examples (e.g., az deployment group create) alongside PowerShell commands.
- Show Bash shell usage for Linux/macOS users, including file path examples with Linux conventions.
- Explicitly state that both PowerShell and CLI can be used, and link to Azure CLI documentation for ARM template deployment.
- Consider alternating the order of Linux and Windows template examples to avoid Windows-first bias.
- Include a note clarifying that PowerShell is cross-platform, but CLI is often preferred on Linux/macOS.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation covers both Windows and Linux Arc-enabled servers, but exhibits notable Windows bias. PowerShell examples dominate, with Windows-centric tools (e.g., New-AzStorageBlobSASToken, New-NetFirewallRule) featured prominently. REST API examples are exclusively Windows-focused (firewall rule via PowerShell cmdlet), and Linux-specific scripting or scenarios are largely absent. Azure CLI examples use PowerShell syntax ('Write-Host'), and there are no explicit Linux shell script examples. Windows terminology and tools are mentioned first or exclusively in several places.
Recommendations
- Add Linux-specific examples for REST API usage, such as configuring iptables or ufw via shell scripts.
- Provide Azure CLI examples using bash/sh syntax (e.g., 'echo Hello World!' or 'id') instead of PowerShell ('Write-Host').
- Balance PowerShell and shell script examples in the PowerShell and CLI sections, clearly indicating which are for Windows and which are for Linux.
- Include guidance for Linux users on generating SAS tokens (e.g., using Azure CLI or portal) rather than only PowerShell.
- Clarify which parameters or features are OS-specific, and provide parity where possible.
- Add Linux-focused administrative scenarios (e.g., patching, log auditing, firewall configuration) alongside Windows examples.
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 and a downloadable script exclusively for Windows/PowerShell environments, with no mention of Linux or cross-platform alternatives. All example commands and tooling are Windows-specific, and there are no instructions for performing the recovery from a Linux or macOS machine.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, ideally using Bash or cross-platform tools.
- Explicitly state if the recovery process is only supported from Windows, and explain why (e.g., SCVMM/PowerShell dependencies).
- If possible, offer a platform-agnostic solution or clarify any technical limitations.
- Add a note about the lack of Linux/macOS support if it is intentional, to set user expectations.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation shows a notable Windows bias, especially in the automation/scripted installation section. The primary at-scale enablement script is a PowerShell script, and instructions for running it reference Windows-only tools (PowerShell, Task Scheduler). There are no equivalent Bash/Linux shell examples, and Linux automation options are not given equal prominence. Out-of-band methods mention Ansible but provide more detailed links and examples for Windows-centric tools (Configuration Manager, Group Policy).
Recommendations
- Provide a Bash or cross-platform shell script for at-scale Arc agent installation, or clearly link to such resources if they exist.
- Include Linux/macOS terminal instructions for running the automation script (e.g., using cron, bash, or systemd timers) alongside the Windows Task Scheduler example.
- Ensure that out-of-band methods give equal detail and prominence to Linux automation tools (e.g., Ansible, shell scripts) as to Windows tools.
- Where PowerShell is used, clarify if the script is compatible with PowerShell Core on Linux/macOS, or provide a native Bash alternative.
- Add explicit Linux/macOS examples for all major steps, not just notes about sudo.
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
Summary
The documentation provides explicit PowerShell instructions for running the deboarding script on Windows, including execution policy guidance and notes about PowerShell ISE. There are no equivalent instructions or examples for running the script on Linux or macOS, nor is there mention of cross-platform script support. Windows instructions are presented first and in detail, while Linux users are left to infer compatibility or usage.
Recommendations
- Add explicit instructions for running the deboarding script on Linux and macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any differences in execution.
- Clarify whether the deboarding script is cross-platform (PowerShell Core compatible) or Windows-only. If it is Windows-only, state this clearly; if cross-platform, provide Linux/macOS usage examples.
- Provide sample commands for running the script on Linux/macOS, including how to set execution policy and handle script prompts.
- Mention any required dependencies or installation steps for PowerShell on non-Windows platforms.
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 automation, without providing Bash or Linux/macOS shell equivalents. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the default scripting environment, which may create friction for non-Windows users.
Recommendations
- Provide Azure CLI command examples in Bash syntax (e.g., using $ variables and shell quoting) alongside PowerShell.
- Offer equivalent Bash scripts for bulk deployment and workflow deletion, or clarify if the PowerShell scripts are cross-platform (e.g., via PowerShell Core).
- Explicitly state that Azure CLI commands can be run in any shell, and provide guidance for Linux/macOS users where relevant.
- Add notes or sections addressing Linux/macOS usage, including any prerequisites or differences in file path handling, quoting, or script execution.
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 the Windows-specific 'winget' tool, 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 command. Throughout, Windows-centric tools and patterns are presented first or exclusively, and Linux/macOS equivalents are missing or not prioritized.
Recommendations
- For kubectl installation, provide Linux/macOS installation commands (e.g., 'curl' or 'apt/yum/brew').
- In Bash file extraction, use standard Linux commands like 'unzip' or 'tar' instead of 'Expand-Archive'.
- Ensure Bash examples use cross-platform commands, not Windows/PowerShell-specific ones.
- Present Linux/macOS instructions alongside Windows instructions, or at least not always after.
- Explicitly note platform differences and provide guidance for Linux/macOS users where Windows tools are referenced.
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, without mentioning Linux/macOS alternatives or providing Bash or cross-platform script options. This creates friction for non-Windows users who may not have access to PowerShell or may need to install it separately.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users.
- Document how to run the PowerShell script using PowerShell Core on Linux/macOS, including installation instructions if needed.
- Clarify whether the migration script is cross-platform or Windows-only, and update prerequisites accordingly.
- Add explicit guidance for Linux/macOS users, including troubleshooting and environment setup.
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 in Azure Arc is heavily biased toward Windows/PowerShell usage. Most command examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). Linux/Bash equivalents are missing or appear only in a few sections. Windows-specific scripting patterns (e.g., PowerShell variable assignment, ConvertTo-Json, Out-File, Base64 encoding via .NET) are used throughout, creating friction for Linux/macOS users.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell examples, especially for Azure CLI, Docker, and kubectl commands.
- Use cross-platform scripting patterns (e.g., environment variables, standard file manipulation tools) instead of Windows/PowerShell-specific constructs.
- Clearly indicate when a command is platform-specific and offer alternatives or notes for Linux/macOS users.
- Review and update file encoding instructions to reference Linux tools (e.g., iconv, file) alongside Windows editors.
- Ensure Base64 encoding examples use standard Linux tools (e.g., base64) as well as PowerShell.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides authentication examples for both Azure CLI and Azure PowerShell, but PowerShell is featured prominently and often alongside CLI, despite PowerShell being primarily a Windows-centric tool (though available cross-platform). Windows/PowerShell commands are presented in parallel to CLI, but Linux/macOS-specific shell examples (bash/zsh) are not provided. The use of PowerShell is emphasized, and the CLI examples do not include explicit Linux/macOS shell syntax or considerations. There is no mention of Linux-specific tools or patterns, and the 'Next steps' section links to PowerShell and CLI guides, but not to Linux/macOS shell guides.
Recommendations
- Add explicit bash/zsh shell examples for authentication, especially for common Linux/macOS workflows.
- Clarify that Azure PowerShell is available cross-platform, but highlight typical Linux/macOS usage patterns (e.g., bash scripts, environment variables).
- Provide guidance for Linux/macOS users on installing and using Azure CLI and Docker, including any OS-specific caveats.
- Include links to Linux/macOS-specific getting started guides or documentation.
- Consider reordering examples so that CLI/bash examples are shown first, or at least equally with PowerShell.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are included, there are no explicit Linux/macOS tool recommendations or examples. Windows tools are presented as primary management options, creating a mild bias toward Windows environments.
Recommendations
- Add explicit mention of cross-platform tools such as Azure Data Studio and highlight their Linux/macOS compatibility.
- Clarify which tools are available on Linux/macOS and which are Windows-only.
- Provide examples or links for managing SQL Managed Instance enabled by Azure Arc from Linux/macOS, e.g., using Azure CLI, Azure Data Studio, or REST APIs.
- Consider listing Azure Data Studio before SSMS to emphasize cross-platform parity.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides installation instructions for client tools across platforms, but Windows-specific guidance and terminology appear first or are emphasized. For example, Windows links are listed before Linux/macOS for kubectl and curl, and there are notes about PowerShell and cmd.exe usage. Some installation instructions for Linux are less explicit or detailed compared to Windows.
Recommendations
- Present installation links for all platforms in parallel (Windows, Linux, macOS) rather than listing Windows first.
- Provide explicit Linux/macOS installation instructions for curl, not just 'install curl package'.
- Avoid Windows-centric notes (e.g., cmd.exe vs PowerShell) unless equally addressing Linux/macOS shell nuances.
- Ensure all examples and guidance are balanced for Linux/macOS users, not just Windows.
- Where possible, add sample commands for Linux/macOS alongside Windows-specific instructions.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, Windows/PowerShell instructions and output are presented first, and PowerShell is referenced in the 'Related content' section before Azure CLI. The Linux example is present and complete, but Windows tools and patterns are prioritized in ordering and references.
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 improve parity.
- Ensure that introductory sections and prerequisites mention Linux and Windows equally, rather than starting with Windows.
- Where possible, provide cross-platform guidance (e.g., using Azure CLI, which works on both Windows and Linux) before platform-specific tools.
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 references Azure CLI installation links that default to Windows, and mentions Azure CLI 32-bit/64-bit requirements without clarifying Linux/macOS equivalents. The management machine requirements link to the Windows Azure CLI installation page, and no explicit Linux/macOS guidance or examples are provided. However, the overall content is not heavily Windows-centric and does not reference Windows-only tools or patterns.
Recommendations
- Add explicit guidance for Linux and macOS users, including links to Azure CLI installation instructions for those platforms.
- Clarify whether Azure CLI 32-bit/64-bit requirements apply to Linux/macOS, or if these are Windows-specific.
- Provide management machine requirements for Linux/macOS, including supported distributions and any additional dependencies.
- Ensure examples and instructions are platform-neutral or include Linux/macOS variants where appropriate.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first in the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout with equivalent instructions.
Recommendations
- Present Windows and Linux instructions side-by-side or in parallel tabs to avoid implicit prioritization.
- Consider alternating the order in which Windows and Linux instructions are presented, or explicitly state that both platforms are equally supported.
- Add a brief note at the start of relevant sections clarifying that both Windows and Linux workstations are fully supported.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell examples, which is a minor bias in favor of Linux/macOS users rather than Windows. No evidence of Windows-only tools, Windows-specific patterns, or missing Linux examples is found.
Recommendations
- No changes needed for Linux parity. If desired, alternate the order of Bash and PowerShell tabs in different sections to balance visibility.
- Continue to provide both Bash and PowerShell examples for all commands.
- Ensure that any future additions maintain cross-platform parity.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all import scenarios, but consistently includes PowerShell examples alongside CLI, and references PowerShell cmdlets and patterns. Azure PowerShell is primarily used on Windows, and its inclusion may signal a Windows bias. Additionally, PowerShell examples are sometimes presented immediately after CLI examples, which can subtly prioritize Windows tools. However, Azure CLI is cross-platform and all examples are available for it, ensuring Linux/macOS parity.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider explicitly mentioning that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- If possible, show Azure CLI examples first, or highlight them as the default for non-Windows platforms.
- Add a brief section on running Azure CLI on Linux/macOS (e.g., installation link, shell compatibility).
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for querying and updating Azure Container Registry SKUs. Azure PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI, but not before it. There are no Linux/macOS-specific tools or shell examples, but Azure CLI is cross-platform and is shown first. No exclusive Windows tools or patterns are used, and no critical steps are Windows-only.
Recommendations
- Ensure that Azure CLI examples are clearly marked as cross-platform (Linux/macOS/Windows).
- Optionally, include Bash or shell script examples for common tasks, especially for Linux/macOS users.
- Clarify that Azure PowerShell is available cross-platform, but that Azure CLI is often preferred on Linux/macOS.
- If possible, add a note that all features and commands shown are available on Linux/macOS unless otherwise stated.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page references SQL Server Management Studio (SSMS) as the primary GUI tool for connecting, which is Windows-only, and mentions it before the cross-platform sqlcmd tool. However, it does provide a sqlcmd example for both Linux and Windows. No Linux-specific GUI tools (such as Azure Data Studio) are mentioned, and the overall focus is slightly Windows-first. All CLI examples use Azure CLI, which is cross-platform, and the sqlcmd example is generic.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for connecting to SQL Managed Instance.
- Provide explicit examples for connecting from Linux/macOS using sqlcmd, including any OS-specific nuances (e.g., authentication, encoding).
- List sqlcmd before SSMS when describing connection methods, or present them together as equal options.
- Clarify that SSMS is Windows-only and recommend Azure Data Studio for Linux/macOS users.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page lists both Windows and Linux-related endpoints, but there is a noticeable Windows bias: Windows NTP server ('time.windows.com') is mentioned, and several URLs reference 'windows.net' and 'windows.com'. The 'Windows NTP Server' is described first, with no mention of Linux NTP alternatives (such as 'pool.ntp.org'). Additionally, the Azure CLI installer is referenced, but no explicit mention is made of Linux-specific installation instructions or endpoints. However, Linux endpoints (e.g., 'packages.microsoft.com', 'linuxgeneva-microsoft.azurecr.io') are also included, and SSH is referenced as a connectivity requirement, which is cross-platform.
Recommendations
- Add Linux NTP server examples (e.g., 'pool.ntp.org') alongside 'time.windows.com' and clarify when each is used.
- Ensure Azure CLI installation instructions and endpoints are clear for both Windows and Linux management machines.
- Where Windows-specific endpoints are listed (e.g., 'login.windows.net', 'sts.windows.net'), clarify if Linux equivalents are needed or if these are universal.
- Consider listing Linux-related endpoints and tools alongside or before Windows ones to avoid 'windows_first' bias.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical steps, but PowerShell is consistently presented as the only alternative to CLI (no Bash or Linux-native shell examples). In some sections, PowerShell is shown before or alongside CLI, and environment variable examples for PowerShell use Windows-style syntax, while Linux/macOS equivalents are only shown for CLI. No Linux-specific tools or workflows are mentioned, and the focus is on Azure CLI and PowerShell, which are both cross-platform but may feel Windows-centric due to the prominence of PowerShell.
Recommendations
- Explicitly mention that both Azure CLI and Azure PowerShell are cross-platform and supported on Linux/macOS, to avoid the impression that PowerShell is Windows-only.
- Where environment variables are set, provide both Linux/macOS (export) and Windows (set/PowerShell) syntax in both CLI and PowerShell tabs.
- Consider adding Bash script examples or referencing Linux-native shells where appropriate, especially for common administrative tasks.
- Clarify that all steps can be performed from Linux/macOS as well as Windows, and link to installation guides for Azure CLI and PowerShell on Linux/macOS.
- If possible, add a short section or callout confirming that no steps require Windows, and that the workflow is fully supported on Linux/macOS.
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 Azure CLI and PowerShell examples for all major operations, with CLI examples shown before PowerShell. The CLI commands are cross-platform, but PowerShell is Windows-centric. In the 'Monitor Azure Arc gateway traffic' section, both Windows and Linux log file locations are documented. There is a minor bias in that PowerShell is included as a first-class method throughout, but Linux users are not disadvantaged as all critical operations are covered with CLI commands. There are no sections that are Windows-only or that lack Linux equivalents.
Recommendations
- Continue to provide Azure CLI examples as the primary cross-platform method.
- Where PowerShell is mentioned, clarify that Azure PowerShell can be used on Linux/macOS if applicable.
- Explicitly state that all CLI commands work on Linux/macOS, and consider adding Bash-specific notes if there are any OS-specific considerations.
- Ensure that any references to file paths or log locations always include both Windows and Linux/macOS equivalents, as is done in the logging section.
- If possible, add a short note at the start of the 'Create an Azure Arc gateway resource' and similar sections stating that all operations can be performed from Linux, macOS, or Windows using the Azure CLI.
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` presents Windows-specific authentication options (interactive browser login, certificate store usage) before Linux equivalents and references Windows tools (such as PowerShell's Get-AzAccessToken) without mentioning Linux alternatives. However, Linux authentication methods (device code, Azure CLI) are well-documented and examples are generally cross-platform. The bias is mostly in ordering and tool references, not in missing Linux functionality.
Recommendations
- Reorder authentication options so that cross-platform or Linux-default methods (device code, Azure CLI) are presented first or equally alongside Windows options.
- When referencing Windows-specific tools (e.g., PowerShell's Get-AzAccessToken), also mention Linux/macOS equivalents (such as using Azure CLI to obtain tokens).
- Clarify which authentication methods are available on Linux/macOS and provide explicit Linux/macOS examples where appropriate.
- Add a note that all examples are valid for both Windows and Linux unless otherwise specified.
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 Windows-related tools and examples (such as Windows Admin Center and download.microsoft.com) are often mentioned first or more prominently. Windows-specific resources and tools are referenced before Linux equivalents in tables and lists. However, Linux is also covered, and critical tasks can be completed on both platforms.
Recommendations
- Present Linux and Windows examples/resources side-by-side or alternate their order to avoid Windows-first bias.
- Where Windows tools (e.g., Windows Admin Center) are mentioned, clarify Linux alternatives or state if no equivalent exists.
- Ensure download and installation instructions for both Windows and Linux are equally detailed and visible.
- Add explicit Linux troubleshooting links or references where Windows troubleshooting is provided.
- Review tables to ensure Linux resources are not always listed after Windows resources.
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 provides troubleshooting guidance for both Windows and Linux, but Windows examples and tools (such as PowerShell syntax and Windows environment variables) are presented first and in greater detail. Windows-specific paths and log locations are mentioned before Linux equivalents, and PowerShell-style command examples are given for Windows, while Linux examples use bash. Some error codes reference Windows tools (e.g., PowerShell version requirements, %TEMP% log paths) before Linux equivalents.
Recommendations
- Alternate Windows and Linux examples so Linux is not always second.
- Provide equal detail for Linux command examples, including at-scale installation and troubleshooting.
- Mention Linux log paths and troubleshooting steps before or alongside Windows paths.
- Where possible, use cross-platform command syntax or clarify differences explicitly.
- Add notes for Linux users about common troubleshooting tools (e.g., journalctl, systemctl) and permissions.
- Ensure error code tables reference Linux equivalents (e.g., /tmp instead of %TEMP%) where applicable.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there are subtle signs of Windows bias: Windows/PowerShell tools and features are sometimes mentioned before Linux equivalents, and some linked resources default to Windows tabs or examples. PowerShell and Windows-specific automation are highlighted, while Linux alternatives are less emphasized or mentioned secondarily. No critical Linux omissions are present, but the documentation could better balance its cross-platform messaging.
Recommendations
- Where automation tools are mentioned (e.g., PowerShell, runbooks), explicitly mention Bash or Linux shell scripting alongside PowerShell, and provide equivalent Linux examples or links.
- When referencing documentation with OS-specific tabs (e.g., 'tabs=windows'), ensure Linux tabs are equally referenced or linked.
- In lists of supported tools or interfaces (e.g., Azure CLI, PowerShell), alternate the order or clarify that both Windows and Linux are supported equally.
- Highlight Linux support in sections discussing VM extensions, monitoring, and update management, and provide direct links to Linux-specific guidance where available.
- Where possible, add Linux-focused examples or callouts to reinforce 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 with download links, while Linux requirements are listed after and with less detail. Windows-specific tools are mentioned (PowerShell, .NET Framework), but Linux equivalents (such as bash or shell scripting) are not referenced. No Linux command examples or links are given, and Windows download links are more prominent.
Recommendations
- Present Windows and Linux requirements in parallel or in a table, rather than listing Windows first.
- Provide download links or installation instructions for Linux prerequisites (e.g., wget, systemd).
- Include Linux command-line examples or references where Windows PowerShell is mentioned.
- Clarify that both Windows and Linux are equally supported for guest management, and provide parity in documentation detail.
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 presents Bash examples before PowerShell. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. The only minor bias is the ordering of examples, with Bash (Linux/macOS) shown first.
Recommendations
- Continue providing both Bash and PowerShell examples for all commands.
- Consider clarifying that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- If possible, add a short introductory note explaining cross-platform support and which shell to use on each OS.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, and sometimes minor inconsistencies in variable syntax or explanation favor Windows/PowerShell users. There are no Windows-specific tools or patterns mentioned, and all instructions are based on the Azure CLI, which is cross-platform. No Linux examples are missing, and no Windows-only tools are referenced.
Recommendations
- Ensure that Bash and PowerShell examples are equally detailed and consistently formatted.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a brief note clarifying that Azure CLI commands work on all platforms, and Bash examples are suitable for Linux/macOS users.
- Where variable assignment or command syntax differs, provide clarifying comments for both environments.
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 for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users rather than Windows. No Windows-specific tools, patterns, or terminology are used exclusively or prioritized. There are no missing Linux/macOS examples, and all instructions are cross-platform via the Azure CLI.
Recommendations
- Maintain the current structure, as both Bash and PowerShell examples are provided.
- Consider alternating the order of Bash and PowerShell examples in future updates to avoid perceived bias.
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, or Windows with the appropriate shell.
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 lists new features for Azure Arc-enabled VMware vSphere, with some Windows-specific features mentioned (e.g., Windows VM customization, Windows Server Management, Extended Security Updates for Windows Server and SQL Server). However, Linux-related enhancements (such as Arc agent installation on Linux via SSH) are also included. In sections referencing tooling, Azure PowerShell is listed after Azure CLI and REST APIs, and Ansible playbook is mentioned alongside Windows-centric tools (System Center, Group Policy). There is a mild tendency to mention Windows features and tools, but Linux parity is generally maintained.
Recommendations
- Ensure Linux-related features and examples are given equal prominence and detail as Windows features.
- Where Windows tools (e.g., Group Policy, System Center) are mentioned, also highlight Linux equivalents (e.g., Ansible, shell scripts) and provide links or examples.
- In sections listing management tools (CLI, PowerShell, REST), clarify cross-platform compatibility and provide Linux/macOS usage notes where relevant.
- For guest OS customization, explicitly mention if Linux VM customization is supported or planned, to avoid ambiguity.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, and in some cases, minor differences in command syntax are explained for Windows (e.g., carriage return handling). There are no Windows-only tools or patterns, and Linux/macOS users are not missing any critical information. The only minor bias is that PowerShell examples are always present and shown after Bash, which could be perceived as 'windows_first' in terms of parity, but does not impact usability.
Recommendations
- Continue to provide Bash and PowerShell examples side-by-side for all steps.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- If possible, add a brief note at the top clarifying that both environments are fully supported.
- Ensure that any platform-specific nuances (such as file encoding or carriage return handling) are clearly explained for both environments, as is already done.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab appears first, and the PowerShell tab is included throughout. There are no Windows-specific tools or patterns (e.g., cmd.exe, Windows file paths), and all commands use the cross-platform Azure CLI. However, the inclusion of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is more commonly used on Windows, though it is available cross-platform. No Linux-specific tools or patterns are missing, and Linux/macOS users can follow the Bash examples without issue.
Recommendations
- Maintain Bash as the first/default example tab, as it is the most universally compatible.
- Clarify in the introduction that all commands use Azure CLI, which is cross-platform.
- Optionally, add a note that PowerShell examples are also compatible with PowerShell Core on Linux/macOS.
- Ensure that any future examples or scripts do not assume a Windows environment (e.g., avoid Windows file paths or cmd.exe).
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI examples primarily in Bash, but the May 2025 release section includes PowerShell syntax for CLI commands, which may suggest a Windows-first bias. There are no explicit Linux/macOS examples or mentions of Linux-specific tools or patterns. However, the Azure CLI is cross-platform, and most examples are generic. The bias is minor and limited to occasional use of PowerShell syntax.
Recommendations
- Provide CLI examples in both Bash and PowerShell syntax, or clarify that Azure CLI commands work identically across platforms.
- Add explicit Linux/macOS example blocks where PowerShell syntax is shown.
- Mention cross-platform compatibility of Azure CLI in the documentation introduction.
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for Azure dashboards using three methods: Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI (cross-platform) is presented before PowerShell, the PowerShell section is included and uses Windows-centric terminology. The PowerShell examples are not flagged as biased since PowerShell Core is available cross-platform, but the documentation refers to 'Azure PowerShell' and the Az.Portal module, which are most commonly used on Windows. The CLI examples are shown first, but there is no explicit mention of Linux/macOS compatibility or shell-specific considerations. No Linux-specific tools or examples are missing, but the ordering and terminology may subtly favor Windows users.
Recommendations
- Clarify that Azure CLI and PowerShell Core are available on Linux and macOS, and provide links or notes about installation on those platforms.
- Explicitly state that all CLI and PowerShell commands work cross-platform unless otherwise noted.
- Consider including a brief example of running Azure CLI commands in Bash or Zsh to reinforce Linux/macOS parity.
- Avoid using Windows-centric terminology (e.g., 'Azure PowerShell') without clarifying cross-platform support.
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 to subscription and tenant IDs, but PowerShell is consistently mentioned before CLI, and the PowerShell module is referenced with a direct cmdlet example. This ordering and emphasis may subtly prioritize Windows/PowerShell users, though CLI is cross-platform and equally capable. No Windows-only tools or patterns are present, and Linux/macOS users can fully complete all tasks.
Recommendations
- Alternate the order in which Azure CLI and PowerShell are mentioned, or present CLI first to reflect its cross-platform nature.
- Provide explicit example commands for both Azure CLI and PowerShell in the main content, not just as links.
- Clarify that both CLI and PowerShell are available on all major platforms, not just Windows.
- Where possible, include screenshots or instructions that are platform-neutral (which is already mostly the case here).
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider alternating the order of Bash and PowerShell tabs in future documentation, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that all CLI commands are cross-platform and can be run on any OS with Azure CLI and Helm installed.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell is consistently presented after Bash. There are no Windows-only tools or patterns used, and all commands are cross-platform (using the Azure CLI and Helm). However, the presence of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is not the default shell on Linux/macOS, but this is mitigated by Bash examples being present and shown first.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for Linux/macOS users.
- Consider clarifying that PowerShell examples are for users who prefer PowerShell, which is available cross-platform, but Bash is recommended for Linux/macOS.
- Explicitly state that all commands are intended to work on both Linux and Windows, and that Azure CLI and Helm are cross-platform tools.
- Optionally, add a note at the top indicating that Bash is the recommended shell for Linux/macOS users, and PowerShell is available for those who prefer it.
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
powershell_heavy
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is not strictly Windows-only, PowerShell is historically associated with Windows, and its mention before Bash or Linux shell scripting may subtly prioritize Windows users. No explicit Linux/macOS examples or tools are referenced, and no Bash or shell script generation is highlighted.
Recommendations
- Explicitly mention Bash or shell script generation as a Copilot capability, alongside PowerShell and CLI.
- Provide examples or clarify that CLI scripts can be used on Linux/macOS, and PowerShell is cross-platform.
- Consider listing scripting options in a neutral order (e.g., 'Generating CLI, Bash, and PowerShell scripts').
- Add a note about Azure CLI being available on all platforms, and PowerShell Core being cross-platform.
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. The CLI example (which is cross-platform and Linux-friendly) is shown first, followed by PowerShell. There are no Windows-specific tools or patterns mentioned exclusively, and Linux/macOS users are not excluded from any critical workflow. However, PowerShell is referenced as an alternative tool, which may be less relevant for Linux/macOS users.
Recommendations
- Maintain Azure CLI as the primary example, as it is cross-platform.
- Consider clarifying that Azure PowerShell is primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Add a brief note indicating that Azure CLI and Cloud Shell are fully supported on Linux/macOS, and PowerShell is optional.
- If possible, provide bash shell scripting examples for automating imports, to further enhance Linux parity.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is mentioned alongside CLI in the introductory text and is given its own example tab. There is a minor bias in mentioning PowerShell and Windows-centric tools (like Visual Studio Code) before Linux equivalents, but Azure CLI is cross-platform and examples are present. No critical steps are Windows-only.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Add a Bash example tab or clarify that the CLI example is suitable for Bash shells on Linux/macOS.
- Mention alternative editors (such as Vim, nano, or VS Code on Linux/macOS) when suggesting how to create the Bicep file.
- When referencing the integrated terminal, note that Linux/macOS users can use their preferred terminal applications.
- Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, but PowerShell examples are given equal prominence to CLI examples, and PowerShell is mentioned as a recommended method for command-line authentication. There are minor signs of Windows bias, such as mentioning PowerShell alongside CLI throughout, and referencing Windows in the Docker installation prerequisites before Linux/macOS. However, all core Docker commands are cross-platform and shown generically, and Azure CLI is available on all platforms.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- List Linux/macOS before Windows in Docker installation prerequisites to avoid subtle Windows-first ordering.
- Add explicit notes or tabs for Bash/Linux shell usage where Azure CLI is shown, to reinforce cross-platform parity.
- Consider including sample commands for Bash shell (e.g., using environment variables, scripting) for Linux/macOS users.
- Ensure that any references to PowerShell are clearly marked as Windows-specific, and avoid implying it is required for Linux/macOS users.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for signing in to the registry, but does not show any Linux-specific commands or shell examples (e.g., Bash). However, it does mention Docker installation for Mac, Windows, and Linux, and the main workflow uses Docker CLI, which is cross-platform. Azure PowerShell is presented alongside Azure CLI, but PowerShell is more commonly associated with Windows, and no Bash or Linux shell equivalents are given for Azure CLI usage. The order of examples (CLI first, then PowerShell) is neutral, but the lack of explicit Linux shell examples may create minor friction for Linux/macOS users.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI commands, clarifying that Azure CLI works on all platforms.
- Mention that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells, not just Windows Command Prompt or PowerShell.
- Consider including a note or tab for Bash usage, especially for commands like az acr login.
- Ensure parity in instructions for signing in and interacting with the registry, so Linux/macOS users see themselves represented.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation generally uses cross-platform tools (Helm CLI, Azure CLI) and avoids Windows-only commands or tools. However, there are minor signs of Windows bias: the environment variable setup uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'), and the order of Kubernetes cluster creation options lists Azure PowerShell before the Azure portal and Azure CLI. No Linux/macOS-specific examples are provided for environment variable setup, and the 'set' command may confuse Linux/macOS users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples for environment variable setup.
- When listing options for creating AKS clusters, show Azure CLI first, as it is cross-platform, or clarify that Azure PowerShell is Windows-only.
- Review all command snippets for platform-specific syntax and add Linux/macOS equivalents where needed.
- Explicitly state that all Helm and Azure CLI commands are cross-platform, and note any exceptions.